Food batch traceability: connect deliveries, ingredients and finished products

Food traceability: supplier, internal and destination records

Food traceability follows the identity and movement of food through defined stages. Supplier traceability tells you where a received lot came from. Internal traceability connects that lot with storage, transformations and finished output. Destination records explain where each output went. A useful system connects these views; a folder of delivery notes alone does not describe the ingredient links created during production.

GS1 separates tracking events from the data describing them. Receiving, transforming and shipping are examples of events; product identity, place, time and related document references describe their instances. Use that distinction to decide where the team must capture information. A barcode can help retrieve an identity, but does not create the missing event records.

GS1 · Global Traceability Standard

Map the hand-offs before choosing software

Draw the path from delivery to storage, production, packing and dispatch or service. Mark where identifiers change. An internal batch code should connect to the original supplier lot; replacing the supplier code without a link loses useful context.

GS1's traceability framework distinguishes tracking events from the data describing them. Our example applies that distinction to a small production workflow.

Build a batch record with explicit links

Use a product name and a lot identifier together. Record a unit next to every quantity and separate actual amounts from estimates. If rework or repacking is used, capture the input-to-output link rather than silently starting a new history.

• Delivery: supplier, product, supplier lot, receipt date and quantity.
• Production: internal batch, ingredient lots and quantities used.
• Output: product, quantity, production date and storage location.
• Movement: dispatch or transfer reference and receiving business where relevant.
• Exceptions: holds, waste, adjustments and the person authorising a change.

Turn a traceability exercise into a buying test

Give each shortlisted system the same sample records. Ask it to show forward and backward links, export the evidence and preserve corrections. Check whether staff can distinguish a practice exercise from a real incident.

Record your own retrieval time as a baseline. Do not assume a universal recall deadline, retention period or legal duty from this guide. Confirm the applicable rules for your jurisdiction, products and trading arrangements.

Resolve missing links before calling the exercise complete

If the supplier lot is unreadable, retain the available delivery evidence, follow the hold procedure and obtain reliable identification. Do not invent an identifier to complete a field. If 2 kg remains unexplained, investigate losses, transfers, returns, missing entries and unit conversions; preserve the original entry with the reason, date and author of each correction.

Use the batch sheet, stock movement register and mock recall worksheet together. Ask a colleague who did not enter the records to repeat the search, record every missing link, assign an owner and review date, then verify the corrections with another search. Keep the exercise clearly labelled so its records cannot be mistaken for a live incident.

Build a retrieval pack, not a folder of unrelated files

For one selected batch, assemble its receipt references, ingredient-use links, actual output, stock movements, destinations and correction history. Name the files or records with stable identifiers and keep their relationship visible in the export. If a batch is split across locations, include both locations. If a product is repacked, retain the original identity alongside the replacement label and its decision basis.

Use one line per actual input/output link and one line per movement. Distinguish a transfer within the business from dispatch to another business. Record losses and samples with their own reasons so the remaining quantity can be explained. When quantities use different units, retain the documented conversion rather than silently making the numbers match.

What this worksheet does—and what requires a separate review

The worksheet tests operational links; it is not a jurisdiction-specific compliance checklist. Before relying on it, identify the products, countries, business activities and customer requirements that apply. Record the approved retention rule, export requirements and responsible contact in your own procedure.

For example, the FDA Food Traceability Rule concerns additional records for certain foods and activities, with scope and exemptions that must be checked separately. Do not infer that a general lot sheet establishes compliance with that rule. Consult the FDA source for the current requirements and timing, particularly when products enter the United States.

FDA · Food Traceability Rule: scope and current requirements

Evaluate traceability software using your difficult cases

Run the same test data through paper records, a spreadsheet and shortlisted software. Include two input lots in one output, one input shared by two outputs, a split delivery and a stock adjustment that remains under investigation. Ask another colleague to trace both directions and export the evidence without changing permissions midway through the test.

Compare completeness before speed. Record which links were recovered, which remained unknown and whether corrections can be reconstructed. A fast search returning only the first matching batch is less useful than a complete search with explicit gaps. Choose a tool only after confirming that the people responsible for receiving, production and dispatch can keep those links current.