IDXE by EDI Partners Talk to an Expert

← Insights

Your 856 Is Becoming a Food Safety Document (FSMA 204)

For most food suppliers, the Advance Ship Notice (EDI 856) has been a receiving document: it tells the DC what's on the trailer. Under FSMA 204, the same transaction is turning into something heavier: the record that shows which lot of a high-risk food left which building, on what date, headed where.

You don't need a new transaction set for that. You need the ASN you already send to carry traceability data accurately, at the right level of the hierarchy, on every load. The X12 is the easy part. The hard part is getting lot, date, and location data out of the warehouse the moment a pallet is built, rather than reconstructing it from the purchase order afterward.

Where FSMA 204 stands in late 2026

FDA's Food Traceability Rule, the part of the Food Safety Modernization Act known as FSMA 204, requires companies that manufacture, process, pack, or hold foods on the Food Traceability List (FTL) to keep Key Data Elements (KDEs) for defined Critical Tracking Events (CTEs). They must also be able to hand that information to FDA within 24 hours, or within a reasonable time FDA agrees to (FDA, Food Traceability Final Rule page).

The original compliance date was January 20, 2026. FDA proposed a 30-month extension to July 20, 2028, and Congress then directed FDA not to enforce the rule before that same date in the FY2026 continuing appropriations act (FDA; Federal Register, Aug. 7, 2025; Congressional Research Service report R48925). FDA has said the extension doesn't change what the rule requires. It only moves when enforcement starts. Retailers didn't treat July 2028 as a reason to wait.

Retailers moved first: what Walmart has published

Walmart's supplier food traceability page is the clearest public example. According to that page:

(Walmart Supplier Enablement, Food Traceability; SPS Commerce, "Food Safety (FSMA) Requirements and Compliance at Walmart," Oct. 2025.)

Walmart also accepts EPCIS over API, but for suppliers already exchanging 850s and 856s, the ASN is the practical path. Other buyers may publish their own requirements on their own timelines, so check each partner's current guide.

What GS1 US changed in March 2026

GS1 US publishes EDI Recommendations for FSMA 204 Critical Tracking Events, a voluntary guideline that shows how to carry the Shipping CTE in an X12 856. Release 1.0 came out in March 2024. Release 2.0, dated March 1, 2026, did not overhaul the approach. Its change log lists:

(GS1 US, EDI Recommendations for FSMA 204 CTEs, Release 2.0.)

That stability is useful: the mapping is settled enough to build to now. GS1 is also explicit that the guidance is voluntary. Where it differs from your retailer's 856 guide, the retailer's guide wins.

The ASN as the traceability channel: segments that usually come up short

The Shipping CTE KDEs are a short list: traceability lot code (TLC), quantity and unit of measure, product description, ship-from, immediate subsequent recipient, TLC source (or reference), ship date, and reference document. GS1 maps each into structures most ASNs already contain. Here's where they tend to fall short:

LIN at the pack level: GTIN and lot. GS1 recommends expressing the TLC as GTIN-14 plus batch/lot, for example LIN*<seq>*UK*<GTIN-14>*LT*<lot>, at the pack hierarchical level. Many existing ASNs carry the GTIN and leave out the lot. Others carry one lot per item line even when a pallet mixes lots. The guidance ties lot to the pack, so a pallet with two lots of the same item needs two pack-level entries, each with its own quantity.

SN1 per lot. Quantity and unit of measure sit in SN1 inside the pack level, counted per lot. A rolled-up item quantity hides the lot split the rule cares about.

N1 with GLNs: ship-from, ship-to, and TLC source. GS1 maps ship-from (N1*SF) and ship-to (N1*ST) to GLNs at the shipment level. The TLC source, meaning the place where the lot code was assigned, goes in a pack-level N1*MP carrying a GLN. To address concerns about exposing commercially sensitive information, the guidance also shows a TLC source reference such as a URL. Suppliers who buy from co-packers or other plants often have no GLN master data for those sources at all.

DTM for the ship date. GS1 uses DTM*011 at the shipment level. A date that comes from the PO or the scheduled pickup, instead of the actual ship event, is a quiet accuracy problem.

MAN and the SSCC link. The pallet SSCC (MAN*GM) has to match the physical label. Under traceability, the SSCC is how a receiver connects a pallet to its lots, so a reprinted label that never reaches the ASN breaks more than receiving.

Reference document. GS1 treats the 856 itself (ST01) and the BSN02 shipment ID as the reference document. Supporting REFs such as the bill of lading still need to be right, because they're how a load gets found later.

Retailer guides may add more. Walmart's KDE list, as SPS summarized it, also includes country of origin, weights, and production, harvest, best-before, sell-by, and expiration dates. Build to the partner's guide and use GS1 as the reference model behind it.

The hard part isn't X12. It's lot data in the WMS.

Every segment above is easy to map if the data exists at ship time. Usually it doesn't, for familiar reasons:

The rule that applies here is the same one behind pack-based ASNs in general: build the 856 from what was actually packed, not from what was planned. (We covered that pattern in Your 856 Is Lying: ASNs From the Pack, Not the Plan.) FSMA 204 adds lot, date, and source to the list of things the floor has to capture at scan time.

Why managed maps and partner-spec testing beat a last-minute scramble

Teams that wait for an enforcement date usually end up keying lots into a portal for whatever items a retailer flags first. That clears a PO. It doesn't scale, and it makes the traceability record depend on whoever is on shift.

A steadier path looks like this:

  1. Scope your items. Decide which SKUs are on the FTL and record it. Walmart asks for a per-item self-declaration.
  2. Close the WMS gaps first. Require lot and date capture at pick and pack for scoped items, including mixed-lot pallets.
  3. Build GLN master data for ship-from, ship-to, and every TLC source.
  4. Map each partner's 856 version. Perishable and general-merchandise guides can differ within one retailer.
  5. Test against partner specs with multi-lot pallets, multiple TLC sources, and label reprints, not just the clean load.
  6. Watch past the 997. An acknowledgment says the file arrived, not that the KDEs passed. Retailer dashboards and application advice tell you that.

That's the gap a managed EDI model is built to cover. IDXE, EDI Partners' proprietary Azure-native managed EDI platform, connects to the WMS and ERP systems that already know what was packed, maintains partner-specific 856 maps including the traceability segments, validates ASNs against each partner's current spec, and watches rejects and exceptions after go-live. Because the managed team owns map changes and partner testing, a guide revision doesn't become a fire drill for your IT staff.

Takeaways

If your 856 still describes cartons and not lots, now is a good time to close that gap before peak season. Talk to EDI Partners about FSMA 204-ready ASNs with IDXE →