EU retailer distribution centres (DCs) receive high volumes of B2B stock every day. At the dock, the first thing inbound teams scan is usually not the packing slip—it is the GS1 logistics label on the carton or pallet. For wholesale brands shipping into those networks, SSCC GS1-128 wholesale shipping is the physical scan layer that must match order, packing, and advance shipping notice (ASN) data. When the label and the electronic message disagree, freight sits, gets reworked, or triggers a chargeback.
This guide explains what an SSCC is, how GS1-128 encodes it, what EU DCs typically expect on carton and pallet labels, how SSCC ties to ASN/DESADV, and how brands keep labels, WMS, and order systems aligned so inbound flows cleanly.
What is an SSCC and how does GS1-128 encode it on wholesale labels?
An SSCC (Serial Shipping Container Code) is a unique serial number assigned to a logistics unit—typically a carton, mixed case, or pallet—for the life of that unit in the supply chain. It identifies this physical package, not the product type inside. That distinction matters: product identity uses a GTIN; the moving box or pallet uses an SSCC.
GS1-128 is the barcode symbology used on GS1 logistics labels to carry SSCC and related data in a machine-readable form. It is the GS1 application of Code 128, structured with GS1 Application Identifiers (AIs) so scanners know which field is which.[1] On a wholesale shipping label, the SSCC is encoded under Application Identifier 00, usually as the dominant barcode on the label face.[1]
In plain terms: the SSCC is the serial; GS1-128 is how that serial (and optional companion data) is printed for automated scan at retailer DC inbound.
A single serial barcode bridging a sealed carton and a pallet
What do EU retailer DCs expect on carton and pallet GS1-128 labels?
Retailer DC inbound routing guides differ by banner, but expectations for GS1-128 label requirements EU wholesale shipments converge on a few practical points:
- A GS1 logistics label on each logistics unit that needs independent handling or scanning.
- A scannable SSCC barcode (AI 00), sized and placed so dock scanners and forklift scanners can read it without unpacking.
- Human-readable text that mirrors the barcode data (SSCC digits, and other printed AIs when used).
- Clear carton vs pallet hierarchy: pallet labels identify the unit load; carton labels identify inner cases when the DC will break or cross-dock at case level.
- Label placement on flat, unbroken surfaces—not over seams, straps, or stretch-wrap edges that distort bars.
- Print quality sufficient for reliable scan (adequate contrast, quiet zones, and undamaged faces after transit).
Many DCs treat the logistics label as the primary key for put-away and receipt. Free-text marks, brand stickers, or carrier-only labels do not replace a proper SSCC when the retailer’s process is GS1-based. For multi-country moves, the same label discipline still applies even when transport documents change; see our cross-border EU B2B shipping guide for how transport and compliance documents sit alongside logistics labels.
Which application identifiers belong on a GS1 logistics label?
A GS1 logistics label can carry more than the SSCC. Application Identifiers tell the scanner what each data field means. On wholesale carton and pallet labels, the fields you most often see are:[1]
| AI | Meaning | Typical wholesale use |
|---|---|---|
| 00 | SSCC | Mandatory serial for the logistics unit |
| 01 | GTIN | Trade item identity of contents (when a single GTIN applies) |
| 10 | Batch / lot | Traceability and FEFO-style handling |
| 17 | Expiry date | Food, beauty, and other dated goods |
| 37 | Count of trade items | Quantity of units or cases in the logistics unit |
Not every AI belongs on every label. Homogeneous cases often carry GTIN plus count; mixed pallets may rely on SSCC plus ASN detail rather than a single content GTIN. Retailer guides specify which AIs are mandatory for their DCs. Overloading the symbol with unused fields can hurt scan reliability; under-labelling forces manual work at the dock.
GTIN setup for sellable units and case packs should already be clean in the catalogue before labels are designed—weak case GTINs show up as weak inbound scans. For catalogue structure, see GTIN setup for units and cases.
Application identifier blocks arranged like labelled cargo tags on a logistics label
How does SSCC tie to the ASN in wholesale shipping?
An ASN (advance shipping notice), often exchanged as DESADV in EDI, is the electronic description of what is on the way and how it is packed. The SSCC is the join key between that message and the physical freight.[2]
In a healthy flow:
- The order is confirmed and allocated.
- Packing builds cartons and pallets; each logistics unit receives a unique SSCC.
- The ASN lists those SSCCs in hierarchy (pallet SSCC containing case SSCCs, or cases only, depending on how the load is built).
- DC scanners read the label SSCC and match it to the ASN line for that unit.
- Receipt, put-away, or cross-dock proceeds against the electronic hierarchy.
If the label shows an SSCC that never appeared on the ASN—or the ASN lists SSCCs that were never applied—the dock has a mismatch. That is the core of serial shipping container code ASN discipline: one serial, used once, shared consistently between print, warehouse, and EDI.
EDI is not mandatory for every SME brand, but when a retailer requires DESADV, SSCC quality becomes non-negotiable. Manual “we’ll fix it at goods-in” does not scale across automated EU DCs.
When do case-level vs pallet-level SSCCs matter for multi-ship wholesale orders?
Carton vs pallet hierarchy is where many wholesale brands under-specify labels.
- Pallet-level SSCC suits full-pallet, single-destination loads that DCs receive and store as unit loads.
- Case-level SSCC matters when the retailer breaks pallets on receipt, cross-docks cases to stores, or scans every carton for high-value or regulated goods.
- Both appear on mixed or multi-line wholesale orders: outer pallet SSCC for yard and dock handling; inner carton SSCCs for content verification.
Multi-ship orders (one PO, several dispatches or several DC destinations) multiply the risk. Each physical departure needs its own logistics units and ASN snapshot. Reusing an SSCC across shipments, or printing pallet labels only when the buyer expects case scan, is a common path to dock rejection shipping labels issues and later deductions.
Split fulfilment also affects documents and invoicing. Keep packing hierarchy aligned with how you invoice and confirm partials so finance and warehouse tell the same story.
How do brands avoid dock rejections for missing or unreadable SSCCs?
Dock rejection and chargeback risk usually comes from process gaps, not exotic barcode theory. Practical controls:
- Assign SSCCs in the system of record at pack time, not on a standalone label printer with no memory of the order.
- Never reuse an SSCC on another logistics unit.
- Print-test GS1-128 symbols under warehouse lighting and after stretch-wrap; reject unreadable stock before dispatch.
- Place labels on adjacent vertical faces when guides require dual-side pallet labelling so forklift approach still scans.
- Match ASN send timing to actual dispatch so the DC is not scanning freight the message has not yet described.
- Train pack stations on retailer-specific exceptions (mixed carton rules, floor-ready requirements, banned label materials).
- Reconcile exceptions the same day—missing label, damaged face, or hierarchy error—rather than waiting for a deduction notice.
Packing documents still matter for humans on the dock, but they do not replace the scan path. Pair logistics labels with clear EU wholesale packing slip requirements so manual checks and automated receipt reinforce each other.
A dock door scanner beam reading a pallet label cleanly
Where should SSCC labels sit relative to packing slips and carrier labels?
Think in three layers:
- GS1 logistics label (SSCC / GS1-128) — retailer DC handling and receipt identity.
- Packing slip / delivery note — human-readable order, lines, and references inside or pouch-mounted on the unit.
- Carrier label — transport network sorting and tracking between ship-from and DC gate.
Do not cover the SSCC with the carrier label. Do not treat the carrier tracking barcode as a substitute SSCC. Carrier labels optimise the linehaul; GS1 logistics labels optimise retailer inbound. Brands that run both cleanly usually integrate print rules so each face of the pallet has a defined home for each label type. For transport-side setup, see carrier labels and tracking for B2B wholesale.
How should WMS, carriers, and order systems share SSCC data?
SSCC only works as a supply-chain key if every system that touches the shipment uses the same values.
Order / B2B layer holds the commercial truth: retailer, PO, lines, ship-to DC, and allowed partials.
WMS assigns or consumes SSCCs as cartons and pallets are built, and captures hierarchy (which cases sit on which pallet).
EDI / ASN publishes that hierarchy outward.
Carrier systems need weight, measures, and routing—not a conflicting serial that overwrites GS1 identity.
What to sync is straightforward in principle: order references, pack hierarchy, SSCC list, GTIN/batch attributes required on labels, and dispatch timestamps. Gaps appear when labels are printed from a local spreadsheet while the ASN is built from the ERP, or when a 3PL assigns SSCCs the brand never sees. Align master data and pack confirmation first; barcode art is the last mile. A practical checklist lives in what brands should sync with a WMS.
Three system nodes exchanging one shared serial token around a shipment
Keeping the physical scan layer honest
For EU wholesale brands, SSCC barcode wholesale discipline is less about collecting standards PDFs and more about one rule: the serial on the carton or pallet is the same serial the ASN and warehouse system already know. GS1-128 is how that serial is presented; Application Identifiers add content context; retailer DC inbound is where mismatches become expensive.
When order capture, packing, and dispatch data stay consistent, labels stop being a last-minute art job and become a reliable scan layer. A branded B2B portal with clean order-to-dispatch data—and optional links to WMS or carrier tools—reduces the manual re-keying that produces SSCC/ASN mismatches in the first place.
If you want to see how Brandgate keeps wholesale orders structured from retailer purchase through fulfilment handoff, book a demo.