How to Keep a Food Batch Traceable Across Processing Handoffs

A food batch is only as traceable as the records connecting it at the points where responsibility changes. A supplier may provide a clear incoming lot reference, and a warehouse may have a dispatch record, yet an investigation can still stall if the connection through production, holding or repacking is missing.

The practical objective is narrower than guaranteeing food safety or meeting every possible compliance obligation. Your team should be able to start with either a finished lot or an incoming material lot and reconstruct the relevant chain: what entered the site, what was done to it, what outputs resulted, and where those outputs went.

This is an operational framework, not a statement of China-specific legal, certification or recall requirements. Local laws, customer specifications, product risks and site controls may require more detailed arrangements.

Start by defining the batch you need to find

Before selecting labels, software or forms, define the traceable unit: the item, group of items or movement that the business needs to identify and follow. A batch number is an identifier. A traceable unit is the thing to which that identifier and its records apply.

This distinction matters because a label alone does not establish the scope of an investigation. For example, a code may refer to:

• one delivery from a supplier;
• one ingredient lot received into the warehouse;
• material issued to a single production run;
• a defined quantity produced during a run;
• a case, pallet or shipment; or
• a finished lot created after packing.

The appropriate unit depends on the questions your operation must answer. If a concern is raised about an incoming ingredient, can the team identify all finished lots made from it? If a concern is raised about a finished lot, can the team identify the inputs, production records and customers connected to it?

The FMI/GS1 implementation guide for fresh fruits and vegetables describes the need for trading partners to determine what will be traced and agree on that traceable item. Although the guide is directed to a particular supply-chain context, the underlying lesson is useful more broadly: two parties cannot reliably exchange traceability information if they are referring to different units.

ACA analysis: choose the smallest practical unit that answers the investigation questions without creating records that teams cannot maintain accurately. A processor does not need to identify every unit individually if its operation can reliably link a defined production lot to its inputs and outputs. Conversely, a broad daily code may be too coarse where multiple input lots, lines or destinations need to be separated.

Write this decision down. A short definition should state what the unit covers, when a new unit is created, and which record establishes the link to the preceding and following stage.

Use a small set of identifiers that can be carried forward

A usable traceability system does not require every record to contain every operational detail. It does require a stable set of references that allow records held by different teams to be joined.

The Food Marketing Research and Information Center handbook presents identification of food, raw materials, suppliers and buyers, together with linkage records, as fundamentals of traceability. The Institute of Food Technologists guidance for processed foods similarly frames traceability around key data elements captured at critical tracking events.

For many processing operations, a minimum working identifier set includes:

Not every item in the table must appear on the physical label. Some information belongs in a receiving log, batch sheet, warehouse transaction or electronic system. The essential point is that the shared identifier is legible, unique within its intended scope, and available to the people who need to reconcile the records.

Keep identifiers separate from descriptive information. A product name, pack size or production date may help a person interpret a record, but it may not uniquely establish the relevant batch. Likewise, an internal lot code should not rely on an informal meaning known only to one shift supervisor.

A Chinese food-production traceability specification included in the research material describes basic traceability information as the information needed to link participants effectively. That is a useful design concept, but this article does not treat that document as a binding requirement or establish its applicability to any individual processor.

Record the link whenever material changes state or custody

Most traceability gaps occur at handoffs, not because teams lack labels. Material is received, staged, issued, mixed, repacked, moved to another warehouse or dispatched. At each point, responsibility shifts and a record may be created in a different place by a different team.

Treat a handoff record as an operational control for continuity. It tells the next team what it has accepted and gives an investigator a way to connect records later.

Common handoffs include:

1. Supplier receipt: Receiving confirms what arrived and connects the supplier’s lot reference to the site’s internal receiving or inventory reference.
2. Warehouse issue to production: The warehouse records which specific internal lots left storage, in what quantity or amount, and for which line, order or run.
3. Processing or mixing: Production records the input lots actually used, rather than relying only on the planned formula or pick list.
4. Holding between stages: If material is held, transferred or reclassified, the record should retain the existing identifier and identify the next responsible area.
5. Packing or repacking: The packing team links the production output to the finished-lot identifier applied to cases, containers or pallets.
6. Finished-goods release and transfer: Warehouse records preserve the finished-lot reference as goods move into storage or another site area.
7. Dispatch: The dispatch record connects finished lots to the receiving party and shipment reference.

