ISO 13485 or ISO 9001? The Capabilities That Decide the Answer

Gavren — Sun, 01 Nov 2026 15:08:28 +0000

Two factories send you certificates. One holds ISO 13485:2016, the other ISO 9001:2026. Both are current. When a design change lands on the line, one can show what was re-verified and the other cannot — and the certificate will not say which. That gap is the real ISO 13485 vs ISO 9001 question for a medical device QMS supplier.
Which capabilities actually separate the two systems?
• Design control. ISO 13485 requires it, covering design inputs, outputs, verification, validation, transfer and change control. ISO 9001 allows design to be excluded from scope entirely — and with design excluded, there is no design baseline, so the concept of a "change" has nothing to attach to.
• Risk management. ISO 13485 requires risk management across the product lifecycle and uses it as a shared input to design and to corrective action. ISO 9001 requires risk-based thinking but no risk file, and does not name ISO 14971 as the method.
The first two are design-time controls. The other three are what you examine after a failure, or before a shipment.
• Corrective action. Both require corrective action. ISO 13485 additionally expects it to connect to the risk file and to be closed with an effectiveness check.
• Traceability. ISO 13485 requires records that trace product and batches. ISO 9001 requires identification and traceability where necessary, without a batch-level obligation.
• Regulatory evidence. ISO 13485 requires you to identify applicable regulations and retain evidence of conformity for inspection. ISO 9001 does not address this layer at all.
Read those five as an engineer rather than a buyer: the first four can be tested on site in an afternoon, and only the fifth is a document review. That is why asking about design change and corrective action beats collecting a certificate copy.
Why does design control decide whether a change is visible at all?
Because without a design baseline, "changed" and "unchanged" are physically indistinguishable. A supplier holding only ISO 9001 can be perfectly consistent and still ship a different wall thickness from the one you approved. It has broken no rule, because its system contains no approved design to depart from.
That is the practical engineering meaning of design control: it converts a verbal promise into a comparable reference. With a reference, a change becomes a traceable event. Without one, a change is just a normal production day that nobody recorded.
Design transfer is the step most often skipped in conversation and most worth asking about. It is the point where a validated prototype becomes a production process: which operations, which fixtures, which inspection points. A prototype built by engineers and a production unit built by the line are two different products until that transfer is documented. The question is what changed between them.
Ask it like this: "Show me the last design change on this model — the change request, what you re-verified afterwards, and the drawing revision that is on the line today."
A good answer sounds like this: the three artefacts agree with each other, the revision in the office matches the part on the line, the re-verification covers the characteristics that change could have affected, and the person can name which operation changed at transfer.
A bad answer sounds like this: "engineering handles that"; the revision does not match the part on the line; the re-test covered dimensions only, not load and fatigue.
What does a corrective action look like when it is actually closed?
Separate the correction from the corrective action: the first fixes this unit, the second fixes this class of failure. What ISO 13485 adds is the link to the risk file plus an effectiveness check — which means a corrective action that changed no risk judgement did not, in system terms, happen.
The records themselves tell you which one you are looking at. A correction shows up as a rework or replacement order against specific serial numbers. A corrective action shows up as a change to a procedure, a drawing, a supplier requirement or a risk entry — something that alters what happens to the next unit. If the file contains only the first, the failure will return.
Ask it like this: "Take the most recent corrective action opened from a customer complaint, and show me which risk file entry it changed and the effectiveness check that closed it."
A good answer: the risk file revision is dated after the corrective action, and effectiveness is shown with data — complaint rates before and after, or sampling results — rather than the sentence "no further complaints received".
A bad answer: the action was closed the same week, the risk file is untouched, and the effectiveness field reads "ongoing monitoring".
At what point does traceability stop being paperwork?
At the moment you have to draw a recall boundary. The value of traceability is not that records exist; it is that they answer one specific question: which incoming lots went into this unit, shipped in that month. If they cannot answer it, a defect leaves you two options — recall everything, or recall nothing. Neither is an engineering decision.
The asymmetry has a commercial edge. If you can bound the affected population to one lot, you replace a hundred units and close the file. If you cannot, the honest move is to quarantine a quarter of stock, and the dishonest one is to ship it. Traceability is what keeps that decision technical instead of commercial.
Ask it like this: "Pick a serial number from a shipment last year and pull up every incoming lot that went into that unit."
A good answer chains all the way: serial number, bill of materials, incoming lot number, incoming inspection record, supplier lot.
A bad answer: traceability stops at the shipment date; lot cards are on paper and not linked to serial numbers; one material changed supplier and the chain has a gap.
How should an elderly care supplier certification decision actually be made?
By asking whose claim the certificate has to support. If the product is sold on a medical device route — EU MDR, US FDA — ISO 13485 is the certificate that matters. If it is sold as a general consumer product with no medical claim, ISO 9001 is defensible, but specification risk then sits with you, the buyer.
One boundary gets skipped often: ISO 13485 is a voluntary standard; what is mandatory is the regulation. EU MDR requires manufacturers to operate a quality system proportionate to device class and risk, and ISO 13485 is the widely accepted route to that, not the regulation itself. Calling 13485 a mandatory certification loses credibility with any competent buyer.
Equally, ISO 9001 is not useless. It governs general quality management; it simply does not carry the device-specific obligations. Choosing the wrong certificate costs you not because of the certificate, but because the capability you needed was never in scope.
Why do the 2026 edition changes make the certificate date part of the question?
Three movements overlap, and together they separate "holding a certificate" from "holding a current one".
The 2015 edition of ISO 9001 came out of force on 16 September 2026, and the 2026 edition took its place. Suppliers have a three-year window, closing at the end of September 2029; after 31 March 2028 no new certificate may cite the 2015 text. A 2015 certificate may still be valid today, but it now carries a known expiry boundary.
ISO 13485 has no such window: the 2016 edition was retained after its systematic review concluded in 2025, and the text is unchanged.
On the US side, the Quality Management System Regulation for 21 CFR 820 took effect in February 2026 and incorporates ISO 13485:2016 by reference. For engineers, the practical meaning is that the old dual maintenance — one system for FDA, one for 13485 — now has a common base.
So when you check a certificate, read three things: the edition, the expiry date, and the product scope it actually covers. Checking the logo alone is checking the cover.
FAQ
Is ISO 13485 a mandatory certification?
No. It is a voluntary standard; the regulation is what is mandatory. EU MDR and 21 CFR 820 require a quality system, and ISO 13485 is the widely accepted way to build one.
Our supplier only has ISO 9001 and the product is a shower chair with no medical claim. Can we sign?
It can hold, provided you accept where the risk lands: specification conformity, change visibility and batch traceability become yours to control through the contract and pre-shipment inspection.
With the QMSR in force, is ISO 13485 now the same as the FDA requirement?
No. The QMSR incorporates ISO 13485:2016 by reference and keeps FDA-specific additional requirements. It is a common base, not an identity.
Can these capabilities be checked remotely?
Partly. Design and corrective action records can be reviewed remotely, but traceability needs a randomly picked serial number, chained live while you watch.
Sources and standards status
• ISO 13485:2016, current; third edition, published 2016; retained after systematic review concluded 2025.
• ISO 9001:2026, current; ISO 9001:2015 withdrawn 16 September 2026; transition to 30 September 2029; new certificates to the 2026 edition only from 31 March 2028.
• 21 CFR 820 Quality Management System Regulation (QMSR), effective February 2026, incorporating ISO 13485:2016 by reference.
• ISO 14971:2019, risk management for medical devices, referenced as the recognised method.

DEV Community: Gavren

ISO 13485 or ISO 9001? The Capabilities That Decide the Answer