Medical Device ERP After QMSR: 7 Capabilities That Keep You Inspection-Ready
Medical Device ERP Snapshot
QMSR is live. Since February 2, 2026, the FDA's Quality Management System Regulation (QMSR) has governed device manufacturing. It folds ISO 13485:2016 into Part 820, and inspectors use a new playbook. Your medical device ERP has to keep up.
An ISO certificate is not a free pass. FDA still inspects, and it added U.S. requirements on top of ISO 13485 that land squarely in your ERP data.
Seven capabilities decide inspection readiness, from recall-speed traceability to a validation plan for cloud updates.
Business Central can do the job when a partner who knows regulated manufacturing, like A BC Consulting Group, configures and validates it.
A medical device ERP is the system that runs your plant's finances, inventory, production and purchasing while keeping the records FDA expects to see: lot and serial genealogy, device history, controlled documents and supplier approvals.
That definition has held steady for years. The rulebook behind it was rewritten this year.
On February 2, 2026, the FDA replaced the Quality System Regulation (QSR) that had governed device manufacturing since 1978. Its successor, the Quality Management System Regulation (QMSR), is the rulebook FDA uses to judge how you build and release devices. If your medical device ERP was configured around the old QSR, your next inspection runs on a different playbook.
Here's the good news: you don't need to rip anything out. You need to know where the new rules touch your system, and close those gaps on purpose.
Let's walk through it together.
Talk to a Medical Device ERP Specialist
Find out exactly where QMSR touches your current system. Our Business Central team will map your gaps in plain English, with zero pressure.
What is a Medical Device ERP, and Why Does QMSR Raise the Stakes?
A medical device ERP is an enterprise resource planning system set up to meet FDA and ISO 13485 record-keeping rules while it runs day-to-day operations.
A generic ERP tracks what you made and what it cost. A medical device ERP also proves how you made it: which lots went in, which revision you built to, who approved the release and when.
That proof used to live in a patchwork of systems for many teams:
The ERP for orders, inventory, costing and finance
A separate QMS for CAPA and complaints
Spreadsheets for supplier approvals and training
Paper travelers on the shop floor
If that list feels familiar, our post on Dynamics 365 manufacturing explains why the shop floor keeps outrunning spreadsheets.
QMSR leaves the patchwork legal. What it changes is visibility: every seam shows up faster during an inspection, because FDA now evaluates your quality system the way ISO 13485 organizes it.
What Did the FDA's QMSR Change for Your Medical Device ERP?
The short version: Part 820 now points to ISO 13485:2016 for most quality system requirements, with a small set of FDA-specific sections layered on top.
Here's what that means in practice:
New structure. The old Subparts A through O are gone. Requirements follow ISO 13485's clause order.
New inspection program. On February 2, 2026, FDA started using Compliance Program 7382.850 and stopped using its older inspection programs, 7382.845 and 7383.001.
FDA add-ons that live in your data. Section 820.10 requires ISO 13485 plus other FDA rules, including MDR reporting (Part 803), corrections and removals (Part 806), device tracking (Part 821) and UDI (Part 830).
Stricter labeling and packaging controls. Section 820.45 requires you to check labels for accuracy before release and document their release for use.
Extra detail in your records. Section 820.35 adds FDA-specific content to complaint and servicing records, plus a UDI on record for every device or batch.
Read that list again with your medical device ERP in mind. UDI data, device tracking, label control and records all sit in, or flow through, your ERP.
The myth that trips up certified plants
Many teams assume their ISO 13485 certificate means they're covered. It doesn't.
FDA has been clear on two points:
FDA does not issue ISO 13485 certificates, and it does not require them
A certificate does not exempt you from FDA inspection
So a clean ISO audit is a great foundation. Your medical device ERP still needs to support the FDA layer on top.
What 7 Capabilities Does a Medical Device ERP Need in 2026?
This is the heart of it. Use these seven capabilities as a checklist against your current medical device ERP. If you can't say "yes, and here's the record" for each one, you've found your gap list.
1. Can your medical device ERP trace a recall in minutes?
When a supplier flags a bad lot, the clock starts. You need to know which finished devices used that lot and which customers received them.
What good looks like:
Lot and serial numbers captured at receipt, inspection, consumption and shipment
Forward tracing (component to customer) and backward tracing (device to components)
One screen and one query, with no exports to Excel
Results you can hand an inspector as a report
Try our 10-minute recall test. Pick a real component lot from last quarter, ideally one used across several products. Time how long it takes your team to list every affected serial number and customer. If it takes longer than 10 minutes, your traceability lives in people's heads, and that's your first project.
2. Does your system hold UDI data where labels can use it?
Unique Device Identifiers sit under 21 CFR Part 830, and QMSR pulls them into your quality system through Section 820.10.
Your medical device ERP should store the device identifier on the item record and generate production identifiers (lot, serial, expiration date, manufacture date) as you build. That data then feeds your label printing and your GUDID submissions without retyping.
Under Section 820.35, the UDI also has to appear in your records for each device or batch, and on your complaint and servicing records. That makes it ERP data, not just label data.
Every manual handoff between the ERP and the label template is a chance for a mismatch. Our post on Business Central integrations covers which connections to build first.
3. Are your electronic records and signatures Part 11-ready?
21 CFR Part 11 covers electronic records and electronic signatures, and FDA's Part 11 guidance explains how it applies them. QMSR didn't replace Part 11, so it still applies to any record you keep electronically to meet FDA rules.
Check your medical device ERP against these four points:
A secure, time-stamped audit trail of who changed what
Unique user IDs with role-based permissions
Electronic signatures tied to the meaning of the action, such as approval or release
Records you can produce in a readable form for an inspector
Most mainstream ERPs, Business Central included, handle the audit trail and permissions natively.
Signature workflows usually come from a validated extension. Know which is which before an inspector asks.
4. Is change control tied to your bill of materials?
A design change that updates a drawing but not the BOM is a nonconformance waiting to happen.
Your medical device ERP should:
Version every BOM and routing
Block production orders from using an unreleased revision
Link each change to its approval record
Show which open orders an engineering change will affect
ISO 13485 covers this in its clauses on document control (4.2.4) and design and development changes (7.3.9). An inspector will follow the thread from change request to the build that used it. Make that thread easy to pull.
A quick tip from our projects: keep engineering and quality on the same change record. Two parallel approval trails are where gaps hide.
5. Does your system control labeling and packaging?
Section 820.45 is one of the few places where FDA spelled out more than ISO 13485. It expects you to check labels and packaging for accuracy, including the UDI and expiration date, and document their release.
In your medical device ERP, that looks like:
Label content driven from the item and lot record
A release step that blocks shipment until the label check is done
A stored record of the check, linked to the lot
Reprint controls so an old label version can't sneak back into use
6. Can you quarantine a supplier's lot before it reaches the floor?
Supplier controls are where a lot of findings start. Your medical device ERP should know which suppliers are approved for which items, and act on it.
What good looks like:
An approved supplier list enforced at purchase order entry
Incoming inspection tasks generated on receipt
Received lots held in a quarantine location until they pass
Supplier performance data (rejects, late deliveries) you can pull into your annual reviews
7. Do you have a validation plan for cloud updates?
Here's the one most teams forget. Cloud ERPs update on a schedule. Business Central ships two major updates a year, in April and October, plus minor updates in the other months.
That's great for security and features. It also means your validated state needs a plan:
A sandbox environment where updates land first
A short, risk-based regression script for your regulated processes
A documented sign-off before the production update window
A record of what changed and what you tested
Microsoft opens preview sandboxes a month before each major release, in March and September, so your team can start testing early. Planning this rhythm from day one is a big part of any smooth ERP cloud migration.
Find Your Gaps in a Single Session
Run the 10-minute recall test with an expert beside you. We'll score your medical device ERP against all seven capabilities.
Can Business Central Run as Your Medical Device ERP?
Yes, for most small and mid-sized device makers, Microsoft Dynamics 365 Business Central makes a strong medical device ERP. The honest answer comes with a split between what's built in and what you add. If you're still weighing platforms, start with Microsoft Dynamics vs NetSuite.
What Business Central handles out of the box
Lot and serial item tracking, including expiration dates
Forward and backward tracing on the Item Tracing page
Versioned production BOMs and routings
Role-based permissions and change logging
Purchasing, sales orders, warehouse locations and inventory costing tied to your financials, backed by Business Central GAAP compliance
AI help that summarizes records and speeds up data entry, covered in Copilot Business Central features
Seeing your stock clearly is where recall readiness starts. In this tips-and-tricks video, the A BC Consulting team shows how inventory on hand reporting works in Business Central.
The video covers how to report on inventory on hand in Business Central, so your team can check stock levels inside the system. For a medical device ERP, that same visibility is the foundation for the lot and serial tracing described above.
What you usually add
Part 11 electronic signature workflows
Electronic device history records (eDHR)
CAPA and complaint workflows, often through a QMS integration
Label printing tied to UDI data
These come from vetted AppSource extensions or work by experienced Business Central developers. If complaints start in your sales or service team, a clean Business Central CRM integration keeps them connected to the lot record. The skill is in choosing the smallest set that covers your risk, then validating it once and well.
You'll sometimes hear that Microsoft Dynamics needs heavy partner configuration for MedTech. There's truth in it. The quality of your medical device ERP depends on the people who set it up. That's exactly why partner choice deserves as much attention as software choice, and why we wrote about the warning signs to watch for in a Business Central implementation partner.
Microsoft's cloud also brings strong protection for regulated data, from encryption to Microsoft Entra ID sign-in controls. Our post on Business Central security features walks through the details.
How Does A BC Consulting Group Set Up Your Medical Device ERP?
A BC Consulting Group is a boutique, Microsoft MVP-led Dynamics 365 partner based in Nashville, Tennessee, and part of the Gestisoft group. We focus on Business Central, so your project is staffed by people who live in it every day.
Here's how we approach a medical device ERP project:
Discovery first. Our Dynamics 365 Discovery maps your processes against the seven capabilities above, so you see your gaps before you spend.
Configure before you customize. We push Business Central's native features as far as they go, then add only the extensions your risk profile needs.
Build the validation pack with you. Requirements and test scripts are written alongside the configuration, with sign-offs built into the project plan.
Migrate your history cleanly. Lot history and open orders need to arrive intact. Our ERP data migration playbook covers how, and if you're facing Dynamics GP end of life, we've done that move many times.
Train the people who'll face the inspector. Your quality and production leads become fluent in the records. Teams that want an in-house expert can explore Business Central functional consultant training.
Stay with you through every release wave. Our support plans can cover sandbox testing before each update.
Partner choice shows up most when a project hits trouble. Here's how one operations leader described bringing our team into a Business Central implementation that had gone off track:
"A few years ago, we engaged Shannon Mullins to help us decide how to proceed with our Business Central implementation. We contacted her and within hours we were on the phone discussing details with her and her team. Shannon was able to quickly assess the situation and come up with a game plan to get us back on track. She is a consummate professional and her knowledge of Business Central is truly impressive. Thanks to her we were put back on track within days."
John, Director of Operations
For a week-by-week view, read what really happens during a Business Central implementation.
For budgeting, our breakdown of Microsoft Dynamics 365 Business Central pricing goes dollar by dollar.
For smaller teams on a tight budget, our Guided Self-Implementation package gives you expert setup and training without full consulting costs.
What Does Medical Device ERP Look Like for Tennessee Manufacturers?
Tennessee is a serious device state. Memphis is a major medical device center, where Medtronic's spinal business has long been based and Smith & Nephew is among the major manufacturers.
That ecosystem creates a specific pressure for local suppliers. When you make components or contract-manufactured devices for larger OEMs, their auditors expect your records to match theirs. A medical device ERP that can hand over clean lot genealogy on request makes you an easier supplier to keep.
A common pattern with growing shops: their first FDA registration or their first big OEM contract arrives before their systems are ready for it. Getting traceability right early costs far less than retrofitting it after a supplier audit finding.
The same pressure runs through the care side of the state, as our look at ERP systems in the healthcare industry shows.
Being local helps too. A BC Consulting Group can be on your floor in Nashville, Memphis, Knoxville or Chattanooga for go-live week, when hands-on help counts most. Walk into your next inspection with confidence, let's make your medical device ERP the easiest part of your next FDA visit. Book a call with our Nashville Business Central team today.
Medical Device ERP FAQ
What is a medical device ERP?
A medical device ERP is an enterprise resource planning system configured to meet FDA and ISO 13485 requirements. It runs finance and production while keeping traceability and controlled records ready for inspection.
Does ISO 13485 certification mean I'm QMSR compliant?
No. QMSR incorporates ISO 13485:2016, but it adds FDA-specific requirements such as UDI and labeling controls. FDA does not require or issue ISO certificates, and certified sites are still inspected.
Is an ERP required for FDA compliance?
FDA does not mandate ERP software. It does require controlled production and quality records. A well-configured medical device ERP is the most practical way to keep those records consistent as you grow.
Can Business Central meet 21 CFR Part 11?
Business Central provides audit trails and role-based permissions natively. Electronic signature workflows typically come from a validated extension. Your validation documentation completes the picture.
How long does a medical device ERP implementation take?
It depends mostly on data migration and how much validation testing your risk profile requires. A discovery phase gives you a real estimate, and our post on ERP implementation plans shows the steps that keep go-live on schedule.
Comments