SSCCSerial Shipping Container Code

A Serial Shipping Container Code is an 18-digit GS1 identifier assigned to a single shipping unit — most commonly a pallet, but it can be a tote, case, intermediate bulk container or any other logistical unit. The SSCC is globally unique and persistent for the life of the shipping unit.

Where GTIN identifies the product, SSCC identifies the physical container holding products. A single SSCC may contain multiple GTINs / lots; the relationship is captured in the EDI 856 ASN that references the SSCC. The SSCC has no semantic meaning beyond identification — it does not encode lot, expiry, weight or destination. Those attributes live in the ASN message or in the GS1-128 barcodes alongside the SSCC barcode.

SSCCs were standardised by GS1 in the 1990s and have been the cornerstone of pallet-level logistics across grocery, foodservice, healthcare, electronics, automotive and apparel ever since. Without an SSCC, the entire ASN-based receiving model collapses into manual line-item reconciliation.

1. Extension digit (1) — assigned by the company to increase capacity (0–9). Allows a single GS1 company prefix to issue ten times more SSCCs.
2. GS1 company prefix (7–10 digits) — identifies the issuing company. Length depends on the prefix the company was assigned by its GS1 Member Organisation.
3. Serial reference (variable, fills the remainder) — assigned by the company. Length = 16 − company-prefix-length.
4. Check digit (1) — standard GS1 mod-10 algorithm. Catches single-digit transcription errors and most adjacent-digit swaps.

Total length is always 18 digits, regardless of the company prefix length. The SSCC is encoded using GS1 Application Identifier (00). The full encoded data string is therefore (00)NNNNNNNNNNNNNNNNNN — the parentheses are visual delimiters and are not part of the barcode itself.

The GS1 check digit is computed identically for GTIN, SSCC, GLN and most other GS1 keys. For an SSCC:

1. Take the first 17 digits (everything except the check digit).
2. From right to left, multiply alternate digits by 3 and 1.
3. Sum the products.
4. Find the smallest multiple of 10 ≥ the sum.
5. Subtract the sum from that multiple. The result is the check digit.

Most SSCC issuance is now automated, but the algorithm is worth knowing because hand-keyed test SSCCs almost always fail because the check digit was guessed. Most retailer EDI gateways validate the check digit on ingest and reject the ASN with a checksum-failure error message that doesn't always identify which SSCC was wrong.

EDI 856 (Advance Ship Notice) is the ANSI X12 transaction that describes a shipment hierarchically — shipment → order → tare (pallet) → pack (carton) → item. The tare level is the SSCC. When the truck arrives at the retailer DC, they scan the SSCC on the pallet, look it up in the ASN, and instantly know everything on it.

If the SSCC is missing, duplicated, or doesn't match the ASN, the receiver cannot book the pallet against the order. Most major retailers chargeback for ASN errors — $50–$300+ per occurrence is typical, and a chronic offender can be moved to a stricter compliance tier with $1,000+ per occurrence chargebacks.

The standard pallet label format defined by GS1 has three zones:

• Top zone — free-format text (ship-to address, carrier, customer PO, ship date).
• Middle zone — human-readable Application Identifiers (product description, GTIN, lot, expiry, quantity).
• Bottom zone — barcodes: typically a GS1-128 with GTIN/lot/expiry/quantity and a separate GS1-128 with the SSCC.

The SSCC should be on its own barcode for scan reliability, and printed at least twice on the pallet (typically two adjacent sides) so it is readable regardless of orientation when the pallet is being loaded into the racking. Most large retailers also specify minimum print-quality grade (typically ANSI Grade C or better, measured by a verifier), barcode height (32mm minimum for SSCC), and label size (A5 / 105×148mm minimum).

SSCCs are not infinite per company prefix but the supply is enormous — even a 10-digit company prefix with no extension digit can issue 100 million SSCCs. With the extension digit, that becomes one billion. Most companies will never come close to running out. Common allocation strategies:

