REACH SVHC BOM screening is now a recurring operational task, not a one-time project. The European Chemicals Agency (ECHA) updates the REACH Candidate List of Substances of Very High Concern roughly twice a year, and the list reached 253 entries with the update on 4 February 2026. Every time ECHA adds a substance, any company placing articles on the EU market must re-check its products against the new entry. For a manufacturer with a 40,000-line bill of materials and hundreds of suppliers, that re-check is the real burden. This guide explains what triggers a re-screen, which obligations attach, why the 0.1% threshold makes large BOMs hard to screen, and how to build a repeatable process.

Key Takeaways

📌 The REACH Candidate List reached 253 SVHC entries on 4 February 2026 and is updated roughly twice yearly, so BOM re-screening is a recurring duty.

⚠️ A new SVHC above 0.1% w/w in any article can trigger three separate obligations: supply-chain communication, ECHA notification, and SCIP reporting.

📊 Under the ECJ ruling in Case C-106/14, the 0.1% threshold applies to each constituent article, not the whole assembled product.

🔗 Screening a large BOM depends on current, component-level substance data from every supplier tier.

⏳ Article 7(2) notification to ECHA is due within six months of a substance being added to the Candidate List where the tonnage trigger is met.

🤖 Automated, BOM-level substance mapping and supplier data collection turn each Candidate List update into a targeted re-screen instead of a full manual restart.

Why REACH SVHC BOM screening became a recurring problem

The Candidate List is not static. It grows on a predictable rhythm, and each addition can create immediate legal duties for producers, importers, and suppliers of articles. That combination, a moving list plus instant obligations, is what makes re-screening a standing operational commitment rather than an annual exercise.

The pain scales with product complexity. A single finished product can contain thousands of components sourced across multiple supplier tiers. When one new SVHC lands, the question "does any part in any product now exceed the threshold?" has to be answered again across the entire portfolio. Manufacturers already managing REACH compliance alongside RoHS and PFAS obligations feel this most acutely, because the same BOM feeds several frameworks at once.

What triggers a re-screen: the Candidate List update cycle

How often the Candidate List changes

ECHA typically updates the Candidate List twice per year, most often in January and in June. Each update can immediately trigger new article assessment, SCIP notification, and customer disclosure obligations. This cadence is the single most important planning input for any product stewardship team: re-screening should be scheduled around the update windows, not treated as an unplanned fire drill.

Because timing and content can shift, teams should always confirm the current entries against the primary source, the ECHA Candidate List table, before acting on any secondary summary.

What "253 entries" actually means

The figure of 253 counts list entries, not chemicals. Some entries cover groups of substances, so the number of individual chemicals in scope is higher than the headline count. This matters for BOM substance re-screening, because a single group entry can implicate a range of related compounds across your parts.

REACH SVHC Candidate List update timeline reaching 253 entries in 2026

Click on image to view full

The three obligations a new SVHC can trigger

Adding a substance to the Candidate List does not ban it. It attaches information and notification duties whenever the substance is present in an article above 0.1% w/w. Three distinct obligations can apply, and they have different tests and deadlines.

Sources for these tests are set out in ECHA's Guidance on requirements for substances in articles and the ECHA Candidate List obligations page. The practical point for compliance engineers is that a single new SVHC can generate downstream communication, an ECHA notification, and a SCIP entry, each requiring different evidence.

Why the 0.1% threshold makes large-BOM screening hard

The 0.1% figure sounds simple until you ask what it applies to. The European Court of Justice settled this in Case C-106/14 (10 September 2015), in the ruling known as "once an article, always an article."

The Court held that the 0.1% w/w threshold applies to each constituent article, not to the whole assembled product. A component that qualified as an article before assembly remains an article afterward. So if a battery cell inside a laptop contains an SVHC above 0.1% by the weight of that cell, the obligation is triggered, even if the concentration across the whole laptop is far below 0.1%.

For a 40,000-line BOM, this is the crux of the difficulty. Screening cannot be done at the finished-product level. It has to reach down to individual articles and sub-articles, which means the underlying substance data must exist at component level for the calculation to be valid. This is why BOM-level compliance tracking and reliable materials and environmental compliance data are prerequisites, not optional refinements.

The re-screening workflow for a 40,000-line BOM

