FSMA 204 recordkeeping: CTEs and KDEs mapped to a lot-based system

The seven Critical Tracking Events

21 CFR 1.1310 defines a Critical Tracking Event (CTE) as an event in the supply chain involving harvesting, cooling before initial packing, initial packing of a raw agricultural commodity, first land-based receiving of a food from a fishing vessel, shipping, receiving, or transformation. That's seven distinct events, and each has its own KDE requirements: Harvesting (removing a raw agricultural commodity from where it grew and preparing it for use as food); Cooling (active temperature reduction before initial packing — hydrocooling, icing, forced-air or vacuum cooling); Initial Packing (packing a raw agricultural commodity for the first time); First Land-Based Receiving (taking possession of a food directly from a fishing vessel, seafood-specific); Shipping (arranging transport between locations, including intracompany moves between different street addresses); Receiving (the mirror of shipping); and Transformation (manufacturing, processing, or otherwise changing a food or its packaging, where the output is itself a Food Traceability List food — this includes commingling, repacking and relabeling).

Key Data Elements: what you actually record at each event

The KDEs scale with the CTE. At Harvesting and Cooling, you maintain location and commodity/variety details, quantity and unit of measure, the farm or growing-area location (or aquaculture container name), and the date — and you provide most of that (minus your own reference-document details) to whoever initially packs the product. At Initial Packing, you assign the Traceability Lot Code and record what you received, from where, and what you produced, referencing the harvester's and cooler's information. First Land-Based Receiving (seafood) works similarly, adding fishing-trip harvest dates and locations.

Shipping and Receiving are lighter but still specific: the TLC, quantity and unit of measure, product description, the other party's location, your own location, the date, and where the TLC was originally assigned (or a reference to it) — shipping additionally does not apply to a raw agricultural commodity before its initial packing. Transformation is the most involved: for every traceability lot used as an input, you record its TLC, what it was, and how much of it went in; for the new food produced, you assign a new TLC and record where and when the transformation happened.

The Traceability Lot Code: when it changes, and when it doesn't

A Traceability Lot Code is a descriptor — FDA doesn't mandate a specific format — used to uniquely identify a lot within the records of whoever assigned it (the 'TLC source'). The regulation is precise about when a new one must be assigned: at initial packing, at first land-based receiving for seafood, or at transformation. Outside those three events, you must not establish a new TLC — meaning a lot's code stays fixed through every shipping and receiving event downstream until the next transformation resets it. If your inventory system treats every shipment as a fresh lot, that's a mismatch with how FDA actually defines lot boundaries under this rule. One edge case worth building into a validation rule rather than assuming away: if you receive from an upstream party who was exempt from assigning a TLC (and isn't a retailer or restaurant), you as the receiver must assign one at that point — a fourth trigger the three-event list above doesn't cover on its own.

The Traceability Plan is a separate, always-required document

Distinct from the CTE/KDE records themselves, every covered entity must maintain a Traceability Plan (21 CFR 1.1315) describing: the procedures used to maintain your records, including their format and location; how you identify which of your foods are on the Food Traceability List; how you assign TLCs, if applicable; a named point of contact for questions about the plan; and, if you grow or raise a covered food (other than eggs), a farm map showing each field or growing area with geographic coordinates, or each aquaculture container. The plan has to be updated as your practices change, and you must retain the previous version for two years after each update.

Format: paper is fine, and there is no FDA-mandated data standard

Records may be kept as original paper or electronic records, or true copies — there is no blanket electronic-recordkeeping mandate. The one place electronic format becomes compulsory is if FDA needs records urgently during a foodborne-illness outbreak or recall: then you generally must supply them as an electronic sortable spreadsheet, though small entities (farms under $250,000 average annual sales, or other businesses under $1 million) are exempt from that specific spreadsheet requirement and can supply records electronically or on paper in another form. Records don't need to live in one system, and existing business records already kept in the ordinary course of business are sufficient as long as they're supplemented with the required KDEs and your Traceability Plan describes where to find them.

FDA is explicit that FSMA doesn't give it authority to prescribe specific technologies or data formats for these records. That's left to industry to standardise on its own — GS1 US's traceability standards (GTIN, GLN, SSCC, EPCIS) are the closest thing to an industry-standard answer for structuring TLCs and location descriptions in an interoperable way, though the detailed implementation guidance is behind a paid course, not freely published.

Where FDA itself says lot-level tracking gets hard

FDA's June 2026 discussion paper on this exact problem — explicitly not final guidance, but the most direct primary-source acknowledgment of where the rule is operationally difficult — flags several unresolved friction points worth designing around now: distribution-center lot mixing (mixed-lot pallets and pick-slot mixing may require case-level scanning, and FDA is weighing whether inferred TLCs from warehouse-management logic could substitute for exact capture); 'eaches' — items sold individually after a case is broken, where the TLC is typically printed on the case rather than the item; and multi-location transformation, such as a central kitchen preparing food shipped to several retail locations. None of these have settled answers yet; if your operation touches any of them, build your system to capture more granularity than the bare minimum rather than assuming the eventual final guidance will validate a thinner approach.

Enforcement: no FDA fines, but real consequences

FDA has stated plainly that it does not have authority to impose fines for violations of this recordkeeping rule. What it does have: a recordkeeping violation is a prohibited act under the Food, Drug and Cosmetic Act, enforceable through Untitled or Warning Letters first, and civil injunction or criminal prosecution if that fails — and multiple entities in a supply chain can be held responsible simultaneously for the same records failure. Farms are specifically excepted from this prohibited-act enforcement mechanism, though they still carry the underlying recordkeeping obligations. Separately, and more immediately relevant for exporters selling into the US: a food can be refused admission at the border if it appears the traceability recordkeeping requirements weren't met — that's the practical teeth of the rule for anyone shipping FTL foods into the US market.