Medical Device Manufacturing
Odoo ERP for Medical Device Manufacturers
UDI, device history records and ISO 13485 traceability in Odoo
Book a free 30-min auditWhy generic ERP fails an ISO 13485 audit
For any unit that reaches the field, a device manufacturer must be able to prove which design revision it was built to, which components went into it, who inspected it, and what happened once a customer complained. A generic ERP only records the sale and the stock move; design control, complaint handling and CAPA get pushed into a separate quality system, and nobody reconciles the two. That gap surfaces at surveillance audit, the moment the device history record stops matching the shipping record. Wire PLM, Quality and serial tracking together from the start, though, and Odoo can carry the whole chain.
Can you produce a device history record on demand?
Say a notified body or a customer requests the complete build history for a single serial number. The BOM sits in the ERP, inspection results are filed away in a binder, the sterilisation certificate is buried in an email attachment, and someone has to reconstruct from memory which design revision was in force when the unit was built.
Because Odoo MRP builds every unit against a specific BOM revision managed in Odoo PLM, the version in force at build time stays permanently attached to the manufacturing order. That same order carries the in-process and final inspection results as quality control points, attachments hold the sterilisation and calibration certificates, and serial tracking can pull the entire chain up from a single unit in seconds.
Do design changes reach the shop floor before they reach the field?
An engineering change gets approved, yet purchasing goes on ordering the superseded component and the line keeps building to the old drawing until stock finally runs out. Nobody can point to which serial numbers represent the last of the old revision, and that is precisely the information a field action needs.
With Odoo PLM, engineering change orders move through approval stages, so a BOM or routing change gets versioned, reviewed and released instead of edited in place. Purchase and MRP can both see effectivity dates, run-out of the old component becomes a deliberate plan rather than an accident, and since every manufacturing order records its own BOM revision, finding the serial break point between two revisions is a matter of running a report, not guessing.
Is complaint handling disconnected from the unit that failed?
Complaints come in by email and by phone, they land in a shared inbox or a spreadsheet, and the link to a serial number is loose at best. Someone tracks trends by hand, CAPA effectiveness gets asserted rather than proven, and the same component failure can repeat across three product lines before anyone notices the pattern.
We route every complaint through Odoo Helpdesk, tied to both the serial number and the customer, and escalate it into Odoo Quality alerts, so investigation, containment and corrective action all share one record. The serial number resolves back to lots, suppliers and a build date, which means you can pull every unit that shares the suspect component lot and scope a field action on evidence rather than defaulting to a worst-case recall.
What we implement for device manufacturers
- Odoo PLM configured for engineering change orders, document versioning and controlled release of BOMs and routings, run under an ISO 13485 change process.
- Serial number tracking that carries UDI data attributes, assembles device history records and traces upstream to component lots and supplier certificates.
- Odoo Quality inspection plans covering incoming inspection on Purchase receipts, non-conformance handling, and CAPA linkage back to Helpdesk complaints.
- Odoo Field Service and Maintenance set up for installed-base servicing, with calibration schedules on test equipment and on-site interventions that stay traceable.
Test Odoo against your device history record
Bring us one serial number and the record you would have to produce for it, and we will show you exactly how much of that chain Odoo already holds natively, and where an eQMS still earns its place.
Book a free 30-min auditFrequently Asked Questions
01
Can Odoo manage UDI data?
Against each tracked unit, Odoo stores the device identifier along with production identifiers, lot, serial, manufacture date and expiry, and prints all of it into GS1 barcode labels. The data model and the label are covered. What it does not do is submit to GUDID or EUDAMED on your behalf, so most manufacturers still keep a submission tool or a service provider for that registry side.
02
Does Odoo replace a dedicated eQMS?
Not entirely, and we won't pretend otherwise. Document versioning, inspections, non-conformance, complaints and change control are all handled well. What's missing is a native validation package, a built-in training record matrix with competency gating, and a pre-certified ISO 13485 template. That is why many Class II manufacturers run Odoo for operations while keeping a specialist eQMS for the design history file and training, integrated at the change order.
03
How does Odoo support supplier control?
Purchase enforces the approved vendor list, incoming inspection runs as Quality control points at receipt, and supplier certificates attach to the lot so they show up automatically in the device history record. Purchase and quality analytics generate the supplier scorecards, though periodic re-evaluation is something you define as a process rather than something the software ships with.
04
How long does a medical device Odoo implementation take?
Usually somewhere between 14 and 20 weeks. A single product family with a straightforward assembly can reach go-live near the 14-week mark. Once you add PLM change control, UDI labelling, complaint and CAPA workflows and an eQMS integration, plan for 20 weeks instead, and start the quality process design well before configuration begins.