Restriction of Hazardous Substances (RoHS) Compliance Guide

Chapters

Chapter 7: Restriction of Hazardous Substances (RoHS) Compliance Guide

Chapters

Restriction of Hazardous Substances (RoHS) Compliance Guide

In 2026, 82 electronic-product samples failed for lead and cadmium levels above permitted limits in solder, and another 51 failed for restricted phthalates in insulation and cable sleeves during European Union (EU) market surveillance testing. Two decades into enforcement, restricted substances still reach the market at scale. Documentation creates a critical failure mode: products can enter the market backed by supplier declarations nobody verified with laboratory testing, then fail when regulators test.

For product development teams, RoHS compliance is as much a data management problem as a chemistry problem, and it runs through component selection and supplier contracts. This guide covers the RoHS substance list, who the directive covers, how to build compliance evidence into your development process, and the recurring challenges that create audit risk.

What Is RoHS Compliance?

RoHS compliance means meeting the substance restrictions of Directive 2011/65/EU, which limits ten hazardous substances in electrical and electronic equipment (EEE) placed on the EU market. The limits apply at the homogeneous material level, which means a material of uniform composition that teams cannot mechanically separate into different materials. Authorities judge compliance on the solder joint, the cable sheathing, and the component tinning individually.

The 2011 directive, known as RoHS 2, turned a substance rule into a conformity regime, the same shift other regulatory standards apply across industries. Manufacturers must assess conformity, draw up an EU Declaration of Conformity (DoC), maintain a technical file, and affix the Conformité Européenne (CE) marking before placing EEE on the market. Importers and distributors also carry obligations, and either one can become responsible as a manufacturer when rebranding EEE or modifying it in a way that affects compliance.

Why RoHS Compliance Matters for Product Development

RoHS compliance protects market access, but the real cost of getting it wrong shows up earlier than a fine or a recall. When a restricted substance surfaces late in development, teams face material substitutions, supplier renegotiations, and design respins that a compliance check earlier in the process would have caught.

The alternative is treating substance evidence as a design input rather than a launch gate. Teams that verify supplier declarations and build exemption tracking into early sourcing decisions keep their components auditable throughout development, instead of reconstructing that evidence after the product has already shipped.

Which Restricted Substances Fall Under the RoHS 10 List

The RoHS 10 list combines six original substances with four phthalates added later. Each limit applies by weight within every homogeneous material.

Substance Maximum concentration
Lead (Pb) 0.1%
Mercury (Hg) 0.1%
Cadmium (Cd) 0.01%
Hexavalent chromium (Cr⁶⁺) 0.1%
Polybrominated biphenyls (PBB) 0.1%
Polybrominated diphenyl ethers (PBDE) 0.1%
Four phthalates: bis(2-ethylhexyl) phthalate (DEHP), benzyl butyl phthalate (BBP), dibutyl phthalate (DBP), diisobutyl phthalate (DIBP) 0.1% each

The phthalate restrictions were phased in later for most EEE and later still for medical devices and monitoring and control instruments. Because the phthalates are plasticizers used in soft rubber and polyvinyl chloride (PVC), older compliance assessments may have missed them in cable sleeves and seals. Grommets that use those materials need the same review.

Which Products and Industries the RoHS Directive Applies To

The directive’s scope spans consumer, information technology (IT), industrial, medical, and monitoring EEE categories. A catch-all category covers other EEE not covered by the listed categories.

Product teams should document the basis for any exclusion, since the main exclusions are:

  • Military and space equipment: Equipment for military purposes and equipment designed to be sent into space.
  • Large-scale equipment: Large-scale stationary industrial tools and large-scale fixed installations.
  • Transport and mobile machinery: Means of transport for persons or goods, plus some professional-use mobile machinery.
  • Specific device classes: Active implantable medical devices, photovoltaic panels, and some research-and-development equipment.

These exclusions are narrow, and medical devices are broadly in scope even though active implants are not. An industrial tool escapes only if it qualifies as large-scale.

How RoHS Compliance Affects Product Development, Teams

The directive determines which parts you can buy and what evidence suppliers owe you when market access is at stake. It also affects design reviews, broader compliance management practices, and post-market record keeping.

What Penalties and Market Consequences Follow RoHS Non-Compliance

Member states set their own penalties, so consequences vary by jurisdiction, but the risk a non-compliant product carries for a development team typically includes:

  • Regulatory fines: Product-level and company-level financial penalties, set independently by each member state.
  • Individual liability: Personal exposure for directors or officers tied to the non-compliant product.
  • Market access loss: A non-compliant product cannot carry the CE marking, which blocks entry to the EU market outright.
  • Customs delays: Import holds or required corrective action at the importer’s expense.
  • Enforcement action: Authorities can order recalls, and competitors may use local enforcement channels to challenge non-compliant products.

