By Deepa ShettyPublished: 2 min read

Table of Contents

For manufacturers selling products into the EU, REACH compliance becomes difficult when substance information is distributed across hundreds of suppliers, components and product records.

The challenge is not simply knowing what REACH requires.

It is being able to answer:

Which substances are in our products, which suppliers and components are affected, and what action is required when the regulatory position changes?

A practical REACH compliance process connects supplier data, product information, SVHC screening and regulatory requirements so compliance teams can identify risks and act before they become market-access or supply-chain problems.

What Does REACH Compliance Require Across a Supply Chain?

The exact obligations depend on your role and what you place on the EU market.

For manufacturers and importers dealing with articles, an effective process typically requires you to:

  • Identify relevant materials, components and articles
  • Determine whether Candidate List SVHCs are present
  • Collect appropriate substance information from suppliers
  • Assess applicable concentration thresholds
  • Communicate relevant SVHC information downstream
  • Assess SCIP obligations where applicable
  • Monitor REACH regulatory changes
  • Maintain evidence supporting compliance decisions

The important point is that you cannot reliably assess your own REACH position if the underlying product and supplier data is incomplete.

For the broader regulatory framework, see the Complete Guide to EU REACH Regulation.

The REACH Supply Chain Compliance Process

A scalable approach can be broken into five connected stages.

1. How to Map Your Products and Supply Chain at the Article Level

Start by establishing what is actually inside your products.

Map:

Product → Assembly → Component/Article → Material → Substance

This allows you to identify where substance information originates and which finished products could be affected if a substance becomes regulated.

Without this relationship, a new Candidate List entry can force compliance teams into a manual search across individual BOMs and supplier files.

Your objective should be simple:

If a substance changes regulatory status, you should be able to identify the products that contain it.

2. How to Collect the Right Data From Suppliers

Supplier data is one of the most common weaknesses in REACH compliance programmes.

A supplier may provide:

  • REACH declarations
  • Full Material Declarations
  • SDS documents
  • IPC-1752A declarations
  • IEC 62474 data
  • Material composition information

But “REACH compliant” is not necessarily enough to perform substance-level screening.

The useful question is:

Does the information allow us to determine what substances are present in the relevant article and assess the applicable REACH requirements?

Where information is incomplete, identify the specific data gap rather than repeatedly requesting a generic “REACH certificate.”

For detailed supplier-declaration validation, link to Why REACH SVHC Declarations from Suppliers Fail Compliance Checks and How to Validate Them.

3. How to Screen Products Against the Current Candidate List

Supplier data becomes useful when it can be compared against current regulatory information.

Screen relevant product and substance data against the current REACH Candidate List and identify:

  • SVHC matches
  • Affected components
  • Affected products
  • Missing substance information
  • Concentration information requiring review

When ECHA adds a new SVHC, the important question is not simply:

“What was added?”

It is:

“Which of our products are affected?”

That requires regulatory data to be connected to product data.

For the latest regulatory changes, link to REACH Candidate List Updates.

4. How to Assess the Resulting REACH Obligations

Identifying an SVHC is only the beginning.

The next step is determining what obligations apply to the affected article or product.

Depending on the circumstances, this can include:

  • Article 33 communication
  • Article 7(2) assessment
  • SCIP reporting
  • Supplier follow-up
  • Customer communication
  • Additional compliance documentation

For relevant articles, the 0.1% w/w threshold is an important part of the Article 33 and Article 7(2) assessments, although the obligations and conditions are not identical.

This is why screening should not simply produce a “pass/fail” result.

It should produce an actionable compliance status.

5. How to Maintain Evidence and Reassess When Things Change

REACH compliance is not a document-collection exercise that ends once a declaration has been filed.

Your evidence should allow you to establish:

Regulatory requirement → Substance → Article/Component → Product → Supplier Evidence → Compliance Decision

Maintain appropriate records such as:

  • Candidate List version/date
  • Supplier declarations
  • FMDs
  • Substance identifiers
  • Concentration information
  • Screening results
  • Product/component mapping
  • Customer communications
  • SCIP information where applicable
  • Follow-up actions

