SSCC and GS1 Logistics Labels for Imported Pallets and Cartons

An SSCC identifies one individual logistics unit. A GTIN identifies a type of trade item. If your Chinese supplier puts the carton GTIN on every pallet and calls it the pallet number, the receiving system still cannot distinguish pallet one from pallet two.

The practical control is to define the handling unit first, assign a unique SSCC to each unit, encode it correctly on a GS1 logistics label and link that same SSCC to accurate contents and shipment data. Then read back the number, barcode, printed text, physical unit and electronic record before dispatch.

That process is useful whether the logistics unit is a pallet, an outer carton, a parcel or another grouping created for storage or transport. The receiving customer's current requirements still control which units must be labelled and what optional data is needed.

Use an SSCC for the logistics unit, not as a replacement GTIN

GS1 Australia defines a Serial Shipping Container Code, or SSCC, as an identifier for an individual logistics unit such as a case, pallet or parcel. The current GS1 General Specifications describe it as an 18-digit key that remains with that unit for its life.

The difference is serial identity:

• A GTIN answers: which trade item is this?
• An SSCC answers: which individual logistics unit is this?
• A shipment or consignment reference answers a different question again: which commercial or transport grouping does the unit belong to?

A pallet can be both a trade item and a logistics unit. For example, a standard pallet configuration may be ordered and invoiced as a trade item while one physical pallet still needs an SSCC for movement and receipt. In that case the identifiers coexist; the GTIN does not replace the SSCC.

Decide what is being identified before a label is built

Do not begin by opening label software. Begin with the actual pack-out and the receiving process.

Lock the product side first. The SKU, GTIN and barcode setup guide explains how to control trade-item identifiers. The packaging specification guide defines the physical pack-out that later becomes the logistics unit.

Then write a unit hierarchy for the shipment: units per inner, inners per carton, cartons per pallet, pallet IDs, mixed-unit rules and which level the receiver will scan. If the factory, consolidator and Australian warehouse use different meanings for carton, case, pallet or handling unit, resolve that vocabulary before number allocation.

Assign each SSCC from one controlled number source

The SSCC uses GS1 Application Identifier AI (00) followed by the 18-digit SSCC data. GS1 Australia says the physical builder or brand owner of the logistics unit is responsible for the GS1 Company Prefix used in the SSCC. The prefix makes the key globally unique; it does not state where the goods came from.

Before a supplier generates any label, record:

• who is authorised to allocate the SSCC;
• which GS1 Company Prefix and number range they are authorised to use;
• whether a factory, consolidator, buyer, 3PL or approved service generates the number;
• which system prevents duplicates;
• when the number is assigned and locked to the physical unit; and
• how cancelled, rebuilt, shipped and decommissioned units are archived.

Avoid unmanaged spreadsheets at two sites drawing from the same range. Also avoid a cloud label tool that silently uses the software provider's prefix. The GS1 Logistic Label Guideline warns that using an IT provider's prefix for shipper labels can weaken traceability and be inconsistent with GS1 rules.

The current GS1 General Specifications state that an SSCC must not be reallocated within one year of the shipment date from the assignor to a trading partner. A regulator, industry body, customer or internal traceability policy may require a longer period. Treat one year as a minimum hold, not a universal instruction to recycle the number on the first eligible day.

Use an SSCC register with at least:

Link the physical unit to the shipment data

An SSCC becomes operationally useful when the receiving system can use it to retrieve the correct unit data. GS1 Australia explains that the code can link the physical unit to a despatch advice or Advance Shipping Notice. The scan is a key into the record; the barcode is not automatically a complete manifest.

For every unit, reconcile the SSCC to:

• shipment, purchase-order and receiver references;
• contained trade items and quantities;
• batch, lot, serial or date information where applicable;
• gross and net weight or dimensions where exchanged;
• dispatch, route and delivery data required by the trading partner; and
• the exact unit that was wrapped, labelled and loaded.

The GS1 Logistic Label Guideline distinguishes homogeneous and heterogeneous units. A homogeneous logistics unit that is not itself a trade item may use AI (02) to identify the contained trade item; when AI (02) is used, GS1 requires it to be combined with AI (00) for the SSCC and AI (37) for the count. A mixed unit cannot truthfully be described by one content GTIN; GS1 recommends electronic messaging linked to the SSCC.

Do not add an Application Identifier because a label template has an empty field. Each encoded field needs a defined source, correct data format and receiving use. If the supplier cannot show where a lot, date, quantity or receiver code came from, hold that field and resolve the data contract.

Give the supplier a label contract, not a barcode picture

The SSCC is the single mandatory element of a GS1 Logistics Label. It is represented in a GS1-128 barcode and shown in human-readable form. Other data and label sections depend on the business process.

Give the supplier a controlled instruction covering:

