The pallet is built, wrapped and ready to leave. What must its label tell the next warehouse? Enough to identify that particular load and connect it to trustworthy shipment information. A successful barcode scan alone cannot establish what is under the wrap. The handoff works when the physical contents, the identifier attached to them and the receiving system’s record describe the same logistic unit.
Separate the load’s identity from its contents
A Serial Shipping Container Code (SSCC) is an 18-digit GS1 identifier for an individual logistic unit, such as a loaded pallet handled as one unit. Two otherwise identical pallets need separate identities. The number is commonly carried in a GS1-128 barcode, but the number and its barcode representation are different things, as explained in the GS1 US SSCC overview. An SSCC does not itself encode a product list, case count, destination or purchase order.
A Global Trade Item Number (GTIN) identifies a trade item: something priced, ordered or invoiced. Packaging levels matter. A consumer unit, a case of those units and a predefined pallet traded as a product can have distinct GTINs. The GS1 GTIN Management Standard governs these distinctions. A GTIN answers which trade item is involved; an SSCC distinguishes the particular logistic unit carrying goods. Identifying a case product does not identify every individual case.
A shipment or consignment groups units for a different purpose. In the GS1 Logistics Interoperability Model Application Standard, Release 1.1.1 (March 2019), a shipment is a sender’s grouping for one customer under a despatch advice and/or bill of lading. A consignment is a carrier’s or forwarder’s transport grouping under one transport document. Several pallet SSCCs can therefore share a shipment reference. A carrier tracking number or routing label serves the transport process; it should not be assumed to replace the pallet’s GS1 identity. Transport and GS1 logistics information may coexist on a combined label.
Build the record around the pallet actually leaving
Consider a hypothetical shipment of Product A. Each case contains 12 consumer units. The approved full-pallet arrangement has 12 cases per layer and five layers, or 60 cases. The customer has ordered 56 cases, and the warehouse builds four complete layers plus eight cases on top. The order is for cases; this pallet groups them for transport. Assume that this partial configuration has been approved for physical handling and transport; this example evaluates the information handoff, not load stability.
The shipping record should therefore describe 56 cases and their actual arrangement, rather than inheriting 60 from the full-pallet plan. The Pallet Calculator can establish a planned physical arrangement and case quantity. When a build departs from that plan, reconcile the final count separately. As the TI/HI explanation illustrates, multiplying cases per layer by layers requires attention to whether those layers are complete.
For this shipment, record Product A’s case-level GTIN against a quantity of 56 cases. The product hierarchy establishes 12 consumer units per case, giving 672 consumer units. Keep the relevant batch or lot information with the contents, together with the order and shipment references. Recording relationships between a logistic unit and the goods inside it is a central principle of the GS1 Global Traceability Standard. The SSCC identifies the load, rather than serving as the permanent asset number of the reusable pallet underneath it.
The practical test is whether someone could reconstruct this build without asking the person who stacked it. A useful record would distinguish the approved full-pallet pattern from the actual partial build, identify the counted packaging level and retain the contents detail needed by the receiver. A free-text note saying “short pallet” would leave too much unresolved: short against which pattern, by how many cases, and of which product?
For this example, the builder allocates the SSCC through its controlled numbering process using its licensed GS1 Company Prefix, following the GS1 allocation approach. The illustrative identity here is DEMO-SSCC-NOT-VALID. It is deliberately non-numeric and unusable, not an SSCC to print operationally. The warehouse associates the real identifier with the completed contents record, prints the label and checks that it is applied to the intended pallet.
Information schematic only. The placeholder is deliberately invalid; an operational label requires valid GS1 identifiers, barcode artwork and the applicable partner requirements.
Read the label as several kinds of information
The GS1 Logistic Label Guideline, Release 1.3, July 2019, identifies the SSCC as the universally mandatory data element. Other fields depend on the unit and trading-partner needs; symbol and presentation requirements still apply. The following is an information map, not a print-ready template. Check operational label artwork against the current GS1 General Specifications and the receiving partner’s requirements.
| Label information | What it communicates | Rule or condition |
|---|---|---|
| SSCC, barcoded and human-readable | This individual logistic unit | GS1’s mandatory identity element. |
| Product identity and quantity | Which trade item, at which packaging level | Conditional: a homogeneous, non-trade-item pallet can carry the contained GTIN and its count; a pallet traded as an item can carry its own GTIN. |
| Batch/lot or relevant date | Attributes associated with identified contents | Conditional GS1 data; use valid associations, not a misleading single value for mixed contents. |
| Plain-language contents | For example, “Product A; 56 cases” | Helpful optional text; a partner may require it. |
| Ship-to, order and routing details | Delivery and commercial context | Partner/process-specific requests; encoded GS1 fields retain their defined rules. |
Scroll to compare all columns.
Human-readable interpretation is the readable representation of barcode data. Descriptive text elsewhere on the label is not necessarily encoded. “Product A; 56 cases” can help a person while remaining outside the barcode payload. Neither should contradict the linked record.
Make the barcode lead to usable shipment information
A barcode carries only the data encoded in it. A GS1-128 barcode can include identifiers and additional structured attributes, such as batch or expiry information, where applicable. Encoding extra fields does not turn the SSCC itself into a container for those fields. They remain separate data elements, and a label need not encode every contained product to make the unit traceable.
For the example pallet, suppose the receiving application scans its SSCC and uses that value to find the expected contents. The scanner has captured an identifier; the application supplies the 56-case contents record. Without that association, the scan cannot reveal the missing information. Equally, a clear product description printed above a barcode does not make that description available to the application through the scan.
An advance shipping notice (ASN), or despatch advice in the relevant messaging arrangement, communicates shipment information electronically. It is separate from both the physical label and the sender’s internal database. The GS1 logistics interoperability model describes this exchange between sending and receiving parties. In this example, the agreed message would link the pallet SSCC to Product A and 56 cases, allowing the receiver to associate the arriving unit with its order.
Agree how and when that association becomes available before relying on scan-based receiving. A sensible handoff check is to inspect the receiver’s expected record, not merely confirm that the sender generated a message. At receipt, whether the pallet can move directly to put-away or needs counting, condition checks or a quality hold depends on the receiving procedure and agreement. The SSCC supplies identity, not permission to bypass those controls.
Catch the mismatch before the receiving dock does
Suppose the physical build is correct but the shipment message still contains the full-pattern quantity of 60 cases. The mismatch is straightforward:
- Actual build: 4 × 12 + 8 = 56 cases; 56 × 12 = 672 consumer units.
- Stale planned quantity: 5 × 12 = 60 cases; 60 × 12 = 720 consumer units.
- Overstatement: 4 cases, equivalent to 48 consumer units.
The label’s SSCC may scan perfectly and retrieve exactly the wrong quantity. If the receiver books the advised quantity without discovering the discrepancy, inventory starts 48 consumer units too high. If the receiver counts first, the same error becomes a receiving exception requiring reconciliation. Neither result is repaired by making the barcode larger or adding another copy of the label.
A hierarchy error can be less visible. Recording “56” against the consumer-unit GTIN describes 56 consumer units, not 56 cases. The number must be interpreted with its product identifier and unit of measure. For this build, the case record, the 12-unit case relationship, the 672-unit equivalent and the partial-layer configuration must agree. A pallet-pattern instruction can explain how to stack the cases, but it cannot identify which completed load arrived or prove that the planned quantity shipped.
Preserve the connection when the load changes
Mixed contents require more than a total case count. A homogeneous pallet has one GTIN at the highest contained packaging level. For an ad hoc mixed load, do not use one component’s GTIN to represent everything, under the GS1 label rules described above. A predefined mixed assortment traded as one item can instead have its own GTIN. In a mixed version of the example, maintain separate contents lines by product and applicable lot. A readable “mixed products” description can flag the need to inspect those lines, but cannot replace them. Even one product can span multiple lots, so product uniformity does not establish lot uniformity.
A partial pallet also raises a product-definition question. Shipping fewer unchanged cases does not, by itself, change those cases’ GTIN. However, changing the defined case quantity of a pallet that is itself a predefined trade item is covered by the quantity-change rules in the GTIN Management Standard, Release 1.1 (September 2023). Establish which situation applies before reusing a full-pallet product description for a partial shipment.
Repalletization requires a record of what moved where. If one received load is broken into two newly built logistic units, allocate distinct identities to those new units and preserve their relationship to the original contents. Copying the original SSCC onto both would make two separate loads claim one identity. Remove superseded identity labels from the newly built units. Recording aggregation and disaggregation relationships is part of the GS1 Global Traceability Standard, Release 2.0 (August 2017). The precise transaction sequence belongs in the site’s warehouse and trading-partner procedures.
A damaged label poses a different question: can the unchanged unit’s existing identity be established reliably? An appropriate controlled response is to reconcile it against trustworthy records or another verified label, then reprint that identity. Do not guess from the product description or assign an unrelated number simply because the printer needs one. Where identity remains uncertain, hold the unit for reconciliation under the local exception process.
Before release, compare the applied identifier, its linked contents and the receiver’s expected information against the actual pallet. Resolve any difference at that point, including who must correct a message already sent. That check makes the label useful beyond the loading dock, where the person who built the pallet is no longer available to explain it.