What the Food Traceability Rule asks you to capture — the events, the data, and the lot codes that tie them — and why the compliance date belongs on FDA's page, not in your memory.
Do these first
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
After this lesson you can name what FSMA 204 asks you to record — the events, the data captured at each one, and the lot codes that tie them together — and tell which of those events actually land on your operation, without freezing a compliance date that is going to move.
FSMA 204 is shorthand for Section 204 of the Food Safety Modernization Act, and for the rule that came out of it: FDA's Food Traceability Rule, officially "Requirements for Additional Traceability Records for Certain Foods," codified at 21 CFR Part 1, Subpart S. It does not cover every food. It covers foods on the , established under Section 204 of FSMA.
The last lesson drew the line between the one-up, one-down floor and full lot genealogy. FSMA 204 is that genealogy discipline written into a federal rule, held to a set standard, for listed foods. Where the older Bioterrorism Act rule asked for one link in each direction, the Food Traceability Rule asks you to record specific events and specific data at each — and to hand them over fast.
The rule organizes recordkeeping around two ideas worth knowing by name.
"CTE" and "KDE" are FDA's plain-language names; the regulation itself groups the recordkeeping sections under the heading "Records of Critical Tracking Events." Stripped down, the whole rule is: at these events, capture this data, in a form you can produce quickly.
The rule names seven Critical Tracking Events: harvesting, cooling (before initial packing), initial packing of a raw agricultural commodity, first land-based receiving (for a food that came off a fishing vessel), shipping, receiving, and transformation.
Seven events, but most of them belong to the start of the chain. Harvesting, cooling, and initial packing are the grower's and packer's events — the people handling a raw agricultural commodity before it is packed. First land-based receiving is the seafood event, for product coming off a fishing vessel. If you buy ingredients and make product, you live in three of the seven:
Receiving — 21 CFR 1.1345
When a shipment of a listed food arrives, you record the KDEs for what came in: the traceability lot code it arrived under, the location it shipped from and the location where you received it, the date, the quantity, and the reference document that carries the details.
Transformation — 21 CFR 1.1350
When you turn inputs into a new product — a batch — you record which input lots you used and the new lot you produced, and tie them together. This is the event the whole rule turns on, and the next section takes it apart.
Shipping — 21 CFR 1.1340
When a listed food leaves your dock, you record the KDEs for what went out — the traceability lot code, where it shipped to, the date, the quantity, and the reference document — and send that traceability information on to the recipient.
Which events apply is not a matter of opinion — it follows from what you physically do to the food. A co-packer who only packs, a distributor who only ships and receives, and a manufacturer who transforms each own a different subset. Walk your own process and the rule's events map onto it.
Every one of those events references a code. The is what lets FDA — and you — follow a specific lot out of one firm's records and into the next. It is not a fresh number stamped at every step.
Under 21 CFR 1.1320, a traceability lot code is assigned at only three moments: when a raw agricultural commodity is initially packed, when a food off a fishing vessel is first received on land, and when a food is transformed. Shipping and receiving do not mint a new one — you carry forward the code the food already has. That is deliberate: a lot keeps its identity as it moves down the chain until someone transforms it into something new.
Transformation is where genealogy is written into the regulation. Under 21 CFR 1.1350, when you transform a listed food you must keep records that link the traceability lot codes of the foods you used as inputs to the new traceability lot code you assign the output — along with the quantity you used from each input lot, where you transformed it, the quantity you produced, and the reference document. Read it as a sentence: the codes coming in, tied to the code going out. That link is exactly the seam a lot-number field drops and full genealogy holds — now required by federal rule for listed foods.
A KDE is a data point, not a form. The rule does not hand you a master document to fill in; it names the information each event has to capture and lets that information live on your own business records. That is what a is for. At each event you note the reference document type and its number, and the KDEs sit on the receiving log, the batch record, or the bill of lading you already keep — as long as those records capture the required fields and you can pull them together fast.
That "fast" is the catch. KDEs scattered across a receiving binder, a spreadsheet, and a pile of bills of lading are all present and still fail the test, because no one can assemble them into one linked picture in the time the rule allows. Capturing each KDE as the work happens — the moment you receive, transform, and ship — rather than reconstructing it later is the difference between records that answer and records that merely exist. Bettr Manager, the operations platform this site is part of, records the KDEs against each event as the work is logged, so the lot code carries through; it is one way to keep them linked, not the only one. A disciplined paper system with real cross-references clears the same bar with far more hand-work. For a concrete look at capturing the receiving KDEs so they stay connected downstream, the docs walkthrough on receiving a purchase order shows one way to record them.
Two record rules decide whether all of this holds up when it is tested.
That sortable spreadsheet is the rule's real test. You cannot build one by hand from scattered records in a day; you can produce it in minutes if the KDEs are already tied to their lot codes. It is the recall clock from the first lesson in this course, written into law for listed foods.
There is also one record you can write before any shipment arrives. Under 21 CFR 1.1315 the rule asks for a written traceability plan that describes how you maintain these records, how you identify which of your foods are on the list, how you assign traceability lot codes, and who the point of contact is (growers add a farm map). It is the piece you can start today.
Here is the number people get wrong. The Food Traceability Rule's original compliance date was January 20, 2026. It has been pushed 30 months, to July 20, 2028. Two things moved it: FDA proposed the extension in the Federal Register in August 2025 (document 2025-14967), and Congress, in the Continuing Appropriations Act of 2026, directed FDA not to enforce the rule before that same date. FDA has said it intends to comply. As of July 14, 2026, July 20, 2028 is the date to plan around.
Confirm this date at the source before you act on it
A compliance date is exactly the kind of fact that rots. This one already moved once — by two and a half years, through a mix of rulemaking and an act of Congress. Never carry it from a lesson, a webinar, or memory. Confirm the current date on FDA's own Food Traceability Rule page, and read the requirements themselves in 21 CFR Part 1, Subpart S.
Knowing what to record is the second question. The first is whether the rule reaches your products at all — whether anything you make is even on the Food Traceability List, and why a large retail customer can bind you to these records regardless of what FDA requires. That is where this course goes next.
Do this in your operation