Start with the unit being transported or stored.
GS1 Australia describes the Serial Shipping Container Code, or SSCC, as the identifier for an individual logistics unit. A unit can be a carton, pallet or another grouping prepared for handling and transport. The SSCC is not simply another name for a product code or batch number. GS1 Australia identification FAQs.
Within the GS1 logistics-label system, the SSCC links the physical unit to information about it. GS1 Australia's fact sheet explains the relationship between barcode scanning and electronic business messages. It identifies the SSCC as the mandatory element of a GS1 Logistic Label. That does not mean every laboratory shipment is universally required to use this system. Confirm the arrangement with the receiving organisation. GS1 Australia logistics-label fact sheet (PDF).
This guide concerns the identity and record relationship. The barcode print-quality guide covers the different task of specifying and reviewing a printed symbol.
A logistics unit, trade item and lot need separate fields.
Before asking for a label, draw the packaging hierarchy used in the actual shipment. Identify which physical grouping will be handled as one unit and which descriptions belong to the contents. Keep your internal warehouse references visible alongside any agreed GS1 identifiers.
| Record level | What it identifies | Keep distinct from |
|---|---|---|
| Logistics unit | The individual grouping handled for storage or transport | Every item inside that grouping |
| Product or trade item | The specified item or pack configuration in the agreed system | A particular production lot |
| Batch or lot | The production grouping recorded for the contents | The carton, pallet or carrier consignment |
| Carrier reference | The carrier's consignment or movement record | The contents list or analytical report reference |
| Receiving entry | Your organisation's record of what arrived | Proof that all technical documents were accepted |
A single scan does not make these different relationships disappear. The receiving record still needs a way to connect the unit to its expected contents.
Identify who supplies and approves the actual identifier.
Ask the trading partners to confirm the logistics-unit definition, identifier assignment responsibility, data source and receiving workflow. Use actual authorised identifiers supplied through the agreed system. This article supplies no sample production SSCC and does not imply that Wholesale Lab Peptides holds a particular GS1 membership or number allocation.
The brief should also identify the label location, required human-readable information, the receiving system and any partner-specific implementation document. Give the artwork supplier the approved data and label requirements rather than asking the designer to invent an identifier that looks plausible.
Retain a populated proof for review. Confirm that the encoded information and the visible reference represent the same intended unit, then use a separately agreed print-quality assessment where required. Content mapping and print quality are complementary checks.
Mixed contents need a controlled mapping.
A logistics unit may contain more than one product, lot or packaging component. Keep a contents record that identifies the actual grouping, line descriptions, quantities and relevant lot references. Do not describe the contents using a convenient single-lot label when the underlying record says otherwise.
For a partial or split shipment, record the relationship between the physical unit, the released quantities and the remaining order lines. A unit's identifier is not a statement that the full order has been supplied. Link it to the goods-receipt reconciliation rather than treating a scan as the whole acceptance decision.
If the grouping changes before handover, ask the responsible operator how the logistics record and identifier relationship will be updated. Preserve the actual handover record; do not reuse an earlier contents list without checking that it still describes the unit.
Keep two delivered units distinct from one order.
Hypothetical example: an Australian receiving site expects one order delivered as two logistics units. The first contains labelled empty containers; the second contains printed outer packaging. The local planning notes call them “unit A” and “unit B”; these are explanatory names, not example GS1 identifiers.
If unit A arrives first, record its actual identifier and received contents against the corresponding order lines. Keep unit B outstanding until its own receiving event. One carrier consignment reference or an invoice covering the full project does not mean both units have arrived.
The same approach makes discrepancies easier to describe: identify the physical unit, its expected contents and the observed difference. A general statement that “the barcode worked” does not resolve a missing or mismatched component.
Carry the agreed mapping into dispatch and receiving.
Before dispatch, retain the approved label/data version, the actual unit-to-contents record and the receiving contact's implementation requirements. On arrival, compare the physical unit with those records and record unresolved differences. The Australian dispatch checklist covers timing, carrier handover and delivery estimates separately.
For a packaging-only project, the Australian labels and cartons enquiry can describe the label layout, quantities, data fields and required proof. Confirm technical feasibility and identifier responsibilities for the actual project; a packaging enquiry does not establish compliance with a particular trading partner's requirements.