GS1-128 / SSCC-18 Labels: Where EDI Meets the Warehouse Dock
An EDI 856 can be perfectly mapped, transmit on time, and still cause a shipment to sit in receiving limbo — because the barcode on the carton doesn’t match the data in the transaction. That single point of failure, the label on the box, is where the abstract world of EDI segments meets the physical world of pallets, dock doors, and scan guns.
What GS1-128 and SSCC-18 Actually Are
GS1-128 is a barcode symbology — a standardized way of encoding structured product data (GTIN, batch/lot, dates, weight, and more) using GS1 Application Identifiers. A single GS1-128 barcode can carry up to 48 data characters, letting one label communicate far more than a simple product code.
SSCC-18 (Serial Shipping Container Code) is a unique, serialized “license plate” number assigned to a specific pallet or carton — a company prefix plus a serial number, encoded using AI (00). It doesn’t describe the product; it identifies that exact shipping unit, and only that one.
Together, they turn a physical box into something a warehouse management system and an EDI transaction can both recognize as the same object.
The Connection Point: The MAN Segment
Here’s where EDI and the physical label actually meet: the 856 Advance Ship Notice contains a MAN (Marking) segment that carries the SSCC-18 number for each carton or pallet in the shipment. When a receiver scans the barcode on the dock, their system looks up that SSCC-18 against the ASN that was transmitted ahead of the truck — and if the two match, the receipt can happen automatically, without anyone re-keying a single line item.
If they don’t match — wrong label, missing label, or an SSCC-18 that was never included in the ASN’s MAN segment in the first place — that automation breaks, and the shipment often gets flagged, held, or charged back.
How This Plays Out at Major Retailers
Walmart builds this connection directly into its food traceability requirements. Under its FSMA 204 program, all pallets containing food must carry an SSCC-18 barcode linked to the corresponding ASN, while cases must carry a GS1-128 barcode. Walmart is explicit that this labeling requirement exists specifically to support the Key Data Elements transmitted in the ASN — the label and the EDI document are two halves of the same compliance requirement, not separate obligations.
Kroger ties its ASN certification process to the same physical detail. As part of certifying a vendor’s ship-from location, Kroger confirms that shipping container marking is correct and that the ASN is being transmitted on the expected timeline — meaning a technically valid 856 still isn’t “done” until the labels on the actual pallets match what was transmitted.
Macy’s separates its EDI Mapping Guides from its Routing Guide and Vendor Standards, but shipping container marking requirements show up across all three — a reminder that label compliance isn’t purely an EDI concern or purely a logistics concern; it sits at the intersection of both.
Walgreens may be the clearest illustration of the label-to-EDI relationship anywhere in retail. Its DC Shipping Guide maps out specific label zones — Zone F for the vendor number, Zone G for the final destination code, Zone I for the SSCC-18 — and states outright which EDI segment each zone corresponds to: Zone G matches the N1 segment’s ship-to qualifier, and Zone I’s SSCC-18 barcode corresponds directly to the ASN’s MAN segment. It’s a rare case of a retailer spelling out, field by field, exactly how the sticker on the box and the EDI document are the same data expressed twice.
Shopbop enforces the connection with real financial teeth. Its vendor manual requires the SSCC-18 on every GS1-128 carton label to match the MAN02 segment of the 856 exactly, and lists specific chargebacks for mismatches — including penalties when carton contents don’t match the ASN, when a pallet’s SSCC label is missing or obscured, or when the ASN doesn’t arrive before the shipment reaches the fulfillment center.
GS1, as the standards body behind all of this, maintains the underlying specifications — barcode symbology, Application Identifier formats, print quality thresholds, and label placement rules — that every retailer’s individual label requirement is ultimately built on. Its industry guidance is what keeps a GS1-128 barcode printed by one supplier readable by any retailer’s scanner, regardless of which ERP or EDI system generated the underlying data.
Why This Matters for EDI Practitioners
It’s easy to treat EDI mapping and physical labeling as two separate workstreams — one belongs to IT, the other to the warehouse or packaging team. But as these examples show, the label is often just another rendering of data that already lives in your EDI transaction. If your ASN’s MAN segment, GTIN, and batch/lot data don’t match what actually gets printed on the carton, no amount of clean X12 syntax will prevent a rejected receipt or a chargeback.
The practical takeaway: whenever you’re mapping an 856, ask who owns label generation and confirm the SSCC-18, GTIN, and batch/lot values are pulled from the same source of truth as the ASN — not entered separately by a packaging system that never talks to EDI. That single alignment is often the difference between a shipment that flows through the dock automatically and one that stalls at the receiving desk.
EDI Academy is a vendor-neutral EDI training and certification provider helping healthcare, retail, supply chain, finance, and IT teams build practical skills for accurate transactions and smoother operations.