A newly printed batch code should not make the earlier product history disappear. When a food batch is repacked, reworked, relabelled or otherwise handled internally, the operating record needs to answer a simple question: what entered this event, what happened, and which batches resulted?
For production, warehouse and quality teams, the objective is not to force every activity into one batch-code format. It is to preserve a readable relationship between source lots, the controlled activity and the output lots. A team should be able to start with an output identifier and work backward to the source material. It should also be able to start with a source lot and identify every output lot that may be connected to it.
This matters during routine stock review, customer enquiries, internal investigations and withdrawal or recall exercises. It also matters at shift handover: a new label may identify the present package, but it does not by itself explain the material’s origin or handling history.
Start with the traceability question the record must answer
The central traceability question is broader than “what code is on the pack?” A useful record should allow the team to establish:
- which original lots or internal batches entered the activity;
- what controlled activity took place;
- when and where the activity took place, where those details matter to the site process;
- which new or continuing identifiers were applied; and
- where the resulting product went next, including storage, further production or dispatch.
The Institute of Food Science & Technology traceability guidance describes the need to trace materials backward and forward through production, processing and distribution, including reworked or semi-processed products. Its practical implication is that incoming, production and dispatch records should connect rather than sit as isolated documents.
A new production code can be part of that connection. The Institute of Food Technologists guidance on food traceability discusses recording a newly assigned production code against a receiving or prior code. This does not establish one mandatory identifier format for every food operation. Instead, it supports a more useful operating principle: when an identifier changes, keep the old and new identities linked in the record.
For example, a warehouse may divide one original lot into smaller retail-ready units. A production area may return approved material into a later process. A packaging team may correct an approved label application. These activities may involve different controls, but each needs an intelligible account of the relationship between the material before and after the event.
Classify the event before assigning or changing an identifier
Before completing the record, describe the event in terms that make sense within the site’s approved process. A vague entry such as “repacked” can conceal a material transformation, a packaging-only change or an administrative correction.
A working classification might distinguish between:
| Event type | Record question to resolve | Why the distinction helps |
|---|---|---|
| Repacking | Was the product placed into different packaging or presentation units? | Makes the package and label relationship visible. |
| Rework | Was previously produced material returned to, combined with or used in another controlled process? | Makes the source material and resulting production relationship visible. |
| Relabelling correction | Was the product unchanged while a label or label application was corrected? | Separates label-control evidence from production evidence. |
| Other internal handling | What approved activity occurred and what identification changed? | Avoids forcing unusual events into an unclear category. |
The Kivloo guide on repacking lot mapping makes a useful practical distinction between package changes, production transformations and administrative label corrections. Its value is not that it creates a universal classification system; it is that it prompts the team to state what actually happened.
Your operation’s own procedures should define which activities are permitted, which approvals are needed and whether any additional controls apply. Those decisions can depend on product type, packaging format, storage conditions, shelf-life management, allergen arrangements and applicable local requirements. Global traceability guidance is not a substitute for Chinese law, Chinese standards, customer specifications or validated site instructions.
Create one transformation record that links inputs to outputs
The most usable approach is often one event-level transformation record. Whether it is paper-based, spreadsheet-based or held in an ERP or warehouse system, it should bring the important links together rather than require a reviewer to infer them from separate documents.
The format can vary. The fields should fit the activity and existing document controls. In many operations, the following fields provide a workable minimum structure:
| Record field | What it should make clear |
|---|---|
| Event identifier | The unique reference for this repacking or rework activity. |
| Event type | Whether the activity was repacking, rework, relabelling correction or another approved process. |
| Date and time, where applicable | When the activity occurred and the relevant production window. |
| Area, line or location | Where the activity took place if this is relevant to site traceability. |
| Responsible role or operator | Who completed the activity record. |
| Source lot identifiers | Every supplier, internal or intermediate lot used. |
| Input quantities and units | How much material from each source lot entered the event. |
| Output lot identifiers | Each resulting batch, package lot or other controlled output identity. |
| Output quantities and units | The amount assigned to each output lot. |
| Loss, retained material or remainder | What did not become output and how it was accounted for. |
| Packaging or label reference | The applicable packaging, artwork, label version or controlled reference, if used by the site. |
| Review or exception record | Any required verification, discrepancy, hold or quality decision. |
The IFT guidance refers to record systems that can track codes, quantities, ingredient use, production time and production line information, alongside reconciliation with batch-sheet information. The practical lesson is not that every event needs every field. It is that the record must contain enough context for a reviewer to understand the material relationship without relying on memory.
Kivloo’s repacking and rework record template offers a fictional worked example including input lots, output lots, quantities, losses or remainder, label references and reviewer information. It can be a useful prompt for designing a local form. It should not be treated as a required standard or evidence that a particular form will suit every product and process.
When several source lots contribute to one output lot, list each source separately. When one source lot becomes several outputs, list every output separately. Avoid recording only a general statement such as “from warehouse stock” or “from previous batch.” Such entries can be understandable at the time but difficult to reconstruct later.
Keep the material balance and status visible
A traceability link is easier to trust when the quantities are reviewable. The record should make a reasonable material balance visible according to the operation’s own units and reconciliation rules.
A simple working relationship is:
total input = total output + retained material + samples + waste or loss
This is a review tool, not a universal acceptance formula. Packaging counts, weight variation, moisture changes, partial units and process-specific measurement conventions may affect how a site reconciles an event. The relevant tolerance, measurement basis and escalation point should come from the site’s own procedures.
Record the disposition of material that did not become output. For instance, the record may need to show whether material was retained for a defined future use, kept as a sample, placed under a hold status, returned to controlled storage or disposed of. A blank quantity difference should not be left for the next shift to interpret.
The IFT guidance distinguishes between soft and hard hold concepts in a traceability context. A site should use its own defined language and controls for holds, release and movement restrictions. Do not assume that a generic hold label has the same meaning across facilities. What matters is that the status is visible, controlled and connected to the relevant lot or event record.
A useful review question is: if the output quantity is lower than the input quantity, can the record show where the difference went? If the answer is no, the event genealogy may be incomplete even when the batch codes were recorded correctly.
Make the genealogy usable in both directions
Traceability is not complete because records exist somewhere. The links must be retrievable in both directions within the time and method set by the operation.
Run a desk-check using an actual completed event record. It does not need to be presented as a field trial; it is a document-retrieval exercise.
Trace backward from an output lot
Start with a finished output identifier and retrieve:
- the repacking or rework event record;
- all source lot identifiers used in that event;
- the associated quantities and material status, where relevant;
- the packaging or label reference used; and
- the earlier goods-in, production or intermediate-batch records needed to continue the history.
Trace forward from a source lot
Then start with one source lot and identify:
- every rework or repacking event in which it was used;
- every output lot created from that event;
- any remaining, retained, sampled or disposed quantity recorded; and
- the subsequent storage, production or dispatch records that apply to those outputs.
The IFST guidance notes that a site process-flow diagram can help illustrate how traceability works across the operation. A simple map can identify where goods-in records, warehouse movements, batch sheets, packaging records and dispatch documents connect. This is often more useful than asking each department to explain the entire system verbally.
A spreadsheet can support food batch rework traceability if it is controlled, current and searchable, and if it preserves the input-to-output relationship. A paper record can also work if it is legible, complete and retrievable. An ERP or warehouse platform may make retrieval faster, but digital storage alone does not create genealogy. The decisive issue is whether the links, revisions and access controls remain reliable in the operation’s normal workflow.
Set ownership, review points and a bounded next step
Traceability records usually fail at handover points: material is moved before its status is clear, labels are applied before the reference is recorded, or quantity differences are noticed without being resolved. Clear ownership makes these gaps easier to detect.
A practical division of responsibilities may look like this:
- Operator or assigned production role: completes the event details, identifies actual source and output lots, and records quantities at the time of activity.
- Production or warehouse role: verifies physical quantities, packaging or label references and the movement of material into the next controlled location.
- Quality role: reviews exceptions, holds, discrepancies and release decisions according to approved site procedures.
- Record owner or supervisor: ensures the completed record is filed or entered into the designated system and remains retrievable.
These are example responsibilities, not a replacement for your site’s authority matrix. Local procedures and applicable requirements should determine approval authority, review frequency, retention periods and escalation rules.
As a bounded next step, select one real rework or repacking pathway in your operation. Map the flow from source lot through the event to the resulting output lots. Then ask two people who were not involved in the event to trace it in opposite directions using only the available records. If either person has to rely on memory, informal messages or assumptions about a newly printed code, improve the record link at that point.
The goal is not a perfect universal template. It is a controlled, understandable chain that survives a label change, a shift change and a later review.
Source and further reading
ACA’s practical examples and working checklists are independent editorial analysis. The linked source provides the underlying reference; it does not endorse this article.



