Skip to content
The Complete Guide to GS1-128 Carton Labels
Spring Systems
Retail Compliance
Back to Blog

The Complete Guide to GS1-128 Carton Labels

May 5, 2025 8 min read Retail Compliance

The GS1-128 label is the physical interface between your shipment and the retailer’s automated receiving system. Every other EDI document — the 850, the 855, the 856, the 810 — is electronic data that exists in systems. The GS1-128 label is where that data meets the physical world: a dock worker scans the barcode on a carton coming off a truck, and that scan is what links the physical carton to the electronic ASN the retailer’s system already has loaded. If the barcode scans cleanly and matches the ASN, the carton flows through automated receiving in seconds. If it doesn’t, the line stops.

What’s on a GS1-128 Label?

A compliant label is divided into four horizontal zones, and each zone feeds a different part of the DC’s receiving process:

Zone A (Top)
The carrier routing information — retailer DC or store address, carrier SCAC, pro number. The DC’s receiving system uses this zone to match the carton to the expected inbound freight schedule and route it to the correct dock staging area. If the carrier SCAC doesn’t match what the routing guide specified, the system flags it before the carton even enters the building.

Zone B (Upper Middle)
Retailer-specific data including store/department number, vendor number, and PO number. The DC system reads these fields to link the physical carton to the correct purchase order in their database and identify which store or department the contents are destined for. A wrong or missing PO number here means the system can’t associate the carton with an expected receipt — which is functionally the same as shipping without an ASN.

Zone C (Lower Middle)
Item-level data: description, quantity, UPC. This tells the receiving system what’s inside the carton without anyone opening it. The UPC in this zone is what the system cross-references against the ASN’s item-level pack structure to confirm the carton contains exactly what the electronic manifest said it would. If the UPC here doesn’t match the UPC in the 856, the system flags a mismatch — and the carton goes to manual reconciliation.

Zone D (Bottom)
The Serial Shipping Container Code (SSCC-18) barcode — the unique identifier for each carton. This is the barcode the dock worker scans when the carton comes off the truck. The SSCC-18 is the key that links the physical carton to its ASN record, triggering the automated routing flow: match found, contents confirmed, conveyor routes to the correct outbound lane. If this barcode doesn’t scan, the entire automated receiving process stops for that carton — there’s no match, no ASN link, no destination lane. The carton comes off the line and goes to manual processing.

Why Label Errors Are One of the Most Common Chargeback Triggers

Label errors generate chargebacks more frequently than almost any other compliance failure, and the reason is mechanical: a barcode that won’t scan stops the receiving line. When a dock worker scans a carton’s SSCC-18 and the scanner returns nothing — because the barcode is smudged, printed at wrong contrast, missing quiet zones, or using a duplicate SSCC-18 — the conveyor can’t route the carton. The system has no match, no ASN link, no destination lane. The carton comes off the automated line and goes to a manual reconciliation station where someone has to open it, count contents, and figure out where it belongs by hand. That’s the same labor cost and cross-dock delay as a late ASN, triggered by a piece of adhesive label stock that cost you five cents to print.

The compounding problem is that label errors are often batch errors. If your thermal printhead is dirty or failing, it doesn’t affect one label — it affects every label printed in that run. A single bad printhead can produce hundreds of cartons with barcodes that look fine to the human eye but won’t scan at the DC. Those cartons arrive at the retailer looking compliant, pass your visual inspection, and then fail at the one moment that matters — the scanner at the dock door. By the time you find out, the chargebacks have already been taken.

Common Mistakes That Cause Chargebacks

  • SSCC-18 not unique per carton — duplicate codes mean the system matches multiple physical cartons to the same ASN record, causing receiving confusion and inventory miscounts
  • Missing Application Identifiers (AIs) — the AI prefixes (like 00 for SSCC, 02 for GTIN) tell the scanner what data format follows; without them, the system can’t parse the barcode content
  • Barcode quiet zones too narrow — the blank margin around a barcode is what lets the scanner distinguish the barcode from surrounding print; compress it and the scan fails intermittently, which is worse than a consistent failure because it’s harder to diagnose
  • Label stock not meeting size requirements (typically 4" x 6") — oversized or undersized labels may not fit the retailer’s automated label applicator or scanner mount
  • Wrong font size or contrast on human-readable text — if the text is too small or low-contrast, a worker doing manual reconciliation can’t read it quickly, extending the processing time and the labor cost the chargeback recovers

Retailer-Specific Requirements

Every retailer has their own spin on GS1-128. Walmart’s zone content requirements differ from Target’s, which differ from Home Depot’s. Field placement, required AI combinations, and even label orientation can vary. A label that’s compliant for one retailer can fail at another’s DC — not because the barcode is wrong, but because the retailer-specific fields in Zone B aren’t in the expected position or format. Spring Systems PortalApp generates retailer-specific compliant labels automatically based on current specifications and updates whenever retailers change their requirements.

Testing Your Labels

Before going live with a retailer, submit sample labels for approval. Most retailers have a certification portal or vendor compliance team that reviews label formats. But the most useful test you can do yourself is simple: scan your labels with a standard handheld barcode scanner, not the one on your shipping line. If a handheld scanner can’t read it reliably, the DC’s industrial scanner — which processes cartons at conveyor speed — won’t either. Catch a print quality issue before the retailer’s compliance team does, and you avoid a certification delay. Catch it after go-live, and you’re looking at chargebacks on every carton in the shipment.

Need Help with EDI Compliance?

Our team has been helping suppliers navigate retailer requirements since 2002. Whether you're onboarding with a new retailer, fighting chargebacks, or looking to automate your EDI process — we can help.

Spring Systems

Spring Systems EDI Team

EDI & Retail Compliance Experts Since 2002

Have Questions About EDI?

Our team is available by phone and email to help with any compliance challenge.