· 2 min read · FoodChainAPI editorial
FSMA 204 CTEs vs. KDEs: Turn Events into Useful Records
A Critical Tracking Event (CTE) describes an activity in the food supply chain. A Key Data Element (KDE) is information recorded for that activity. A product category helps you begin the review; your actual operations determine which event records you need.
Start with the activity, then the fields
Map one product through your facility before designing a universal traceability form. A distributor receiving sealed cases and shipping them onward has a different workflow from a processor combining ingredients into a new product. FDA identifies event-specific records for activities including harvesting, cooling, initial packing, first land-based receiving, shipping, receiving, and transformation.
Draw each activity as a separate step. Identify the business location, the system that records it, and the person responsible for fixing missing information. Then compare that step with FDA's event-specific KDE resources. A list of category-level field names is useful orientation, but it is not a complete specification for every business.
- Identify the food and its relevant FTL form.
- Document exemptions separately from category matching.
- List activities you actually perform.
- Map each applicable event to required fields and source records.
An example from a distributor
Consider a shipment of fresh cucumbers received on Monday and split across two customers on Tuesday. Your product catalog identifies the SKU. The receiving record captures the inbound event and its lot information. The two shipping records connect portions of that lot to the recipients. A product master alone cannot answer who received the affected lot.
Avoid a single overwritten 'latest supplier' field. Historical events need their own records so a later supplier change does not rewrite the story of earlier deliveries. Keep quantities and units explicit, and retain the reference documents needed to interpret each event.
Where FoodChainAPI fits
Use FoodChainAPI's lookup to identify possible Food Traceability List categories, then inspect the exclusions and FDA sources. Use the result to route a product into your traceability review workflow. The lookup does not collect your receiving or shipping records and cannot determine an operation's obligations from a food name alone.
Before approving a field map, test a split shipment, a returned case, and a missing supplier lot. Those examples reveal whether your records describe real events or merely store a collection of labels.
Put the product review into practice
Start with a candidate category in the free FTL lookup. Check product form and exemptions against FDA sources, then save the evidence behind your decision.
API referenceUse in Chrome, ChatGPT, or ClaudeProduct review walkthrough
Sources and scope
FDA sources checked October 4, 2026. Workflow suggestions are implementation guidance; category matches do not establish exemption or compliance status. Check the current FDA requirements for your product and activities.