This also makes reassessment easier when the product or regulatory position changes.

What Happens When a Supplier Does Not Provide the Required Data?

This is where many REACH programmes become reactive.

A supplier may:

  • Not respond
  • Provide a generic declaration
  • Submit outdated information
  • Provide data for the wrong part
  • Submit an incomplete material declaration
  • Refuse to disclose substance information

The solution should not automatically be:

Send another email.

First identify what is actually missing.

For example:

Data gap

Appropriate response

No SVHC declaration

Request current declaration

No substance composition

Request FMD/material data

Wrong part/revision

Request corrected declaration

Missing concentration

Request concentration/range

Supplier cannot provide data

Escalate or evaluate alternative evidence

High-risk unresolved component

Consider additional assessment/testing

Supplier engagement is therefore part of the compliance workflow, not a separate administrative activity.

How Often Should REACH Compliance Be Reviewed?

A strong programme should reassess compliance when something meaningful changes.

Triggers can include:

  • Candidate List updates
  • New components
  • Product revisions
  • Material changes
  • Supplier changes
  • New supplier information
  • Customer requests
  • Identified compliance gaps

This is particularly important for Candidate List changes.

A new SVHC can affect products that previously appeared compliant, which means regulatory monitoring needs to connect directly to product-level screening.

Common REACH Supply Chain Compliance Mistakes

1. Treating a supplier declaration as the final answer

A declaration is evidence. It still needs to be assessed for scope, currency and relevance.

2. Maintaining static spreadsheets

Static files can quickly become outdated when products, suppliers or regulations change.

3. Monitoring REACH without mapping products

Knowing that ECHA added an SVHC is not enough. You need to know whether the substance exists in your products.

4. Screening only when a customer asks

Reactive screening creates unnecessary urgency and increases the chance of incomplete responses.

5. Failing to document the assessment

A compliance decision without supporting evidence is difficult to defend during an audit or customer review.

A Practical REACH Supply Chain Checklist

Use this as a quick operational check:

Turning REACH Compliance Into Supply Chain Risk Management

The strongest REACH programmes do more than answer whether a product is compliant today.

They help identify what could become a compliance or supply-chain problem next.

For example:

Candidate List update

→ SVHC identified

→ Supplier/component match

→ Affected products identified

→ Compliance obligation assessed

→ Supplier contacted

→ Evidence updated

→ Product status updated

That turns REACH from a periodic documentation exercise into a continuous product and supply-chain risk process.

For a broader risk-management perspective, see How REACH Compliance Drives Supply Chain Risk Management.

How Regilient Helps Operationalize REACH Compliance

Regilient connects regulatory monitoring, product data and supplier information so compliance teams can identify affected products and manage the resulting workflow.

Relevant capabilities include:

  • BOM and component screening
  • Automated supplier outreach
  • Supplier declaration validation
  • SVHC monitoring
  • Regulatory change alerts
  • Compliance status tracking
  • Evidence management
  • SCIP workflow support

Explore Regilient's REACH compliance software capabilities.

Topics

REACH

Speak to Our Compliance Experts

Questions about compliance, partnerships, or support? We're here to help.

Share

Frequently Asked Questions

What is REACH SVHC screening?
REACH SVHC screening is the process of comparing substances present in products, materials, components or articles against the REACH Candidate List to identify affected products and determine what further compliance assessment may be required.
When should manufacturers perform SVHC screening?
Screening should be performed when the Candidate List changes and when relevant products, materials, components, suppliers or substance information changes.
Does finding an SVHC mean a product is non-compliant?
No. Finding an SVHC does not automatically mean that the product is prohibited. The relevant concentration, article, regulatory requirements and applicable obligations must be assessed.
Can a supplier declaration prove SVHC compliance?
A supplier declaration can provide important evidence, but it should be assessed for its scope, currency, product/part coverage and substance-level information.
What happens after an SVHC is identified?
The manufacturer should identify the affected article and products, assess the applicable REACH obligations, update the compliance record and communicate information where required.