Bridging Purchasing and Regulatory on RoHS and REACH

Cross-department friction shows up as a sentence in a meeting: “Purchasing already marked it compliant.” Regulatory opens the file and finds the wrong directive, an expired letter, or a distributor statement that does not name the manufacturer revision on the BOM. The conflict is rarely personal. Purchasing and regulatory optimize for different outcomes, and without a shared definition of “cleared for buy,” both sides will keep rework cycles that delay NPI and anger suppliers.

This article defines a shared clearance model, the checklist that should live where POs are created, and the tools that speed Q&A without replacing human acceptance of evidence.

What does each side optimize for?

• Purchasing optimizes availability, price, lead time, and supplier relationships.
• Regulatory / product compliance optimizes evidence that survives customer audit, market surveillance, and contractual substance restrictions.
• Engineering optimizes function, second sources, and change speed.
• Quality optimizes controlled processes and traceable decisions.

Neither purchasing nor regulatory is wrong. The system fails when “compliant” means “supplier said OK in an email” on one side and “full material declaration against current obligations” on the other—without a written bridge.

Why is RoHS not the same as REACH?

Training must separate regimes in plain language:

• RoHS (Restriction of Hazardous Substances) limits certain substances in electrical and electronic equipment placed on applicable markets. Evidence often takes the form of declarations, exemptions, and sometimes test data for homogeneous materials.
• REACH is broader chemical regulation in the EU/EEA context, including registration duties for many substances and communication duties around Substances of Very High Concern (SVHCs) on the Candidate List when present above thresholds in articles, among other obligations.

A part can be “RoHS OK” on a letter and still create REACH SVHC communication duties—or fail a customer’s stricter RSL. For primary REACH guidance and candidate list information, use ECHA. For EU product and chemicals policy context, the European Commission publishes official materials your procedure should cite rather than paraphrase from memory.

Shared clearance checklist (put it where buyers work)

Agree in writing—and publish in the ERP/PLM/AVL workflow, not only in a QA binder:

1. Which regimes apply per product family — RoHS, REACH SVHC, SCIP where required, Prop 65, customer RSLs, halogen-free, conflict minerals if in scope, and any medical or automotive extras.
2. What evidence is acceptable — full material declaration, certificate type, lab test class, manufacturer vs distributor letters.
3. Identity rules — manufacturer name, MPN, revision; when family declarations are allowed.
4. How often evidence expires — calendar revalidation plus event triggers (revision change, ownership change, failed screen).
5. Who can grant exceptions — named roles, maximum duration, required compensating controls.
6. Where status is stored — green / yellow / red (or equivalent) visible to buyers at PO time.
7. What “green” means — full clearance vs “RoHS only, REACH open” partial states if you allow them.

If buyers cannot see status without opening a SharePoint folder, the checklist will lose to schedule pressure.

Operating model: one register, two owners

Use a single compliance register (PLM attribute set, eQMS module, or dedicated substance tool) where:

• Purchasing opens and ages supplier requests
• Regulatory accepts or rejects evidence against the checklist
• Engineering is notified when a preferred part goes red
• Quality can audit exception aging

RACI sketch:

| Activity | Purchasing | Regulatory | Engineering | | --- | --- | --- | --- | | Commercial chase | R | C | I | | Acceptance criteria | C | R | C | | Part selection / dual source | C | I | R | | Exception approval | C | R (or joint) | C | | Customer questionnaire answers | C | R | C |

For non-response and identity mismatch handling detail, see handling supplier non-response and mismatched declarations. For penalty and enforcement context on supplier gaps, see supplier regulatory compliance and EU penalty risk.

How do you stop rework on every PO?

Cache accepted evidence against manufacturer part + revision (and manufacturer legal entity). Re-open only when:

• Revision changes
• Evidence expires under your procedure
• A regulatory trigger hits (for example Candidate List update affecting your substances)
• Analytical screening or customer failure contradicts the file
• Supplier or ownership changes in a way that voids prior statements

Identical reorders of an unchanged line should not restart the full questionnaire ritual. That is how programs die of fatigue.

NPI and AVL gates that actually bite

