Lot and Serial Number Traceability
Components, work in process and finished goods are traced from the raw material supplier through to the customer, in both directions.
Medical devices
NetSuite for medical device companies that need traceability, controlled change, supplier visibility and clear records across the product lifecycle. We configure NetSuite around how your products are made, tracked and supported, so the records you need are connected from supplier to customer.
In short
NetSuite for medical device companies, and for diagnostics, biotech and other life sciences manufacturers with the same obligations, has to do more than keep inventory records. It needs to show which lot or serial number went into a product, which specification was in force, which supplier provided the component and where the finished device went. Where the product requires it, the NetSuite quality management module holds inspection and non conformance records against those same transactions.
Serialisation narrows a field action to individual units, while lot control is lighter to operate and widens any investigation to the whole lot. The decision is made per product family before go live, because changing it afterwards means reprocessing history.
Controlled fields require approval before they change, keep the previous value, and carry an effective date, so you can answer which specification applied to a unit built years ago rather than showing today's specification.
Qualification status sits on the vendor record and is enforced on purchase orders for controlled items, so an unqualified source blocks the order rather than just producing a warning that gets clicked through.
Most device businesses keep a separate quality management system. Ownership is agreed per record type so one system is authoritative and the other reads from it, which removes the drift that produces audit findings.
From the supplier and component lot through production, quality, shipment and returns, each record stays connected so you can trace a device back to where it came from and forward to where it went.
Components, work in process and finished goods are traced from the raw material supplier through to the customer, in both directions.
Individual units carry their own identifier through production, despatch, field service and return, so a field action can narrow to the specific units affected.
Where full serialisation is not needed, lot control tracks a batch as a group, widening any investigation to the lot rather than the individual unit.
Inspections, non-conformance tracking and corrective actions attach to the same records as traceability. This runs through the separate Quality Management SuiteApp, not the base NetSuite license, and is scoped accordingly.
Qualification status sits on the vendor record and is enforced on purchase orders for controlled items, so sourcing from an unqualified supplier is blocked rather than just flagged.
Stock held at a contract manufacturer or sterilisation site stays inside the same inventory view as stock on your own floor, so nothing drops out of the chain.
When a complaint or field action arrives, the questions come in a fixed order. Which units are affected, which component lots went into them, which supplier provided those lots, and which customers received the units. Each step needs to be answered from records, not from memory.
Traceability is configured so that the answer runs in both directions inside NetSuite: backward from a finished unit to its components and suppliers, and forward from a component lot to every unit and customer it reached. A mock recall run before go live is the practical test that the chain holds.
The Unique Device Identifier can be held as an attribute on the item and on the lot or serial record, so it travels with the unit through production, shipment, service and return.
A device history record draws on production, inspection and change records. NetSuite holds the transactional part of that record, such as which lots, which work order and which specification revision, and the configuration decides how easily it can be pulled together for a given unit.
Most device companies keep complaint handling, CAPA, document control and design history in a dedicated quality management system. NetSuite holds the operational records those processes refer to.
The boundary is agreed record by record before go live, together with how the two systems pass information, for example a non conformance in the QMS placing a lot on hold in NetSuite. Whether the combined process meets ISO 13485 or FDA requirements is a decision for your quality and regulatory function.
We configure NetSuite around your products, suppliers and quality processes, so the records follow a device from component lot to customer. Serial and lot rules, controlled change and supplier qualification are decided for each product line before go live, because changing them afterwards means reworking history.
This page is part of TechCloudPro's Oracle NetSuite and ERP practice.
Tell us where traceability, controlled change, supplier qualification or outsourced production is getting in the way. We'll help you work out where NetSuite can make a difference.
Talk to a Medical Device SpecialistOther ways to reach us