How Long Would a Product Recall Actually Take You?

Thursday, 2:12 p.m. A customer calls. Three pallets delivered last week show a bonding defect. He gives you a lot number, 24-0719, and asks one question: is the rest of my order affected?

You open the production binder. July's travellers are in the cabinet in the methods office. The quality manager is on leave. Around 5 p.m., someone works out that lot 24-0719 consumed reel MP-3312. But nobody knows which other manufacturing orders used that reel. Or where those finished lots went.

This is not a discipline problem. It is a structural one: traceability was treated as filing, when it is actually a path.

What does the regulation actually require?

Legal traceability does not ask you to know everything. It asks you to identify, for any given product, your upstream supplier and your downstream customer, and to produce that information quickly when an authority asks. That is the one step back, one step forward principle.

In food, Article 18 of Regulation (EC) No 178/2002 has required it since 2005, and notifying the national authority is mandatory as soon as you have reason to believe a product placed on the market is unsafe; the European RASFF system then relays the alert between Member States. For non-food consumer products, Regulation (EU) 2023/988 on general product safety, applicable since 13 December 2024, requires economic operators to keep the identity of their suppliers and business customers, and structures recalls through the Safety Gate portal. That identification must remain available for ten years after the product was supplied.

So the question is not whether you must be able to walk the chain, but how fast.

Why the binder works, until it doesn't

A paper or spreadsheet system works while the chain is short and people's memory fills the gaps. Six situations break it, and all of them happen eventually:

1. One raw material lot feeds several manufacturing orders. The binder is organised by order, not by material. Going from a reel back to every order that consumed it means re-reading everything.
2. A leftover lot goes back into production three weeks later. Nobody writes it down.
3. The product goes to a subcontractor. The chain stops at the factory gate and restarts on return, with no link between the two.
4. A customer returns goods that are put back into stock. They lose their original lot.
5. Repackaging turns three lots into one. The information from all three is gone.
6. The person who knew has left. The most common cause, and the least documented.

What a real traceability path looks like

A complete path links eight steps without a break: goods receipt with its supplier lot, put-away to a location, reservation, consumption in a manufacturing order, creation of the finished lot, quality check, transfer, then customer delivery. If a single step is entered after the fact or from memory, the chain is not evidence: it is a reconstruction.

That difference matters in front of an auditor. A reconstruction is debatable. A timestamped stock move, attributed to a user and linked to its source document, is not.

How Odoo links those steps

Odoo does not create traceability: it makes it structurally hard to lose, provided capture happens in the right place. In the industrial projects we run at Prism Technology, that means:

• Lot or serial tracking enabled per product. Once set on the product form, no stock move can be validated without a lot.
• The traceability report walks the chain both ways from any lot in one click: which orders consumed it, which finished lots came out, which customers received them.
• FEFO removal strategy for products with expiry dates: the system reserves the lot expiring first, not the one at the front of the rack.
• Barcode app and shop-floor tablet view. The operator scans the lot as it is consumed. They do not copy it out.
• Native subcontracting: the lot keeps existing during the external operation instead of vanishing for three weeks.
• Blocking quality control points on critical operations: the work order cannot move on until the check is done.
• The Odoo chatter keeps who validated what, and when, on every document.

The real breaking point: capture at source

This is what most projects get wrong. An ERP does not manufacture data: it structures it. If the operator writes the lot number on a sticky note at 5 a.m. and an administrator re-keys it at 11, no platform will save the chain.

What actually works on a shop floor comes down to three rules: the lot is scanned rather than typed; the system proposes a default that is right 90 % of the time; and the quality check blocks the next operation instead of flagging it afterwards. Any capture step that slows the operator down will be worked around, and the chain will break exactly there.

How long does a recall take when the chain is complete?

Illustrative example, typical of our client base: an 80-person industrial SME running batch production.

• Without a structured chain: one to three days to scope the recall, with enough uncertainty that you recall wide, which means you recall too much.
• With a complete chain in the ERP: the exact scope, lot by lot and customer by customer, in minutes.
• The economic gap is not the time spent, it is the volume recalled. Recalling 4 lots instead of 40 because you know exactly which ones is where the difference lies.

Frequently asked questions

Lot tracking or serial numbers?

A serial number identifies a single unit; a lot identifies a batch made together. In series production, lots are enough and cost far less in data entry. Serial numbers become necessary for warranted equipment, medical devices, and anything tracked individually after sale.

Does Odoo handle traceability at a subcontractor?

Yes. Subcontracting is a native Odoo MRP flow: components sent and products received stay attached to their lots, and the traceability report crosses the external operation without a break.

Can lot traceability be added to a live Odoo database?

Yes, but enabling it does not back-fill history: it applies to movements from go-live onward. The right moment to switch it on is a stock count close, with clean opening lots.

Take action

Prism Technology is an official Odoo partner in Belgium, based in Walloon Brabant, focused on manufacturing, inventory and supply chain. If you want to know how long a recall would really take you today, the test takes 30 minutes: give us a lot number, and let's walk the chain together.

👉 Book your 30-minute demo — Contact us