These consequences reach past legal exposure into schedule and supply chain risk, which is why penalty exposure belongs in development planning rather than a post-launch legal review.

How to Build RoHS Compliance Into Your Development Process

The technical-documentation route to compliance depends on collecting trustworthy substance data and testing where trust runs out, with a coherent technical file tying the record together. Each step works best planned during development, not reconstructed after launch.

Collect Material Declarations From Suppliers

Standardized material-declaration formats exchange substance data across the supply chain. Declaration levels range from a basic compliance query and reply up to a Full Material Disclosure (FMD) that reports substance identity and mass by homogeneous-material location. FMD gives original equipment manufacturers (OEMs) reusable substance data, so teams with FMD data already have the answer when a new substance is restricted, while teams with untracked chemistry must reopen supplier outreach.

A stronger declaration is signed by an authorized individual at the supplier and states the worst-case concentration of any RoHS substance per homogeneous material, without disclaimers. Statements of “no intentional use,” or claims that parts were “screened” for compliance, may not meet technical-documentation expectations. Every component substitution should trigger a fresh declaration.

Test Components at the Homogeneous Material Level

A typical electronic product has too many homogeneous materials to test all of them. Teams screen risk-ranked materials using X-ray fluorescence (XRF) spectrometry to check the restricted metals and brominated substances it can detect. Results fall into pass, fail, or an inconclusive band that goes to a confirmatory lab.

XRF has limits for organic substances made of light elements, so plastic parts may need other analytical methods such as infrared spectrometry or gas chromatography-mass spectrometry. Where supplier data is complete and traceable, the documentation route can replace much of this testing.

Document Compliance Through Technical Files and DoCs

Those records need to tie evidence to the exact material, part, or sub-assembly they cover. The technical file should include:

  • Product description: A general description of the product with model, manufacturer, and category information.
  • Material documentation: Supplier declarations, certificates of compliance, and test reports tied to a bill of materials (BOM) with substance identity.
  • Mapping information: Records connecting each document to the specific materials, parts, or sub-assemblies it covers.
  • Standards and risk records: The harmonized standards applied and the risk assessments behind each documentation decision.

The risk assessment determines how much evidence each part needs, using the same failure mode and effects logic teams already apply elsewhere in development. The probability that restricted substances are present, weighed against supplier confidence, decides whether a declaration alone suffices or a recent analytical test report is required.

The DoC follows the directive’s model. It uniquely identifies the EEE, names the manufacturer, declares conformity with Directive 2011/65/EU under the manufacturer’s sole responsibility, and references the harmonized standards used, with product-specific exemptions listed as recommended practice. Manufacturers must retain the full technical file for the required post-market record-keeping period.

Manage RoHS Exemptions for Restricted Substances

RoHS exemptions apply across different equipment categories, and the exemption system changes because exemptions expire unless renewed. Some lead-related exemptions have been narrowed or replaced by more specific sub-exemptions, while others have been renewed with shorter transition periods and new conditions.

Renewal applications must be filed 18 months before expiry, and a planned transfer to the European Chemicals Agency (ECHA) will change exemption processing. China’s 2026 catalogue expansion adds 23 product categories to its own conformity assessment system starting August 2027, on top of the EU exemption calendar. Engineering teams need a live map of which BOM lines depend on which exemption, and when it expires, because compliant products can lapse without warning.

Common RoHS Compliance Challenges for Engineering Teams

RoHS compliance gaps trace back to recurring structural pressures rather than a single design mistake. Supplier depth, regulatory change, and overlapping regulatory regimes create most of the RoHS gaps engineering teams encounter.

Tracking Substance Data Across Multi-Tier Supply Chains

Even a modest assembly can contain chemicals across materials sourced through multiple supplier tiers. Deeper tiers may not know which substances are declarable. Substance data can end up fragmented across product lifecycle management (PLM) and enterprise resource planning (ERP) systems.

Silent part substitutions compound the problem, since a weak change control process description can miss process or supplier-tier changes entirely. Testing can also uncover issues in overlooked small parts and accessories, and any one of them can fail the entire product.

Keeping Up With RoHS 2 and RoHS 3 Recast Changes

RoHS 2 changed the obligation by adding CE marking, the DoC, the technical file, and economic operator duties, then expanded scope after a phase-in period. “RoHS 3” is informal shorthand for the delegated update that restricted the four phthalates, which means parts qualified years ago may no longer comply.

