Product change at the supplier: reviewing and approving PCNs securely
New material, new tool, new site: how automotive and machinery manufacturers approve supplier change notifications in an audit-proof way.

- A product change at a supplier needs a documented customer approval before changed parts are delivered.
- E-mail chains lose versions, deadlines and proof of who approved what and when.
- A guided process with NDA, stages, deadlines and receipts makes every change audit-proof.
A supplier of plastic parts reports that it has to switch granulate because the current manufacturer is discontinuing the material. The quality engineer's inbox receives a data sheet, three test reports and a request for approval by the end of the month. Whoever approves a product change at the supplier takes responsibility for series parts. Yet in many companies this decision still runs via e-mail and shared Excel lists.
Why change notifications are delicate
A change notification (often called a Product Change Notification, PCN) concerns materials, tools, processes, sites or sub-suppliers. In the automotive industry, IATF 16949 requires controlled change management, and the customer must approve changes to product or process before series delivery — in Germany often following VDA Volume 2 (production process and product approval). In machinery and plant engineering, comparable rules are set out in quality assurance agreements.
The documents involved are confidential. Drawings, formulas, test reports and prices reveal a lot about product and costing, on both sides.
Where things get stuck in practice
- Versions: three versions of a test report sit in three e-mails, and nobody is sure which one was approved.
- Deadlines: the supplier's deadline passes because the notification was in the wrong mailbox during the holidays.
- People involved: quality, engineering and purchasing must agree, but only quality sees the e-mail.
- Proof: in an audit or a field failure, there is no evidence of who decided what, when and on what basis.
- Confidentiality: documents are forwarded, reach third parties and can no longer be retrieved.
Rule of thumb: A change is only approved once it is traceable who approved it, on what basis and when.
Supplier product changes as a guided process
Instead of an e-mail chain, every change becomes a separate case with fixed steps:
- NDA first: the supplier only sees the case once a valid non-disclosure agreement is in place. It applies to all further cases with that supplier.
- Notification with mandatory details: part number, type of change, planned date, affected deliveries, test reports attached.
- Team review: quality, engineering and purchasing see the same version and approve or request more in a defined order.
- Deadline and reminder: both sides see by when a decision is due; a reminder arrives before it expires.
- Receipt: the approval is signed and filed traceably for both sides.
Each change thus gets its own file that is ready within minutes at the next audit.
Frequently asked questions
Does the customer have to approve every product change by the supplier?
That is governed by the quality assurance agreement and the industry standard. In the automotive industry, changes to product or process usually have to be approved by the customer before series delivery; which changes must be notified is set out in the agreement.
What belongs in a change notification?
At minimum the part number, type and reason for the change, planned date, affected deliveries and evidence such as test reports or samples. The clearer the mandatory details, the faster the approval.
How long must approvals be kept?
That depends on customer requirements and product liability; for safety-relevant parts often many years beyond end of series. What matters is that the file remains complete and unchanged.
Does the supplier need its own account?
No. With Partner Flow the supplier works via a protected link, after confirming its e-mail address and signing the NDA.
What you can do now
- List the types of change your suppliers must report and the details you need for them.
- Decide who must approve internally and in which order.
- Agree deadlines for your response, including in the quality assurance agreement.
- Make sure documents are only kept where you can control access.
- Check whether your evidence would survive an audit without searching.
With PQVault Partner Flow
PQVault Partner Flow maps change notifications as a guided process between companies. It includes an NDA register, stages with conditions, deadlines, four-eyes approval and a signed receipt for each step. All documents are end-to-end encrypted and additionally protected with post-quantum cryptography. The supplier does not need its own account. For exchanging large test reports, Store & Share complements it. More scenarios under Mobility & automotive and in the article on TISAX-compliant data exchange with suppliers.
PQVault is a product of QuantiCor Security GmbH, Darmstadt — specialists in post-quantum cryptography. More about QuantiCor Security
