SCIP Database and ESPR: Why Your DPP Substance Data Is a Different Beast Entirely

If your team has been filing SCIP notifications since January 2021, you already know the drill: identify SVHCs above 0.1% w/w, prepare an IUCLID dossier, submit to ECHA, repeat whenever the Candidate List updates. It's a mature workflow. The temptation, when ESPR's substance-of-concern (SoC) requirements land, is to assume the hard work is done.

It isn't. SCIP and the Digital Product Passport are built on different legal foundations, serve different audiences, and demand different data structures. Understanding exactly where they diverge - and where your existing SCIP data can be leveraged - is the practical compliance question for 2025 and beyond.

What SCIP Actually Is (and What It Was Never Designed to Do)

SCIP stands for "Substances of Concern In articles as such or in complex objects (Products)" and is a database established and maintained by ECHA under the Waste Framework Directive (WFD). Its mandate is specific: companies supplying articles containing SVHCs on the REACH Candidate List in a concentration above 0.1% weight by weight (w/w) on the EU market have had to submit information on those articles to ECHA as from 5 January 2021.

The duty holders are broad. Producers, assemblers, distributors, and importers all fall within scope. The goal was to ensure hazardous substance information travels with a product through its entire lifecycle - including, critically, the waste stage - so that recyclers and waste operators could handle materials safely.

As of April 2026, ECHA had received over 17.5 million SCIP database notifications from EU suppliers. That's a significant compliance infrastructure. But the Commission's own assessment found a problem: the data was too complex for most end-users, query volumes from waste operators were low, and the practical benefit to recyclers was limited. SCIP was designed as a regulatory notification system, not a machine-readable product intelligence layer.

The Environmental Omnibus: SCIP Is Proposed for Repeal - But Not Gone Yet

Here is the most consequential development for compliance teams right now. As part of the Environmental Omnibus package published on 10 December 2025, the European Commission formally proposed repealing the SCIP database, citing high administrative costs and limited practical benefits. The Commission concluded that the Digital Product Passport under ESPR would provide a more effective digital solution for substance transparency.

The Commission estimates annual savings of approximately €225 million for businesses if SCIP is repealed.

The direction of travel is clear: the Commission intends the DPP to absorb SCIP's function. But the transition period is undefined, and REACH Article 33 supply-chain communication duties - informing downstream users and consumers about SVHCs in articles - are entirely unaffected by the SCIP repeal proposal. Those obligations sit in a different regulation and are not on the table.

How the DPP Substance-of-Concern Requirement Differs from SCIP

This is where compliance teams need to think carefully. The DPP is not a digital SCIP dossier. The differences are structural.

The substance scope expansion is the most significant operational change. Under ESPR, the DPP must carry information on substances of concern as defined in Article 2(27) of Regulation (EU) 2024/1781 - a definition that goes well beyond the REACH Candidate List. CLP hazard classifications, persistent organic pollutants, and substances that impede recycling or recovery all fall within scope. Your SCIP programme only ever tracked Candidate List SVHCs. The DPP will require you to assess a broader chemical universe for each product group, once delegated acts confirm the specific substance lists.

The granularity shift is equally important. A SCIP dossier is an article-level notification to a regulatory database. A DPP substance-of-concern entry must specify - for each substance - its chemical identity, its location within the product (which component or material), its concentration, and instructions for safe use and end-of-life handling. That location-in-product field alone requires a level of bill-of-materials traceability that most SCIP workflows never needed.

The Data Quality Problem Hidden in Your SCIP Archive

Here is the practical risk that most compliance teams underestimate. Your SCIP submissions were built to satisfy a notification obligation. They were not built to be the source of truth for a machine-readable product passport that market surveillance authorities, recyclers, and consumers will query directly.

Common data quality issues that SCIP workflows tolerate - but DPP workflows cannot:

• Concentration ranges instead of point estimates. SCIP accepts ranges; DPP delegated acts are likely to require specific concentration values or at least tighter bands.
• Component-level ambiguity. SCIP dossiers often reference the article as a whole. DPP requires substance location mapped to a specific sub-component.
• Supplier-asserted data without traceability. SCIP submissions frequently rely on supplier declarations with limited audit trails. DPP data will be publicly accessible and subject to market surveillance verification.
• Static snapshots. SCIP dossiers are updated when the Candidate List changes. DPP obligations will require ongoing data governance as products change.

The organizations moving fastest toward DPP readiness share one characteristic: they are not treating DPPs as a standalone project. Instead, they are investing in the underlying product intelligence architecture that makes any compliance output - DPPs, REACH reporting, SCIP submissions, sustainability disclosures - easier to produce from a single governed dataset.

Your Practical Checklist: From SCIP Reporter to DPP-Ready

The window between now and the first product-specific delegated acts is the time to close the gap between your SCIP data and DPP-grade substance data. Here is where to focus:

The Interoperability Opportunity

One constructive development worth tracking: the DPP registry implementing act is expected to address interoperability between the DPP infrastructure and ECHA's existing REACH-IT ecosystem. ECHA's REACH-IT infrastructure already holds substance and substance-in-article data - from REACH, CLP, and SCIP - that overlaps directly with DPP substance-of-concern fields. If that interoperability is realised, it could allow the same governed dataset to power both REACH compliance and DPP substance declarations without redundant supplier outreach.

That outcome is not guaranteed, and the technical standards (the CEN-CENELEC EN 1821x series) are still in advanced drafting. But it reinforces the strategic logic: invest in data quality and structure now, and the same investment pays dividends across multiple regulatory outputs.

The Bottom Line

SCIP was built to notify a regulator. The DPP is built to inform a market. Those are different jobs, and they require different data. The good news for teams that have been doing SCIP reporting since 2021 is that you have a head start on substance identification and supplier engagement. The work ahead is about upgrading data quality, expanding substance scope, and building the component-level traceability that DPP delegated acts will require.

The SCIP repeal, if and when it comes, will remove one reporting channel - not the underlying obligation to know what is in your products. That obligation is only getting more demanding.