SCIP (WFD) Compliance Software

The obligation falls on any company that produces, assembles, imports, or distributes articles containing SVHCs above 0.1% w/w on the EU market. That includes EU-based producers, assemblers, first importers, and distributors. The only exemption is retailers that sell directly and exclusively to end consumers. If your company is based outside the EU, you are not legally required - and in fact are not permitted - to submit SCIP notifications yourself. But here’s the practical reality: your EU customers (typically the importer of record) carry the legal obligation, and they will need substance-level data from you to build their dossier. Many OEMs and EU importers are now writing SCIP data requirements into supplier contracts. So while the legal duty doesn’t sit with you, the commercial expectation absolutely does.

This is one of the most misunderstood aspects of SCIP, and getting it wrong leads to either incomplete submissions or a lot of unnecessary rework. An article as such is the smallest component that cannot be further disassembled into separate articles - think of it as the atomic unit. A cable, a gasket, a coated screw. An complex object is an assembly of two or more articles - a circuit board assembly, a motor, a finished electronic device. Why it matters: SCIP requires SVHC declarations at the article-as-such level, not the product level. You can’t simply declare an SVHC at the finished-product level and call it done. You need to trace and report at the individual article within the product that actually contains the Candidate List substance.

They’re related but not identical. REACH Article 33 requires you to communicate the presence of SVHCs above 0.1% w/w to your downstream customers - it’s a supply chain communication duty. SCIP takes that a step further: it requires you to formally notify ECHA by submitting a structured dossier into a public database. The data overlap is real - both use the same Candidate List and the same 0.1% w/w threshold. But SCIP adds several mandatory fields that Article 33 doesn’t require: article category codes (from a list of over 20,000 options), material/mixture category, concentration ranges, safe-use instructions, and the hierarchical complex-object structure. So if you’ve been collecting Article 33 declarations, that’s a solid starting point - but you’ll need to enrich that data significantly before it’s submission-ready for SCIP

No - and this is a question we’re hearing constantly. In December 2025, the European Commission published the Environmental Omnibus package, which includes a formal proposal to repeal the SCIP database obligation under the Waste Framework Directive. The Commission cited high administrative costs and limited practical use by waste operators and recyclers. However, this is still just a legislative proposal. It must pass through the European Parliament and the Council before it becomes law - a process that could take well into 2027 or beyond. Until then, the SCIP obligation remains fully in force. ECHA has not issued any guidance suggesting companies should slow down submissions, and Candidate List updates continue on schedule (the list now includes 251 entries as of late 2025). The smart move: continue complying, but do it efficiently.

SCIP enforcement happens at the national level - each EU Member State transposes the Waste Framework Directive into its own laws and sets its own penalties. This has led to an uneven enforcement landscape so far. In practice, most Member States have not yet aggressively enforced SCIP-specific penalties, which has led some companies to deprioritize it. That said, the risk profile is changing. Germany, for example, treats deliberate non-compliance with REACH obligations (including SCIP reporting) as a potential criminal matter, with fines up to €1 million and imprisonment up to five years. Other Member States are building enforcement capacity. The fact that enforcement has been slow doesn’t mean it will stay that way - and when it does arrive, companies that have been building quality datasets will be far better positioned than those scrambling to reconstruct years of missing submissions.

The Candidate List is updated roughly every six months, and each update can add new SVHCs that may be present in articles you’ve already notified. The Waste Framework Directive itself does not specify a fixed deadline for updating existing SCIP submissions after a Candidate List change. However, enforcement bodies in some Member States have historically considered a timeframe of about one year to be acceptable for updating - though this is guidance, not a hard legal deadline, and individual authorities can set different expectations. Practically speaking, each Candidate List update should trigger a review cycle: screen your BOM and supplier data against the newly added substances, collect or verify declarations from affected suppliers, and update the relevant SCIP dossiers. If an SVHC is present in an article within a product you’ve already notified, you update the existing dossier - the SCIP Reference ID stays the same.