SCIP Database Reporting Failures: Why Many Submissions Are Rejected

The dossier was submitted. The notification was rejected.

A compliance team spends weeks collecting SVHC data from suppliers, structuring it into IUCLID format, and submitting SCIP notifications to ECHA. The submission portal accepts the upload. The team marks the task as complete.

Then the validation report comes back with errors. The reference substance dataset doesn't match the current Candidate List package. The article hierarchy doesn't reflect the "once an article, always an article" principle. The concentration range is missing for one of four SVHCs in a complex object. The article category code was pulled from an outdated picklist.

The notification is rejected. The compliance team starts over, often unsure exactly what went wrong or how to fix it.

This is not an edge case. The SCIP database now contains information on over 10 million article notifications submitted by approximately 6,000 companies across the EU/EEA. Behind those numbers is a large volume of failed, incomplete, or incorrectly structured submissions that never made it through validation, or that were accepted but contain data quality issues that undermine their usefulness for waste operators and regulators.

As recently as January 29, 2026, ECHA reported severe delays in the SCIP Dissemination process due to technical problems preventing the publication of successfully submitted notifications. This is the operational reality of a database that was designed for a circular economy but built on a technical infrastructure (IUCLID) that was never optimised for product-level reporting at scale.

This article examines the most common SCIP submission failures, why they happen, and how to build a notification process that passes ECHA validation consistently.

What SCIP Requires: A Quick Refresher

The SCIP database was established under the revised EU Waste Framework Directive (2008/98/EC, as amended by Directive 2018/851) and became operational on January 5, 2021. The obligation applies to any company placing articles on the EU/EEA market that contain SVHCs on the REACH Candidate List at a concentration above 0.1% weight by weight (w/w).

Who must notify: EU/EEA producers, assemblers, importers, and distributors of articles. Retailers supplying directly and exclusively to consumers are excluded. Non-EU companies cannot submit directly but are often contractually required to provide SCIP data to their EU customers.

