Lot, batch and serial traceability

Choose the level before the technology

A product identifier represents a type of item. A lot or batch identifier distinguishes a group associated with a defined production or handling context. A serial identifier distinguishes one individual instance. A logistics-unit identifier can identify a case, pallet or other shipping unit.

Organisations sometimes use “lot” and “batch” differently. Document your own definitions and agree their meaning with partners. Do not assume a supplier lot and an internal production batch are the same group, or that either has a globally unique reference on its own.

Make the identifier unambiguous

A code such as B42 may repeat across factories or suppliers. Pair local references with the relevant product and issuer context, or adopt an appropriate standardised identity scheme. The important result is that every receiving system can distinguish the intended object.

Keep the original supplier reference as well as any internal replacement. Otherwise a supplier complaint may cite an identifier your team can no longer resolve. Maintain the mapping and its effective dates when identities change.

Preserve packaging relationships

When items are packed into a case, record the relationship between the case and its contents. When cases are placed on a pallet, record that relationship too. Unpacking, splitting or repacking can change those associations.

A scan of the pallet should resolve the relevant recorded contents at that point in time. It should not imply that every item ever associated with the pallet is still inside it. Event history and current containment need different interpretations.

Balance precision and effort

Serial-level tracing can offer more precise item histories, but it increases capture and data-management demands. Batch-level tracing may be adequate for some questions, while creating a larger affected population during an investigation. Choose the level using the risk, process variation and intended use of the data.

Test operator workload as well as record precision. If a serial process encourages skipped scans at peak production, a theoretically detailed design can deliver weaker practical coverage.

Questions for a pilot

• Can two suppliers use the same local lot code without creating a collision?
• Can split quantities still be reconciled?
• Does repacking preserve the previous identity?
• Can a customer’s reference resolve to your original batch?

GS1 offers identification keys for several object types. Consult the official key definitions before assigning them; the choice of an identifier alone does not establish legal compliance. Continue with event records to connect identities to activity.

Frequently asked questions

Is a batch code unique on its own?

Not necessarily. A short local code may repeat across issuers, products or facilities. Preserve the context required to identify the intended group and agree that context across partner interfaces.

Must every product be serialised?

There is no universal answer for every industry and use case. Evaluate the applicable product rules, customer contracts and precision needed for the investigation. Serialisation also needs reliable capture and relationships; numbering alone is insufficient.