Key Data Elements (KDEs) are the specific pieces of information FSMA 204 requires you to record about a food. Critical Tracking Events (CTEs) are the supply-chain moments where you must record them, harvesting, cooling, initial packing, first land-based receiving, shipping, receiving, and transformation. Which KDEs apply depends on which CTE you perform.
If you have read our broader FSMA 204 overview this post zooms in on the two mechanics that actually generate the recordkeeping work: the events that trigger a record, and the data fields each event demands. Get these two concepts right and the rest of the rule is bookkeeping. Get them wrong and you will collect the wrong data at the wrong moments and fail the 24-hour test. This is the KDE-and-CTE deep dive.
What are Key Data Elements and Critical Tracking Events?
A Critical Tracking Event is a point in a food's journey where the rule says a record must be created; a Key Data Element is a specific fact that record must contain. The two are inseparable: CTEs are the when KDEs are the what. FDA built the framework this way so that everyone in a supply chain records the same standardized facts at the same standardized moments, which is what lets the agency stitch one company's records to the next during a traceback.
The set of KDEs is not uniform across events. A shipping CTE requires different data than a transformation CTE, because the questions FDA needs answered differ. What ties them together is the traceability lot code, a single identifier that travels with the food so that a receiving record at one facility can be matched to the shipping record at the facility before it. Understand the lot code and the CTE list, and the KDE requirements fall into place.
What is a traceability lot code, and where does it come from?
A traceability lot code (TLC) is the identifier that links FSMA 204 records across the whole supply chain. It is assigned at three defined moments: when a food is initially packed (for produce), when it is first received by a land-based receiver (for seafood off a vessel), and when it is transformed into a new product. It is not created at every step, and it is never reassigned during simple shipping and receiving, that is the point. The code stays constant as the food moves so that everyone handling that lot references the same identifier.
The one place a new TLC is born mid-chain is transformation. When a manufacturer cuts, cooks, or combines an FTL food into a new product, they assign a fresh TLC to the output and record the link between the input lots and the new lot. That linkage, inputs in, new code out, is where traceability chains most often break in the real world, because it forces a plant to connect inbound receiving records to production batch records to outbound shipping records. Nailing the lot code discipline is the single highest-leverage thing a manufacturer can do to get ready.
Which foods trigger KDE and CTE recordkeeping?
Only foods on FDA's Food Traceability List (FTL). If a food is not on the FTL and does not contain an FTL food as an ingredient, the KDE and CTE requirements do not apply to it. The list was built from a risk-ranking model the statute required, and it covers categories such as soft and semi-soft cheeses, shell eggs, nut butters, a set of fresh produce items (cucumbers, herbs, leafy greens, melons, peppers, sprouts, tomatoes, and tropical tree fruits), fresh-cut fruits and vegetables, finfish and crustaceans, molluscan shellfish, and refrigerated ready-to-eat deli salads.
The authoritative source is FDA's Food Traceability List page and you should check it rather than a summary, because the category definitions decide edge cases (what counts as a hard cheese, what counts as fresh-cut). Note too that the rule follows the food: a manufacturer using an FTL ingredient in a larger product is generally covered for that ingredient unless an exemption applies. Map your products and ingredients against the FTL first; that scoping decides everything downstream.
What are the Critical Tracking Events?
The rule defines a set of CTEs that run in supply-chain order. Not every party performs all of them; a manufacturer typically performs receiving, transformation, and shipping. The list below walks them in sequence.
- Harvesting. A farm harvests a raw FTL crop. The harvester records what and how much was harvested, the field and farm location, and the date, and passes it forward.
- Cooling (pre-initial packing). If the crop is cooled before it is packed, the location, date, and the lot are recorded and passed to the packer.
- Initial packing. The first packing of a raw agricultural commodity. This is where the traceability lot code is assigned, along with the product description, quantity, packing date and location, and the harvest and cooling information received.
- First land-based receiving. For seafood obtained from a fishing vessel, the first land-based receiver assigns the TLC and records the harvest date range and locations, the seafood analog of initial packing.
- Shipping. Any time an FTL food is shipped to another location, the shipper records the TLC, product, quantity, ship date, and origin and destination, and sends the required KDEs forward to the receiver.
- Receiving. The receiver records the TLC, product, quantity, receipt date, who shipped it, and where the TLC was assigned. Receiving records are the seams FDA uses to connect one company's data to the next.
- Transformation. A manufacturer changes the food, cutting, cooking, combining, and assigns a new TLC to the output, recording the input lots and quantities in and the new product and lot out.
What KDEs must you capture at each event?
The KDE set is tailored to each CTE, but a few fields recur almost everywhere: the traceability lot code, a product description, the quantity and unit of measure, the relevant date, the location descriptions involved, and a reference to the record documenting the event. The table maps the events a manufacturer most often performs to the KDEs at their core. Treat it as an orientation, not a substitute for the rule text at 21 CFR Part 1, Subpart S which specifies each field precisely.
| Critical Tracking Event | Core Key Data Elements |
|---|---|
| Receiving | Traceability lot code; product description; quantity and unit of measure; location of the immediate previous source; location where received; date of receipt; reference document; location where the TLC was assigned |
| Transformation | New traceability lot code for the output; the input TLCs, product descriptions, and quantities used; new product description; location and date of transformation; reference document |
| Shipping | Traceability lot code; product description; quantity and unit of measure; location shipped from; location of the immediate subsequent recipient; ship date; reference document; location where the TLC was assigned |
| Initial packing | Traceability lot code assigned; product description; quantity; packing location and date; harvest and cooling KDEs received; the TLC source reference |
By the numbers
- KDE and CTE requirements apply to foods on the FDA Food Traceability List and the rule is codified at 21 CFR Part 1, Subpart S.
- Records must be provided to FDA within 24 hours of a request, and, in an outbreak or recall traceback, as an electronic sortable spreadsheet, per FDA's Food Traceability Rule.
- The compliance date is July 20, 2028: FDA moved to extend the original January 20, 2026 date by 30 months, and Congress directed FDA not to enforce the rule before then, per the Federal Register extension notice.
Where do KDEs get captured on the plant floor?
KDEs are captured at the exact points where the work happens, the receiving dock, the production line, and the shipping bay, which is precisely why the rule is hard for paper-based plants. A receiving KDE is created when the dock crew logs an inbound lot. A transformation KDE is created when a batch is built, tying input lots to the output lot. A shipping KDE is created when a case leaves. Each of those is a moment on the floor, under time pressure, done by an operator, not a moment at a desk.
The honest test is the 24-hour one: if FDA asked today for every KDE on one lot of one FTL product, could you assemble it in a day? For most binder-and-spreadsheet operations the answer is no, because the transformation link, which input lots went into which batch, lives in someone's memory or in disconnected logs. Capturing receiving, batch, and shipping records digitally at the station, tied to your existing lot and batch numbering, is what makes a 24-hour sortable production possible instead of aspirational. Transformation KDEs are really just disciplined production records, the same records your HACCP plan, your GMP program and your food safety management system already lean on.
When do the requirements take effect?
July 20, 2028. The original compliance date was January 20, 2026, but in 2025 FDA moved to extend it by 30 months, and Congress locked the new date in by directing FDA not to enforce the rule before then. The requirements themselves did not change, only the date. Read conflicting dates online with that history in mind, and confirm the current status on FDA's rule page before you set internal deadlines.
The extension is time to build lot-level data plumbing, not permission to wait. The hard part, coordinating lot codes and KDEs with every supplier and customer you touch, does not compress well, and it is exactly what the extra 30 months exist to let the industry fix. Plants that digitize capture now, the way CLS did with Harmony for production logging, already have the raw material of KDE compliance flowing as structured data tied to their ERP. No rip-and-replace; the same records become queryable in minutes instead of days.