What must be notified: Each article (as such) or complex object (product) containing one or more Candidate List SVHCs above 0.1% w/w. The notification must include article identification (name, identifiers, article category code), substance identification (using ECHA's Candidate List reference substances), concentration range, safe use information, and article hierarchy within complex objects.

How notifications are submitted: Through ECHA's Submission Portal, using IUCLID format. Submissions can be made via the IUCLID online tool hosted by ECHA, the IUCLID offline software, or a third-party system-to-system (S2S) integration.

When updates are required: Whenever a new SVHC is added to the Candidate List and is present in a previously notified article above 0.1% w/w. The notification must be updated and resubmitted. Changes made in IUCLID do not automatically flow to the SCIP database: the dossier must be recreated and resubmitted through the portal.

The Six Most Common SCIP Submission Failures

1. Outdated Candidate List reference substance packages

ECHA publishes Candidate List reference substance packages that SCIP notifiers must import into their IUCLID instances. These packages are updated with each Candidate List expansion. The February 2026 package, for example, includes 12 new reference substance datasets reflecting the addition of n-Hexane and BPAF.

The most common failure: a company imports the reference substance package once and never updates it. When new SVHCs are added to the Candidate List, notifications referencing those substances fail validation because the reference substance in the company's IUCLID instance doesn't match the current package. ECHA has noted that using the updated package can trigger a quality warning ("reference substance is not in the Candidate List") until the next IUCLID release aligns, but submissions can still proceed. Companies that don't import the latest package at all, however, will see hard validation failures.

2. Article hierarchy errors in complex objects

The SCIP database requires that SVHCs be reported at the article level, not the complex object level. Under the Court of Justice of the EU's 2015 ruling (Case C-106/14), each component of a complex object retains its status as an article: "once an article, always an article."

A pencil sharpener, for example, is a complex object containing a plastic housing, a metal blade, and a screw. If the metal blade contains lead above 0.1% w/w, the SVHC must be reported against the blade (the article), not against the pencil sharpener (the complex object). The complex object notification must then link to the article notification, creating a proper hierarchy.

Common failures include: reporting SVHCs at the complex object level rather than drilling down to the component article; omitting the linking between complex object and constituent articles; and creating flat structures where all SVHCs appear to be in the top-level product rather than in specific sub-articles.

3. Incorrect or outdated article category codes

SCIP requires each notified article to be classified using an ECHA article category code from a standardized picklist of over 20,000 options. This picklist mirrors the EU TARIC list. SCIP format version 6.0 (released May 2025) included an updated picklist.

Companies using older picklist versions, or manually selecting category codes from outdated references, submit notifications that fail picklist validation. Even when submissions pass technical validation, incorrect category codes undermine the usefulness of the notification for waste operators, because the article is classified in the wrong product category.

4. Missing or inconsistent concentration range data

For each SVHC in an article, the notification must specify the concentration range. This is not the precise concentration but rather a range selected from a predefined picklist (e.g., ">0.1% to 1%", ">1% to 5%", etc.).

Common failures: omitting the concentration range entirely; providing a range that contradicts supplier data (e.g., declaring ">5% to 25%" based on outdated information when the current supplier declaration indicates ">0.1% to 1%"); and applying the concentration range against the complex object weight rather than the article weight.

5. IUCLID format version mismatches

ECHA maintains multiple IUCLID format versions in parallel (currently v.6 and v.7). Reference substance packages, picklists, and submission schemas must all be in the same IUCLID format version. A common error is importing a v.7 reference substance package into a v.6 IUCLID instance (or vice versa), which causes format mismatches that result in validation failures.

ECHA explicitly warns: "Make sure that you use the reference substance of the same IUCLID format version as the rest of the submission." This seems straightforward, but in organisations where multiple teams manage different product lines in separate IUCLID instances, format version drift is a persistent problem.

6. Failure to update notifications after Candidate List changes

When a new SVHC is added to the Candidate List, any previously notified article or complex object containing that substance above 0.1% w/w must be updated. This requires modifying the article record in IUCLID, recreating the dossier for the complex object containing that article, and resubmitting through the portal.

Many companies treat the initial SCIP notification as a one-time task and do not have a process for monitoring Candidate List updates and triggering re-notifications. With the Candidate List now at 253 entries (as of February 2026) and updates occurring roughly twice per year, the re-notification backlog grows with every update cycle.

Why SCIP Is Harder Than It Looks

The REACH/SCIP confusion

SCIP and REACH Article 33 are separate obligations with different legal bases, different data requirements, and different submission mechanisms. Compliance with Article 33 (communicating SVHC presence to customers) does not satisfy the SCIP notification requirement, and vice versa. Many companies conflate the two, assuming that their REACH communication programme covers SCIP. It does not. SCIP requires a structured digital notification to ECHA's database; Article 33 requires communication to downstream users. Both must be done independently.

The data collection challenge

SCIP notifications require article-level SVHC data: which specific article within a complex object contains which specific SVHC, at what concentration range. Most supplier declarations provide compliance information at the product level ("this product is REACH compliant"), not at the article level within the product. Translating product-level supplier data into article-level SCIP notifications requires either detailed material composition data from suppliers or independent testing.

The scale problem

A manufacturer of complex electronic or automotive products may have thousands of articles within hundreds of complex objects, each requiring individual SCIP notifications with proper hierarchical linking. A single product revision (adding a component, changing a material) requires updating and resubmitting the entire complex object dossier. At this scale, manual IUCLID entry is not operationally viable.

Building a SCIP Notification Process That Doesn't Break

1. Maintain a current Candidate List reference substance package

Import the latest ECHA reference substance package into your IUCLID instances within two weeks of every Candidate List update. Set a calendar reminder tied to the ECHA update cadence (typically January/February and June/July). Verify that the package version matches your IUCLID format version before importing.

2. Structure article hierarchies correctly from the start

Build your SCIP data model around the article hierarchy, not the product structure. Every article (as such) that contains an SVHC above 0.1% w/w gets its own record. Complex objects link to their constituent articles. This architecture makes re-notifications straightforward when new SVHCs are added or when product structures change.

3. Collect article-level SVHC data from suppliers

Generic "REACH compliant" declarations are insufficient for SCIP. Request suppliers to identify: which specific articles within their products contain SVHCs, which SVHCs are present (by CAS number or ECHA reference substance), and the concentration range per article. This data feeds directly into the SCIP notification structure.

4. Validate dossiers before submission

Use IUCLID's built-in validation tool to check dossiers before submitting through the ECHA portal. Address all validation errors and review quality warnings. A quality warning about a newly added reference substance is expected (and can be submitted through); a hard validation error about format mismatch or missing mandatory fields must be fixed before submission.

5. Automate re-notification triggers

Build a monitoring process that: tracks Candidate List updates, identifies which articles and complex objects are affected by new SVHCs, generates updated IUCLID dossiers, and queues them for re-submission. This should not be a manual review; it should be an automated workflow triggered by ECHA's Candidate List publication.

6. Separate your REACH Article 33 and SCIP workflows

Maintain separate compliance workflows for Article 33 communication and SCIP notification. They share the same data source (Candidate List SVHC presence in articles above 0.1% w/w) but require different outputs: a supply chain communication for Article 33, and a structured IUCLID dossier submission for SCIP.

A Self-Check for Your SCIP Notification Process

Six questions to pressure-test your process:

• Package currency: Have I imported the February 2026 Candidate List reference substance package (reflecting 253 SVHCs, including n-Hexane and BPAF) into my IUCLID instances?
• Article hierarchy: Are my SCIP notifications structured at the article level with proper linking to complex objects, or am I reporting SVHCs at the product level?
• Format consistency: Are all my IUCLID instances, reference substance packages, and picklists on the same IUCLID format version?
• Re-notification process: Do I have an automated or systematic process for updating SCIP notifications when the Candidate List is expanded?
• REACH separation: Do I have separate workflows for REACH Article 33 communication and SCIP database notification?
• Supplier data quality: Are my suppliers providing article-level SVHC data (substance identity, concentration range, article identification), or only product-level compliance declarations?

If more than two answers reveal gaps, your SCIP notification process is likely producing submissions that either fail validation or pass validation but contain data quality issues that will surface during audits or waste operator queries.

Where Regilient fits in

SCIP notification at scale requires more than IUCLID expertise. It requires a data architecture that connects supplier SVHC declarations to article-level product structures, monitors Candidate List changes, and generates submission-ready dossiers automatically. Regilient's agentic sustainability platform handles the parts of SCIP compliance that break when managed manually:

• Automated SCIP dossier generation from product BOM data and supplier SVHC declarations, structured with correct article hierarchies and complex object linking
• Candidate List monitoring with automatic identification of affected articles and complex objects when new SVHCs are added, triggering re-notification workflows
• Reference substance package management that ensures all IUCLID instances are aligned with the latest ECHA Candidate List package and IUCLID format version
• Article-level supplier data collection that captures SVHC identity, concentration range, and article identification at the granularity SCIP requires
• Validation and submission tracking that catches format mismatches, missing fields, and picklist errors before dossiers reach the ECHA portal

The SCIP database was designed to close the information gap between product manufacturers and waste operators. Five years after the notification obligation took effect, that gap is still open for many companies, not because the regulation is unclear, but because the technical complexity of IUCLID-formatted, article-level, hierarchically linked notifications overwhelms manual processes. The companies that automate SCIP notification will close the gap. The companies that manage it in spreadsheets will keep submitting dossiers that fail validation.

Book a Regilient demo to see how agentic SCIP compliance generates validated, submission-ready dossiers from your product data and supplier declarations.

Regilient provides agentic sustainability software for product compliance, supplier engagement, and regulatory intelligence across REACH, RoHS, PFAS, CMRT, SCIP, and global chemical regulations.