Kroger supplier traceability requirements: why "it's not on the FTL" doesn't work here

There is a sentence small producers say to themselves that feels like relief, and with Kroger it is simply wrong:

"My product isn't on the Food Traceability List, so none of this applies to me."

For FSMA 204, that reasoning holds. FDA's rule applies to foods on the Food Traceability List and nothing else. If you make granola, or shelf-stable sauce, or hard cheese, the federal rule genuinely does not reach you.

Kroger's policy, published in December 2023, says this instead:

"Kroger intends to collect and record traceability information for all food products entering Kroger facilities to ensure the safety of food supply for every customer."

All food products. Not the FTL. Not high-risk categories. Everything you ship them.

That single scope difference is the reason this post exists, and it is why the exemption question that dominates small-producer forums is a trap. Exemption from FDA is not exemption from your buyer, and your buyer is the one who can stop your purchase orders this quarter.

The deadline already passed

Kroger set June 30, 2025 as the date all suppliers had to transition to its updated traceability requirements. That was more than a year ago.

It is worth understanding the sequence, because it explains a pattern you are now living inside. Kroger published its accelerated timeline in late 2023, which per iFoodDS made it the first major grocery retailer to publish a FSMA 204 timeline ahead of FDA's. Several other retailers followed within months. Wegmans set its own supplier deadline of August 31, 2025. Costco built a program whose traceback bar sits at two to four hours, well inside FDA's 24.

So when FDA's compliance date moved to July 20, 2028, none of those retailer deadlines moved with it. They were never pegged to FDA in the first place. This is the single most expensive misunderstanding in the category right now: producers read the extension as three more years of breathing room, while the people who actually write their purchase orders are already a year past their own date.

The four asks, decoded

Kroger's requirements are unusually concrete, which is good news. There are four.

1. Adhere to Kroger's EDI 856 ASN guideline

The specification lives on edi.kroger.com under Kroger EDI 856 Specifications. This is the governing document, and it is worth reading before you build anything, because the other three asks are all downstream of it.

2. Send an EDI 856 ASN for every shipment

Every shipment, to any Kroger facility. The Advance Ship Notice is an electronic document that tells the receiving dock what is arriving before the truck does.

The thing to understand about the ASN is that it is the vehicle for the traceability data. You are not sending Kroger a separate traceability report. The lot-level information rides inside the shipping document you were already going to send. That is the same architecture Wegmans uses, and it is why "we will handle traceability later" tends to collide with an EDI project you did not budget for.

3. Align your logistic units to Kroger's Track and Trace Supply Chain Receiving Specifications

This is about how product is physically palletized and labeled so the dock can scan it and reconcile against the ASN. Case counts, pallet configuration, and label placement all have to match what you declared.

4. Certify that dock barcode labels correspond to the ASN

The reconciliation step, and the one that fails most often. It is not enough for the ASN to be correct and the labels to be correct separately. They have to agree. A pallet whose label says one lot while the ASN says another is a mismatch at receiving, and mismatches at receiving become chargebacks and supplier scorecard damage.

The data Kroger actually wants

Per ReposiTrak's Kroger supplier guidance, each shipment needs to carry:

ReposiTrak is a vendor with a commercial interest in this list, so treat it as guidance rather than the governing spec, and confirm against Kroger's own EDI documentation before you build. That said, it lines up closely with what the rule asks for anyway.

Which is the useful part: compare that table against the KDE checklist for shipping events and most of it is the same data. The TLC, the ship date, the quantity, and the reference document are all things FSMA 204 already requires you to capture at a shipping Critical Tracking Event. Kroger adds the GTIN and standardizes the packaging fields.

You are not building two systems. You are building one set of lot records and expressing it in the format each buyer wants. That reframing matters, because producers who treat every retailer program as a separate project burn out around retailer number three.

The GS1 point, stated plainly

We have written before that FSMA 204 does not require GS1. FDA's rule is technology-agnostic and mandates no particular standard. That remains true.

