Handling Supplier Non-Response and Mismatched Declarations

Purchasing needs parts. Regulatory needs evidence. The failure mode in between is familiar: the supplier does not answer, or answers with a declaration that does not match the BOM line you actually buy. Non-response and mismatched paperwork are not rare exceptions; they are the normal operating condition of multi-tier electronics, plastics, and chemical supply chains. A program that only works when every supplier replies on the first email will never clear a real portfolio.

This article describes an operating pattern mid-market manufacturers can run without a giant PLM program: request discipline, comparison rules, quarantine, and documented disposition.

Why is a “signed compliant” declaration not enough?

Market surveillance and customer audits increasingly test products—not filing cabinets. A tidy PDF that says “RoHS compliant” can still fail lab screening if restricted substances are present above thresholds, if exemptions are misapplied, or if the declaration covers a different part revision than the one on your shelf.

Treat declarations as claims that need:

• Identity (manufacturer, manufacturer part number, revision or date code rules)
• Scope (which regime: RoHS, REACH SVHC, SCIP, Prop 65, customer RSL, halogen-free, and so on)
• Validity window (issue date, expiry or revalidation policy)
• Authority (who signed, on what basis: full material declaration, testing, or self-assessment)
• Follow-up rules when claims conflict with composition data, customer failures, or analytical screening

For official REACH substance and candidate list context, use primary sources such as the European Chemicals Agency (ECHA) rather than secondary blogs when you set internal acceptance criteria.

The five-step operating pattern that scales

1. Request with a deadline and a defined evidence pack

Do not send “please send RoHS.” Send a structured request that states:

• Exact manufacturer part number and revision you buy (or the distributor SKU mapped to it)
• Regimes required for your markets and customers
• Acceptable evidence types (full material declaration, IPC-1752A class, certificate form, test report)
• Response deadline and escalation path
• Whether a partial response (for example RoHS only, REACH missing) counts as open

Templates reduce buyer freestyle and make non-response measurable.

2. Escalate non-response on a clock

Escalation should be automatic in the compliance register, not dependent on memory:

• Day 0: request logged against MPN + supplier contact
• Day N: reminder to supplier quality / sales
• Day N+M: purchasing commercial escalation (volume influence, alternate source threat)
• Day final: disposition—exception, alternate supplier, or hard stop on new POs

Track aging open requests on a weekly board shared by purchasing and RA. Silent aging is how “temporary” gaps become five-year orphans.

3. Compare returned documents to purchasing identity

Most mismatches are identity failures, not chemistry debates:

• Declaration covers a family series, not your MPN
• Manufacturer name differs from the brand on the reel
• Revision on the letter is older than the revision on the PO
• Distributor letter restates compliance without naming the manufacturer evidence
• Date is years old with no revalidation policy accepted by your procedure
• Substance list references an outdated candidate list date for REACH SVHC

Build a checklist reviewers tick before status moves to “accepted.” Cite the checklist version in the record so acceptance criteria are reconstructible.

4. Quarantine mismatched lines

Do not clear the part in the compliance register until identity and scope match. Quarantine means:

• New production BOMs cannot treat the part as green
• Buyers see a visible hold reason in the system they already use
• Existing inventory may stay usable under a time-boxed risk decision—or may be blocked—depending on substance risk and market

Quarantine without a communication path to buyers is theater. The hold must appear where POs and AVL decisions happen.

5. Record the disposition so the next buyer does not re-open a closed gap blindly

Every closed loop needs an outcome code: accepted, accepted with exception, rejected, alternate sourced, manufacturer revised declaration, customer waiver. Store the evidence file hash or document ID, reviewer, date, and next revalidation date. Without that, the same mismatch returns on the next NPI.

Related reading: bridging purchasing and regulatory on RoHS and REACH and supplier regulatory compliance and EU penalty risk.

Who owns supplier declarations—purchasing or regulatory affairs?

Purchasing owns the commercial relationship and the ability to escalate volume, dual-source, and payment terms. Regulatory owns acceptance criteria for evidence and the decision that a declaration is scientifically and legally sufficient for your use case. Both need the same system of record for open requests, ages, and dispositions.