• logistics-unit definition and label quantity per unit;
• SSCC allocator, prefix authority and number source;
• required GS1 Application Identifiers and the source field for each;
• human-readable data titles and approved language;
• receiver, route or customer data supplied by the buyer;
• label stock, printer, placement surface and protection from seams or wrap;
• label location and duplicate-label arrangement;
• barcode verification and evidence required before dispatch;
• filename, artwork revision and approval owner; and
• what to do if a pallet is rebuilt, a carton count changes or a label is damaged.

The December 2024 GS1 Australia Logistic Label Fact Sheet recommends two identical labels on adjacent pallet sides and provides current GS1-128 size, quiet-zone and placement guidance. Use the current specification and the receiver's implementation rules for final artwork; do not reduce those rules to a screenshot copied from a previous shipment.

GS1 Australia's Logistics Labelling Tool may help eligible small businesses create labels. Its current service page says the browser tool has no connection to internal databases. Generating a label therefore does not by itself update an ASN, warehouse record or SSCC register.

Read back the data and the physical label before dispatch

Artwork approval is not final-label verification. Thermal print settings, ribbon, label stock, surface, wrapping and application can all change the result.

Require one evidence pack for each label format and a shipment-level data export:

Scan each final label into a neutral capture view where practical, but do not confuse one successful scan with standards verification. A scan can return the wrong number perfectly. Verify the data structure and physical quality as well as readability.

At loading, cross-check the SSCC against the unit loaded. The container loading check is the last physical opportunity to detect a labelled-unit substitution before the seal is applied. At destination, connect discrepancies to the incoming quality inspection and quarantine process rather than silently correcting the warehouse record.

Control relabelling, consolidation and unit changes

Origin consolidation changes unit identity if cartons are regrouped onto new pallets or a mixed pallet is rebuilt. The multi-supplier consolidation guide explains the wider receiving and dispatch controls; the SSCC rule is narrower: the label must continue to identify the actual logistics unit represented in the data.

Use a fail-closed exception sequence:

1. Stop the affected unit from dispatch.
2. Record the old SSCC, unit state and reason for change.
3. Decide whether the physical logistics unit still exists unchanged or a new unit has been created.
4. Assign a new SSCC where the applicable unit rule requires it.
5. Replace or cancel the electronic record and remove obsolete live labels.
6. Reprint, reapply and repeat the physical/data read-back.
7. Archive the superseded relationship and preserve the reuse hold.

Never leave two active SSCC labels on one unit after relabelling. Never move a label from a cancelled pallet to a new pallet because the numbers are visually convenient.

Worked example: three pallets and one mixed pallet

This example is hypothetical and is not an OPL customer case.

An importer orders two product variants. The factory builds three homogeneous pallets of variant A and sends loose cartons of variant B to a consolidator. The consolidator creates one mixed pallet containing the remaining A cartons and all B cartons.

• Each of the four physical pallets receives its own SSCC.
• The three homogeneous pallets can be linked to variant A's GTIN and quantity in the applicable message structure.
• The mixed pallet is linked by its SSCC to an electronic contents record listing both variants and their quantities; it is not described as one contained GTIN.
• The factory and consolidator use separate authorised allocation controls. The importer receives one manifest showing which party assigned each SSCC.
• Before loading, photographs, scan output and the shipment record show that all four SSCCs match the four wrapped pallets.

If the consolidator removes cartons from the mixed pallet after that read-back, the unit/data relationship has changed. The record must be corrected and the affected unit released again before loading.

Use one release sequence for every shipment

Start with the receiver. Ask which physical levels are scanned, which GS1 data is required, how shipment data is exchanged and which exceptions cause rejection. Then define the pack hierarchy and allocator before production labels are generated.

For each shipment:

1. freeze the trade-item and packaging hierarchy;
2. define the logistics units and receiving scan points;
3. confirm allocator authority and the SSCC number source;
4. assign one unique SSCC per relevant unit;
5. bind each SSCC to accurate contents and shipment data;
6. print and apply the final labels;
7. reconcile the unit, register, barcode, human-readable text and shipment message;
8. confirm the labelled units at loading; and
9. archive the unit life and reuse hold.

Hold dispatch if the supplier cannot prove which unit a label identifies, which system issued the number or which electronic record the receiver will retrieve. The purpose is not to print more barcodes. It is to make every physical logistics unit and its data agree before it enters the Australian receiving chain.

Sources

1. GS1 General Specifications, release 26.0
2. GS1 Logistic Label Guideline, release 1.3
3. GS1 Australia — Serial Shipping Container Code
4. GS1 Australia — Identification FAQs
5. GS1 Australia — GS1 Logistic Label Fact Sheet, December 2024
6. GS1 Australia — Logistics Labelling Tool