REACH Compliance for Product Engineering Teams

On 4 February 2026, the European Chemicals Agency (ECHA) added two substances to the Candidate List of Substances of Very High Concern (SVHCs). The addition brought the total to 253. Bisphenol AF can raise material-review questions for epoxy-based materials and adhesive systems across product bills of materials (BOMs). That recurring update cycle makes REACH compliance as much a product engineering problem as a chemistry one.

Engineering teams need traceable substance evidence tied to controlled change records to manage REACH obligations. This article covers who these obligations apply to, the recurring REACH triggers that engineering teams need to track, and how to fold substance evidence into change management.

What Is REACH Compliance?

REACH compliance means meeting the obligations of Regulation (EC) No 1907/2006, the European Union (EU) regulation on chemicals. It applies to substances, mixtures, and articles, the physical products engineering teams design and ship.

The REACH Regulation (EC 1907/2006) Explained

Since the late 2000s, REACH has served as the EU-wide framework for chemical product obligations. It sets duties for manufacturers and importers and holds downstream users responsible for foreseeable use conditions.

Registration, Evaluation, Authorization, and Restriction Defined

The name describes four mechanisms used to control chemical risk. Each mechanism creates different engineering data needs:

• Registration: Manufacturers and importers must register qualifying substances made or imported in the EU, submitting hazard data and a risk assessment to ECHA.
• Evaluation: ECHA evaluates registration dossiers to judge whether a substance’s risks can be managed.
• Authorization: Substances on Annex XIV generally require European Commission authorization before continued use.
• Restriction: Annex XVII limits or bans specific substances or uses EU-wide.

An Annex XIV listing can leave a path to continued use through an authorization application, while an Annex XVII entry takes effect across the market immediately. Engineering teams need to know which route applies because the design response differs.

The Role of ECHA in REACH Compliance

ECHA manages the registration, evaluation, authorization, and restriction processes for REACH. It works with EU Member States and the European Economic Area (EEA) Member States, and with the European Commission, which grants authorizations and adopts restrictions.

Who Needs to Comply With REACH?

Obligations depend on supply chain role, which companies must determine for each substance they handle and which can change by product, supplier arrangement, or market path.

Manufacturers and Importers

EU manufacturers and importers carry the heaviest load: registration at qualifying volumes, SVHC notifications, and supply chain communication. Non-EU manufacturers often have no direct REACH obligations, so the EU importer complies unless the manufacturer appoints an EU-based Only Representative (OR).

Downstream Users and Distributors

Downstream users who work with chemicals supplied by others must follow conditions of use and authorization terms in safety data sheets. Distributors pass hazard and safe-use information up and down the chain, and a broken link leaves everyone downstream exposed.

Product Engineering Teams

For engineering teams, the binding obligations attach to articles, the physical products and components they design. Article suppliers must communicate when an article contains an SVHC above 0.1% w/w and provide safe-use information. Teams should evaluate that threshold at the level of individual components, not the finished assembly.

A small seal containing an SVHC above the threshold can raise a compliance question inside a much larger machine. Article-level substance evidence must support design and release decisions across procurement.

REACH Compliance Requirements

Four sets of requirements create recurring compliance tasks for product manufacturers, each with its own threshold and clock. Teams need each trigger captured in the records used for material choice and supplier review.

Substance Registration Thresholds

Registration applies to substances manufactured or imported at qualifying annual volumes per registrant, but those volume rules don’t remove other REACH duties, so low-volume activity can still create compliance exposure. Substances in articles must also be registered when they exceed the applicable volume threshold and are intended for release under normal or foreseeable conditions.

SVHCs

The Candidate List covers carcinogenic, mutagenic, or reproductive toxic (CMR) substances, as well as persistent, bioaccumulative, and toxic substances, and very persistent, very bioaccumulative substances. It changes as substances are added, triggering distinct duties for article suppliers.

The Substances of Concern in articles as such or in complex objects (Products) (SCIP) database adds another reporting track alongside customer communication, and dossiers must stay current as new SVHCs are added. Each row below applies once an SVHC exceeds 0.1% by weight (w/w) in an article, a threshold that applies on a component-by-component basis, not to the finished product.