• Sequential — issue 1, 2, 3, … and let the check digit follow. Simplest and most common.
• Date-encoded — first six digits of the serial reference are YYMMDD, remainder is a daily sequence. Aids manual reconciliation but reduces capacity per day.
• Plant / line encoded — reserve a digit for plant ID and another for line ID. Useful in multi-site companies but reduces capacity.
• Random — generate random serials and verify uniqueness. Avoids predicting business volume but adds complexity.

Whatever the strategy, GS1 mandates that SSCCs not be reused for at least 12 months after the shipping unit has last left the company's control. Most retailers' systems and 3PL WMSs enforce this internally — if a duplicate appears within the window, the ASN is rejected or the pallet is held for manual reconciliation. For sites issuing tens of thousands of SSCCs per year, reuse risk is effectively zero. For low-volume sites with short serial ranges, it can become real and should drive a wider serial range.

• Reusing an SSCC within 12 months of last use — GS1 forbids reuse for at least a year. Symptom: retailer rejects ASN or holds pallet.
• Generating SSCCs from an unowned company prefix — typically caused by hand-keyed test data or a borrowed prefix. Symptom: ASN passes superficially but creates supplier-onboarding compliance issues.
• Mismatch between SSCC on the pallet and SSCC in the ASN — most common chargeback cause. Symptom: pallet scanned, no matching tare in ASN, manual hold.
• Wrong check digit due to in-house calculation error. Symptom: gateway rejects with checksum failure.
• SSCC barcode print quality below ANSI/ISO C — fails scan at retailer DC. Symptom: manual re-keying chargeback.
• Two pallets with the same SSCC due to an out-of-sync sequence counter. Symptom: ASN rejected for duplicate tare.
• SSCC missing the (00) Application Identifier in the barcode. Symptom: barcode scans as a generic numeric string and isn't recognised as an SSCC.
• SSCC barcode positioned too low or wrapped around a corner. Symptom: scanner can't read; pallet held.
• ASN sent before the pallet physically ships (false-positive ASN) or after the truck arrives (late ASN). Symptom: chargeback for ASN timing.

Chargeback windows are usually 14–30 days, after which the deduction is final. A site with monthly chargebacks above 1% of dispatch volume is at risk of being moved to a stricter compliance tier with multiplied per-occurrence fees.

