Traceability
Digital traceability does not reduce the number of recalls. It decides whether you withdraw two production runs or a fortnight of output.
Digital traceability does not reduce the number of recalls you have. It changes how wide they are and how fast you can run them, and those two things are where the money is.
A business that can show which production runs used an affected ingredient lot withdraws those runs. A business that cannot withdraws everything from that window. Same incident, very different invoice.
People use these interchangeably and they mean different things under Article 19 of Regulation (EC) 178/2002.
The obligation is triggered the same way. If you have reason to believe a food you placed on the market is unsafe, you must withdraw it and inform the competent authority. In Ireland that is the FSAI, in the UK the FSA or Food Standards Scotland. If the product has already reached consumers, you recall it and inform the public.
The speed of your traceability determines which of the two you end up running. Product caught in your own warehouse is a withdrawal. The same product caught three days later is a recall.
In 2024 peanut contamination was found in mustard powder. Because mustard is an ingredient rather than a finished product, the contamination did not stay with one manufacturer. Traced through the supply chain, it affected 59 brands and 307 products.
This is the scenario every traceability system is really built for. A business buying that mustard powder had one question to answer: which of our production runs used the affected lot, and where did those runs go?
Businesses with batch links made at production answered it in minutes and withdrew specific products. Businesses without them had to work it out from delivery dockets and production diaries, while their customers waited.
Not through negligence. Through the shape of the records.
See food traceability software for how the chain is captured, or the guide to Article 18 for the legal baseline. Greenaway Foods describe tracing backwards and forwards becoming a single process.
Run a mock recall twice a year and time it. Pick a batch at random, identify the affected product, quantify it, list the customers, and produce the records. Scheme audits run a timed version of exactly this exercise.
The gaps a mock recall finds are cheap to fix in advance and expensive to find during a real one. A timed traceability exercise is also part of a BRCGS audit, and the underlying controls come from your critical control points.
Undeclared allergens, by a clear margin in the UK and Ireland. Around 23% of UK recall events in 2024 were allergen related, ahead of Listeria in second place. Most allergen recalls are labelling and records failures rather than hygiene failures.
A withdrawal removes product from the supply chain before it reaches consumers. A recall retrieves product that consumers already have, and requires public notification. How fast you can trace often determines which one you are running.
Immediately. Article 19 of Regulation 178/2002 requires you to withdraw unsafe product and inform the competent authority without delay once you have reason to believe it is unsafe. There is no grace period while you work out the scope.
The FSAI in Ireland, and the FSA or Food Standards Scotland in the UK, alongside your own customers and suppliers. Where a risk crosses borders, RASFF notifies other member states.
By making the links during production rather than reconstructing them afterwards. That converts a trace from an afternoon of cross referencing into a single search, and it narrows the scope of the withdrawal to the batches actually affected.
Yes. A mock recall twice a year, timed, tells you more about your readiness than any procedure document. It is also part of what scheme auditors assess.
Digital HACCP records, filtered and exported in under a minute. Live the same day on a sector template.
Start free trial →WhatsApp us