A printed batch code can identify a package without explaining its history. Traceability depends on the records connecting that package to incoming materials, production events and onward shipments. A useful test therefore follows the connections rather than counting how many labels have been printed.
The GS1 Global Traceability Standard, Release 2.0 distinguishes the events that happen to traceable objects from the data describing those events. It also illustrates recording production inputs and outputs at batch level. These are foundational concepts for the exercise below, not a claim that completing it satisfies a legal, certification or GS1 implementation requirement.
Start with a finished batch
Choose a batch and ask the team to identify its production record, incoming materials and outgoing shipments. Preserve each link as it is found. If someone needs to rely on memory, record that as a gap rather than treating a verbal explanation as a permanent replacement for the evidence.
Ask the same question in the other direction: where did an incoming lot go? The two searches test different parts of the record chain. A system that can explain one finished package may still be unable to find every use of a particular input.
Identify the moment when the code changes
Splitting, combining, repacking or processing can introduce a new identifier. The important record is the relationship between the old and new identifiers, together with the event that created it.
Consider a hypothetical packing operation that divides one incoming lot into several cases. A new case code is useful only if the records retain the parent lot. If two lots are combined in a production run, the output record needs the actual input relationship rather than a default supplier name copied from the last run.
Build an event map before adding fields
Sketch receiving, storage, transformation, packing and dispatch in the order used by the operation. At each relevant event, ask who creates the record and how it connects to the adjacent step. This is an ACA design exercise using the standard’s concepts, not a reproduction of its full specification.
| Event in the exercise | Connection to check |
|---|---|
| Receiving | Supplier lot to the accepted goods |
| Internal movement | Batch to the recorded location |
| Transformation | Actual inputs to the resulting output |
| Packing | Output batch to its cases or other units |
| Dispatch | Shipped units to the outgoing reference |
Keep units and quantities understandable where they are used. A correct identifier attached to an unexplained quantity still leaves the team with a question.
Test retrieval with the people who use it
Ask a receiving operator and an office-based colleague to retrieve the same record independently. Note where terminology, permissions or the filing system slows either person down. Improving those points may matter more than adding another report screen.
Record the date of the exercise, the chosen batch and each unresolved link. Give the gap an owner. A later repeat should test whether the connection was repaired, not simply whether the team now remembers the selected batch.
Keep the scope honest
This exercise checks whether the team can reconstruct a record chain. It does not validate the safety of the food, establish that all quantities reconcile or prove compliance with every market’s traceability requirements. Those questions need their own appropriate controls and review.
For readers working in China, use the standard as a common vocabulary while checking the requirements applying to the actual product and transaction. A barcode is an entry point to evidence; the evidence must remain connected across the whole operation. For the storage part of that chain, see our warehouse record framework.
Source and further reading
- GS1 Global Traceability Standard, Release 2.0
GS1 · Accessed 2026-10-13
ACA’s practical examples and working checklists are independent editorial analysis. The linked source provides the underlying reference; it does not endorse this article.