A repeatable re-screen turns each Candidate List update into a targeted diff against your existing data, rather than a full restart. The workflow below is the practical shape of REACH SVHC and Annex XVII change management at scale.

Step 1: Ingest the new Candidate List entries

Capture the new substances, their identifiers, and any group scope from ECHA. Normalize identifiers (CAS, EC) so they can be matched against your parts data cleanly.

Step 2: Map new SVHCs against BOM substance data

Cross-reference each new entry against the substance composition of every part in the BOM. Flag any article where the substance is present at or above 0.1% w/w at the component level.

Step 3: Identify data gaps

Any part without current, component-level substance data is a gap, not a pass. Missing data is the most common source of false confidence in a re-screen. Gaps drive the next step.

Step 4: Cascade targeted supplier requests

Request updated declarations only from suppliers of parts implicated by the new entry or affected by a data gap. Targeted requests, supported by streamlined supplier documentation, are faster and less noisy than a full portfolio resend.

Step 5: Generate obligations and evidence

Where the threshold is met, produce the Article 33 communication content, assess the Article 7(2) tonnage trigger, and prepare or update SCIP notifications. Retain time-stamped records so the position can be reconstructed later. This connects directly to collaborating with suppliers on the evidence that supports each declaration.

REACH SVHC BOM re-screening workflow from Candidate List update to obligations

Click on image to view full

Where manual re-screening breaks down

Spreadsheet-based screening struggles for predictable reasons, and each one becomes a risk at portfolio scale.

• Version control. Which BOM revision, and which supplier declaration date, was the screen run against? Without an answer, the result is hard to defend in an audit.

• Data currency. Declarations captured for a prior Candidate List version may not cover the newest substances, so old data silently passes new checks.

• Component-level reach. Whole-product data cannot satisfy the per-article calculation required by C-106/14.

• Supplier follow-up. Chasing missing responses by email does not scale across hundreds of suppliers and multiple tiers.

• Evidence retrieval. When a customer audit or an authority inquiry arrives, teams need the point-in-time state, not a best guess.

These are data and evidence problems as much as regulatory ones. Moving off spreadsheets toward a scalable compliance system is what makes each re-screen repeatable.

How automation changes REACH SVHC BOM screening

Automation does not remove legal responsibility, and no platform can make a company "audit-proof." What it can do is reduce compliance surprises, speed up evidence retrieval, and shorten response time on every Candidate List update.

Certivo is designed as a system of record for product compliance, with BOM-level compliance intelligence that links substances to specific parts. When a new SVHC lands, CORA-powered regulatory intelligence helps map the entry against BOM data, flag parts crossing the 0.1% per-article threshold, and highlight where supplier data is missing. Automated supplier data collection then targets only the affected parts, and continuous compliance monitoring keeps the position current between updates.

The same data backbone supports audit-ready documentation across internal audits, customer evidence requests, and certification audits such as ISO 9001 and ISO 14001. Because the BOM feeds several frameworks, the effort spent structuring substance data for REACH also supports chemical and hazmat compliance and adjacent obligations. For teams that also run RoHS in parallel, the practical lessons in RoHS and REACH compliance actions apply directly to this workflow.

What leaders should ask before the next update

For the CFO, the relevant question is cost of rework: a manual re-screen consumes engineering and stewardship hours on every update, and that recurring cost compounds across a large portfolio. For compliance and quality leaders, the question is evidence: can the team reconstruct which BOM revision and which supplier declarations supported a given declaration on a given date? For supply chain leaders, it is data reach: does component-level substance data exist across the relevant supplier tiers, or are decisions resting on gaps? Answering these before the next Candidate List update is the difference between a controlled re-screen and a scramble.

Conclusion

REACH SVHC BOM screening is a permanent operational discipline because the Candidate List keeps moving, reaching 253 entries in February 2026 and updating roughly twice a year. The 0.1% per-article rule under Case C-106/14 means screening must reach component level, and each new substance can trigger Article 33 communication, Article 7(2) notification, and SCIP reporting. The manufacturers that handle this calmly are the ones that treat each update as a targeted re-screen against current, structured BOM and supplier data, rather than a full manual restart every six months.

To see how Certivo maps new SVHC entries against your BOM and automates supplier data collection on every Candidate List update, request a compliance review with a Certivo compliance specialist.