ESPR Conformity Assessment: How You Prove It, Not Just What You Must Do

Most of the ESPR conversation focuses on what the regulation demands - durability parameters, recycled content thresholds, Digital Product Passport data fields. Far less attention goes to the procedural question that market surveillance authorities will actually ask first: how did you demonstrate it?

That is the conformity assessment chain. It is the mechanism by which a manufacturer converts design choices and test results into a legally defensible statement that a product meets the applicable ecodesign requirements. This post is about that mechanism - not the substantive requirements, not the penalties for getting it wrong, but the procedural proof itself.

---

The two procedures ESPR provides

ESPR Article 20(1) requires manufacturers to follow the conformity assessment procedure set out in Annex VI or Annex VII, as specified in the applicable delegated act, to demonstrate that the product complies with the applicable requirements. There is no single ESPR-wide answer to which procedure applies - that is settled product group by product group, in each delegated act.

Annex VI - Internal production control is the simpler route. The manufacturer assesses compliance internally, without involving a notified body, implements internal production controls to ensure that products placed on the market conform to the technical documentation, and issues the EU Declaration of Conformity. It is the expected default for most product categories. Think of it as analogous to Module A under the New Legislative Framework: the manufacturer self-certifies, carries the full burden of evidence, and the DoC is the public-facing output of that process.

Annex VII - Management system is the more demanding route. It requires a documented quality management system covering product design, manufacturing, and testing. Where the delegated act requires it, that management system must be assessed and approved by a notified body, which then issues a certificate of conformity. The notified body's identification number must appear alongside the CE marking.

The critical point for planning purposes: you cannot choose your procedure. The delegated act for your product group specifies it. Until that delegated act is published, the procedure is not settled. What you can do is understand both routes well enough to prepare the underlying evidence regardless.

---

The technical documentation chain

Whether you end up under Annex VI or Annex VII, the technical documentation is the foundation. Under ESPR Article 23 and Annex IV, manufacturers must compile technical documentation demonstrating compliance with the applicable ecodesign requirements before the product is placed on the EU market.

That documentation must include, at minimum:

• A general description of the product and its intended use
• Design drawings and manufacturing information
• A list of harmonised standards applied (and, where standards are not applied, the solutions adopted to meet the requirements)
• Test reports demonstrating compliance with performance requirements
• Conformity assessment records
• Supplier declarations for materials and components
• A copy of the EU Declaration of Conformity

The technical documentation must be kept available for inspection by market surveillance authorities for a minimum of ten years after the last unit of the product model is placed on the EU market. The clock runs from the last unit placed on the market, not from the first sale date - so for active product lines, this is a rolling obligation, not a one-time filing.

Importers carry a related but narrower obligation: they are not required to hold the full technical file, but must retain a copy of the EU Declaration of Conformity and ensure it is accessible to authorities for ten years.

---

The EU Declaration of Conformity

The EU DoC is the formal output of the conformity assessment. Under ESPR Article 43 and Annex V, the EU Declaration of Conformity is the manufacturer's signed statement that the product complies with all applicable ecodesign requirements - and it may be embedded in the Digital Product Passport.

The DoC must identify the product, the manufacturer, the applicable delegated act, the conformity assessment procedure followed, the harmonised standards or other technical specifications applied, and the authorised signatory. It is a living document: if the product changes materially, the DoC must be updated.

One structural point worth noting: the DoC is the conclusion of the conformity assessment, not the evidence itself. Market surveillance authorities who want to verify a claim will look past the DoC to the technical file behind it. A signed DoC with no traceable evidence chain underneath it is not a defensible position.

---

CE marking under ESPR

ESPR Article 45 requires the CE marking to be affixed where the applicable delegated act specifies it. The CE mark must be visible, legible, and indelible on the product, its packaging, or accompanying documentation where physical affixation is not practicable.

The interaction with other CE regimes is a practical issue for many manufacturers. A product that already carries CE marking under, say, the Low Voltage Directive, the Radio Equipment Directive, or the Electromagnetic Compatibility Directive does not acquire a second CE mark when an ESPR delegated act applies to it. The single CE mark covers all applicable regimes simultaneously. What changes is the Declaration of Conformity: it must list every regulation under which the mark is affixed, and the technical documentation must address each regime's requirements separately.

For electronics manufacturers in particular, this means the ESPR conformity assessment sits alongside existing LVD and RED assessments - it does not replace them. The ecodesign requirements (durability, repairability, recyclability, substances of concern) are additive to the safety and radio requirements already in scope. The technical file grows; the CE mark does not multiply.

Where a delegated act requires Annex VII and a notified body is involved, that body's identification number must appear on the CE marking and in the DoC. Where Annex VI applies, no notified body number appears.

---

Harmonised standards and the presumption of conformity

Products that comply with harmonised standards published in the EU Official Journal are presumed to conform to the ecodesign requirements those standards cover. This is the standard New Legislative Framework mechanism, and it applies to ESPR in the same way it applies to other CE-marked product legislation.

