✦ Sector
Food traceability software: what your system has to record
Food traceability software has to link every batch you produce to the ingredient lots that went into it and the customers it was shipped to, and it has to prove that link in a mock recall - not just store the data somewhere.
Haystak · 11 August 2026 · Updated 11 August 2026 · 8 min read
Food traceability software records where every ingredient lot came from, which batches it went into, and where those batches were shipped - commonly described as one-step-back, one-step-forward. UK food law requires businesses to be able to identify their immediate supplier and immediate customer for any product, and to produce that information without delay if asked.
The system that matters isn't the one with the nicest dashboard. It's the one that survives a mock recall: can you find every affected batch, everywhere it went, within the time your customers and the [Food Standards Agency](https://www.food.gov.uk/business-guidance/food-allergy-and-intolerance) would expect.
One-step-back, one-step-forward, done properly
The regulatory minimum is knowing your immediate supplier and immediate customer for each product. In practice, that's not enough to run an effective recall on its own - you also need to know which specific batches of raw material went into which specific batches of finished product, and which customer orders those batches were shipped against.
| Link | What it must answer | Where it usually breaks |
|---|---|---|
| Supplier to goods-in | Which supplier lot arrived on which delivery | Supplier labels not matched to internal lot codes |
| Goods-in to production batch | Which raw material lots went into this batch | Manual batch sheets, written after the fact |
| Production batch to finished goods | Which finished lot codes came from this run | Repacking or blending loses the original lot reference |
| Finished goods to customer | Which customers received which batches | Despatch records not linked to lot numbers |
What good traceability software actually records
A traceability system worth the name captures batch genealogy at every stage above, automatically where possible rather than as a separate paperwork exercise that happens after production. If it's a bolt-on to your existing system rather than integrated with production and despatch, it will drift out of date exactly when you need it most.
- Ingredient lot receipt - supplier, lot number, quantity, and date, linked to the goods-in record.
- Production batch record - which lots and quantities of each ingredient went into which output batch.
- Allergen data at batch level - not just per product, because ingredient substitutions and shared-line contamination risk vary batch to batch.
- Shelf life and use-by tracking - calculated from production date and ingredient shelf life, not entered by hand each time.
- Despatch record - customer, batch, quantity and date for every shipment out.
This overlaps closely with quality management, which we cover in our broader look at the types of manufacturing software a food producer typically needs - traceability and quality usually should share the same batch record rather than keeping two.
Allergens need batch-level accuracy
Allergen information has to reflect what's actually in a specific batch, including any last-minute ingredient substitution or shared-equipment cross-contamination risk. A system that only stores allergens at the product level, based on a standard recipe, will miss the cases that matter - the batch that ran differently to plan.
Guidance from the Food Standards Agency on allergen labelling and Natasha's Law sets out what has to reach the consumer; your internal system needs to hold enough batch-level detail to generate that information correctly every time, not just for the standard recipe.
Shelf life tracking
Shelf life should be calculated from the production date and the shortest shelf life of any ingredient used, not entered manually per batch. Manual entry is where use-by dates quietly become wrong - either too conservative, wasting stock, or too generous, which is the more serious failure.
- 01Hold shelf life data against each raw material, kept current as suppliers change.
- 02Calculate finished product shelf life automatically from the shortest constraining ingredient.
- 03Flag exceptions - new ingredients, new suppliers - for manual review rather than defaulting silently.
Buy or build - where the line sits
Established traceability products handle standard batch genealogy well and are the sensible starting point for most food producers. Where they fall short is usually complex multi-ingredient blending, co-packing arrangements, or traceability that needs to integrate tightly with a bespoke production process - situations covered in our broader manufacturing software work.
If your current system can't answer a mock recall question in minutes, or your production process doesn't map cleanly onto an off-the-shelf batch model, get in touch and we'll look honestly at whether the fix is process, configuration, or a bespoke system.
✦ Where this fits
More on this from us: our work in manufacturing software.