You have a routing guide in front of you. It says every carton must carry a compliant GS1-128 label with a valid SSCC barcode, and your next shipment is scheduled for Thursday. If those terms are unfamiliar, you are not behind on EDI theory. You are behind on what your label printer needs to output before the truck leaves.<\/p>\n
An SSCC barcode encodes the Serial Shipping Container Code, an 18-digit number that uniquely identifies a single logistics unit. That logistics unit can be an outer case, a pallet, a layer on a pallet, or any other grouping of goods that is packed together and handled as a unit during storage or transport.<\/p>\n
The most important thing to understand about the SSCC barcode is that it does not identify the product inside the container. A UPC or GTIN identifies the product. The SSCC identifies the container. If you scan an SSCC barcode on a pallet at a retailer’s distribution center, you learn which pallet it is and what the ASN says it contains. You do not learn the product UPC directly from the SSCC.<\/p>\n
That distinction matters because it changes how you assign and manage these numbers. Every logistics unit that needs to be tracked independently receives its own unique SSCC. Under GS1 standards, an SSCC should not be reassigned for at least one year after the shipment date, although regulatory, industry, or trading partner requirements may require a longer period.<\/p>\n
If one retailer’s routing guide asks for a UCC-128 label and another asks for a GS1-128 label, do not be confused by the terminology. UCC-128 and EAN-128 are older names associated with what is now called GS1-128.<\/p>\n
UCC-128 was the name commonly used in North America, while EAN-128 was used internationally. After the Uniform Code Council and EAN International became GS1, the standard became known as GS1-128. Because routing guides have not been updated consistently, suppliers still encounter all three terms.<\/p>\n
The practical path forward is simple: a routing guide using UCC-128, EAN-128, or UCC barcode terminology is referring to the standard now called GS1-128. Suppliers should still follow each trading partner’s current label specification, including its required data fields, layout, and print-quality rules.<\/p>\n
GS1-128 uses standardized Application Identifiers, or AIs, to tell a scanning system what the barcode data represents. For example, AI (00) identifies an SSCC, while other AIs can identify information such as a GTIN, lot or batch number, or expiration date. This structure lets supply chain systems interpret the encoded data consistently.<\/p>\n
If you need proof that your labels meet the standard before shipping, label certification is available through TrueCommerce.<\/p>\n
The SSCC-18 has four components that add up to 18 digits total.<\/p>\n
A quick example of how the four components fit together: a company with the prefix 0614141 might assign SSCC-18 values in sequence starting at 000001. Extension digit 3, prefix 0614141, serial reference 000001, check digit calculated from those 17 digits combined. The resulting 18-digit string is what encodes inside the AI (00) barcode on the label.<\/p>\n
A GS1 logistics label typically combines the machine-readable GS1-128 barcode with human-readable information that helps warehouse teams identify and process the shipment. The SSCC is the required identifier on a GS1 logistics label, while exact human-readable fields and additional barcode data vary by trading partner.<\/p>\n
Many retail compliance labels are organized into zones. Depending on the trading partner’s requirements, the upper portion may include human-readable information such as ship-from and ship-to details, carrier information, purchase order number, and item or department information. The GS1-128 barcode carrying the SSCC is commonly placed in the lower portion of the label.<\/p>\n
The data fields and layout vary by retailer. GS1 defines the identification and barcode standards, while each trading partner may publish additional requirements in its routing guide or vendor compliance manual. A label configured for one retailer may not satisfy another retailer’s rules, even when both use GS1-128 and require an SSCC.<\/p>\n
Print quality also matters. A barcode can contain the correct data and still be difficult or impossible to scan because of printer settings, label material, placement, damage, or poor contrast. Follow the scan-grade and print-quality requirements in the trading partner’s routing guide, and test labels before shipping.<\/p>\n
Each logistics unit that needs to be tracked independently should have its own unique SSCC. Depending on the trading partner’s requirements, that may mean identifying a pallet, individual cases, or other shipping units separately. A pallet SSCC and a case SSCC are different identifiers.<\/p>\n
Some retailer workflows use a packaging hierarchy in the ASN, with a pallet identified as the parent logistics unit and separately identified cases listed beneath it. Other workflows require only certain packaging levels. Always follow the retailer’s routing guide and ASN requirements when deciding which units need SSCCs and how their relationships should be reported.<\/p>\n
This SSCC label hierarchy is a common source of practical errors. Problems can occur when required case identifiers are omitted, the same SSCC is assigned to more than one logistics unit, or the physical packing structure does not match the ASN. These discrepancies can require manual receiving and may lead to chargebacks.<\/p>\n
The safest practice is to identify every logistics unit required by the trading partner, assign each one a unique SSCC, and keep the physical packing structure aligned with the ASN. If a labeled unit is split, combined, or reconfigured, update the labels and shipment data as required by the applicable workflow before shipping.<\/p>\n
This relationship is the most important part of the labeling process.<\/p>\n
The sequence usually works like this. Your warehouse packs the shipment and assigns an SSCC to each logistics unit that requires identification. Your system generates GS1-128 labels carrying those SSCCs and transmits an advanced shipping notice<\/a>, commonly an EDI 856<\/a>, that describes the shipment. At receiving, the retailer scans the SSCC encoded in the GS1-128 barcode and uses it to connect the physical logistics unit with the shipment information received electronically.<\/p>\n When the scanned SSCC matches the information in the ASN, the retailer’s receiving system can use that identifier to connect the shipment with the relevant order and packing details. That can support faster, more accurate receiving, subject to the retailer’s processes and other compliance checks.<\/p>\n When the label and ASN do not match, the shipment may require manual review. Someone may need to identify what arrived, reconcile it with the purchase order, and resolve the discrepancy. Depending on the retailer’s compliance program, that extra handling can cause delays and potential chargebacks.<\/p>\n The most common failure modes are:<\/p>\n Many retailers use automated checks during receiving. If the SSCC on the label does not match the ASN, the barcode cannot be scanned, or a required field is missing, the shipment may be flagged. Depending on the retailer’s compliance program, the result can include manual receiving, delays, and chargebacks.<\/p>\n Requirements differ among trading partners and can change over time. A label configuration that passes one retailer’s validation may fail another’s. Food suppliers may also face additional traceability requirements under regulations such as FSMA 204. Learn how SSCC-18 pallet labels<\/a> can support food traceability workflows without assuming that FSMA 204 specifically mandates them.<\/p>\n The cost of a labeling failure is not just a potential chargeback on one shipment. It can include receiving delays, added labor on both sides of the transaction, and risk to the trading partner relationship if violations accumulate. A connected compliance process can help suppliers avoid chargebacks<\/a> by reducing preventable label and ASN discrepancies.<\/p>\n A frequent underlying issue is that label generation and ASN generation are disconnected. They may happen in different systems, at different times, or through manual re-entry. Connecting the processes helps keep the SSCC printed on the physical shipment aligned with the SSCC communicated electronically.<\/p>\n The case for connected label generation is primarily about accuracy and compliance, with time savings as an added benefit.<\/p>\n When label generation and ASN creation are connected, the same shipment data can support both processes. That reduces manual re-entry and helps keep the SSCC printed on the physical logistics unit aligned with the SSCC communicated in the ASN. If the shipment changes after labeling, the related label and shipment data still need to be reviewed and updated before transmission or shipping.<\/p>\n\n
Why Label Errors Become Chargebacks<\/h2>\n
Generating Compliant Labels Without Manual Work<\/h2>\n