top of page

Change Notification: What Medical Device Customers Expect from Suppliers

4 days ago
6 min read

Reviewed by Aaron Lyon, President of A.P. Lyon and former Director of Quality Assurance and International Regulatory, with more than 30 years in medical device quality. Last reviewed November 18, 2026.


For a supplier to the medical device industry, nothing damages a customer relationship faster than an unannounced change. A new plating house, a cheaper coolant, a moved machine or a re-cut mold cavity may look minor from inside the shop. To a device manufacturer it can mean a failed incoming inspection, a validation that no longer covers the product, or a design file that no longer matches what is being built.


This guide explains why device customers insist on change notification, which changes they expect to hear about, how to notify them, and how to make sure your own suppliers do the same for you.


Where the requirement comes from


A device manufacturer covered by FDA's Quality Management System Regulation must document a quality management system that complies with ISO 13485 (21 CFR 820.10(a)). ISO 13485:2016 clause 7.4.2 says purchasing information includes, as applicable, a written agreement that the supplier notifies the organization of changes to the purchased product before implementing changes that affect its ability to meet purchase requirements.


Three parts of that sentence matter to a supplier:


  • Written agreement. The customer needs your promise in writing, usually in a quality agreement or in the purchase order terms.

  • Before implementing. Notice after the fact does not meet the requirement. The customer must hear about the change before changed product is made or shipped.

  • Affects the ability to meet purchase requirements. The test is the effect on the product, not the size of the change in your shop.


The device manufacturer then has its own work to do. ISO 13485 clause 7.3.9 requires it to review design changes, including their effect on constituent parts, product in process and delivered product, and on risk management. Clause 7.5.6 requires revalidation criteria for validated processes. Your notice is the input that lets it do that work.


ISO 9001:2026 already requires you to review and control changes to production (clause 8.5.6) and to plan QMS changes (clause 6.3). What it does not require is telling the customer first. That is the device-specific layer.


Which changes to notify


The quality agreement should list notifiable changes. When it is silent or vague, treat at least these as notifiable for every device-customer part:


  • material, material grade or material source

  • a sub-tier supplier of material, a component or a special process such as plating, heat treatment, passivation, coating, cleaning or sterilization

  • manufacturing site, building or production line

  • a change to a validated process: new or modified equipment, a new or modified mold, tool or cavity, or parameters outside the validated range

  • cleaning agents, the cleaning method or other process agents that touch the part

  • packaging, labeling, storage or shipping method

  • inspection or test method, sampling plan or acceptance criteria

  • software used to make or inspect the part

  • discontinuation of the part, the material or the process


When you are not sure, notify. A customer will rarely complain about a notice it did not need. It will always complain about a change it did not hear about.


Notify versus approve


Separate two ideas. A notifiable change is one the customer must hear about before you make it. An approval-required change is a notifiable change that the customer must approve in writing before changed product ships. The quality agreement or purchase order should say which changes need approval. For those, your release process must block shipment until the approval is on file.


How to notify


A good change notice gives the customer everything it needs to decide quickly:


  1. What is changing and why. Describe the change in plain terms and the reason for it.

  2. Which parts are affected. List part numbers and revisions.

  3. When. Give the planned implementation date and the first lot that will be made with the change.

  4. What evidence you will provide. For example a first article inspection, revalidation results, comparison data between old and new material, or cleanliness test results.

  5. Who to contact. Give a name and a way to reach them.


Send the notice to the change contact named in the quality agreement, no later than the agreed lead time before implementation. Record the customer's reply. If the customer rejects the change, do not implement it for that customer's parts.


When changed product ships for the first time, identify it. Reference the change number on the certificate of conformance for the first shipment and mark the first lot on the production record. That lets the customer's receiving inspection and design team connect the product to the decision.


A worked example: a new passivation supplier


A contract manufacturer of stainless steel surgical instrument components wants to move passivation from its current supplier to a closer one.


  1. Screen. The engineer raises an engineering change. Because a special process sub-tier supplier is changing, it is notifiable for every device-customer part that is passivated.

  2. Check the agreement. The quality agreement with one customer requires 90 days' notice and approval before changed product ships. Another customer's agreement requires 60 days' notice and no approval.

  3. Plan the evidence. The engineer arranges a trial lot at the new passivation supplier and plans a first article inspection and the customer-specified passivation tests on that lot.

  4. Notify. The customer service manager sends both customers a notice describing the change, the affected part numbers, the planned first lot and date, and the evidence offered.

  5. Approve and release. The first customer reviews the data and approves in writing. The second acknowledges. Quality releases the first changed lots only after the first customer's approval is on file, and the certificate of conformance for each first shipment names the change number.


Changes at your own suppliers


Many unannounced changes start one tier down. Your plating house changes chemistry, your resin distributor switches to a different production plant, or your heat treater replaces a furnace. If you promised your device customer advance notice, you need the same promise from them.


Put an advance notice requirement in every purchase order to sub-tier suppliers of materials, components and special processes for device-customer parts, with a lead time longer than the one you owe your own customer. When a sub-tier notice arrives, treat it as the start of your own change process: raise an engineering change, screen it and notify your customer.


When a change is found without notice


Sooner or later, an unannounced change will be discovered at receiving inspection, in an audit or through a complaint. Treat it as a nonconformance. Hold the affected product, tell the customer promptly, and open a corrective action to find out why the change bypassed your process. ISO 13485 clause 8.3 requires the device manufacturer to justify and approve any concession and, when it evaluates a nonconformity, to decide whether any responsible external party must be notified. Your prompt notice gives it what it needs to make those decisions.


Common mistakes


  1. Notifying after the change. A notice the week the changed product ships is not advance notice.

  2. Sending notices to the wrong person. Use the change contact named in the agreement and confirm receipt.

  3. Judging by the size of the change, not its effect. A small change to a validated process parameter can matter more than a large change to an unrelated area.

  4. No release block. For approval-required changes, product ships before the approval arrives because nothing in the release process checks for it.

  5. No flow-down. The change came from a sub-tier supplier that was never asked to give notice.


Putting it in your quality system


Change notification works best as a short section of your engineering change process, not a separate system. In the ISO 9001 QMS Complete system, the Engineering Change Notice already has a section for customer notification. The Supplying the Medical Device Industry supplier pack adds the Customer Change Notification Procedure (SOP 4-101-MDS) and the Change Notification to Customer form (FORM 0102-MDS), which take each change from screening through customer reply to release, and covers changes at sub-tier suppliers too.



Frequently asked questions


How much notice should a supplier give a medical device customer before a change?


As much as the quality agreement requires. ISO 13485 requires notice before implementation but sets no number of days, so the lead time is agreed between supplier and customer. Choose one long enough for the customer to review the change and for any revalidation.


Do I need to notify the customer if the change does not affect form, fit or function?


The ISO 13485 test is whether the change affects the product's ability to meet purchase requirements, and the quality agreement may list specific changes regardless of effect. If you are unsure, notify.


What if my sub-tier supplier makes a change without telling me?


Treat it as a nonconformance: hold affected product, notify your customer and open a corrective action. Then add an advance notice requirement to your purchase orders to that supplier.


Building a complete quality system? Build Your QMS lets you choose ISO 13485 + FDA QMSR, Dual-Standard or ISO 9001:2026 procedures in one place, and applies volume discounts automatically: 20% off 5–9 procedures, 35% off 10–19, 50% off 20–39 and 60% off 40 or more.


Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.

Comments


bottom of page