ESPR vs REACH and RoHS Ecodesign, DPP, and substance controls

ESPR targets the environmental sustainability of products placed on the EU market through product-group ecodesign requirements. The Commission overview describes ESPR as extending ecodesign beyond energy-related products and improving circularity, energy performance, recyclability, and durability.

REACH and RoHS are treated here as substance-control comparators only. The grounding cites REACH as Registration, Evaluation, Authorisation and Restriction of Chemicals and cites RoHS as restricting certain hazardous substances in electrical and electronic equipment.

Do not use a REACH or RoHS substance review as proof that ESPR ecodesign requirements are met, and do not use ESPR sustainability evidence as proof of a REACH or RoHS result without a separate source.

ESPR evidence normally sits with product compliance, engineering, sustainability, supply-chain data owners, and the economic operator placing the product on the EU market or putting it into service when a delegated act applies.

The grounding does not support a detailed REACH/RoHS actor map. Keep REACH and RoHS ownership with the team that already controls chemical, supplier-material, and electrical/electronic hazardous-substance evidence.

Name separate owners for ESPR product-sustainability evidence and substance-control evidence, then add a shared data owner only for fields that appear in both evidence packs.

ESPR action starts when a product group is covered by an ESPR delegated act or related ESPR requirement. The delegated act determines the specific product parameters, methods, DPP data, and conformity evidence to prepare.

For REACH/RoHS, this page can only flag that a separate substance-control trigger may exist. The grounding does not provide product-specific REACH tonnage, candidate-list, RoHS category, exemption, or threshold rules.

Use the ESPR delegated act as the ESPR trigger source and a separate REACH/RoHS source for substance triggers; do not infer one trigger from the other.

ESPR delegated acts may set performance requirements, information requirements, or both. The regulation links those requirements to product parameters such as durability, repairability, energy efficiency, recyclability, carbon and environmental footprints, and substances-of-concern information.

REACH and RoHS obligations are not expanded in this grounding set. Keep them limited here to chemical registration/evaluation/authorisation/restriction context and restriction of certain hazardous substances in electrical and electronic equipment.

Build the ESPR workplan around sustainability performance, information, DPP, and conformity outputs; keep chemical-control conclusions in a separate REACH/RoHS workplan.

ESPR evidence should connect the applicable delegated act, technical documentation, measurements against ecodesign requirements, information provided under information requirements, declaration of conformity, DPP fields, and market-surveillance response process.

REACH/RoHS evidence is source-limited in this file. Keep any substance declarations, supplier material data, SCIP or ECHA references, and RoHS files in the substance-control record set unless a grounded ESPR requirement asks for the same data in the DPP.

Create a crosswalk field by field: source, product scope, data owner, date/version, public or restricted DPP access, and whether the evidence supports ESPR, REACH, RoHS, or only an internal material review.

ESPR timing depends on the relevant delegated act and product group. DPP design guidance repeatedly points teams back to the specific delegated act for information requirements, access, and update expectations.

The grounding folder does not support REACH or RoHS deadline calendars for this page. Avoid adding REACH registration dates, RoHS transition dates, exemption expiries, or penalty clocks here.

Track ESPR delegated-act dates and REACH/RoHS substance-control dates in separate calendars; merge reminders only after the source, product scope, and evidence owner match.

ESPR assurance runs through technical documentation, declarations of conformity, conformity marking where required, market surveillance, corrective action, and Member State penalties for infringements.

The grounding does not provide REACH or RoHS enforcement detail. Keep any enforcement comparison limited to the fact that REACH/RoHS are separate substance-control regimes and verify enforcement facts from their own source set before publication.

For reviews, ask two questions: does the product satisfy the ESPR delegated act and evidence model, and has the separate substance-control owner validated REACH/RoHS status from its own sources?

Use ESPR when the decision concerns product sustainability performance, product information, DPP data, conformity documentation, public or restricted product information access, or market surveillance under an ESPR delegated act.

Use REACH/RoHS only for the separate chemical or hazardous-substance question, and use a dedicated REACH/RoHS source before stating thresholds, exemptions, dates, categories, penalties, or product-specific restrictions.

If both lanes touch the same product data, publish only the claim each source supports: ESPR for ecodesign/DPP information, REACH/RoHS for substance-control status, and a crosswalk for shared fields.

ESPR can require tracking and communication of substances-of-concern information as sustainability information across a product life cycle, including support for decontamination and recovery when products become waste.

ESPR itself says it should not restrict substances primarily for chemical-safety reasons because other Union chemicals law addresses that function. RoHS remains a separate hazardous-substance restriction regime for electrical and electronic equipment in the limited grounding available here.

Treat ESPR substance fields as sustainability and lifecycle information unless a source shows a product-specific restriction; keep chemical-safety restriction decisions in the REACH/RoHS lane.