For the Digital Product Passport specifically, the picture has recently sharpened. On 27 May 2026, CEN and CENELEC published the first six European Standards for the EU Digital Product Passport - the EN 1821x series - developed by joint technical committee CEN-CLC/JTC 24. These are horizontal standards: they define how a DPP identifies products, exchanges data, remains accessible over time, and operates consistently across systems. They do not specify which data fields each product group must carry - that remains in the delegated acts.

On 15 July 2026, the Commission cited EN 18216, EN 18219, EN 18220, EN 18221, EN 18222, and EN 18223 as harmonised standards in the Official Journal via Implementing Decision (EU) 2026/1736. A DPP built to these standards therefore carries a presumption of conformity with the technical infrastructure requirements of ESPR. Two further standards - prEN 18239 (security and access rights) and prEN 18246 (data authentication and integrity) - were under formal vote as of mid-July 2026 and are expected to complete the package.

For a deeper treatment of what each standard in the EN 1821x series does and how they fit together, see our dedicated post on the CEN/CENELEC DPP standards.

---

How the DPP changes the evidence picture

The Digital Product Passport is not merely a product information tool - it is part of what must be correct and verifiable for conformity purposes. ESPR Article 43 explicitly permits the EU Declaration of Conformity to be embedded in the DPP. That creates a direct link between the passport and the conformity chain: if the DPP data is inaccurate, the embedded DoC is inaccurate.

The EU DPP Registry became operational on 19 July 2026 under Article 13 of ESPR. The registry does not store passport data centrally - it routes unique product identifiers to the decentralised systems where passport data is hosted. But it is the mechanism by which market surveillance authorities, customs, and other authorised parties locate and verify DPP records. A product whose DPP identifier cannot be resolved via the registry is, in practical terms, non-compliant from the moment the registry is live.

This means the conformity file now has a digital dimension that did not exist under the old Ecodesign Directive. The technical documentation must support the DPP data, and the DPP data must be consistent with the technical documentation. Version control across both becomes essential: if you update a product's composition or performance data, both the technical file and the DPP must be updated in step.

For a full account of the registry's architecture and what the 19 July 2026 date means operationally, see our post on the EU DPP Registry.

---

What a defensible conformity file looks like today

Your delegated act has not landed yet. That does not mean there is nothing to do - it means the work you do now determines how quickly you can close the gap when it does.

Beyond the widget, here is what the artefact inventory looks like for a team building a defensible file before their delegated act is confirmed:

What to assemble now

Artefact	Owner	Common gap
Design drawings and manufacturing specs	Engineering / R&D	Outdated versions; no change log
Test reports per performance parameter	Quality / Lab	No lab accreditation record; standard version not specified
Supplier declarations (composition, substances)	Procurement	Tier-2 and tier-3 gaps; declarations not dated or version-controlled
Conformity assessment procedure record	Regulatory affairs	Not yet drafted; procedure not yet confirmed by delegated act
EU Declaration of Conformity (draft)	Legal / Regulatory	Template not prepared; signatory authority not assigned
DPP data set (draft)	Product / IT	Not linked to technical file; no version control
Harmonised standards list	Regulatory affairs	EN 1821x series not yet reviewed

The three gaps that recur most often

1. No supplier declaration trail. Manufacturers frequently hold declarations from tier-1 suppliers but have no visibility into tier-2 or tier-3 material composition. ESPR's substances-of-concern requirements will reach into that chain.

2. Untraceable test evidence. A test report that does not identify the accredited laboratory, the standard version tested against, or the specific product model it covers is not useful evidence. Market surveillance authorities will ask for all three.

3. No version control on product data. When a component changes, the technical file must change with it. Teams that manage documentation in email threads and shared drives routinely find that the file they can produce does not match the product currently on the market.

---

What is fixed now, and what only the delegated act will settle

It is worth being explicit about the boundary between what ESPR already determines and what remains open.

Fixed in the regulation today:

• The two conformity assessment procedures (Annex VI and Annex VII) and their structure
• The requirement for an EU Declaration of Conformity (Article 43, Annex V)
• The CE marking obligation where required (Article 45)
• The ten-year retention period for technical documentation and the DoC
• The content requirements for technical documentation (Annex IV)
• The DPP Registry operational date (19 July 2026)
• The EN 1821x harmonised standards for DPP technical infrastructure (cited in OJ 15 July 2026)

Only settled by the delegated act for your product group:

• Which conformity assessment procedure (Annex VI or Annex VII) applies
• Whether a notified body is required and, if so, which scope
• The specific ecodesign performance requirements to be demonstrated
• The DPP data fields that must be populated
• The compliance date from which the conformity assessment obligation bites

The practical implication: build the evidence infrastructure now, to the structure ESPR already specifies. When the delegated act arrives, you will be filling in the performance thresholds and procedure confirmation - not starting from scratch on the documentation architecture.