FSMA 204 Moved to 2028. Walmart's Deadline Already Passed.

Late in 2025, Congress wrote the food industry a thirty-month reprieve into an appropriations act: FDA may not enforce the FSMA 204 traceability rule before July 20, 2028, two and a half years past the original January 2026 compliance date. Walmart's supplier portal answered the reprieve in one sentence: "we expect suppliers to meet the original compliance timelines outlined in our previous communications." Walmart's own date for foods on the traceability list passed in August 2025.

That is the current state of FSMA 204 for a specialty food brand: one federal enforcement date that moved, and a growing set of buyer deadlines that did not. The rule's requirements are unchanged. Only the question of who enforces them first has been settled, and the answer is not FDA.

The rule is a recordkeeping rule, and the records are rows

Section 204 applies to anyone who manufactures, processes, packs, or holds a food on FDA's Food Traceability List, which reaches deeper into specialty food than most operators assume: nut butters, fresh soft and semi-soft cheeses, fresh herbs, fresh peppers and tomatoes, refrigerated ready-to-eat deli salads, fresh-cut fruits and vegetables, and any food in which a listed ingredient keeps the form the list names. For those foods, the rule defines seven critical tracking events, from initial packing through transformation to shipping and receiving, and requires key data elements recorded at each one: the traceability lot code, quantities, locations, dates, and the reference documents that tie them together. The lot code is born at initial packing or transformation and must survive every handoff after that.

Then comes the operational teeth: on request during an outbreak investigation, the records go to FDA as an electronic sortable spreadsheet within 24 hours. Not a binder. Not a portal export from three systems. One sortable file.

The exemptions do not rescue a wholesale brand. The thresholds sit at $25,000 in annual produce sales for farms and $250,000 for retail food establishments and restaurants. A kill step exempts the food it is applied to, but only for a manufacturer that keeps receiving records for the listed ingredients that went into it. Foods off the list are out entirely. A $3M-$50M brand with a listed food, or a listed ingredient, is in scope.

Every requirement in the rule serves one question: where did the lot go, answered by tomorrow.

The binding deadline belongs to the buyer

Retailers read the 2028 date and declined it. Reporting Repositrak's count, Grocery Dive puts more than 70 retailers, wholesalers, and foodservice companies at announced traceability programs, and nearly half of them are asking all food suppliers for traceability data, not just suppliers of listed foods. The programs now define the work:

| Who sets the deadline | What it covers | The date | |---|---|---| | FDA, per Congress | FTL foods only | July 20, 2028 | | Walmart | All food: SSCC-18 pallet labels and GS1-128 case labels tied to the ASN. FTL foods: lot, batch, and date codes on top. Everything else "as soon as possible" | August 1, 2025, passed | | Albertsons, Sam's Club, KeHE, Kroger, Target, and Walmart again | All food suppliers, not just FTL | Programs running now | | Aldi, H-E-B, Meijer, Publix, Wegmans | Supplier deadlines set ahead of the federal date | Earlier than 2028 |

Two rows change the work. Walmart's requirement is lot and batch data transmitted on the ASN and encoded on the case label, not a spreadsheet on file, which makes traceability an EDI and labeling requirement enforced at the DC door. And the all-foods rows mean the FTL, the one scoping mercy the rule offers, does not scope your buyer's program.

The FDA gave the industry thirty months. The buyers already spent them.

For Cinderhaven, the 24-hour ask is 13,000 rows

Cinderhaven Provisions is a fictional sauce and salsa brand, fifty SKUs on a synthetic dataset, and the arithmetic below is the kind any supplier of a listed food can run on itself. Eleven of those SKUs are on the list: the refrigerated fresh-salsa line, where the tomatoes, peppers, and cilantro stay fresh in the jar and so keep the form the list names. The hot-fill sauces and dry rubs are exempt as finished goods, but only because the kill step is documented, and only while Cinderhaven keeps receiving records for the fresh peppers it buys to make them. Eleven listed SKUs at roughly 40 co-packer production runs a year is 440 traceability lot codes. Each lot ships against about 30 orders, so a year of shipping-event records runs 440 × 30 = 13,200 rows, before the receiving records on the inbound side.

Today those rows exist, scattered. The lot is born on a co-packer batch sheet, received into NetSuite under a PO number, shipped by a 3PL whose system logs a different reference, and invoiced with none of the above. The sortable spreadsheet FDA wants in 24 hours is the same three-system join a recall demands in 72, with the scope growing every hour the join takes. Walmart's version of the ask is stricter still: the lot rides the 856 ASN, where a mismatch already draws a chargeback, and the GS1-128 case label, where an unreadable barcode already costs real money.

The spreadsheet is sortable. The three systems it comes from are not.

Twenty-two months is enough to build it once

Of the thirty months Congress granted, twenty-two remain as of this writing. FDA's own economic analysis prices the rule at a primary estimate of $570 million a year across the industry, in 2020 dollars at a 7% discount rate. At mid-size scale the build starts as a field-capture decision rather than a software purchase: give the traceability lot code one home in the product master, whether that is NetSuite, a database, or a disciplined spreadsheet, capture it at co-packer receipt, and carry it outward to the ASN and the case label. Every requirement in the table above is the same key, demanded at a different door.

The brand that builds it once gets the byproduct: recall scope-mapping collapses from a 72-hour reconstruction into a query, and the buyer's traceability form becomes an export instead of a project.

One listed SKU, traced end to end

Pick one listed SKU and send me its last production run's paper: the co-packer batch sheet, your receiving record, and one customer ASN. I will map it against the CTE and KDE tables and write back with the fields you already capture, the ones you do not, and which of your buyers will ask for the missing ones first. Start with one SKU. One SKU tells you the shape of all fifty.