One of the costliest ERP mistakes in medical device manufacturing is deciding on a system to improve accounting, only to discover its limitations during a product recall. Finance gets cleaner books, but Quality cannot trace a product’s full history beyond the warehouse. The remaining traceability records sit in spreadsheets and emails, making it harder to track affected products quickly.
That mistake is avoidable if the evaluation starts with traceability, not the general ledger.
Table of Contents
- Key takeaways
- What does a medical device company need from an ERP?
- Which regulations shape the ERP decision?
- What does Business Central provide for traceability?
- Should a device manufacturer choose Business Central or Dynamics 365 Finance and Supply Chain Management?
- How should a device company plan the implementation?
- What should you ask an ERP partner?
- Why Choose Dynamics Square for Medical Device ERP Implementation?
- The final word
- Frequently Asked Questions
Key takeaways
Business Central handles item-level traceability well: lot, serial, expiration, and warranty settings are standard, and items can be traced backward and forward.
An ERP supports compliance but does not create it. Your quality system and regulatory lead remain accountable.
FDA's Quality Management System Regulation took effect on February 2, 2026, and incorporates ISO 13485:2016. Process records now matter more than ever.
UDI data has two parts. The device identifier is fixed. The production identifier carries lot, serial, and expiration data that your ERP must hold accurately.
Most mid-market device companies fit Business Central. Dynamics 365 Finance and Supply Chain Management fit larger multi-site operations.
What does a medical device company need from an ERP?
Device companies sell into environments where a missing record is a regulatory problem, not just an operational one. The ERP must answer five questions quickly: what was received, what was made from it, where did it ship, which customers hold it, and what changed along the way.
That translates into these requirements:
Lot and serial traceability from supplier receipt to customer shipment.
Expiration control and first-expired-first-out (FEFO) picking.
Bill of materials and routing control for manufactured or kitted devices.
Supplier approval and purchasing controls.
Nonconformance, complaint, and corrective action records, usually through a quality module.
Audit trails and controlled change.
The sixth point is where generic ERPs struggle. Traceability is a data problem the ERP solves. Quality management is a process problem that usually needs a dedicated application connected to the ERP.
Which regulations shape the ERP decision?
Two FDA topics drive most evaluations.
QMSR: FDA states that its Quality Management System Regulation became effective on February 2, 2026. It amends the device current good manufacturing practice requirements in 21 CFR Part 820 and incorporates ISO 13485:2016. FDA's page frames the rule as applying to finished device manufacturers. Distributors and relabelers should confirm their own obligations with regulatory counsel.
UDI: FDA describes a Unique Device Identifier as a device identifier (DI) plus, when applicable, a production identifier (PI). The PI can include a lot or batch number, serial number, expiration date, or manufacture date. The FDA's GUDID database holds the DI only, not the PI. That split matters: the PI lives on your labels and in your records, so your ERP is where it must be accurate.
If your system creates or stores electronic records and signatures, ask your regulatory lead whether 21 CFR Part 11 applies and how the vendor and partner support validation. Do not assume it from the platform name.
What does Business Central provide for traceability?
Microsoft Learn documents the core capabilities through Item Tracking Codes.
| Requirement | Business Central standard | Likely needs design or an add-on |
|---|---|---|
| Lot and serial control | Lot-Specific and SN-Specific Tracking on the Item Tracking Code | Rules for which items are tracked |
| Expiration control | Use Expiration Dates, Require Expiration Date Entry, Strict Expiration Posting | Picking policy by expiry, customer minimum shelf life |
| Warranty dates | Warranty Date Formula, Require Warranty Date Entry | Service contract processes |
| Recall tracing | Trace Item-Tracked Items, backward and forward | Recall procedure, mock recall testing |
| Warehouse accuracy | Lot and serial warehouse tracking settings, bins | Mobile scanning and label printing |
| UDI barcode labels | Not a core feature | ISV labeling or integration |
| Quality events and CAPA | Not a core feature | Quality management ISV |
| Validation evidence | Not provided by the ERP | Your own plan with partner support |
Microsoft states that tracing items with serial and lot numbers is useful for quality assurance and product recalls. We explain the setup in lot expiration in Business Central and the controls in quality and compliance with Business Central.
Should a device manufacturer choose Business Central or Dynamics 365 Finance and Supply Chain Management?
For most mid-market device companies, Business Central is the practical starting point. It combines finance, inventory, purchasing, sales, and manufacturing in one system with a lower implementation burden. Our guide to manufacturing in Business Central covers production orders, BOMs, and costing.
Dynamics 365 Finance and Supply Chain Management become the better answer when the scenario includes large transaction volumes, many sites, advanced warehouse processes, or complex consolidation. The trade-off is cost and project size. Read the comparison in Business Central vs. Finance and Supply Chain Management before assuming bigger is safer.
Choose based on process complexity, not company pride.
Improve Medical Device Traceability with Business Central
Connect with Dynamics Square USA to align your ERP with manufacturing and traceability needs.
How should a device company plan the implementation?
Implementation risk concentrates in four places.
Item master design: Decide tracking rules by product family before migrating data. Retrofitting lot tracking onto history is painful.
Data migration: Open lots, expiration dates, and supplier records must be accurate on day one. Migrate less history, not dirtier history.
Validation approach: Agree with quality early on what needs documented testing. Validation scope is a project cost and a timeline driver.
Integrations: Quality systems, label printers, scanners, and e-commerce portals each add scope. Our implementation guide outlines phases.
Run a mock recall before go-live. Pick a lot, and time how long it takes to list every customer shipment. If it takes hours, fix the design before launch.
What should you ask an ERP partner?
Ask for specifics. Which device clients or similar regulated manufacturers has the team supported? How do they handle validation documentation? Which quality ISV do they recommend and why? What is out of scope in the quote? A partner that answers with product features instead of your recall scenario has not understood the problem.
If you are weighing a rebuild of a struggling system, see our view on Business Central reimplementation.
Why Choose Dynamics Square for Medical Device ERP Implementation?
Dynamics Square USA helps medical device manufacturers implement Microsoft Dynamics 365 Business Central to improve inventory visibility, lot and serial number traceability, and manufacturing control. With 14+ years of experience, 150+ Microsoft Certified Consultants, and 500+ implementation projects completed, our team helps businesses configure ERP workflows around their operational and traceability requirements.
We also help identify where quality management, UDI labeling, and regulatory documentation require specialized applications or integrations, supporting a more informed and structured ERP implementation.
The final word
A medical device ERP must track lots and serial numbers, control expiration dates, trace products forward and backward, and support supplier, document, and change control. Microsoft Dynamics 365 Business Central covers lot, serial, and expiration tracking and tracing natively. Quality management, UDI labeling, electronic signatures, and validation typically require add-on applications, configuration, and your own documented process.
Frequently Asked Questions
A medical device ERP is business software configured for regulated product traceability, inventory, manufacturing, purchasing, and finance. It maintains lot and serial history, expiration dates and supplier records so teams can respond to audits and recalls. Quality events and electronic signatures often need add-ons connected to the core system.
Business Central suits many mid-market device manufacturers because it provides lot, serial, and expiration tracking, production orders, and traceability in one system. Regulated processes such as CAPA, validation, and UDI labeling typically need extra applications and documented controls, so scope those during discovery.
Business Central stores the lot, serial and expiration data that make up a UDI production identifier. Generating compliant UDI barcode labels and submitting device data to the FDA's GUDID usually requires an ISV solution or integration. Confirm label requirements with your regulatory lead.
FDA's Quality Management System Regulation became effective on February 2, 2026. It amends 21 CFR Part 820 and incorporates ISO 13485:2016. For ERP selection, it raises the value of controlled records, supplier management, and traceable processes, so evaluate how the system supports those workflows.
Yes. Microsoft Learn describes tracing items with lot and serial numbers backward and forward through the supply chain, noting its value for quality assurance and recalls. Accuracy depends on a consistent item tracking setup and disciplined data entry in receiving, production, and shipping.
