Traceability System

What is a Food Traceability System?

A food traceability system is the combination of processes, records, and tools that allow a food business to track food and its ingredients through every step of the supply chain — from the source of raw materials to the end consumer. The core principle is one-step-back and one-step-forward: at any point in the chain, a business should be able to identify where its inputs came from and where its outputs went.

In Australia, FSANZ Standard 3.2.2 requires all food businesses to maintain records that enable this traceability. The Food Industry Recall Protocol administered by FSANZ relies on effective traceability systems to enable targeted, efficient recalls.

One-Step-Back, One-Step-Forward

The international standard for food traceability — adopted by Codex Alimentarius and reflected in Standard 3.2.2 — is based on the principle that every business in the food chain needs to know its immediate supplier (one step back) and its immediate customer (one step forward). This creates a linked chain: each business holds one segment of it.

In practice, this means:

One step back: For every ingredient or raw material you receive, you must be able to identify the supplier and the lot or batch number of the delivery.

One step forward: For every batch of finished product you despatch, you must be able to identify the customer and the product identification (batch code) of what was sent.

When a recall is triggered anywhere in the chain, each business can identify the affected product within its own scope and pass the information one step in each direction.

What Records a Traceability System Must Maintain

A functional food traceability system should capture, at minimum:

• Incoming deliveries: Supplier name, ingredient name, lot/batch number, quantity received, date received.
• Production records: Batch code, date of production, ingredients used (with lot numbers), quantities, yield, and operator.
• Outgoing deliveries: Customer name, product name, batch code, quantity, date despatched, delivery docket or invoice number.

These records must be retained for a period appropriate to the shelf life of the product and the recall risk. Standard 3.2.2 does not specify a minimum retention period, but two years is commonly used as a benchmark for shelf-stable products.

Internal Traceability vs Supply Chain Traceability

Internal traceability covers what happens within your own facility — the link between incoming raw materials and outgoing finished products. This is what you directly control.

Supply chain traceability depends on the traceability practices of your suppliers and customers. Even if your internal traceability is perfect, a recall triggered by a supplier's lot number requires that supplier to also have records linking that lot to your delivery. Working only with suppliers who maintain documented lot traceability reduces your exposure when a recall occurs upstream.

Common Mistakes

Paper records that cannot be searched. A folder of handwritten production records that must be read page by page to find a specific lot number does not support a rapid recall response. Effective traceability requires records that can be searched, filtered, and queried — digitally where possible.

Missing the link between supplier lot and internal batch. Many businesses record their own batch codes but fail to record the supplier lot numbers of the ingredients used. When a supplier issues a recall, they can only identify which businesses purchased their lot — the businesses themselves must do the product-level mapping.

Gaps in outgoing despatch records. Traceability is only as strong as its weakest link. If you have perfect incoming and production records but incomplete customer despatch records, you cannot complete the recall response — you know what was made but not where it went.

How Batchbase Implements Food Traceability

Batchbase is built around the batch record as the central traceability document. Every production run in Batchbase records:

• All ingredients used, with their quantities and supplier lot numbers
• The production date and operator
• The finished batch code and expected yield

This creates a complete internal traceability record for every batch. In the event of a supplier recall or a customer complaint, you can search Batchbase by ingredient lot number to identify every finished product batch that used that lot — within seconds, not hours.

Related Standards and References

• FSANZ Standard 3.2.2 — Food safety practices — traceability requirements
• FSANZ Standard 3.2.1 — Food safety programs (batch documentation)
• FSANZ Food Industry Recall Protocol — foodstandards.gov.au/industry-and-trade/food-recall
• Codex Alimentarius General Principles of Food Hygiene (CAC/RCP 1-1969)
• FSANZ food standards code