REACH compliance in wire harness manufacturing is usually treated as a paperwork exercise until it blocks revenue. A buyer asks for a custom harness, the supplier quotes wire, terminals, seals, and overmold parts, and everyone assumes the material declarations will be easy to collect later. Then the end customer asks whether any Candidate List substance is present above 0.1% w/w, whether SCIP submission is needed, or whether the latest statement covers the actual production revision. At that point, a missing declaration can stop the program even if samples already passed electrical test.
The operational problem is simple: a wire harness is an assembly of many articles and materials sourced from different manufacturers. Jacket compounds, connector housings, TPE boots, adhesive heat shrink, labels, inks, potting compounds, and plated terminals may all come from separate supply chains with different update cycles. If one supplier sends a vague blanket statement while another sends a part-number-specific declaration, the buyer cannot tell whether the compliance file is strong enough to support shipment into the EU market.
This guide is written for OEM buyers, sourcing managers, SQE teams, and program engineers who need a practical process rather than legal theory. It connects directly to the supplier-control disciplines in our <a href="/blog/wire-harness-component-sourcing-guide" class="text-blue-600 hover:text-blue-700">wire harness component sourcing guide</a>, the change-control logic in our <a href="/blog/material-substitution-wire-harness-manufacturing" class="text-blue-600 hover:text-blue-700">material substitution guide</a>, and the release discipline in our <a href="/blog/wire-harness-rfq-checklist" class="text-blue-600 hover:text-blue-700">wire harness RFQ checklist</a>. It is operational guidance for manufacturing teams, not legal advice, so buyers should still align final obligations with their compliance or legal function.
1. What REACH Means for a Wire Harness Program
REACH is the EU framework for the Registration, Evaluation, Authorisation and Restriction of Chemicals. For wire harness buyers, the daily issue is not chemical registration in the abstract. The issue is whether the harness, or any article inside it, contains a Substance of Very High Concern on the Candidate List above the reporting and communication threshold, and whether the supplier can prove what is actually in the shipped revision. A harness may be electrically correct and still be commercially blocked if the compliance file is weak.
In practice, many harnesses are treated as articles assembled from smaller articles. That means buyers should not rely on one top-level declaration without understanding what sits underneath it. A cable jacket compound can be compliant while a connector seal is not. A terminal may pass RoHS but still require additional review under REACH if a plating chemistry, pigment, flame retardant, plasticiser, or stabiliser introduces SVHC exposure risk. Buyers who collapse everything into one yes-or-no vendor statement lose the ability to trace the real problem when a customer escalates.
The most important mindset shift is this: REACH control is revision control. If your drawing rev changes, if a supplier proposes an alternate seal, if a resin compound changes lot source, or if ECHA updates the Candidate List, the compliance status can move even when the harness looks identical on the bench. That is why strong manufacturers connect REACH review to BOM release, approved alternates, and purchasing approval instead of filing one certificate once and forgetting it.
Authoritative guidance from ECHA on Candidate List substances in articles and the broader REACH regulation overview is useful background, but buyers still need a plant-level decision path to screen real harness BOMs.
Commercial gate
Without credible REACH evidence, an otherwise acceptable harness can miss shipment approval, AVL release, or final customer onboarding.
BOM control issue
Every approved alternate, supplier change, and drawing revision can change which declarations still apply to the shipped assembly.
Traceability issue
A generic statement from a trading company is weaker than a part-number declaration tied to the actual resin, metal finish, or adhesive system.
Escalation issue
Once an OEM asks for Article 33 support or SCIP-related evidence, weak files create urgent rework at the worst point in the schedule.
"When buyers ask us for REACH support, the first thing we check is not the logo on the certificate. We check whether the declaration is linked to the exact part number, revision, and material family used on the harness build. That single discipline prevents most last-minute compliance arguments."
Hommer Zhao
Technical Director
2. Where REACH Risk Hides in the Harness BOM
Most REACH surprises do not come from the obvious copper conductor. They come from the supporting materials around it: insulation compounds, connector housings, grommets, TPE boots, seals, labels, tapes, adhesives, potting, ink systems, and plated metal parts. Buyers should screen the BOM by risk density rather than by cost. A low-cost seal or label can create more compliance exposure than a far more expensive machined part simply because its chemistry is less visible and its supplier documentation is weaker.
Connector housings and cable jackets deserve special attention because they often combine base resin, flame retardant package, colorant, stabiliser, and processing aid into one molded part. The commercial part number may stay the same while the underlying compound revision changes. The same is true for adhesive-lined heat shrink, overmold materials, and encapsulants used for waterproof or high-flex assemblies. If the supplier cannot identify the exact material system, the buyer does not have a reliable REACH position.
Plating and surface finishes also matter. Tin, nickel, silver, and gold finishes may be compliant, but the declaration should still tie back to the actual finish stack and supplier source. For high-volume programs, buyers should also ask whether solder, flux residues, marking inks, and packaging contact materials sit inside the declared scope or outside it. A compliance file that quietly excludes those items creates audit risk later.
This is also why REACH review should sit beside process review. Our prototype cable assembly workflow and waterproof cable assembly process both show how material choices change validation work, not just purchase price.
| BOM Area | Typical REACH Exposure | What Buyers Should Ask For | Why It Commonly Fails |
|---|---|---|---|
| Wire and cable insulation | PVC, XLPE, TPU, LSZH compounds, colorants, plasticisers | Part-number declaration or FMD tied to jacket material and supplier | Blanket cable statement does not identify the exact compound revision |
| Connector housings | PA66, PBT, PP, flame retardants, pigments | Material declaration linked to housing series and resin family | Same housing family may use multiple resin systems by color or plant |
| Seals, boots, grommets | Elastomer additives, curing agents, process oils | Supplier declaration with article-level scope and latest review date | Low-cost molded parts often have the weakest traceability |
| Adhesives, tubing, potting | Adhesive-lined heat shrink, encapsulants, overmold compounds | Part-specific declaration plus alternate control for process changes | Commercially equivalent materials can use different chemistry packages |
| Terminals and plating | Metal finishes, coatings, lubricants, process residues | Finish-specific compliance statement from the approved source | Metal parts are often declared too broadly without finish detail |
A useful buyer rule is to review the lowest-visibility chemistry first. The less obvious the material is to the naked eye, the more likely it needs part-number-level documentation instead of a marketing statement.
"In harness compliance work, the expensive connector usually has decent paperwork. The surprise is the small seal, label adhesive, or overmold resin that nobody challenged during sourcing. Those are the parts that create the 11th-hour scramble."
Hommer Zhao
Technical Director
3. Which Documents Buyers Should Demand
A strong REACH file starts with scope clarity. Buyers should ask whether the supplier declaration covers the complete shipped harness, each major purchased article, or only selected raw materials. If the answer is unclear, the document is already weak. The practical goal is to build a traceable chain from finished assembly back to the highest-risk components, so that if a customer asks about one connector family or one heat-shrink part number, the supplier can answer without rebuilding the file from scratch.
The most useful evidence is usually a part-number-specific supplier declaration, supported where needed by a full material declaration, analytical test report, or manufacturer statement from the original component source. Buyers do not need the same depth for every line item. They do need escalation logic. High-volume programs, regulated sectors, and customer-specific compliance portals justify deeper proof than a low-risk internal fixture harness. But even simple programs should define who approves incomplete declarations, who signs off alternates, and what happens when a supplier cannot confirm Candidate List status.
Dates matter. A declaration from two years ago may still be acceptable for a frozen material, but it may also predate later Candidate List additions. Buyers should treat declaration age the same way they treat drawing revision mismatch: not an automatic rejection, but a clear trigger for review. The question is whether the document still covers the actual shipped revision under the current regulatory baseline.
For release decisions, it helps to separate three buckets: acceptable evidence, conditional evidence, and unacceptable evidence. Acceptable evidence is part-specific and traceable. Conditional evidence is close but missing one link, such as a dated declaration that needs reconfirmation. Unacceptable evidence is vague, unsigned, supplier-agnostic, or disconnected from the BOM. That kind of sorting is more useful than asking whether the supplier is generally "good at compliance."
| Document Type | Best Use | Strength | Buyer Decision |
|---|---|---|---|
| Part-number REACH declaration | Standard production release | Strong when tied to exact item and revision | Accept if date and scope still match the build |
| Full Material Declaration (FMD) | High-risk or customer-audited programs | Very strong when substance disclosure is complete | Use for deep screening and customer escalations |
| OEM or component-maker statement | Connector, wire, seal, and resin trace-back | Strong if it names the actual part family | Prefer over distributor-only statements |
| Analytical test report | Escalation or disputed materials | Useful but only for defined samples and methods | Use when declarations are incomplete or challenged |
| Generic company compliance letter | Initial RFQ screening only | Weak | Never use as the only release document for production |
"A REACH file should behave like a control plan, not like a folder of random PDFs. We want a buyer to see the harness BOM, the approved alternates, the declaration owner, and the document date in under 2 minutes. If it takes 20 minutes, the process is already too weak."
Hommer Zhao
Technical Director
Minimum release package
Finished-harness declaration linked to the shipped assembly revision
Part-specific declarations for high-risk items such as cable, housings, seals, tubing, adhesives, and plating
Approved-alternate list showing which supplier parts are inside the compliance scope
Review date and owner for the compliance file before PO release
Escalation triggers
Supplier cannot confirm whether the declaration covers the latest Candidate List update
Document references a family name but not the ordered part number
Customer requests Article 33 wording, SCIP data, or full material visibility
A material substitution or plant transfer changes the actual source of chemistry
4. When Article 33, SCIP, and Escalation Matter
The operational threshold many buyers know is 0.1% w/w for Candidate List substances in an article. Once that threshold is relevant, Article 33 communication duties become the real commercial issue because the recipient of the article must receive sufficient information for safe use, including at least the name of the substance. For some producers or importers, Article 7(2) notification can also matter when the annual tonnage and other legal conditions are met. Buyers do not need to become regulatory lawyers, but they do need to know when a normal document request has crossed into formal escalation territory.
SCIP adds another practical layer for many EU-facing programs. Even when the harness supplier is outside the EU, the EU importer, assembler, or brand owner may ask upstream suppliers for the information needed to complete SCIP-related workflows. That is why weak upstream declarations create problems far beyond the immediate component purchase. A harness manufacturer may not be the party making the final submission, but it is often expected to provide the material data that makes submission possible.
The safest buyer behavior is to define escalation early. If any BOM item is suspected to contain an SVHC above threshold, stop treating the issue as a routine quote document. Pull in compliance ownership, identify the exact article level affected, confirm whether the declaration is current, and decide whether redesign, substitution, customer communication, or formal reporting is required. The cost of escalation is real, but the cost of shipping without a defensible file is usually higher.
ECHA explains the article obligations and the six-month notification timing in its official materials on notification of substances in articles. For buyers, the takeaway is practical: once a harness is close to an Article 33 or SCIP discussion, document ownership and exact article definition become more important than general supplier assurances.
A practical plant rule is simple: if the supplier cannot tell you which article the declaration covers, you are not ready to answer an Article 33 question from the customer.
Routine screening
Low frictionUse when declarations are current, part-specific, and there is no evidence of SVHC presence above threshold. Purchasing can proceed under the normal approval workflow.
Conditional hold
Needs closureUse when the file is close to complete but a critical declaration is outdated, missing part-number traceability, or unclear about the covered article level.
Formal escalation
Compliance-ownedUse when an SVHC-above-threshold case is suspected, a customer requests Article 33 wording, or SCIP-related data must be assembled from upstream suppliers.
5. RFQ and Supplier Checklist for REACH Control
The best time to control REACH risk is before the quote is finalized. Buyers should state the compliance expectation in the RFQ, define whether customer-specific declarations or full material visibility may be required, and clarify whether alternates are allowed without prior written approval. This shifts the conversation from reactive document chasing to planned supplier response. It also filters out vendors who can build the harness electrically but cannot support the compliance record expected by serious OEMs.
At supplier nomination, confirm who owns the compliance file, how updates are tracked, and what happens when a sub-tier declaration expires or a component goes obsolete. If the nominated supplier treats REACH as a one-time sales attachment instead of a controlled process, the problem will reappear the first time the BOM changes. That is especially true for long-life industrial, medical, and transportation programs where components remain in service long after the initial sample build.
For conversion, your CTA should not be vague. If you want a useful compliance review, send the drawing, BOM, annual or project quantity, intended EU market or customer requirement, environment, approved alternates, and target shipment timing. In return, you should expect a gap review, a realistic lead-time assessment, and a document list that tells you exactly which supplier declarations are already usable and which ones need escalation before production.
State REACH compliance requirement directly in the RFQ, not only in later purchase terms
Request part-number declarations for high-risk items: cable, connector housings, seals, tubing, adhesives, and plating-critical terminals
Ask whether the declaration covers the exact shipped revision and approved alternates
Flag any customer expectation for Article 33 wording, SCIP-related data, or full material declaration before samples are built
Assign one owner for document collection and one owner for release approval
Hold shipment if a critical declaration is vague, outdated, or disconnected from the actual BOM
Re-open REACH review after any material substitution, supplier move, or major Candidate List update
Is a RoHS certificate enough to prove REACH compliance for a wire harness?
No. RoHS and REACH cover different obligations. A harness can pass RoHS screening and still need deeper REACH review for Candidate List substances, Article 33 communication, or customer-specific documentation. Buyers should collect REACH-specific declarations rather than assuming one certificate covers both regimes.
Should buyers request a declaration for every single BOM line?
Not always at the same depth, but every high-risk chemistry zone should be covered by traceable evidence. In most harness programs that means cable compounds, connector housings, seals, adhesives, tubing, potting, labels, and plating-sensitive metal parts receive tighter control than simple mechanical hardware.
What is the most common document failure in harness sourcing?
The most common failure is a generic supplier letter that says products are compliant without naming the exact part number, revision, or covered article. That kind of statement is weak for production release because it cannot answer customer escalation on the shipped build.
When should a wire harness buyer escalate REACH review internally?
Escalate when any BOM item may contain an SVHC above 0.1% w/w, when a customer asks for Article 33 or SCIP-related support, when the supplier cannot confirm the declaration scope, or when a material change makes the existing file unreliable. At that point compliance ownership should move beyond routine purchasing.
Can an approved alternate component break the REACH file even if fit and function are unchanged?
Yes. Mechanical interchangeability does not guarantee the same resin, additive package, adhesive chemistry, or plating process. Every approved alternate should be checked against the compliance scope before it is released into production.
What should I send a supplier if I want a fast REACH compliance review with my quote?
Send the drawing, BOM, quantity, intended market, environment, target lead time, customer compliance target, and the list of approved alternates. A good supplier should return a quote, document-gap review, and a clear list of which declarations are already acceptable and which items need escalation before shipment.
6. Frequently Asked Questions
Does REACH apply differently to a complete cable assembly than to individual components?
The operational issue is article definition and traceability. Buyers should understand whether the declaration covers the complete cable assembly, the smaller articles inside it, or both. That distinction matters because Article 33 communication is tied to the relevant article and the 0.1% w/w threshold.
How current should a REACH declaration be before I accept it for production?
There is no universal single-date rule that fits every program, but the declaration must still match the shipped revision and the current regulatory baseline the customer expects. If the file predates later Candidate List updates or a supplier process change, treat it as a review trigger instead of assuming it is still valid.
Is lab testing mandatory for every wire harness REACH review?
No. Most programs rely first on supplier declarations and part-level traceability. Lab testing becomes useful when declarations are incomplete, disputed, or too weak for a customer escalation. It is usually a targeted escalation tool, not the first document buyers should ask for on every harness.
Why do low-cost seals and labels create so many REACH surprises?
Because they often come from lower-visibility sub-tier suppliers with weak document discipline. The chemistry may include additives, pigments, or adhesive systems that are not obvious from the commercial description, and the paperwork is often less precise than for large branded connectors or cable families.
What should I expect back from a capable harness supplier after I send a compliance-focused RFQ?
You should expect a realistic quote, lead time, part-level declaration plan, identification of high-risk BOM items, and a clear statement of any open gaps before sample release or shipment. If the reply is only a price and a generic REACH promise, the review is not deep enough.
Can REACH status change without any visible difference in the finished harness?
Yes. A compound change, alternate source, plating revision, or new Candidate List update can change the compliance file even if the harness looks and tests the same. That is why REACH control has to be tied to BOM revision and supplier change management, not only to visual inspection or electrical test.