FSMA 204: what changed, and why Walmart and Kroger still matter

The short version: FDA enforcement for the FSMA 204 Food Traceability Rule is no longer the immediate January 2026 cliff. FDA now says it will not enforce the rule before July 20, 2028. But that does not mean food suppliers can wait until 2028 to build traceability records. Walmart, Sam's Club, Kroger, and other large buyers can require traceability data sooner as a condition of doing business.

For a food manufacturer, processor, packer, distributor, restaurant group, or retailer, the practical question is not just "when will FDA enforce?" It is "when will my customer require the data on shipments, labels, advance ship notices, and item setup?"

What FSMA 204 actually changed

FSMA 204 is the FDA's Food Traceability Rule. It adds recordkeeping requirements for foods on the Food Traceability List, often shortened to FTL. The rule is built around Critical Tracking Events and Key Data Elements.

In plain English:

• A Critical Tracking Event is a point in the supply chain where something important happens to the food, such as harvesting, cooling, initial packing, shipping, receiving, or transformation.
• Key Data Elements are the specific fields that must be kept for that event, such as the traceability lot code, location, dates, item identifiers, and reference document details.
• Covered businesses must be able to provide required traceability information to FDA quickly when requested.

FDA's Food Traceability List includes categories such as certain cheeses, shell eggs, nut butters, cucumbers, leafy greens, herbs, melons, peppers, sprouts, tomatoes, tropical tree fruits, fresh-cut fruits and vegetables, finfish, crustaceans, mollusks, and ready-to-eat deli salads.

That list is narrower than "all food," but it touches many supply chains. A distributor may handle both listed and unlisted products, and a processor may transform a listed ingredient into a finished product.

The federal date moved, but the rule did not go away

FDA's FSMA 204 final-rule page now says the original compliance date was January 20, 2026, that FDA proposed a 30-month extension to July 20, 2028, and that Congress directed FDA not to enforce the rule before that same July 20, 2028 date. FDA says it intends to comply with that directive.

The important part for food businesses: the extension is about timing. FDA's page says the traceability requirements themselves are still the final rule's requirements.

So the planning window changed. The work did not disappear.

What FDA's latest readiness work says

FDA's 2026 traceability materials point to the same practical conclusion: covered businesses need a repeatable records workflow, not just a policy memo.

FDA's FSMA traceability FAQ continues to frame the rule around covered foods, Critical Tracking Events, Key Data Elements, traceability lot codes, and records that can be shared when FDA asks for them. FDA's 2026 traceability readiness tabletop update says the exercises tested whether firms could find traceability records for a specific product and date window and provide the information in an electronic sortable spreadsheet within 24 hours.

That is the useful rehearsal. Pick a covered product, a lot, and a shipping window. Then ask whether the team can produce one sortable packet with:

• Traceability lot code and lot-code source
• Product description and item identifiers
• Location identifiers for each receiving, shipping, or transformation event
• Event dates and reference documents
• Quantity and unit of measure
• Trading-partner details tied to the shipment or receipt
• The person or system that can explain the record

If the answer depends on a warehouse export, an EDI report, a QA spreadsheet, and someone remembering which lot was split, the records are not ready yet.

Why Walmart and Sam's Club still pull the timeline forward

Walmart's public food traceability requirements say that, as of August 1, 2025, Walmart and Sam's Club require suppliers of all food and beverage items to comply with ASN and packaging requirements. Walmart also says food suppliers must confirm FSMA 204 eligibility of products in the item catalog if they have not already done so.

For suppliers, that turns FSMA 204 from a future regulatory project into a current shipping and customer-compliance project:

• Confirm whether each item is FSMA 204 eligible or in scope
• Send advance ship notices with traceability fields where required
• Make pallet and case labels match the buyer's receiving process
• Keeping traceability lot codes tied to shipment and product data
• Make sure item-master, warehouse, QA, and EDI records agree

The operational risk is not only an FDA inspection. It is a chargeback, rejected shipment, delayed onboarding, or buyer noncompliance notice.

Kroger's supplier policy is another reason not to wait

Kroger's Food Traceability Policy & Requirements tells suppliers it is implementing FSMA 204 and describes the need to track and share traceability information for products moving through its supply chain.

That buyer-driven approach matters because retailers often standardize around a broader operating requirement than the minimum federal rule.

The hard part is making sure the data survives real operations:

• Receiving a lot into the warehouse
• Splitting, combining, repacking, or transforming product
• Assigning the correct lot to a production run
• Printing a compliant case or pallet label
• Sending the same lot and shipment identifiers in EDI

What to do now

Start with a narrow inventory of products and customers. Do not begin with software selection.

For each item, answer:

• Is the product, or a material ingredient in it, on FDA's Food Traceability List?
• Which customers buy it?
• Do Walmart, Sam's Club, Kroger, or another buyer already require traceability fields for this item?
• Where is the traceability lot code created?
• Where is it stored after receiving, production, shipping, and invoicing?
• Can you connect the lot code to the shipment, customer, date, and reference document?
• Can the team retrieve that packet without asking three systems and two people?

Then run one real product through a mock event. Pick a lot, identify every shipment that used it, pull the receiving and shipping records, and compare the traceability data to the buyer-facing ASN or label.

How this fits RegFile's current workflow

RegFile is live today for OSHA 300A filing, not FSMA 204 filing. But the operating pattern is the same: identify the obligation, gather the records, keep the signer in the loop, and preserve an evidence trail.

If you are a food facility that also has OSHA 300A obligations, start with the filing checker to confirm the March filing question and see the other filings tied to the same site. If the checker shows an OSHA 300A filing path, RegFile keeps review, certification, filing, and evidence together.

For FSMA 204, treat the July 20, 2028 federal enforcement date as breathing room, not idle time. Retailer mandates can make the real deadline much earlier.

Start the filing checker ->

This is informational, not legal advice. Verify FSMA 204 scope, retailer requirements, and state or customer obligations against the applicable source documents.