| KEY TAKEAWAYS
• Enforcement of the FDA Food Traceability Rule (FSMA 204) is set for July 20, 2028; Congress has barred FDA from spending funds to enforce it before that date, and the requirements themselves are unchanged. • The rule applies to foods on the Food Traceability List — including finfish, smoked finfish, crustaceans, bivalve molluscan shellfish, fresh and fresh-cut produce, soft cheeses, shell eggs and nut butters — and to whoever manufactures, processes, packs or holds them. • Compliance rests on three things: a traceability plan, key data elements captured at each critical tracking event, and the ability to hand FDA an electronic sortable spreadsheet within 24 hours. • FDA’s own 2026 readiness exercises found that supply-chain coordination, not technology choice, separated the firms that could produce records from those that could not. |
The Deadline Moved. The Requirements Did Not.
FDA published the Food Traceability Rule — the regulation implementing Section 204(d) of the Food Safety Modernization Act — on November 21, 2022, codified at 21 CFR part 1, subpart S. The original compliance date was January 20, 2026. In March 2025 FDA announced its intent to extend that date by 30 months, and in August 2025 published a proposed rule moving it to July 20, 2028. Congress then went further: the FY2026 appropriations act directs that no appropriated funds may be used to administer or enforce the rule before July 20, 2028.[1][2][3]
Two details matter for planning. First, FDA has stated the extension does not amend the requirements and that it does not intend to amend them.[4] Second, the delay exists because supply chains were not coordinated enough to comply, not because the expectation softened. FDA estimated the rule would cover more than 323,000 domestic businesses operating more than 484,100 establishments.[1] For a processor, that means most of your suppliers and customers are working on this at the same time you are.
Who Is Actually Covered
The rule applies to persons who manufacture, process, pack or hold foods on the Food Traceability List (FTL), including foods that contain listed foods as ingredients in the same form.[5] For processors in the sectors Lot Axis serves, the relevant entries include:
- Seafood: finfish (fresh and frozen, including histamine-producing and ciguatoxin species), smoked finfish (refrigerated and frozen), crustaceans such as shrimp, crab and lobster, and bivalve molluscan shellfish — oysters, clams and mussels — unless a shellfish-specific exemption applies.[6]
- Produce: fresh leafy greens and fresh-cut leafy greens, melons, sprouts, cucumbers, tomatoes, peppers, herbs, tropical tree fruits, fresh-cut fruits and fresh-cut vegetables.[5]
- Other: cheeses other than hard cheeses, shell eggs, nut butters and refrigerated ready-to-eat deli salads.[5]
Meat is the part that gets misread. The Food Traceability Rule covers only FDA-regulated foods; food that is within the exclusive jurisdiction of USDA is exempt, which takes beef, pork, lamb and domestic poultry out of scope for FSMA 204 recordkeeping.[7] But three situations pull meat and protein plants back in: FDA regulates meat from non-amenable species such as bison, venison, elk and rabbit;[8] dual-jurisdiction plants that receive FTL ingredients through a shared receiving area still need receiving records for those ingredients; and shippers sending FTL food into a USDA-regulated facility still have shipping obligations. Customer requirements do the rest — many distributors and retailers are asking for lot-level data regardless of whether the rule compels it.
What FSMA 204 Actually Requires
Strip away the acronyms and there are three obligations.
- A traceability plan. A written description of how you keep required records, how you identify FTL foods, how you assign traceability lot codes, and who to contact about it. Farms and aquaculture operations also need a map of fields or containers. Previous versions must be kept for two years after an update.[9]
- Key data elements at each critical tracking event. The critical tracking events (CTEs) are harvesting, cooling, initial packing, first land-based receiving, shipping, receiving and transformation.[10] Each carries its own required key data elements (KDEs). Central to all of it is the traceability lot code (TLC) — the code that uniquely identifies a lot — plus the TLC source, the physical location where that code was assigned.[11]
The assignment rule is narrow and worth memorizing: you assign a TLC when you initially pack a raw agricultural commodity, when you perform first land-based receiving of food from a fishing vessel, or when you transform a food. You must not create a new code for other activities such as shipping.[12] For a processor, transformation is the moment of truth: when lots are cut, cooked, mixed, repacked or combined, a new TLC is assigned, and the records must link the input lot codes to the new one along with the location, date, product description, quantity and reference document.[13][14]
- Records that can leave the building fast. Records must be kept at least two years and be available to FDA within 24 hours of a request. When FDA needs it to prevent or mitigate an outbreak or support a recall, the information must be provided as an electronic sortable spreadsheet; FDA publishes an example template but does not mandate a specific format or technology. Smaller farms, restaurants and firms under defined sales thresholds may provide it another way.[15] Paper records remain legal — but FDA’s 2026 guidance update emphasized digital records precisely because of the 24-hour clock.[4]
The 24-Hour Test
The most useful readiness check is not a gap analysis. It is a drill: pick a finished lot you shipped last month and reconstruct, in one day, every input lot, every location, every date, and every customer that received it — in a sortable spreadsheet.
FDA ran that drill for real. Between March 9 and April 1, 2026, it held tabletop exercises with 15 companies across the supply chain, asking for traceability records in an electronic sortable spreadsheet within 24 hours. Most firms responded in time. The finding worth repeating: participants used everything from invoices and bills of lading to WMS, ERP, RFID and GS1 barcodes, and the technology mattered less than whether supply chain partners had agreed on what data to collect, keep and share.[16] Even smaller firms generally had access to most of the required data.
That reframes the work. Software does not create traceability on its own; agreements, labels and disciplined capture do — and then software makes them fast and repeatable.
Why Preparing Early Pays Outside of Compliance
FDA’s own economic analysis of the rule assumed better records would cut the time it takes to trace a product to its origin by roughly 80 percent, and it counted non-health benefits alongside public health ones: avoiding overly broad recalls, improving supply chain management and inventory control, and starting and finishing recalls sooner.[17]
Those benefits are not reserved for audit day. The same lot-linked data that answers an FDA request also tells a plant manager which lots are oldest, which are on hold, which are committed, and which customers received a specific production run. GS1 US maintains implementation guidance showing how standard identifiers — GTIN, batch/lot, SSCC and GLN — can carry that information between trading partners on case and pallet labels and in shipping messages, so the same scan serves both operations and compliance.[18]
A Practical Sequence for the Next 24 Months
- Confirm scope. List every product you make and mark which are on the FTL, which are exempt, and why. Document the reasoning — that record is the start of your traceability plan.
- Write the traceability plan. It is the cheapest deliverable in the rule and it forces the other decisions.
- Fix lot identity at the source. Decide how TLCs are assigned at initial pack, first land-based receiving and transformation, and get them onto labels and into scans, not clipboards.
- Instrument transformation. Most processor risk hides in reboxing, blending, cooking and repacking. If input-to-output lot links are manual, they will not survive a 24-hour request.
- Align with trading partners now. Agree what data arrives with inbound loads and what you will send outbound. This was the differentiator in FDA’s exercises.
- Run the drill annually. Reconstruct one shipped lot end to end, on the clock, and log what was missing.
How Lot Axis Fits
Lot Axis was built for lot-controlled food processing: barcode-driven receiving, production and shipping that keep one current record of every lot from receiving through transformation to the customer. Because the traceability lot code follows the product through every scan, the data FSMA 204 asks for is a byproduct of running the plant rather than a separate compliance project — and the same records give supervisors daily visibility into inventory, aging and production. That is what we mean by Lot Intelligence™: traceability data used every day, not only during an audit or a recall.
July 20, 2028 is far enough away to do this properly and close enough that starting late will hurt. The processors who will be ready are the ones treating traceability as an operating discipline now.
Want to see what a 24-hour traceability request looks like when the data is already there? Schedule a Lot Axis demonstration and we will walk one of your product flows — receiving, transformation, shipping — end to end.
This article is general information about a federal regulation, not legal advice. Confirm your obligations against the current text of 21 CFR part 1, subpart S and FDA’s Food Traceability List.
Sources
- FDA — FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods https://www.fda.gov/food/food-safety-modernization-act-fsma/fsma-final-rule-requirements-additional-traceability-records-certain-foods
- FDA — Food Traceability List https://www.fda.gov/food/food-safety-modernization-act-fsma/food-traceability-list
- 21 CFR 1.1315 — Traceability plan requirements https://www.law.cornell.edu/cfr/text/21/1.1315
- 21 CFR 1.1320 — When traceability lot codes must be assigned https://www.law.cornell.edu/cfr/text/21/1.1320
- 21 CFR 1.1455 — How records must be maintained and made available (24-hour rule) https://www.law.cornell.edu/cfr/text/21/1.1455
- U.S. Government Accountability Office — GAO-24-106563, Food Safety: FDA Should Finalize Plans to Implement Its Rule to Help Trace Source of Outbreaks https://www.gao.gov/assets/gao-24-106563.pdf
- GS1 US — Application of GS1 System of Standards to Support FSMA 204 (Release 3.0) https://documents.gs1us.org/adobe/assets/deliver/urn:aaid:aem:8037d451-b557-4b0f-9fa8-fc94f94e4547/GS1-US-Application-of-GS1-System-of-Standards-to-Support-FSMA-204-Guideline.pdf
- Food Safety Magazine — Shutdown Deal Restricts Funds for FSMA 204, Produce Safety Rule Enforcement (Nov. 13, 2025) https://www.food-safety.com/articles/10872-shutdown-deal-restricts-funds-for-fsma-204-produce-safety-rule-enforcement