Wrong SSCC Format on a Pallet Label: How to Identify and Fix It
The SSCC — Serial Shipping Container Code — is the most critical field on a pallet label. It is the unique identifier for that specific pallet in that specific shipment. If the SSCC is wrong, the pallet cannot be received automatically, and everything downstream — the ASN match, the three-way PO reconciliation, the payment — breaks.
SSCC errors are extremely common and often invisible until the pallet arrives at a retail DC. Here is how the SSCC structure works and how to identify and correct errors before they reach the dock.
What Is an SSCC?
An SSCC is an 18-digit number that globally and uniquely identifies a logistic unit — a pallet, a tote, a container, any unit that moves through a supply chain. "Globally and uniquely" means no two SSCCs, anywhere in the world, should ever be the same — not just in your company, not just in your country.
SSCCs are structured as follows:
[Extension Digit] [GS1 Company Prefix] [Serial Reference] [Check Digit]
Total: 18 digits.
The Extension Digit (1 digit): A value from 0 to 9 that extends the numbering capacity. You choose this digit. Most suppliers use 0.
The GS1 Company Prefix (7–10 digits): Assigned to your company by GS1 US. This is the foundation of all your GS1 identifiers. You cannot generate valid SSCCs without a real GS1 Company Prefix.
The Serial Reference (6–9 digits, depending on prefix length): A sequential number you assign to each pallet. The serial reference + extension digit + prefix must total 17 digits combined, leaving one digit for the check digit.
The Check Digit (1 digit): Calculated mathematically from the preceding 17 digits using the Luhn algorithm (specifically the GS1 check digit formula). This digit allows scanners to confirm the SSCC was not corrupted in transmission or printing.
The Most Common SSCC Errors
Error 1: Fabricated Company Prefix
The supplier doesn't have a GS1 Company Prefix (or doesn't realize they need one) and uses a random number. The SSCC looks like 18 digits but is not registered to any real company. Most retailer systems can detect this because the prefix doesn't appear in the GS1 Company Database. GS1 US Company Prefixes start at $250/year. There is no workaround — you need a real prefix to generate valid SSCCs.
Error 2: Wrong Check Digit
A manually entered SSCC with a typo in any digit will also have the wrong check digit. The scanner detects this as a malformed barcode even if the barcode itself prints correctly. This is invisible without a validation tool — the barcode looks fine visually.
Error 3: SSCC Too Short or Too Long
18 digits exactly. Not 17, not 19. Template errors or manual entry often produce SSCCs with the wrong digit count.
Error 4: SSCC Reuse
An SSCC used on a previous shipment is reused on a new pallet. The retailer's WMS sees the same SSCC arrive twice and flags it as a duplicate — a compliance violation that generates a SSCC Already Used chargeback.
Error 5: SSCC Not Sequential
SSCCs don't have to be sequential, but your serial reference counter must increment. If the counter resets to 1 after a system reboot or end-of-year rollover, you will start reusing SSCCs. Track your highest-used serial reference number and never reset below it.
How to Validate an SSCC
Manual validation: Calculate the check digit using the GS1 check digit formula and confirm it matches the 18th digit of your SSCC. Use GS1 US's free online check digit calculator at gs1us.org.
Automated validation: Use a compliance tool that validates SSCC structure — correct prefix format, correct length, correct check digit — before generating the barcode.
How to Fix a Wrong SSCC
If you catch the error before the truck leaves: Regenerate the label with a correct SSCC. Update the ASN to replace the wrong SSCC with the correct one. Retransmit the ASN. Confirm acknowledgment before departure.
If the truck has already left: Call the DC's receiving department immediately and provide the correct SSCC and the pallet position on the truck. Some DCs will manually update the system. Most will not — the chargeback is likely unavoidable, but proactive communication may speed up the receiving process and prevent a full shipment refusal.
If you received a chargeback and believe the SSCC was correct: Pull your ASN transmission record and your original label data. If both show the same correct SSCC and the chargeback cites a different number, it may be a scanning error or a system error at the DC. Document this thoroughly for the dispute.
Tag Verify validates SSCC structure — correct prefix, correct length, correct check digit — before generating the barcode. An SSCC that fails structure validation doesn't make it to the print command.
Build your next pallet label at tagverifyapp.com — free, no account required.