SSCCs are required by every major US grocery and mass-merchant retailer (Walmart, Target, Kroger, Costco, Sam's Club, Publix, Albertsons, Whole Foods, Amazon Fresh, H-E-B) on every inbound pallet that is part of an ASN'd shipment. Most large foodservice distributors (Sysco, US Foods, PFG) also require them. In the EU, retailers similarly require SSCCs aligned to GS1 standards, and most UK retailers do under GS1 UK's logistic label.

Outside retail, SSCCs increasingly appear in:

• Healthcare distribution — DSCSA-compliant pharma traceability (US) uses GTIN + serial at pack level and SSCCs at pallet level.
• Foodservice — Sysco/US Foods/PFG require SSCC on every inbound pallet ASN.
• FSMA 204-covered foods — SSCC + GTIN + lot satisfies the pallet-level KDE requirements.
• Cosmetics, supplements and OTC — large retailers extend the same SSCC/ASN model to non-food categories.
• Cross-border logistics — customs and 3PL WMSs increasingly key off SSCC for receipt and put-away.
• Returns logistics — same pallet, same SSCC, makes reverse-flow reconciliation possible.

V5 issues, prints and reconciles SSCCs as part of the outbound shipping flow, not as a separate WMS bolt-on:

• Company prefix and extension-digit strategy configured per ship-from site.
• Sequential or date-encoded serial allocation, with a 12-month no-reuse guard enforced at issue.
• Check digit computed and verified on issue and again at label print.
• SSCC linked to the work order, pallet build event, GTIN composition, lot, expiry, net/gross weight and ship-to.
• GS1 logistic label rendered with all three zones, top-zone customisable per ship-to.
• Two-side print (sides A and B) standard, with retailer-specific overrides for orientation and AI set.
• ANSI Grade C minimum print quality target — barcode rendered at correct module width for printer DPI, with verifier-friendly quiet zones.
• ASN built from the pallet record automatically — tare HL = SSCC, pack HL = optional carton serials, item HL = GTIN+lot+expiry+quantity.
• Retailer-specific ASN rule pack validates the message before send (Walmart, Target, Kroger, Sysco, US Foods presets).
• Reprint workflow preserves the original SSCC if the physical pallet is intact, or issues a fresh SSCC and voids the old if it isn't.
• Chargeback dashboard correlates rejected ASNs and held pallets to operator, line, shift and reason — closing the loop on the most expensive root causes first.

The most expensive SSCC failures don't come from check-digit math errors — they come from architectural decisions about where the serial counter lives. A serial issued twice across two systems, two sites, or two co-pack partners breaks the receiver's WMS and produces a hold-and-investigate before any chargeback math runs. The architecture that works:

1. Single serial-counter authority per GS1 company prefix — typically a database sequence in the central manufacturing system, never two parallel counters in WMS and ERP.
2. Pre-allocated ranges per site / per co-packer / per line — when central allocation isn't possible (offline label printers, 3PL partners), issue a non-overlapping serial range per issuer and reconcile usage daily.
3. Atomic serial-claim transaction — the serial is reserved at pallet-build start, not at label print, so a re-print never re-uses and a failed build returns the serial to a 'voided' state (never re-issued — voided permanently).
4. Voided-serial register — every voided SSCC is logged with reason + operator + timestamp; the receiver's call-back lookup must find the void, not silence.
5. Daily reconciliation — issued vs printed vs shipped vs ASN'd; any divergence is investigated within 24 hours before chargebacks accumulate.

Two architectural anti-patterns produce 90% of real-world duplicate-SSCC chargebacks: (a) the WMS issues serials but a manual label-reprint workflow generates them independently from a label printer with its own counter; (b) two sites share a GS1 prefix without coordinating ranges, and both happen to start at serial 0000001. The fix in both cases is to centralise the counter, even at the cost of slightly higher integration complexity — the chargebacks of a single duplication event usually exceed the integration cost.

A single-SKU full pallet is the easy case. Real shipments contain mixed-SKU pallets, layered display pallets, partially built pallets and nested logistic units (case-on-pallet-on-trailer). The GS1 General Specifications and the EDI-856 SPI hierarchy handle this with parent-child SSCCs and AI-37 (count of contained items) on each level.

Two rules dominate mixed and nested logic. First: AI-37 must reflect what is physically on the pallet, not what was scheduled — partial pallets with the full-count AI-37 are the second most common chargeback cause after duplicates. Second: when child SSCCs exist (parent pallet with SSCC'd inner cases), every child must be enumerated in the ASN; receiving systems that scan inner cases will reject the pallet if the inner SSCC isn't in the message.

FSMA 204 (the Food Traceability Rule, effective January 2026 for covered foods on the Food Traceability List) requires Critical Tracking Events with Key Data Elements captured at lot level. The rule doesn't mandate SSCC specifically — but the practical implementation pattern the FDA expects, and that every major receiver has standardised on, uses SSCC at pallet level as the carrier for the KDE aggregation.

The mapping that works:

• Each shipped pallet gets an SSCC; the pallet's manifest includes every lot / case on it (Traceability Lot Code = TLC).
• Each TLC includes its KDEs (product description, quantity, units, harvest date for produce, transformation date for processed, originator, immediate previous source).
• The ASN (EDI 856) ties SSCC → TLC → KDE in a single message that is electronically reproducible within 24 hours per the rule.
• Receivers store the SSCC-keyed manifest as their KDE record on receipt; the SSCC is the join key for any subsequent trace exercise.

Sites covered by FSMA 204 that do not issue SSCCs at pallet level usually end up issuing them anyway within 6–12 months of the effective date because every covered receiver demands them. Building the SSCC programme proactively is materially cheaper than retrofitting under chargeback pressure — labels, printers, scanners and WMS integration all touch in a coordinated rollout once, instead of in a series of customer-driven emergencies.