Walmart supplier traceability requirements: the KDE nobody can produce, and the freight rejection waiting for it

Walmart's food traceability requirements ask suppliers for three Key Data Elements. Two of them you almost certainly have. The third is the one FDA's own research says most firms cannot produce.

Here they are, from Walmart's supplier enablement documentation:

1. Lot or batch codes
2. Date code or codes
3. The source or originating location of the lot/batch code generation

Number three is not "where you shipped from." It is where the lot code was created. In FSMA 204 vocabulary that is the Traceability Lot Code source, and it is the single data point FDA found firms struggled with most. In FDA's spring 2026 traceability readiness tabletop exercises, only 40 percent of participating companies captured a properly assigned TLC across every Critical Tracking Event they performed.

So the largest grocery retailer in the United States is asking for precisely the field the industry is worst at producing, and rejecting freight when it does not arrive.

The deadline was a year ago

August 1, 2025 for Food Traceability List products. For everything else, Walmart's guidance is to begin compliance immediately rather than wait for a second date.

That is now twelve months in the past. And as with Kroger's June 2025 deadline and Wegmans' August 2025 deadline, it did not move when FDA's compliance date slid to July 20, 2028. Retailer programs were never pegged to FDA's calendar. They were pegged to the retailer's own risk.

If you have been reading the 2028 extension as breathing room, this is the third major grocer whose date has already passed.

What makes Walmart different: the consequences are physical

Every retailer program in this category asks for broadly similar things. What separates Walmart is that it publishes what happens when you fail:

• Freight rejection
• Monetary fines
• Relationship review for repeat violations
• Plus the possibility of FDA enforcement action

That list changes the nature of the risk. FSMA 204 is enforced through inspections and records requests, on a timeline that ends in 2028. Walmart's version is enforced at the receiving dock, on the next truck, by a person with a scanner.

A rejected truck is not a compliance finding you remediate over a quarter. It is product on a dock, freight you paid for, a purchase order unfilled, and a scorecard entry. For a small producer running thin margins, one rejection can cost more than the entire year of getting the records right.

The scope: all food, explicitly

Walmart's requirements apply to all food suppliers and all food products. The documentation explicitly names baby food, pet food, beverages, meat, and poultry, categories that sit well outside FDA's Food Traceability List.

Enforcement monitoring begins with FTL products, which is the practical concession. But the stated scope is all food, and the guidance for non-FTL items is to start now.

This is the second major retailer we have covered whose program is broader than the federal rule. Kroger says the same thing in its own words. The pattern is worth naming directly: retailers do not want to run two parallel receiving processes, one for FTL items and one for everything else. It is operationally cheaper for them to require traceability on everything. Expect that logic to keep spreading, and stop treating "not on the FTL" as a durable position.

The three asks, decoded

1. An ASN with KDEs on every food shipment

An Advance Shipment Notification containing the Key Data Elements, for all shipments or deliveries of food to Walmart. The updated EDI 856 standards incorporating FSMA 204 KDEs are published through Retail Link, which is where you should get the authoritative spec rather than from a summary like this one.

As with Kroger and Wegmans, the traceability data rides inside the shipping message. There is no separate traceability document. If you do not have EDI capability today, that is the long-lead item, and it is a procurement decision rather than a form.

2. SSCC-18 barcodes on pallets, linked to the ASN

The Serial Shipping Container Code is an 18-digit GS1 identifier for a logistics unit. Walmart wants it on the pallet, and it has to link to the corresponding ASN.

The word "linked" is carrying the weight. The scanner at the dock reads the pallet, looks up the ASN, and expects them to describe the same thing. When they disagree, that is the rejection.

3. GS1-128 barcodes on cases

Standard case-level barcode encoding, so case contents can be read and reconciled the same way.

The GS1 point, again

We have written that FSMA 204 does not require GS1, and that remains true. FDA mandates no particular standard.

But SSCC-18 and GS1-128 are both GS1 constructs, and an SSCC requires a GS1 Company Prefix. So supplying Walmart means GS1 membership in practice.

That is now the third retailer where this is true. Costco, Kroger, and Walmart all effectively require GS1 while the federal rule does not. If you sell into any national grocer, the honest advice is to stop treating a GS1 prefix as an optional expense and start treating it as the cost of that shelf.

Where small producers actually fail

The third KDE. Where the lot code was generated is a field most small operations have never recorded, because it was never needed. If you make product in one facility it feels self-evident, so nobody writes it down. But the ASN has a field for it, and "obvious" does not populate a field. Worse, if you use a co-packer, the answer is genuinely not your address, and getting it wrong is a data-integrity problem rather than a formatting one.

The label and the message disagree. This is the failure that produces rejections. The ASN says one lot, the pallet label says another, usually because a human retyped a lot code somewhere between production and shipping. Our 24-hour traceback drill breaks at the same seam: the lot code exists on the label but never made it into the record, so every downstream use of it is a re-entry.

No EDI at all. Many small producers ship to independents on purchase orders with no EDI anywhere. Walmart requires an ASN per shipment. Solving that takes weeks, not days.

Assuming pet food and beverages are out of scope. They are explicitly named as in scope.

A prep plan

1. Pull the actual EDI 856 spec from Retail Link. Build to the document, not to this post.
2. Answer the third KDE first. Write down, right now, the location where your lot codes are generated. If you use a co-packer, get their answer in writing. This is free and it is the field most likely to be wrong.
3. Get a GS1 Company Prefix if you do not have one, then assign GTINs and set up SSCC serialization.
4. Fix the lot code at the source. Capture the TLC on the production record at the moment of transformation. The worked examples show three product types end to end, and the KDE checklist shows what belongs on each event record.
5. Reconcile one pallet by hand before you transmit anything. Take a real shipment, write out the ASN fields from your records, print the label, and check that they agree. Every mismatch you find on paper is a truck you did not lose.

One live example of why this matters

In July 2026, recalled Marketside-brand iceberg lettuce was sold at Walmart stores across fifteen states as part of the Cyclospora outbreak traceback that reached 1,947 cases. FDA identified the source without a single confirmed positive product sample, working backward through distribution records until the trail converged.

That is what the ASN data is for. Not paperwork, not an audit artifact, but the thing that lets an investigator draw a boundary around a lot and clear everyone outside it. When a retailer says it wants the lot code and the location where it was generated, it is buying the ability to answer that question in hours rather than weeks.

Where FSMA204Hub fits

Everything above reduces to one capability: for any lot you ship, produce the lot code, the date, where the code was generated, what went into the lot, and where it went, from one place and in whatever format the buyer wants.

That is the bet behind FSMA204Hub. One row per finished lot, inputs and customers hanging off the same code, and the TLC source recorded once instead of assumed. The compliance score flags the lots that would fail a buyer's request before a receiving dock does.

If a Walmart or Kroger packet is on your desk, start a free 14-day trial. No credit card. We answer questions within a working day.

---

Onboarding with Walmart and unsure what to put in the lot-code-source field? Email [email protected] and tell me whether you produce in house or use a co-packer. That single detail decides the answer.

Further reading

• Walmart: Food traceability supplier requirements
• FDA: Report on Traceability Readiness Tabletop Exercises
• FDA: Food Traceability List

Related on this site

• Kroger supplier traceability requirements
• Wegmans supplier traceability requirements: the four asks, decoded
• Costco supplier traceability requirements (2026 edition)
• The FSMA 204 KDE checklist by event type
• Does FSMA 204 require GS1?

Written by Anas Marwan, Co-founder of Darza Technologies. Last reviewed 2026-08-05.