The record should be made at the event, or under a defined procedure that prevents later reconstruction from memory. Delayed entries increase the risk that a planned movement is mistaken for an actual movement.

A useful handover record answers five questions: what moved, from where, to where, under which identifier, and who accepted responsibility when? Depending on the operation, it may also need quantities, equipment or line identification, status information, and exceptions such as returns or rework.

Treat repacking, splitting and combining as explicit transformations

One-in-one-out lot logic fails when material is divided, merged or placed into new packs. These are not unusual exceptions; they are routine transformation points that need explicit records.

The Produce Traceability Initiative repacking guide discusses repacking and commingling in terms of receiving, shipping, communication and document reconciliation. Its sector-specific terminology should not be treated as universal processing guidance, but its emphasis on reconciling records is directly relevant when product relationships become more complex.

Use a transformation record that retains both directions of the relationship:

• Parent-to-child: Which new lots resulted from one input lot?
• Child-to-parent: Which input lots contributed to one finished lot?

For a split, one incoming lot may become several finished lots. For a blend, several ingredient lots may contribute to one output lot. For repacking, the physical product may not change substantially, but the new pack configuration, destination or handling process can create a new traceability relationship.

Hypothetical example: a split and a blend

This example is illustrative only; it is not an observed processor event.

A receiving team assigns internal material lot RM-47 to an incoming ingredient shipment. Production uses RM-47 in a morning run and creates two packed finished lots, FG-101 and FG-102. The transformation record lists RM-47 as a parent lot for both finished lots.

Later, a second run uses remaining material from RM-47 together with another material lot, RM-52, and creates finished lot FG-103. The production record lists both RM-47 and RM-52 as parent lots for FG-103.

If the team later starts with RM-47, it should identify FG-101, FG-102 and FG-103. If it starts with FG-103, it should identify both RM-47 and RM-52. Neither direction should depend on a person remembering the event.

Where rework, returns or retained material are used, define whether they remain under an existing lot reference or receive a new internal identifier. The choice matters less than documenting the rule and recording each actual connection.

Give each team a handover record they can complete and verify

Traceability often becomes unreliable when a site assigns broad ownership to “quality” or “the system” while the physical handoffs are made by receiving, warehouse, production and dispatch teams. Assign record responsibilities to the people closest to the event, with review or escalation routes for exceptions.

Adapt these roles to the site’s actual workflow. A smaller operation may combine several tasks under one person; a larger site may use separate planning, inventory and quality functions. The point is not to force a particular organisational chart. It is to ensure that no handoff has an undefined record owner.

Before adding complex systems, examine the forms, warehouse transactions and production sheets already in use. A simple record that teams complete consistently is more useful than a detailed template that is completed after the fact or bypassed during busy periods.

Test whether the record chain answers the investigation question

A traceability design should be checked by retrieving records, not by reviewing a flowchart alone. Choose a real closed or historical lot where records can be reviewed without disrupting current operations. This is an internal record-retrieval exercise, not a claim about a legally required testing frequency or recall outcome.

Run two bounded checks:

• Trace back: Start with one finished-lot identifier. Retrieve its packing, production, input, receiving and supplier-link records.
• Trace forward: Start with one incoming material lot. Identify all related production and finished lots, then retrieve the warehouse and dispatch records for those outputs.

Record what the team could find, what was unclear and who had to interpret the data. Useful findings may include an unreadable lot label, a receiving reference that was not copied to production records, a repacking record without parent lots, or a dispatch record that names a product but not the finished lot.

Do not redesign the entire system immediately. First classify the gap: was the traceable unit poorly defined, was an identifier missing, was a transformation not recorded, or was responsibility unclear? Then make the smallest change that closes that specific break.

The practical standard is modest but demanding: a batch should remain connected as it crosses teams, changes state and leaves the site. Stable identifiers, timely handover records and explicit transformation links will not solve every food-safety or supply-chain problem. They can, however, make the affected material and its record history substantially easier for your team to investigate.