Requirement	Inform customers	Respond to consumer requests	Notify ECHA	Submit to the SCIP database
Threshold	SVHC above 0.1% w/w per article	SVHC above 0.1% w/w	SVHC above 0.1% w/w and over 1 tonne per producer or importer per year	SVHC above 0.1% w/w
Timeline	Upon supply	Within 45 days, free of charge	Within 6 months of Candidate List inclusion	Before placing on the market

Safety Data Sheets (SDS) and Supply Chain Communication

SDS requirements are set out in Annex II of REACH, as amended by Commission Regulation (EU) 2020/878. Suppliers must provide an SDS to professional users of hazardous substances and mixtures, consistent with the chemical safety report. When an SDS is updated, suppliers must distribute the new version to recent recipients.

Authorization and Restriction Processes

The authorization process follows fixed deadlines, and applicants must demonstrate adequate risk control or the absence of suitable alternatives. It can be demanding for substances used in established industrial processes such as hard chrome plating. Annex XVII works by prohibition instead, imposing concentration limits such as restrictions on certain phthalates in plasticized material.

Per- and polyfluoroalkyl substances (PFAS) show how restriction can extend to an entire substance family. Engineering teams therefore need to track whether a substance is moving through authorization, restriction, or both.

Product Engineering Impact of REACH Compliance

Substance regulation creates material constraints and redesign work, with data obligations tied to every BOM part. Those obligations can block market access and turn late redesign into cost and schedule pressure.

Material and Component Selection Constraints

SVHCs can be found in engineering materials, including plastics, coatings, paper, synthetic leather, textiles, foam, and composites. Switching a printed circuit board from conventional epoxy resin to halogen-free alternatives increases material costs and requires thermal stability and dielectric testing.

Design Changes Required by Restricted Substances

Chromium trioxide illustrates how a widely used substance can transition to a permission-based authorization regime. Hard chrome plating delivers high hardness with strong wear and corrosion resistance, so replacement can require application analysis and design changes before selecting a substitute. Aerospace suppliers may treat SVHCs in new designs as a future risk of substitution.

Supply Chain Traceability Challenges

Per-component thresholds mean compliance evidence must exist for individual parts and materials, making Full Material Disclosure (FMD) the norm. Detailed Class D-style declarations support substance-level disclosure, including substance identifiers, concentration data, and material weights across BOM lines. Without that data, teams fall back on spreadsheets and supplier emails, turning untracked chemistry into a long investigation.

Financial and Legal Risks of Non-Compliance

REACH is built around the ‘no data, no market’ principle, so a missing registration can halt deliveries outright. Penalties vary by Member State and can escalate sharply for serious violations. Enforcement can expose registration gaps in imported mixtures, and an EU Safety Gate notification can trigger follow-up.

Common REACH Compliance Challenges in Engineering Workflows

Keeping substance data current across suppliers and design revisions as the Candidate List changes creates recurring workflow failures. Teams must connect regulatory change to product evidence quickly enough to act.

Tracking Evolving SVHC Candidate Lists

Each update can set off the same chain of work. Teams rebuild the article tree across BOMs and sub-assemblies, collect supplier data, recalculate thresholds, redraft customer statements, and refile SCIP entries. In spreadsheets and shared inboxes, that work is hard to complete on time or defend in an audit. Companies selling in both the EU and Great Britain must still track separate UK and EU REACH SVHC lists.

Coordinating Compliance Data Across Global Suppliers

Supply chain visibility weakens through each supplier tier, and responses can trail each update because sub-tier suppliers need time to provide data. Some declarations arriving after an update may still reflect a previous list version. A defensible declaration identifies the covered parts, the compliance basis, the applicable REACH reference, and any SVHCs above the threshold.

Maintaining Traceability Through Design Revisions

