Food Traceability: How to Track Ingredients From Supplier to Finished Product

Why traceability matters more than it seems

Traceability feels like box-ticking until the day you need it. Then it becomes the single most important thing in your business. If a supplier issues an ingredient recall, or a customer reports a problem, or an allergen ends up somewhere it shouldn't, traceability is what lets you identify exactly which batches are affected, contain the problem, and prove you've contained it.

Get it right and a potential crisis becomes a quick, controlled action. Get it wrong and you're recalling everything, guessing, and watching the cost and the reputational damage spiral. Here's how to build traceability that actually works when you need it.

What the law requires

In the UK, traceability is a legal requirement under retained EU food law (Article 18 of Regulation (EC) 178/2002). The core principle is "one step back, one step forward."

In plain terms, that means you must be able to identify:

1. One step back: who supplied you with each ingredient or material, so you can trace any input back to its source.
2. One step forward: who you supplied your finished products to, so you can trace any product forward to where it went.

There's an important exception: if you sell directly to the final consumer, you don't need to keep detailed records of individual customers. A producer selling at a farmers' market doesn't need every shopper's name. But you still need full records of who supplied your ingredients.

The FSA's guidance distinguishes between legal requirements and best practice. The one-step-back, one-step-forward records are the legal minimum. Internal traceability, linking your inputs to specific finished batches, is best practice and is what genuinely protects you in a recall.

The piece the law doesn't force, but you need anyway

The legal minimum connects your suppliers and your customers, but it doesn't require you to link the two through your own process. That internal link, knowing which ingredient batches went into which finished product batches, is what turns a recall from "withdraw everything" into "withdraw exactly these three batches."

Imagine a supplier tells you a batch of an ingredient is contaminated. With only the legal minimum, you know you bought it, but not which of your products it ended up in, so you may have to withdraw far more than necessary. With proper internal traceability, you identify the precise finished batches that used it and recall only those. The difference is enormous, in cost, in waste, and in how the incident looks to a buyer.

This is why every serious certification standard, including SALSA and BRCGS, expects internal traceability, not just the legal minimum.

How to build a traceability system

Effective traceability comes down to consistent batch identification and good records at every handover point. The building blocks are:

1. Batch or lot codes on everything. Every batch you produce gets a unique identifier. Every ingredient batch you receive is recorded against its supplier and their batch code.
2. Goods-in records that capture supplier, product, quantity, batch code, and date for each delivery.
3. Production records that link the ingredient batches used to the finished batch produced. This is the internal link.
4. Despatch records that capture which finished batches went to which customers and when.
5. A clear coding system so batch codes are meaningful and consistent, not improvised each time.

Done well, you can pick any finished batch and follow the thread in both directions: back to every ingredient and supplier, forward to every customer.

Test it with a mock recall

A traceability system you've never tested is a system you don't actually know works. Run a mock recall at least once a year:

• Pick a finished product batch at random.
• Trace it back to every raw material and supplier.
• Trace it forward to every customer it was sold to.
• Time the whole exercise and document it.

Auditors specifically look for evidence of a tested recall procedure, and a mock recall is also the best way to find the gaps in your own system before a real incident does. If the exercise takes you a day and involves digging through folders, that's exactly what you need to know now rather than in a genuine recall.

Where paper struggles

Paper traceability can meet the legal requirement, but it shows its limits under pressure. Tracing a batch by hand means cross-referencing goods-in sheets, production logs, and despatch records across different folders, and the more batches and ingredients you handle, the slower and more error-prone it gets. In a real recall, speed matters, and so does being certain you haven't missed anything.

A digital system holds the links rather than asking you to reconstruct them. FoodSafe's traceability works alongside its supplier register so that goods-in, production, and despatch are connected, letting you trace a batch in both directions quickly rather than rebuilding the chain by hand. When a buyer or the FSA asks you to demonstrate traceability, you can show it on the spot instead of promising to get back to them.

The habits that make it work

Traceability isn't a system you install once; it's a discipline you maintain every day. The producers who can trace instantly are the ones who record batch codes at goods-in without fail, link ingredients to finished batches as they produce, and capture despatch details every time something leaves. None of it is difficult. It just has to be consistent, because the one delivery you didn't record is the one the recall will hinge on.

Build the habit, test it annually, and traceability stops being a worry and becomes one of the quiet strengths of your business.

For how traceability fits into the wider picture of approving and managing your suppliers, see our guide to supplier approval and management.

Food safety compliance, handled.