Industry · Medical supplies
Recall readiness for medical supply companies in Odoo
A recall tests your data on a deadline. What has to be in place in Odoo before the notice arrives, and a mock recall run step by step on a hypothetical company.
Key takeaways
- Recall readiness is decided at receiving, not on recall day.
- Track lots or serials, with expiry dates, on components as well as finished goods.
- A lot's traceability report shows where it came from and every delivery that shipped it.
- Consigned stock at a hospital is still on hand, so check those locations too.
- Lots, expiry and FEFO run on Community. Quality, Barcode and Documents are Enterprise.
- Odoo supports the records. UDI labels, Part 11 controls and validation take extra work.
When a supplier or a regulator flags a lot, the first question is simple: which customers received it? In many medical supply companies the answer sits in packing slips, spreadsheets and one person's memory, and rebuilding it takes days. Odoo can answer it from one report, but only if every lot was recorded correctly from the day it arrived.
This article covers what to set up in Odoo 17 to 19 before a recall, then walks through a mock recall at a hypothetical company. The company, products and lot numbers are invented. It also marks where Odoo stops, because being ready for a recall and being compliant are not the same thing.
What has to be in place before the notice arrives
Recall readiness is decided at receiving, months before any recall. Six settings do most of the work.
- Tracking on every product that could be recalled. Tracking is set per product: by lot for gauze, gloves and kits, and by serial number for devices tracked one unit at a time. Include the components you assemble into kits, not only what you sell.
- Expiry dates on each lot. With expiration dates turned on, each lot carries an expiration, best-before, removal and alert date, calculated from the product's shelf life at receipt. The first-expiry-first-out (FEFO) removal strategy then reserves the earliest-expiring lot first.
- Lots captured at the dock. Receivers record the lot on every receipt. The Barcode app (Enterprise) reads GS1 barcodes that carry the GTIN, lot, expiry date and serial number, which removes most typing errors.
- A quality step between receiving and stock. Three-step receipts (input, quality, stock) keep uninspected product off the shelf, and control points in the Quality app (Enterprise) set the checks each receipt must pass.
- Component lots on every manufacturing order. If you assemble kits or build devices, each manufacturing order records which component lots went into which finished lot. That link is what lets a component recall reach finished goods.
- A location per hospital for consigned stock. Stock placed at a hospital is still yours. Held in its own internal location, it stays on the books lot by lot.
One habit matters as much as any setting: no side doors. Inventory adjustments, returns, samples and replacements all have to move through lot-tracked operations. One adjustment made without a lot leaves a gap in the chain that no report can fill later.
A mock recall, step by step
Here is the hypothetical. A distributor of single-use supplies also assembles dressing kits in-house. On a Tuesday morning, its gauze supplier writes that gauze lot GZ-4471 failed a sterility test after release. The distributor sells that gauze loose and uses it in its kits. Every name and number below is invented.
Step 1: Open a quality alert and freeze the lot
The quality lead opens a quality alert in the Quality app on the gauze product and lot GZ-4471, with the supplier's notice attached. The alert becomes the file for the whole recall. Without the Quality app, a note and an activity on the lot record do the same job with less structure.
Next, the lot has to stop moving. The pattern that works in Odoo 17 to 19 is a quarantine location that sits outside the stock location deliveries draw from, so nothing in it can be reserved. Move every on-hand quantity of GZ-4471 there, then unreserve any open deliveries or manufacturing orders that had already reserved the lot. A quarantine location inside the main stock location defeats the purpose, because Odoo reserves from child locations too.
Step 2: Trace downstream from the component lot
Open lot GZ-4471 and its traceability report. Upstream, it shows the receipt the lot arrived on and the purchase order behind it. Downstream, it shows every move since: loose gauze shipped on deliveries, and the manufacturing orders that consumed it. In our example, three manufacturing orders used the lot and produced kit lots KIT-2609, KIT-2614 and KIT-2620. Those three kit lots are now part of the recall, and each has its own traceability report to follow.
Step 3: Find everything still in your hands
Before notifying anyone, pull the stock report grouped by location and lot for GZ-4471 and the three kit lots. It shows what is on hand in each warehouse, in quarantine, and in each hospital's consignment location. Consigned kits have not been delivered in Odoo's terms. They sit in your own locations at the customer's site, so they will not appear on a list of deliveries. Add them to the quarantine moves and to the customer list.
Step 4: Build the customer notification list
Moves History, filtered to the four lots and to customer destinations, lists every delivery that shipped them. Export it with the customer, delivery address, delivery reference, date and quantity on each row, then add the consignment sites from step 3. That spreadsheet is your notification list and a record of what you knew and when. Attach it to the quality alert, or file it with the supplier's notice in the Documents app (Enterprise).
Step 5: Notify customers and track each response
The wording of the notice belongs to your quality and regulatory team; Odoo carries it out. Send it from each customer's record so the message is logged there, or from the Email Marketing app for a long list. Schedule a follow-up activity for each customer to confirm they received the notice and to record how much affected stock they still hold. The activity list then shows who has answered and who has not.
Step 6: Bring stock back and settle the accounts
Returns are created against the original deliveries, so each one is linked to the shipment it reverses, and the receiver records the lot as it comes back into quarantine. Credit notes or replacement orders follow from the same records. Consigned stock comes back with an internal transfer. Anything destroyed is scrapped with its lot recorded, so the write-off appears in the accounts and the lot's history shows where every unit ended.
Step 7: Close the alert with root cause and actions
The quality alert records the root cause and the corrective and preventive actions, for example a new control point that checks this supplier's certificate on every receipt. Any report to the FDA or another regulator is written by your quality team; Odoo supplies the quantities, consignees and dates it needs. When the last response is in and the stock is accounted for, the alert closes.
Rehearse it, and time it
A mock recall is only useful if it is timed. Pick a real lot, run steps 2 to 4 on live data, and run the steps that change stock, such as quarantine moves, returns and scrap, in a copy of the database. Write down how long each step took and every time someone had to leave Odoo to find an answer. Those moments are your to-do list.
The usual gaps are lots not recorded at receipt, stock adjustments made without a lot, kits built without component lots, consigned stock kept in a generic location, and customer contacts nobody has checked in years. A named contact for quality notices on each customer account saves time on the day. In our implementation plan, a trial recall on test data happens during migration and training, before go-live, so the first real rehearsal is not the first time anyone opens the traceability report.
Where Odoo stops
Odoo supports the records a medical device quality system relies on. It does not make a company compliant on its own, and it is not validated out of the box. This is what standard Odoo gives you, and what the rest takes.
| Requirement | Standard Odoo | What else it takes |
|---|---|---|
| Lot and serial traceability | Upstream and downstream report per lot | Configuration |
| Expiry dates and FEFO | Expiration, removal and alert dates; FEFO removal | Configuration |
| Quality holds and CAPA | Control points and quality alerts with corrective and preventive actions (Quality, Enterprise) | Enterprise license and configuration |
| GS1 barcode scanning | Reads GTIN, lot, expiry and serial (Barcode, Enterprise) | Enterprise license and configuration |
| UDI labels and GUDID submissions | Product and lot labels, not compliant UDI layouts | Custom label templates, a labeling tool or a partner app |
| 21 CFR Part 11 audit trail and e-signatures | Change history on tracked fields | Customization or partner apps, plus your validation |
| ISO 13485 software validation | Not validated out of the box | Your own validation work |
Traceability, expiry and FEFO are configuration. Label layouts and Part 11 controls are custom Odoo development or partner apps. Validation is work your quality team owns. Each belongs in the scope as its own line, so none of it surprises you after go-live.
Where to start
If your recall process runs on spreadsheets today, start with inventory: lot and expiry tracking, FEFO, three-step receipts and a quarantine location. That alone turns a recall search into a report. Quality, Barcode and Documents can follow, along with any label and validation work. We use AI across configuration, development and testing to shorten delivery. Custom label work, many consignment locations or your own validation testing can take longer, and your proposal states the date and one fixed price before kickoff.
We have not published a medical-supplies case study yet. The closest is a custom-parts manufacturer running Inventory, Quality and Barcode on one Odoo database, linked below. Our Odoo for medical supplies page shows the full build, from contract pricelists to consignment locations.
Frequently asked questions
How do you run a mock recall in Odoo?
Pick a real lot and open its traceability report. Follow it downstream to every finished lot and delivery, check on-hand stock by location including consignment sites, and export the customer list from Moves History. Run the steps that change stock, such as quarantine moves and returns, in a copy of the database, and time each step.
Can Odoo stop a recalled lot from being shipped?
Yes, by moving it out of reach. The pattern that works in Odoo 17 to 19 is a quarantine location outside the stock location that deliveries draw from. Move the lot's stock there and unreserve any open deliveries or manufacturing orders that had reserved it. Some companies add a small customization that keeps a flagged lot from being reserved at all.
Which Odoo apps does recall traceability need?
Inventory covers lot and serial tracking, expiry dates, first-expiry-first-out picking and the traceability report, and it runs on Community. Manufacturing records component lots if you assemble kits or build devices. Quality, Barcode and Documents are Enterprise apps.
Is Odoo compliant with FDA 21 CFR Part 11 or ISO 13485?
No software makes a company compliant on its own, and Odoo is not validated out of the box. It supports parts of a quality system: control points, quality alerts with corrective and preventive actions, lot traceability and change history on tracked fields. A Part 11 audit trail, electronic signature controls and software validation need customization, partner apps and your own validation work.
How fast could you trace a lot today?
A scoping conversation about your lot rules, quality gates and consignment sites.
Book a discovery callKeep going
Related industries, services and reading
From 3-day planning cycles to same-day scheduling
A custom-parts manufacturer with 85 staff moved 340 BOMs, 12 work centers and its planning into Odoo MRP in 14 weeks, with Inventory, Quality and Barcode on the same database.
Every lot, from receipt to recall
Lot and serial tracing, FEFO picking, quality holds, contract pricelists and consignment stock in Odoo.
Odoo for medical suppliesLabels, EDI and the gaps
Upgrade-safe custom modules and integrations for what standard Odoo leaves out, such as label formats.
Odoo customization and integration IndustryOdoo MRP for manufacturing: a 2026 practical guide
BOMs, work centers, shop floor, quality and subcontracting in Odoo, and which edition you need.
ImplementationThe 12-point pre-go-live checklist we run on every Odoo project
Migration dry-runs, real-workflow testing, rollback plans and backups, signed off before go-live.
Find out how recall-ready your data is
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751