SVHC list updates can trigger engineering change orders (ECOs), but impact assessment only works if the substance requirements are connected to the affected designs. When requirements, design artifacts, and test results live in separate systems, such as a product lifecycle management (PLM) tool, gaps appear at handoff points. Manual spreadsheets and skipped impact assessments when regulations change are the failure modes that surface in audits, especially during inspections.

Best Practices for Managing REACH Compliance

Early material screening belongs in the same review cadence as functional requirements, with centralized evidence linked to engineering change control.

Building Compliance Requirements Into Early Design Stages

Compliance checks belong inside design reviews from the first concept gate. Choosing SVHC-free alternatives during the design phase, such as lead-free solder, and capturing each substance restriction as a version-controlled requirement gives change management something to trace. Procurement and compliance input at concept stage keeps materials from being locked in early.

Centralizing Documentation and Test Reports

Records should be organized by product and regulation for each reporting period. The evidence set should stay clear:

• Supplier declarations: Keep current declarations tied to the product, part, and reporting period.
• Test reports: Store test evidence with the material, supplier, and revision it supports.
• BOM records: Preserve BOM snapshots that show which articles were assessed.
• Supplier correspondence: Retain supplier responses that explain the basis for compliance.

A list of declarable substances broader than the current regulatory minimum helps when a watched substance later becomes restricted, since the data already exists to respond more quickly.

Establishing Change Management for Regulatory Updates

A substance master aligned to current EU and UK SVHC lists turns each ECHA publication into a focused view of affected materials, products, and declarations. An SVHC listing that invalidates a material choice touches every requirement, design element, and test case tied to it. Change management should connect the regulatory trigger to the requirement, part, verification evidence, and release baseline.

How Jama Connect Supports REACH Compliance

Substance obligations become manageable in the same traceability model as every other requirement. In Jama Connect®, Traceability Information Models (TIMs) define the expected relationships between compliance requirements, design elements, and test cases, and Live Traceability™ keeps those connections current as the design changes.

For teams absorbing SVHC-related changes, versioned baselines capture the compliance state at each release. Review Center gives reviewers and approvers one place to review, comment on, and approve proposed changes to released-product records. Impact analysis and suspect-link tracking flag downstream artifacts for reassessment before redesign work starts, keeping documentation ready for customer or authority review.

Build REACH Compliance Into Engineering Change Management

Controlled product records make REACH substance data usable after changes to the SVHC list or BOM. Before the next Candidate List publication, identify the released products that rely on supplier declarations older than the current list.

If your team still rebuilds evidence manually after each Candidate List update, Jama Connect can open an impact review from the affected requirement and confirm downstream records before release. You can start a free trial to see how traceability supports regulated product development.

Frequently Asked Questions About REACH Compliance

Is REACH compliance mandatory outside the EU?

EU REACH directly binds EU-based manufacturers, importers, and downstream users. Selling into the EU market still requires evidence that the product meets applicable duties, and non-EU manufacturers may appoint an OR to handle registration and notification, similar to regimes in Korea and Turkey. Engineering and Quality & Regulatory Affairs teams can assign evidence ownership through ECOs so market-entry decisions are tied to controlled product records.

What happens if a product fails REACH compliance?

Market access goes first, since national authorities can withdraw products from sale or detain them at customs until documentation is complete. Fines vary by Member State, and serious cases can create further legal exposure for senior-level involvement or neglect. Jama Connect can show which requirements, modeled design items, and verification records need review to speed impact analysis.

How often is the SVHC list updated?

ECHA updates the Candidate List on a recurring cycle, with occasional extra additions. Each publication can trigger customer communication plus notification or SCIP work, so teams should monitor releases and refresh supplier data accordingly. Jama Connect helps teams keep requirements, evidence records, and design revisions linked when regulatory updates trigger reassessment.

Does REACH apply to software or only physical products?

REACH governs chemical substances and physical articles, so software itself sits outside its scope. For a connected product, REACH applies to the circuit board, enclosure, cabling, and packaging, not to the firmware running on them. Hardware-adjacent software teams should still link firmware requirements to test cases and hardware evidence when a material substitution changes behavior.

This article was authored by Mario Maldari and published on August 7, 2026.