Insert hard questions at known gates:

• Concept / early design — preferred parts with existing green status
• AVL add — no new manufacturer part without a compliance owner and request ticket
• Release to production — red parts blocked unless exception with expiry
• Supplier change — treat as new identity even if “equivalent” form-fit-function
• Customer special RSL — project-level overlay, not a silent tribal rule

If the only gate is “someone in RA will check before ship,” you will discover problems after inventory is already bought.

How to run the weekly bridge meeting

A 30-minute standing meeting beats monthly blame sessions:

• Open red/yellow parts by revenue or build impact
• Aging requests past SLA
• Exceptions due to expire in 30 days
• New Candidate List or RoHS exemption news that affects open designs
• Decisions logged in the register during the meeting—not in private notes

Invite purchasing lead, regulatory lead, and a rotating engineering representative for the hottest programs.

Tools that help without replacing judgment

Cited Q&A over approved substance rules can answer “does this declaration cover REACH Article X for our use case?” faster than email threads. Humans still accept or reject the part. Pair search tools with:

• Structured storage of the exact PDF or FMD version accepted
• Diff alerts when supplier portals replace files
• BOM explosion reports that list open compliance states for a product

Keep a human-in-the-loop pattern for acceptance; see human-in-the-loop AI for regulated workflows.

Training content that changes buyer behavior

One lunch-and-learn is not enough. Embed micro-training in the tools:

• Hover text on status codes explaining RoHS vs REACH
• Example of a bad distributor letter vs an acceptable manufacturer declaration
• Escalation button that creates the RA ticket with MPN pre-filled
• Short quiz for new buyers before AVL edit rights

Measure success by reduced red-part POs and fewer emergency RA reviews the week before a customer audit.

Customer and contract pressure

OEMs often flow down substance requirements stricter than the legal minimum. Map customer RSLs as overlays:

• Base legal regimes for markets you sell into
• Customer-specific bans and reporting formats
• Due dates for full material disclosure on new programs

Purchasing should see the customer overlay when quoting programs that include that OEM—not after the contract is signed and parts are tooled.

Metrics executives understand

• Percent of production BOM lines with current accepted evidence
• Average days from AVL request to green status
• Exception count and age
• Number of line-down events caused by compliance holds
• Customer audit findings related to substance documentation
• Cost of dual-source projects driven by uncooperative suppliers

Report these next to classical purchasing KPIs so “cheap part, no evidence” is visible as false savings.

Common failure stories (and the fix)

1. Green sticker on the part bag — warehouse labels are not regulatory evidence. Fix: status only from the register.
2. “We buy from a huge distributor, they are fine” — size ≠ part-specific evidence. Fix: identity match required.
3. Engineering redesigns while RA chases old MPN — parallel paths diverge. Fix: ECO includes compliance impact.
4. RA accepts family letter; later revision changes polymer — silent material change. Fix: revision-linked evidence and change notices.

FAQ

Is RoHS the same as REACH?

No. RoHS restricts certain substances in electrical and electronic equipment in applicable jurisdictions. REACH is broader chemical regulation, including SVHC communication duties for articles among other obligations. Buyers often confuse the paperwork; training and status codes must separate them.

How do we stop rework on every PO?

Cache accepted evidence against manufacturer part plus revision. Re-open only on revision change, expiry, regulatory trigger, contradictory test data, or supplier identity change—not on every reorder of the identical line.

Who should own the AVL compliance field in ERP?

Regulatory should own the acceptance rules and the final status values; purchasing should own timely supplier engagement and data entry of requests. System permissions can allow purchasing to set “requested” while only RA (or a trained designee) can set “accepted.”

What if leadership prioritizes cost over clearance?

Escalate with quantified risk: customer audit findings, potential shipment holds, redesign cost if a substance ban hits, and historical line-down events. Offer dual paths—exception with expiry versus true green—so leadership makes an explicit choice rather than an implicit one.

Do we need full material declarations for every fastener?

Risk-based sampling is common for low-complexity hardware, but your written procedure must say so. Customer contracts and certain markets may still demand broader disclosure. Document the rationale by commodity class so the rule is not reinvented per PO.