An industrial paint manufacturer, a solvent distributor, an automotive supplier handling technical adhesives: they all share one thing in common. Their regulatory compliance depends on their information system’s ability to manage accurate, versioned chemical data that can be communicated across the entire value chain. REACH and CLP define what is mandatory. Your ERP determines whether you can prove it during an inspection.
This guide explains what REACH and CLP concretely require from your information system, which ERP features are essential, and how to assess your current level of compliance.
REACH and CLP: the Two EU Chemical Regulatory Pillars That Impact Your ERP
REACH (Regulation EC No 1907/2006): Who in Your Organisation Is Affected?
REACH applies to any company that manufactures or imports chemical substances in quantities of one tonne or more per year within the EU, as well as downstream users who use those substances in their processes or formulations. The regulation covers three categories of actors:
- Manufacturers and importers: required to register substances with ECHA (the European Chemicals Agency). ECHA has recorded over 23,000 substances with valid registration dossiers.
- Downstream users: companies that use substances or mixtures in industrial or professional activities. They do not register, but must operate within the conditions of use described in their suppliers’ Chemical Safety Reports (CSR).
- Distributors: required to pass through Safety Data Sheets (SDS) received from their supplier to their own customers, without modification.
For your ERP, this means that the item master record for a hazardous substance or mixture must contain far more than a product code, a price, and a stock level.
CLP (Regulation EC No 1272/2008): Classification, Labelling, Pictograms
The CLP Regulation (Classification, Labelling and Packaging) aligns EU legislation with the UN’s Globally Harmonised System (GHS). It defines how to classify hazardous substances and mixtures, which GHS pictograms to place on labels, which hazard statements (H-phrases) and precautionary statements (P-phrases) to include.
For your ERP, CLP data translates into structured fields in the item master:
- hazard class and category (e.g. flammable liquid category 2)
- associated GHS pictograms
- signal word (Danger or Warning)
- applicable H and P statements
This data feeds directly into the generation of regulatory labels and SDS content — two obligations your ERP must be able to automate.
SVHC Substances: The ECHA Candidate List and Related Obligations
SVHC (Substances of Very High Concern) are substances identified as extremely concerning due to their properties: carcinogenic, mutagenic or reprotoxic (CMR), persistent bioaccumulative and toxic (PBT), or endocrine disruptors. The candidate list stood at 253 substances in February 2026, following the addition of two new entries by ECHA (SGS, ECHA Expands Candidate List to 253 SVHCs, February 2026).
Once a candidate SVHC substance is present in an article at a concentration above 0.1% by mass, two obligations are triggered:
- Communication to customers (REACH Article 33): inform the recipient of the substance’s presence and provide information needed for safe use.
- Notification to ECHA via the SCIP database (since 5 January 2021): obligation applicable to producers and importers of articles.
What Changes in 2026: Tightening of SCIP Enforcement
ECHA recorded over 17.5 million SCIP notifications as of 30 April 2026 (Z2Data, ECHA SCIP Database, 2025), a sign that the volume of obligations is enormous. The European Commission has also proposed revising certain aspects of REACH under the “Chemical Strategy for Sustainability,” with tightening of enforcement controls expected across member states.
Safety Data Sheets (SDS): A Living Reference to Manage in Your ERP
SDS Supply Obligation: Who Provides Them, and When?
REACH Article 31 requires an SDS to be provided for any hazardous mixture and for any article containing an SVHC substance above the 0.1% threshold. The SDS must be provided free of charge, in paper or electronic format, in the language of the country where the product is placed on the market.
Your ERP must be able to answer three questions in real time:
- Does this product require an SDS?
- What is the current version of the SDS for this product?
- Has the SDS been transmitted to this customer, for this order, on this date?
Integrating SDS into the ERP Item Master
An SDS is not a PDF attachment filed without structure in a DMS. It must be linked to the item master with precise metadata:
- version number and revision date
- available languages
- country validity (the same substance may have different SDS depending on local legislation)
- status: current, archived, pending revision
Some industrial ERPs allow managing these attributes natively within the product record. For others, a connector with a dedicated SDS management software solution is required.
SDS Versioning: Tracking Which Version Was Provided to Which Customer
Consider a scenario: you deliver a chemical mixture in January 2026 with SDS version 4.0. In April 2026, one of the mixture’s substances enters the SVHC candidate list. You must revise your SDS (version 5.0) and send it to all customers who received this product within the past 12 months — without delay.
Your ERP must be able to answer: which customers ordered this product between date X and date Y? Did they receive the SDS version current at the time of delivery? Does a new version need to be resent to them?
Without this history in your ERP, this exercise becomes a manual task using spreadsheets — with the risk of missing a customer during an inspection.
Automation: Attaching the SDS to Transaction Documents
The goal is to systematise transmission: every time an order involves a product requiring an SDS, the current document (in the customer’s language) is automatically attached to the invoice or delivery note, and the dispatch is logged. The ERP must enable this workflow without manual intervention at each transaction.
SCIP and Substance Traceability in the Value Chain
SCIP Database: Who Must Declare and Why
Since 5 January 2021, every producer or importer of articles containing an SVHC substance above 0.1% by mass must submit a SCIP notification to ECHA. The objective is to provide waste sorting facilities with information about hazardous substances present in end-of-life products.
A SCIP notification requires describing the article (category, reference number, image), the substance concerned (name, CAS/EC number, concentration), and information enabling safe use. SCIP data is publicly available — it is visible in the ECHA online database.
Tracking SVHC in the Bill of Materials (BOM)
To declare that a finished article contains a given SVHC substance at a given concentration, your ERP must be able to propagate information from the purchased component through to the delivered product. This requires:
- each raw material to be chemically qualified in the ERP (pure substance or mixture, with identification of SVHC substances and their concentration)
- the bill of materials (BOM) to automatically propagate these attributes during production or assembly
- the finished product to inherit a consolidated list of present SVHC substances and their concentrations
In formulation industries (chemicals, cosmetics, paints and coatings), this propagation is handled by a “formula management” module. In discrete manufacturing (assembly), it requires chemical qualification of purchased components, typically provided by suppliers via compliance declarations (IPC-1752A, for example, in electronics).
Communication Down the Supply Chain (REACH Article 33)
REACH Article 33 requires communicating to the customer information about the presence of SVHC substances in supplied articles, if the concentration exceeds 0.1%. This communication must take place within 45 days of the customer’s request.
Your ERP must therefore have a mechanism to generate this Article 33 compliance declaration on demand, drawing on the BOM’s chemical data. Without this automation, each customer request becomes a manual investigation.
ECHA Declarations via IUCLID: The ERP’s Role in Data Collection
IUCLID (International Uniform ChemicaL Information Database) is ECHA’s tool for submitting REACH registration dossiers and SCIP notifications. Your ERP is not IUCLID — but it must feed IUCLID with structured data. The best ERP/IUCLID integrations allow automatic export of article and substance data in IUCLID 6-compatible format, without manual re-entry.
ERP Features to Require for Operational REACH/CLP Management
”Hazardous Products” / EHS Module: Expected Functions
An EHS (Environment, Health & Safety) module integrated into the ERP must cover at minimum:
- substance and mixture record management with regulatory attributes (REACH, CLP, GHS, ADR transport)
- versioned SDS repository with language and country validity
- pre-market validation workflow (verifying the SDS is available in the required language)
- restricted substance list database: Annex XIV (substances subject to authorisation), Annex XVII (usage restrictions), SVHC candidate list
- automatic alerts when a substance is added to a regulatory list
Automated Alerts: Expired SDS, SVHC Threshold Exceeded, Restricted Substance
The SVHC candidate list is updated several times per year. A substance can be added without your teams being alerted, even while your formulations contain it. Your ERP must continuously monitor the SVHC list and trigger an alert as soon as a substance present in your catalogue exceeds the 0.1% threshold in a sold article.
Similarly, an SDS has a lifespan: if data on the substance or mixture changes (new classification, new restriction), the SDS must be revised and re-sent. The ERP must track revision dates and alert the regulatory team before expiry.
Generating Regulatory Labels from the ERP
A CLP label for a hazardous mixture must contain: the supplier’s name, emergency contact number, GHS pictograms, signal word, H and P statements, and ADR-specific elements if the product is transported as dangerous goods.
An ERP with an EHS module can generate these labels on the fly, drawing on classification data stored in the item master. Generation is triggered during order picking or when producing a new batch.
Audit Trail for Regulatory Inspections
During an inspection by the competent national authority (DREAL in France, the HSE in the UK, or the relevant environmental agency in each EU member state), you must be able to produce: the list of SDS transmitted to your customers for a given period, with the version transmitted and the date; Article 33 declarations sent; SCIP notifications submitted; any exemptions or authorisations requested. The ERP must generate this audit trail in a few clicks, not in a few days.
Under REACH Article 126, each EU member state is required to set effective, proportionate, and dissuasive penalties. In France, violations are governed by Article L521-21 of the Environmental Code: up to 2 years’ imprisonment and €75,000 in fines for the most serious offences (false information to ECHA, non-compliance with prohibition measures); up to 3 months and €20,000 for failure to provide an SDS or to notify ECHA (Légifrance, Art. L521-21 Code de l’environnement). Germany and the Netherlands impose comparable or higher fines under their own national REACH enforcement frameworks.
ERP Solutions with Native REACH/CLP Modules or Certified Connectors (2026)
SAP S/4HANA + SAP Product Compliance
SAP has integrated its product compliance capabilities into SAP S/4HANA for Product Compliance, the renamed and redesigned successor to SAP EHS. The module covers REACH, CLP, GHS, TSCA, SCIP, RoHS, and sustainability requirements. It manages substance dossiers, multilingual SDS, GHS classifications, regulatory list alerts, and integrated chemical approval workflows (SAP Community, Product Compliance Transition to S/4HANA).
Strengths: global regulatory coverage, native integration with PP-PI for formulation industries, full audit trail, certified IUCLID connector.
Limitations: high cost, requires a specialist EHS consultant for configuration, steep learning curve.
Target profile: large chemical groups, pharma, cosmetics companies; organisations already in the SAP ecosystem.
Infor CloudSuite Chemicals + Native REACH Compliance
Infor CloudSuite Chemicals natively integrates REACH/GHS compliance into its formula management module. The platform tracks SVHC substances in formulations, generates multilingual SDS, and supports SCIP declarations (Infor CloudSuite Chemicals). It is one of the few ERPs where chemical compliance is not an add-on, but a foundational layer of the product.
Strengths: deep industry vertical, co-product and by-product management, multi-regulatory compliance (REACH, EPA TSCA, GHS).
Limitations: smaller partner network in some EU markets compared to Germany or the Netherlands, significant implementation cost.
Target profile: mid-market chemical companies (150 to 3,000 employees) with advanced batch traceability and compliance needs.
Sage X3 + Partner Safety & Compliance Connectors
Sage X3 does not offer a native EHS module comparable to SAP or Infor. However, its partner ecosystem provides certified connectors through specialised compliance integrators, adding SDS management, CLP classification, and REACH declarations to Sage X3. The quality of the integration depends on the partner chosen.
Strengths: more accessible cost for industrial SMEs and mid-market companies, already deployed in many European manufacturing businesses.
Limitations: chemical compliance relies on a third-party module — verify the roadmap and functional depth before committing.
Target profile: SMEs and mid-market companies already on Sage X3 seeking a targeted compliance extension without changing ERP.
Odoo + Third-Party Connectors (Chemicalize, Community Modules)
Odoo does not offer an EHS module in its standard offering. Community modules (OCA) partially cover hazardous product management. Connectors to APIs such as Chemicalize can enrich product records with chemical data. The approach is flexible but consumes development and maintenance effort.
Strengths: total flexibility, zero or low licence cost.
Limitations: no native regulatory certification, maintenance burden on community modules, risk of divergence between Odoo versions and third-party modules.
Target profile: SMEs with limited chemical compliance needs, willing to invest in custom development.
Dedicated REACH/SDS Solutions as ERP Complements
When your ERP lacks a satisfactory EHS module, the alternative is a specialised SDS and chemical compliance software solution, connected to your ERP via API or import/export:
- Lisam EXP (formerly Lisam Systems): a complete solution for SDS management, GHS labelling, REACH/CLP/TSCA compliance, used by companies such as Solvay and BASF.
- Verisk 3E: a regulatory chemical data management platform, strong in both North American and European markets.
- Chemwatch: chemical database + SDS management + REACH compliance, available as SaaS.
These solutions interface with ERPs via standard connectors (REST API, EDI) to synchronise product data and regulatory data in both directions.
Compliance Checklist — 8 REACH Points to Verify in Your ERP
Answer yes or no to each question. Fewer than 5 “yes” answers: your REACH compliance in the ERP is inadequate and exposes your organisation to regulatory risk.
-
Does your item master contain CLP data? Classification, GHS pictograms, H and P statements structured in dedicated fields — not merely a PDF attachment.
-
Are SDS versioned in the ERP? With the revision date, available languages and status (current / archived).
-
Is the SDS automatically attached to transaction documents? Delivery notes, invoices, transport documentation — without manual action at each dispatch.
-
Does the ERP log which SDS version was transmitted to which customer, on which date? History queryable by product and by customer.
-
Does your bill of materials (BOM) propagate SVHC data? From purchased component through to finished product, with concentration calculation.
-
Does your ERP generate alerts when a substance enters the SVHC candidate list? And does it automatically identify the affected articles?
-
Can you generate an Article 33 REACH declaration on demand from a customer? In less than an hour, without manually searching through supplier records.
-
Can you produce a full SDS transmission audit trail? With date, recipient, and version — ready for a regulatory inspection.
REACH/CLP compliance is not a one-time project — it is an ongoing process, because regulatory lists evolve, formulations change, and customers ask increasingly precise questions about the chemical composition of the products they purchase. An ERP that manages this data statically is not equal to the challenge.
To go further, read our ERP comparison for chemistry and life sciences (SAP PP-PI, Oracle, Infor, BatchMaster), our guide on ERP and quality management (QMS, nonconformances, CAPA) and our CSDDD guide for supply chain traceability.