Reconciling RoHS With Registration, Evaluation, Authorization and Restriction of Chemicals (REACH), Waste Electrical and Electronic Equipment (WEEE), and Other Regional Rules

RoHS and REACH use related threshold concepts but assess products differently.RoHS assesses homogeneous materials, while REACH assesses articles.

Some phthalates restricted by RoHS can also trigger REACH obligations. Where the two overlap, the strictest limit applies. WEEE rules cover the same products at end of life. Outside the EU, substance lists tend to match up, but procedures don’t. South Korea’s K-RoHS is expanding from about 50 product categories to nearly all EEE, and other markets are building their own certification and conformity systems rather than copying the EU’s approach.

How Jama Connect Supports RoHS Compliance

Multi-tier supply chains, recast changes, and overlapping regional rules all create the same underlying problem: siloed requirements and verification records make trace gaps hard to see during development. Jama Connect®, a web-based requirements management and traceability platform for complex, regulated product development, helps teams model RoHS obligations in the same trace network as product requirements, closing those gaps before they reach an auditor. Teams can capture substance restrictions and exemption dependencies as requirements, then use Live Traceability™ to see upstream and downstream relationships across integrated tools, including the PLM and ERP systems where substance data tends to fragment across supplier tiers. Teams can also build and execute verification and validation test plans directly in Jama Connect’s Test Center, keeping test cases, pass/fail results, and defects linked to the substance requirements they verify rather than tracked in a separate tool.

When an upstream requirement changes, every linked downstream item is flagged as suspect, so a revised substance limit, a RoHS 3 phthalate restriction, or an expiring exemption surfaces in the component specifications and verification activities it touches. Traceability Information Models (TIMs) define required relationships, so a compliance requirement with no linked verification appears as a coverage gap during development rather than an audit finding. Because those requirements sit in one trace network rather than separate REACH, WEEE, and regional compliance trackers, teams can check a substance against multiple regimes from a single record. Jama Connect baselines capture project state at a single point in time, and workflows track comments and states throughout the review process.

Keep RoHS Compliance Evidence Ready for Change

RoHS compliance keeps moving under products that were compliant on day one, as exemptions expire and other markets add their own conformity mechanisms on top of the EU calendar. Jama Connect keeps supplier evidence, test reports, and exemption status linked to the requirements and BOM lines they cover, so a lapsed exemption shows up as a gap during development instead of during an audit.

Bring your own BOM and supplier evidence into a trial to see those gaps before an auditor does. Start a free trial of Jama Connect to test a traceable RoHS workflow.

Frequently Asked Questions About RoHS Compliance

What is the difference between RoHS 2 and RoHS 3?

RoHS 2 is Directive 2011/65/EU, a full legal recast that introduced CE marking, the DoC, technical file duties, and defined roles for manufacturers, importers, and distributors. “RoHS 3” is the informal name for the later delegated amendment that restricted four phthalates, so supplier documents citing “RoHS 3” are claims against Directive 2011/65/EU as amended. A certificate referencing RoHS 3 in one document while excluding phthalates in another is a recognized audit red flag.

Is RoHS compliance mandatory outside the EU?

The EU directive applies only in the EU, but jurisdictions outside it run their own versions. Substance lists often overlap, while scope, marking, and conformity mechanisms differ by jurisdiction. Some regimes accept self-declaration, while others require third-party certification or product-specific reporting.

How often should suppliers update material declarations?

Suppliers should refresh declarations on a regular cadence and issue a new one with every component or process change. Re-review cadence works better tied to regulatory calendar dates, since REACH Candidate List updates and RoHS exemption expirations follow their own timetables. Suppliers providing FMD data cut this burden, because existing substance data can be re-checked against new restrictions without a fresh outreach cycle, much like supply chain collaboration formats reduce redundant exchange elsewhere. Jama Connect can help keep supplier declarations linked to the requirements and verification records they support.

What happens during a RoHS compliance audit?

A market surveillance authority may request the technical file and check whether the DoC, supplier declarations, test reports, and exemption justifications build an audit trail that holds together. Common findings include declarations with disclaimers or “no intentional use” language, references to expired exemptions, and conflicts between certificates and test reports. In Jama Connect, linked compliance requirements, supplier evidence, verification results, and review records can make that chain easier to assemble. Documentation gaps can still create market-access risk, even when the underlying substances are not the issue.

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

Book a Demo

See Jama Connect in Action!

Our Jama Connect experts are ready to guide you through a personalized demo, answer your questions, and show you how Jama Connect can help you identify risks, improve cross-team collaboration, and drive faster time to market.