REACH compliance statements: what they prove

A REACH compliance statement is often requested as if there were one official certificate that settles everything. There is not. REACH is a large chemical framework with different duties for substances, mixtures and articles. A useful statement says what it covers and which question it answers: Candidate List substances in an article, Annex XVII restrictions, registration, or another specific duty.

TL;DR

A REACH compliance statement is a supplier or manufacturer declaration describing how a product, material or article meets specified REACH duties. Its value depends on precise scope, an identified product and supporting evidence, not on the phrase ‘REACH compliant’ alone. The useful rule is simple: decide the scope before commissioning work, retain evidence that identifies the actual product, and review it whenever the product or supply chain changes.

What the decision is really about

A REACH compliance statement is a supplier or manufacturer declaration describing how a product, material or article meets specified REACH duties. Its value depends on precise scope, an identified product and supporting evidence, not on the phrase ‘REACH compliant’ alone. Teams get into trouble when they treat the visible label, certificate or checklist as the beginning of compliance. It is the end of a chain that starts with an accurate product description. Write down the model, intended use, users, markets, components and functions. That short note gives engineering, purchasing and whoever approves packaging the same facts to work from. It also stops a perfectly good report being attached to a slightly different product six months later.

The European regulatory framework is deliberately product-specific. A decision that is sound for one product can be wrong for the next even when they share a supplier or a casing. That is not a reason to overcomplicate every launch. It is a reason to record the boundary of the decision, the evidence used and the owner who will revisit it after a meaningful change.

The questions worth answering before release

The table is a working aid, not legal advice. Its value is in making assumptions visible early, when changing a part or updating an instruction is still easy. Keep it next to the bill of materials and the product record rather than letting it disappear into a quotation email.

A practical working sequence

• Tell the supplier the product, material, market and REACH question you need answered.
• Ask for the Candidate List or restriction version considered.
• Link the reply to the bill of materials, prioritising PVC, coatings, adhesives and metals.
• Review when ECHA updates the Candidate List or the supplier changes formulation.
• Retain evidence with the product file and give support teams a clear response path.

Do those steps in that order. Starting with a lab quote, a label proof or a supplier certificate can feel productive, but it can also hard-code the wrong assumption into the project. The better sequence is to establish what the finished product is and which route applies, then ask for the exact evidence that route needs. That makes quotes clearer and makes it much easier to explain why a particular report, declaration or record is in the file.

Evidence that holds up when someone asks

The Candidate List changes over time. A statement can be accurate when signed and still become stale later, so record the assessed list date rather than only an upload date. That lets a team focus updates on affected materials instead of asking every supplier for a new blanket PDF after every ECHA update. For Annex XVII, record the exact restriction and intended use: an SVHC statement does not automatically answer that separate question.

The best files are boring in the best sense: each document has a date, version, product link and owner. An engineer who was not part of the original project should be able to follow the trail without guessing which attachment is final. A retailer, customs officer or market-surveillance authority is not looking for an enormous folder; they need a clear account of why the product meets the requirements claimed. See what goes in a technical file for a useful shared structure.

Keep the decision live after launch

The REACH compliance statement decision should not become invisible after the first shipment. Build a short review into ordinary product change control. Ask whether a proposed change affects the product description, market, intended user, materials, radio function, supplier, software, lab evidence, declaration or label. Most changes will not require starting again. The point is to make a considered decision before the change is released, with a note that someone can find later.

This is also where the person closest to the product needs a route to raise uncertainty without being treated as a blocker. A buyer may see a new material first. A support colleague may hear that a customer uses the product in a way the instructions never anticipated. An engineer may know that a firmware release alters a performance limit. Each observation can be recorded as a review trigger, checked against the original evidence, and closed with a short explanation. That approach is simpler than a giant annual audit because it catches changes while the people who understand them are still in the room.

For REACH compliance statement, give that review a named owner and a realistic deadline. A task assigned to ‘compliance’ is usually a task assigned to nobody. A small, visible record of decisions is better than a perfect-looking dashboard that cannot explain why a product is green.

Mistakes that create avoidable rework

• Using ‘REACH certificate’ as if it were an official universal format.
• Mixing article SVHC information with substance-registration duties.
• Not recording the Candidate List date.
• Forgetting a complex product can contain multiple articles.

None of these errors are fixed by adding more confident wording to a declaration. The manufacturer or responsible economic operator still needs to understand the claim and have evidence for the exact configuration placed on the market. Supplier documents, test reports and software records are valuable inputs, but responsibility does not move just because a PDF has a reassuring title.

A realistic pre-launch moment

A furniture accessory includes a frame, PVC feet and a bonded foam pad. One generic REACH statement arrives for the assembly. The compliance owner asks for the Candidate List date and material-level confirmation where uncertainty lies, giving the business a solid basis for a retailer follow-up.

The point is not that every change needs a panic. It is that a named review gate makes the sensible response routine: record what changed, ask whether the evidence remains representative, update the file if it does not, and only then release the product. That is calmer than rediscovering the issue when stock is already in a warehouse.

What to do next

Rewrite supplier requests around a named duty, then read REACH compliance explained. Start by mapping one live product in the requirements checker. Once the underlying work is complete, the Declaration of Conformity generator can turn the verified details into a consistent document.