Anti-patterns:

• RA chases suppliers with no commercial pull and no buyer copy
• Buyers accept any PDF to clear a PO date
• Quality stores certificates in a shared drive purchasing never opens
• Exceptions live in email with no expiry

A joint RACI and a single register beat heroic individuals.

Mismatch categories and standard responses

| Mismatch type | Typical response | | --- | --- | | Wrong MPN / family letter | Reject; request part-specific evidence | | Old revision | Reject or conditional accept if change notice proves no material change—and document the logic | | Distributor-only letter | Request manufacturer declaration or approved FMD | | Missing REACH SVHC while RoHS present | Partial open; do not mark full chemical clearance | | Conflict with XRF / lab screen | Hold lots; open supplier corrective action; do not “average away” the conflict | | Supplier refuses substance detail | Escalate commercially; evaluate alternate; document risk if sole source |

When should you block POs—and when allow controlled exceptions?

Policy depends on risk class, not mood:

• Hard stop for high-risk substances, regulated markets with active enforcement, safety-critical applications, or customers with contractual RSLs that leave no room
• Time-boxed exceptions for low-risk spares, non-product MRO, or sole-source parts with compensating controls (incoming screening, limited volume, named owner, expiry date, customer notification if required)
• Never silent exceptions—every exception has an owner, expiry, and revalidation task

Exception abuse is how non-response becomes permanent. Audit exception age quarterly; chronic exceptions should trigger dual-sourcing projects.

Sole-source and strategic suppliers

Some suppliers will not answer mid-market questionnaires quickly. Options that still protect you:

• Accept industry-standard data formats they already publish (and verify identity match)
• Use portal downloads with version capture rather than email PDFs
• Contract compliance deliverables into quality agreements and new business awards
• Fund third-party full material declaration programs when spend justifies it
• Design out the part over a planned ECO if strategic risk stays high

Document which path you chose; “we asked twice” is not a control.

Multi-tier and “unknown formulation” chemicals

For formulations, adhesives, and masterbatches, the non-response problem is often upstream of your direct supplier. Require your supplier to cascade requests or provide composition under NDA sufficient for your regulatory duties. If they cannot, your risk file must say so explicitly—including whether you can still place the product on the market for intended uses.

Metrics that show the program is working

• Median days to first response and to accepted evidence
• Percent of AVL lines green / yellow / red
• Exception count and average age
• Mismatch rate by supplier tier
• Number of production holds caused by compliance identity errors (should fall as comparison rules improve)
• Customer audit findings related to supplier declarations (should fall)

How software and AI help without replacing judgment

Systems help when they:

• Age open requests and notify owners
• Compare declared MPN strings to BOM lines
• Flag expired evidence before PO release
• Cite the rule text used for acceptance decisions

Humans still accept or reject evidence, especially where exemptions, intentional additives, and use-case scope require judgment. For the cross-functional side of clearance definitions, see the bridging article linked above; for penalty and market risk context, see the supplier compliance article.

FAQ

Should we block all POs on missing declarations?

Policy depends on risk class. High-risk substances and regulated markets often justify hard stops. Low-risk spares may use time-boxed exceptions with named owners—never silent exceptions.

Who owns chasing suppliers—purchasing or RA?

Purchasing owns the commercial relationship. RA owns acceptance criteria for evidence. Both need the same system of record for open requests, ages, and final dispositions.

What if the supplier sends a certificate for a similar but not identical part?

Treat it as a mismatch until the manufacturer confirms coverage in writing for your exact MPN and revision, or until an accepted FMD shows equivalence. “Close enough” is a common root cause of failed customer substance screens.

How often should accepted declarations be refreshed?

Set a default revalidation interval in your procedure (for example annually or on candidate-list updates for REACH SVHC communication duties), plus event-driven refresh on part revision change, supplier change of ownership, or analytical failure. Do not rely only on “until something goes wrong.”

Can we rely on distributor compliance portals alone?

Portals help collection speed. You still need identity match, regime coverage, and archival of the exact version you accepted. Portal content can change; store what you relied on at clearance time.