GS1 Sunrise 2027 Puts New Load on EDI 856 Data

What happened

GS1's global 2D-barcode transition, known as Sunrise 2027, now sits roughly 14 months from its formal deadline of December 31, 2027. By that date, major retailers across the United States and globally will require the ability to scan and process 2D barcodes such as GS1 DataMatrix and GS1 Digital Link QR codes at point of sale, running alongside the 1D UPC/EAN codes that have carried retail for five decades. GS1 launched the initiative in 2022, and the program's stated goal is for retailer and point-of-care scanning systems to read both barcode types by the target year.

This is not a government mandate. It's an industry-coordinated commitment, which means enforcement runs through retailer supplier agreements rather than regulatory penalty. Walmart, Target, Carrefour, Tesco, Woolworths, Kroger, Dillard's and Safeway are all setting 2D barcode requirements for their suppliers, and several have already pushed requirements to specific supplier categories well ahead of the formal 2027 date. If you're waiting for a single industry-wide deadline to start planning, you're already behind the retailers that matter most to your business.

Why this lands on the EDI team's desk, not just packaging

The reason this isn't purely a labeling project: 2D barcodes carry lot numbers, expiration dates, and serial numbers in addition to the GTIN. That data often exists today only in your ERP or WMS, not printed on a label. Once it's in a scannable 2D code, it has to match, exactly, what you're transmitting electronically to the retailer. If your 856 Advance Ship Notice says one lot number and the case barcode encodes another, you've created a reconciliation problem that shows up as a receiving exception, not a packaging defect.

You don't have to guess what this looks like in production. It's already happening with FSMA 204 traceability at Walmart. All ASNs (EDI 856s) must incorporate the FSMA 204 KDEs, and Walmart has published updated EDI 856 incorporating FSMA 204 KDEs, split into separate guides for perishable and resale goods. The pattern is identical to what Sunrise 2027 will demand more broadly: barcode-level identifiers and EDI transaction data have to agree, and the EDI team owns that agreement, not the label print vendor.

Downstream, your TMS or multi-carrier platform sits right in the middle of this. Cargoson, MercuryGate, Descartes, and Shipmondo all consume or validate shipment data generated upstream of label printing, and each will need to pass through new GTIN, lot, and serial identifiers without breaking existing label-to-ASN mapping that's worked fine for years.

The retailer-by-retailer reality: don't wait for 2027

For most suppliers, December 2027 is a ceiling, not the planning date. Walmart has already communicated requirements to certain supplier categories ahead of the 2027 deadline, and Kroger's traceability-adjacent deadline for food items landed even earlier, on June 30, 2025, well before Walmart's own August 1, 2025 cutoff for Food Traceability List items.

After the formal deadline, retailers are no longer obligated to support products carrying only a 1D barcode. That's the ceiling. Your actual exposure is whichever of your top retail partners moves first, and several already have.

What changes in the 856, and what doesn't

The 1D barcode isn't disappearing on a fixed date. Dual marking, 1D and 2D together, is the expected state through 2027 and likely well beyond it. What changes is the data richness your 856 needs to support. GTIN plus lot (AI 10), expiration (AI 17), and serial number (AI 21) encoded in the 2D symbol need corresponding fields in your hierarchical loop structure, the same way FSMA 204 forced new KDE segments into Walmart's 856 spec. If you've already done that mapping work for food traceability, you have a head start. If you haven't, Sunrise 2027 is going to force the same conversation across a much wider set of product categories.

A practical readiness checklist

• Audit which SKUs or categories already have a retailer-communicated 2D deadline. Don't plan against the 2027 date if Walmart or Kroger has already told you otherwise for specific lines.
• Confirm GTIN, lot, and serial data actually exists cleanly at the record level in your ERP or WMS before it's expected to appear in a barcode or an 856 segment.
• Test 2D-to-856 reconciliation in a sandbox with at least one early-adopter retail partner before it becomes a live receiving exception.
• Loop in packaging and label teams early. EDI can't fix a print quality problem, but it owns the data behind what gets printed, and misalignment between the two is where chargebacks come from.

Where this fits in the API vs. EDI conversation

The long-term carrier for this denser data is probably not the 856 at all. Walmart's current FSMA 204-aligned requirements accept traceability data through an ASN over EDI or through EPCIS via API, giving suppliers a choice based on technical maturity. Sunrise 2027 looks like another incremental push in that same direction: not a wholesale replacement of EDI, but one more reason hybrid architectures, where EDI handles the transaction backbone and APIs carry the richer, more frequently updated identifier data, keep gaining ground. EDI isn't going anywhere. What it's being asked to carry just keeps getting denser.