Food Traceability Software in the UK: Batch Tracking, Quality Checks and Recall Readiness
How UK food manufacturers can build traceability software: one step back, one step forward, batch genealogy, quality checks, allergens and recall readiness.
What should food traceability software do?
Food traceability software should record every lot of raw material and packaging received (supplier, lot, quantity, dates), every production batch and what it consumed, quality checks and outcomes at each step, finished goods lots and which customers received them, so you can trace from any lot backwards to suppliers and forwards to customers in minutes. It should also link recipes and specifications to allergens and labels, and support withdrawals and recalls with ready lists, contacts and records. UK law sets a minimum of one step back and one step forward; customers and certification schemes usually expect internal batch genealogy as well.
This guide is for operations, technical and quality managers at UK food manufacturers and processors. It is general information as at October 2026, not legal or food safety advice.
Key takeaways
- Capture lot numbers at receipt, consumption, production and dispatch.
- Record quality checks against batches, not on separate paper.
- Link recipes and ingredient specs to allergens and labels.
- Run mock recalls from the system and time them.
- Keep customer and authority contact lists ready.
- Design capture to be quick on the floor, or it will be skipped.
What UK rules require
In Great Britain, the traceability requirement comes from Regulation (EC) No 178/2002, which is now assimilated law: food businesses must be able to identify the businesses that supplied them and the businesses they supplied. GOV.UK guidance says: ‘you need to be able to identify your suppliers and food business customers’, and that you must immediately withdraw or recall food you believe is unsafe or fails legal requirements (GOV.UK: food incidents, withdrawals and recalls).
Northern Ireland follows different arrangements under the Windsor Framework for some food law, and Scotland's regulator is Food Standards Scotland. Confirm which rules and contacts apply to each site.
Traceability levels
| Level | What it links | Who expects it |
|---|---|---|
| One step back, one step forward | Supplier and delivery to receipt; dispatch to business customer | Legal minimum for most food businesses |
| Internal batch genealogy | Which raw material lots went into which production batches and finished goods lots | Customers, certification schemes and effective recalls |
| Process traceability | Line, shift, equipment, operators and checks per batch | Root cause analysis and quality improvement |
| Mass balance | Quantities in versus out per lot, including waste and rework | Mock recalls and audits |
Data model
| Entity | Key fields |
|---|---|
| Supplier and specification | Approval status, ingredient specs, allergens, certificates |
| Goods-in lot | Supplier lot, quantity, dates, temperature, inspection result |
| Recipe | Version, ingredients, allergens, label link |
| Production batch | Recipe version, line, start and end, lots consumed and quantities |
| Quality check | CCP or check type, limit, result, who, when, corrective action |
| Finished goods lot | Batch, pack date, best-before or use-by, quantity |
| Dispatch | Customer, delivery, lots and quantities |
| Rework and waste | Source lots, destination batch or disposal |
Capturing data on the floor
Most traceability gaps start on the production floor: lots not scanned, rework not recorded, checks filled in at the end of a shift. Make capture part of the work, not extra admin.
- Barcode or QR labels on every incoming lot and intermediate container.
- Scan lots at the line to consume them into a batch; block unapproved or expired lots.
- Tablet forms for checks such as temperatures, metal detection and label verification, with limits enforced.
- Record rework explicitly so genealogy stays intact.
- Work offline and sync when connectivity drops; see offline-first mobile apps.
- Integrate scales and printers where weights and labels come from equipment.
Allergens and labels
Recipe changes and ingredient substitutions are a common cause of allergen recalls. Link each recipe version to ingredient specifications and the label artwork, flag any change that affects allergens, and require approval before production uses a new version. For prepacked for direct sale (PPDS) food, labels have had to show the name of the food and a full ingredients list with the 14 regulated allergens emphasised since 1 October 2021 across all four UK nations (FSA: PPDS). PPDS covers food packed where it is sold before it is ordered; food you supply to other businesses for resale is labelled under the ordinary prepacked rules.
Recall readiness
When something goes wrong, the system should produce the affected lots, quantities, locations and customers in minutes, with contact details and records of what was notified and when. The FSA provides templates for enforcement authority and business-to-business notifications, allergy alerts and point-of-sale notices, and advises a root cause analysis afterwards.
- Backward and forward trace from any lot, with mass balance.
- Customer contact list and notification log.
- Templates mapped to the FSA's formats.
- Hold and block affected stock across sites.
- Mock recalls on a schedule, timed and reviewed.
Hypothetical example: a sauce manufacturer
This example is hypothetical. A UK sauce manufacturer supplying retailers and food service traced batches through paper production records and took most of a day to complete a mock recall. It labelled incoming lots with barcodes, added tablet stations at mixing and filling to consume lots and record checks, linked recipe versions to allergen data, and generated dispatch records from its order system. The next mock recall took under an hour, and a supplier's undeclared allergen notice was traced to four finished goods lots and two customers.
Common mistakes
- Tracing only to the supplier and customer, not internally.
- Rework and reused materials left out of records.
- Quality checks on paper, separate from batch records.
- Recipe changes without allergen review.
- Never testing a recall end to end.
Sources
GOV.UK: food incidents, product withdrawals and recalls (updated 20 August 2026); FSA: prepacked for direct sale allergen labelling.
Accessed 10 October 2026. Food law differs between Great Britain and Northern Ireland and Scotland has its own regulator; nothing here is legal or food safety advice.
Conclusion
Good traceability is mostly disciplined data capture: lots scanned in, consumed, produced and shipped, checks recorded against batches, and recipes linked to allergens. Meet the legal one-up, one-down minimum, build internal genealogy for real recalls, and test it regularly. For quality workflows, see quality management software, and for connecting production systems, manufacturing software integration.
Still tracing batches through paper records?
ZSpace Labs is a remote-first technology studio that works with clients globally on production and traceability systems and shop-floor tablet apps. We have no UK office and work alongside your technical and food safety teams. If it would help to plan traceability capture and recall reporting, we are happy to talk it through.
Common questions.
Food businesses must be able to identify their suppliers and their food business customers, often called one step back and one step forward, under assimilated Regulation (EC) No 178/2002 in Great Britain. Businesses selling only to final consumers do not need customer traceability. Many customers and certification schemes expect more detailed internal batch traceability.