FSMA 204 Traceability: An Operator's Guide to KDEs, CTEs, and the 2028 Deadline

If you handle a food on the FDA Food Traceability List (FTL), FSMA 204 requires you to capture Key Data Elements (KDEs) at each Critical Tracking Event (CTE) in your part of the supply chain, assign and carry traceability lot codes, keep a written traceability plan, and be able to hand FDA a sortable electronic record within 24 hours of a request. The compliance deadline is 20 July 2028, extended 30 months from the original date in March 2025. This guide breaks down what that means operationally and where environmental records fit.

This is a plain-language operator's overview, not legal advice. Confirm your obligations against the FDA final rule and your own products.

What is FSMA 204?

FSMA 204 — the FDA Food Traceability Final Rule, from Section 204 of the Food Safety Modernization Act — establishes additional recordkeeping for anyone who manufactures, processes, packs, or holds foods on the Food Traceability List. The goal is faster outbreak traceback: when contaminated food turns up, FDA wants to follow it forward and backward through the chain in hours, not weeks.

Who is actually subject? Check the Food Traceability List

This is where many summaries overreach. FSMA 204 applies to foods on the FTL — not to all produce or all growers. Being in a category that sounds covered is not the same as being subject; the FTL is specific, and there are exemptions (certain small producers, farms selling direct to consumers, and foods that later receive a qualifying kill step, among others).

FTL categories that overlap controlled-environment and cold-chain operations include:

• Fresh leafy greens and fresh-cut produce
• Soft and semi-soft / fresh soft cheeses (note: hard, aged cheeses are not on the FTL)
• Shell eggs, sprouts, herbs (fresh), melons, peppers, tomatoes, cucumbers, tropical tree fruits
• Finfish, crustaceans, and molluscan shellfish
• Ready-to-eat deli salads

If you also hold these foods — a cold-storage or distribution operation — you are a covered party for the receiving, holding, and shipping events even if you never grow or process anything. Always verify your specific product against the current FTL.

KDEs and CTEs: the core of the rule

The rule is built on two ideas:

• A Critical Tracking Event (CTE) is a point where food is handled in a traceability-relevant way: harvesting, cooling (before initial packing), initial packing, first land-based receiving (for seafood off a vessel), shipping, receiving, and transformation (combining or changing the food).
• Key Data Elements (KDEs) are the facts you record at each CTE: the traceability lot code, location identifiers, dates, quantities and units, and references tying the event to the lot.

The through-line is the traceability lot code: it is assigned at certain CTEs (initial packing, transformation) and travels with the food, so each downstream party records KDEs against the same lot. That is what lets FDA stitch the chain together.

What you have to be able to do

1. Maintain KDEs for every CTE you perform, tied to traceability lot codes.
2. Pass KDEs to the next party so the chain stays continuous.
3. Keep a traceability plan describing your procedures, the FTL foods you handle, and how you assign lot codes.
4. Produce records to FDA within 24 hours, in an electronic, sortable spreadsheet format.

That 24-hour, sortable-electronic requirement is the operational sting: paper binders and scattered logs do not meet it. Records have to be structured and retrievable fast.

Where environmental records fit

FSMA 204 traceability is about lot-level chain-of-custody data — lot codes, locations, dates, quantities. It is not primarily an environmental-monitoring rule. But the operations it covers, especially cold storage and holding, almost always run alongside temperature and condition records that auditors and your own food-safety plan (HACCP) demand — and those records have the same problem: they must be timestamped, durable, and retrievable.

This is where automated logging earns its place. LoopString compliance logging keeps automatic, timestamped, audit-ready environmental records — cold-room and holding temperatures, humidity, and alarm events — in a structured, exportable form, so the condition side of your records is continuous and tamper-evident instead of a clipboard someone fills in twice a shift. It complements your traceability system (the lot-code chain) rather than replacing it: think of it as the always-on record that your holding and cold-chain CTEs happened under control.

Before the 2028 deadline

1. Confirm scope. Check each product against the current FTL; do not assume.
2. Map your CTEs. List the harvesting/packing/holding/shipping/receiving/transformation events you actually perform.
3. Fix lot-code assignment and hand-off so KDEs flow to the next party.
4. Get records electronic and sortable, including the environmental/condition logs your cold-chain and HACCP plan already need.
5. Write the traceability plan.

The deadline moved to 20 July 2028, but the operations — lot codes, structured records, continuous condition logging — take time to build into daily practice. Starting from automated, exportable records is a lot easier than retrofitting a clipboard.