Kroger's program is built on GS1 standards and asks for a 14-digit GTIN. So for Kroger specifically, a GS1 Company Prefix and GTINs are effectively the entry ticket.

Both statements are true at once, and holding them together is the whole skill. The federal rule will not make you buy a GS1 prefix. Costco, Wegmans, and Kroger effectively will. Decide based on where you sell, not on what the rule says.

Where small producers actually fail here

Four failure modes, in rough order of how often they bite.

No EDI capability at all. Many small producers ship to independents and specialty grocers on purchase orders and invoices, with no EDI anywhere in the business. Kroger requires an ASN on every shipment, which means either an EDI service provider, a network like ReposiTrak, or a broker who transmits on your behalf. This is a procurement decision with a lead time, not a form to fill in. Start it before you need it.

The lot code lives on the label but not in the record. This is the same break point that sank hour one of our 24-hour traceback drill, and FDA's own 2026 tabletop exercises found only 40 percent of participating firms captured a properly assigned TLC across every Critical Tracking Event. If your production record does not carry the lot code, you cannot populate the ASN without a human retyping it, and humans retyping lot codes is precisely how ASN and label drift apart.

Production and shipping in two systems. The ASN needs shipping data and lot data in the same message. If your make sheets live in a binder and your shipping lives in QuickBooks, something has to join them for every single shipment. That join is either a system or a person, and the person does not scale.

Assuming the 2028 extension applies to Kroger. It does not. Kroger's date was 2025.

What this means if you are not yet a Kroger supplier

Two things worth taking even if Kroger is not on your account list.

First, Kroger moved first and others followed. The retailer-ahead-of-FDA pattern is now the norm rather than the exception, and the specific mechanics repeat: an ASN, a GS1 identifier, a lot code that reconciles between the label and the message. Building that once prepares you for the next questionnaire regardless of whose logo is on it. Our retailer questionnaire breakdown covers what these asks look like when they arrive cold.

Second, the all-foods scope is likely to spread. Kroger's reasoning, that it wants traceability on everything rather than maintaining two parallel processes for FTL and non-FTL items, is operationally sensible for a retailer. Expect others to reach the same conclusion. If you have been counting on being off the FTL, that is a shrinking position.

A prep plan

If a Kroger onboarding packet just landed, work in this order:

1. Pull Kroger's EDI 856 specification from edi.kroger.com before anything else. Build to the actual document, not to a summary like this one.
2. Decide how you will transmit. EDI provider, ReposiTrak, or broker. This has the longest lead time, so start it on day one. Our ReposiTrak playbook covers that route.
3. Get your GS1 Company Prefix and assign GTINs if you do not have them.
4. Fix the lot code at the source. Make sure your TLC is captured on the production record at the moment of transformation, not reconstructed from a label afterward. The worked examples show the format for three product types.
5. Run one shipment end to end on paper before you transmit anything. Write out the ASN fields by hand from your actual records. Every field you cannot fill from an existing record is a gap you will otherwise discover at the dock.

Step 5 is the one people skip and the one that finds the problems.

Where FSMA204Hub fits

Everything above reduces to one requirement: for any finished lot, you can produce the lot code, what went into it, and where it went, from one place, on demand and in someone else's format.

That is the bet behind FSMA204Hub. Each finished lot is one row. The input lots and the customers hang off the same code. When a buyer asks for shipping KDEs in their layout, it is a filter and an export rather than a reconciliation project. The compliance score tells you which lots would fail that request before a retailer finds out for you.

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

---

Onboarding with Kroger and stuck on the ASN? Email [email protected] with how you currently record lot codes and ship, and I will tell you the shortest path to a clean ASN.

Further reading

• SeafoodSource: Kroger among companies stepping up FSMA 204 compliance efforts
• ReposiTrak: Traceability for Kroger suppliers
• FDA: Food Traceability List

Related on this site

• 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?
• ReposiTrak supplier onboarding: a 7-day playbook

Written by Anas Marwan, Co-founder of Darza Technologies. Last reviewed 2026-07-30.