DPP vs EPREL: Does EPREL Replace, Feed or Sit Alongside a Digital Product Passport?

EPREL can reduce duplicate DPP data, but it is not simply the DPP. See current law, the June 2026 proposal and safe data-reuse boundaries.

Last verified: 3 September 2026

LinkedIn X Email

Navigate this page

Overview
EPREL and the DPP are related, not identical
What EPREL already contains
What current DPP law says about alternative systems
What the June 2026 EPREL proposal would change
Which EPREL data is a good candidate for reuse?
Model data and item data need different treatment
Do not turn a label PDF into your master data
A practical EPREL-to-DPP operating model
The common misconception
Direct answers
Primary official sources
Keep exploring

EPREL does not simply become the Digital Product Passport. But the EU is now explicitly designing the two systems so equivalent model data does not have to be reported twice. Today, EPREL is the European Product Registry for Energy Labelling used for product models covered by the energy-labelling framework. The ESPR establishes the DPP framework and allows another Union digital system to stand in where the Commission considers it achieves the relevant DPP objectives. The Commission's 2025 ESPR working plan names EPREL as the example.¹² In June 2026, the Commission went further. Its proposal COM(2026) 565 would apply a once-only principle so products for which EPREL provides equivalent information do not have to be registered again for that equivalent information in the DPP Registry. It proposes interlinking EPREL's central administrative and common model information with item-level DPP Registry information.³ That proposal is not yet adopted law. EUR-Lex lists procedure 2026/0169/COD as ongoing as at 3 September 2026.⁴ So the current business answer has two layers:

Build for reuse now: govern model data so EPREL and a DPP can draw from the same controlled facts.
Do not hard-code the proposed legal shortcut yet: the once-only/interlinking amendments can still change before adoption.

Question	EPREL	Digital Product Passport / DPP Registry
Main role	Product database for energy-labelling rules, with public product information and a compliance layer	Product-information framework under ESPR and sector rules; the Registry registers DPP identifiers and metadata
Typical object	Product model	Model, batch or item, as the applicable DPP rule specifies
When registration happens	Suppliers register in-scope models before the first unit is placed on the market	DPP availability and Registry registration follow the applicable DPP legislation
Public data	Public model information, labels and product information	DPP data accessible according to the access rights and content specified by the applicable act
Authority-only / restricted data	EPREL compliance information	DPP can also have access-restricted data depending on the legal design
Central vs decentralised	EPREL is a central Commission product database	The DPP system is decentralised for substantive passport data; the central Registry holds the identifier and associated metadata
Relationship under current ESPR framework	Can be an alternative Union digital system where it provides equivalent information	ESPR allows exemption from DPP where another Union system achieves the relevant objectives
June 2026 proposal	Would be interlinked with DPP Registry and support once-only reuse of equivalent model information	Would avoid duplicate registration/reporting for equivalent EPREL information

That last row is the part most likely to be misread. The Commission is proposing interlinking and avoidance of duplicate reporting. It is not saying every EPREL record is automatically a complete DPP for every product and every level.

What EPREL already contains

The Commission's supplier guidance says suppliers must register product models in EPREL before the first unit of a model covered by the energy-labelling rules is placed on the EU market. EPREL separates public model information from a compliance system used by authorities.⁵

The public record is designed to help purchase choice and includes information used to generate the energy label and product information. As of 20 July 2026, suppliers can also add a commercial name, GTIN and model picture to registered models.⁵

That makes EPREL unusually useful for DPP preparation because several identity and model-level values already exist in structured form.

It does not make every EPREL field portable without a test.

What current DPP law says about alternative systems

Article 9 of the ESPR allows the Commission to exempt a product group from the DPP requirement where other Union law includes a digital information system the Commission considers achieves the relevant DPP objectives.²

The Commission's 2025-2030 ESPR working plan makes the intended direction clearer: products subject to ecodesign measures will have a DPP except where an alternative digital system provides equivalent information, and it gives EPREL for energy-labelled products as the example.¹

The July 2026 DPP Registry implementing regulation also anticipates EPREL integration. Its recitals and technical design aim to prevent unnecessary duplication where systems are integrated, while its semantic repository provides machine-readable DPP data models and definitions.⁶

So the legal architecture already expects coexistence and interoperability. The exact operational relationship for a particular product still depends on the applicable product rules.

What the June 2026 EPREL proposal would change

COM(2026) 565 is unusually explicit about the problem businesses care about: double registration.

The Commission proposes that where EPREL provides information equivalent to information required under an ESPR delegated act, that equivalent information should not have to be registered again in the DPP Registry. It also proposes a technical link between:

EPREL's central administrative information
common model-level information in EPREL
item-level information in the DPP Registry.³

The impact assessment describes the economic objective in the same terms: information already in EPREL should not need to be re-entered into the DPP system, with the databases linked instead.⁷

That is a strong direction of travel. It is still a proposal. The correct status line on 3 September 2026 is ongoing ordinary legislative procedure.⁴

Which EPREL data is a good candidate for reuse?

Candidate fact	Reuse position	Why
Supplier / operator identity	Can reuse with role checks	The same organisation may appear in both systems, but its legal role must match the target record
Brand / trademark	Can reuse	Stable model identity data, provided the same brand/trademark definition is being used
Model identifier	Strong reuse candidate	EPREL is model-centric and the model identifier is fundamental to its record
GTIN	Can reuse where present	EPREL now allows GTIN; it still has to identify the same object and level used by the DPP
Commercial name	Can reuse with caution	Useful identity data but not necessarily a legally unique identifier
Model picture	Can reuse for presentation	Useful for identification, but not a substitute for the regulated identity fields
Energy / performance values	Depends on DPP requirement	Reuse only if the target DPP definition, method, unit and model scope are equivalent
Energy label / product information sheet	Reference or render from governed values	The artefact is not necessarily the underlying source of truth for every value
EPREL registration record / number	Keep as its own system record	It identifies EPREL status; it does not by itself make the DPP Registry entry
Authority-only technical data	Do not expose by default	Access rights and confidentiality remain part of the system design

The semantic point is more important than the field list. If EPREL stores annual energy consumption under a product-group method and a future DPP asks for a similar-looking energy field under another definition, the labels matching is not enough. Method, unit, reference conditions and model scope all need to match.

That is the same problem covered more generally in what does not map cleanly into a DPP.

Model data and item data need different treatment

EPREL is fundamentally a model register. DPPs can be model, batch or item level depending on the applicable law.²⁵

This is exactly why the Commission's 2026 proposal talks about common model-related EPREL information being interlinked with item-level DPP Registry information.³

A practical system should therefore avoid cloning one EPREL record into every item passport. Instead:

govern the common model facts once
let each item or batch reference the relevant model layer where the DPP design permits it
store item-specific events or serial information separately
preserve the EPREL registration as its own external record
render only the data that the target DPP is allowed and required to show.

For the underlying hierarchy, see model, variant and SKU facts.

Do not turn a label PDF into your master data

One easy implementation mistake is to scrape the EPREL label or product-information PDF and treat that artefact as the source of truth.

That is backwards. The label is a rendered output of structured model data and regulated calculation rules. If the same values are needed elsewhere, the stronger architecture is to govern the underlying data and provenance, then produce EPREL, DPP and customer-facing outputs from it.

That reduces two common problems:

a value gets rounded or reformatted in one output and the rounded version is then copied elsewhere
nobody can tell whether a later correction should change EPREL, the DPP, both or only one.

The operating principle is the same as owning a published field: a published value needs a traceable owner and source, not just a place where somebody once saw it.

A practical EPREL-to-DPP operating model

1. Keep one governed model identity

Maintain brand/trademark, commercial name, model identifier, GTIN where used and operator identity as controlled facts with their source and status.

2. Preserve EPREL as a separate regulatory record

Store the EPREL model record identifier, registration status and timestamps as system-specific metadata.

3. Separate common model facts from unit-level DPP facts

Do not duplicate model data into every item record in your internal architecture unless the downstream interface genuinely requires it.

4. Map against the legal DPP data model

When a product-specific DPP rule arrives, compare EPREL fields to the actual DPP semantic definitions. Mark each as CAN REUSE, TRANSFORM, REFERENCE ONLY or NOT EQUIVALENT.

5. Keep access rights attached

A value sitting in EPREL's compliance layer is not automatically public because a DPP exists. Treat access class as part of the data, not as a page-design decision.

6. Watch the 2026 proposal rather than coding it as settled law

Design the integration so the once-only link can be adopted without rebuilding your model, but keep the legal workflow configurable until the final text is adopted and operational details are published.

The common misconception

"EPREL is the DPP for energy-labelled products, so we can ignore the DPP system."

That is too broad.

The current framework allows an alternative digital system such as EPREL to avoid a separate DPP where the legal conditions are met, and the Commission is proposing much tighter once-only interlinking. But the applicable product rule still determines what information is required, at what level and through which system.

The safe business interpretation is:

Use EPREL as a high-value existing regulatory dataset. Reuse equivalent model facts. Keep EPREL's record and the DPP/Registry record distinct in your architecture until the applicable law explicitly joins them.

For tyres, where the live estate already owns the sector-specific reuse question, see EPREL data reuse for tyre DPPs. For broader electronics context, see ICT and electronics DPPs.

Direct answers

Does EPREL replace a DPP?

Sometimes EPREL may serve as the alternative Union digital system for equivalent information under the ESPR framework, but there is no universal rule that every EPREL record is a complete DPP. Check the applicable product legislation.

Will EPREL feed the DPP Registry?

The Commission's June 2026 proposal would interlink EPREL's central and common model-level information with DPP Registry information and apply a once-only principle to equivalent data. As at 3 September 2026, that proposal remains in an ongoing legislative procedure.

Do suppliers have to enter the same data twice?

The policy direction is explicitly to avoid duplicate entry of equivalent model information. Do not assume the proposed exemption is already final law. Build your internal data so one governed value can feed both systems while you wait for the final legal and technical implementation.

Can a GTIN from EPREL be reused in a DPP?

Yes, where it is present and identifies the same object at the same level. EPREL has allowed suppliers to add GTIN to registered models since 20 July 2026.⁵

Is EPREL the source of truth for every DPP field?

No. It is an official model register for a particular regulatory purpose. A DPP can require different or additional facts and may operate at batch or item level.

Keep exploring

Next question: If several EU systems hold overlapping product facts, which value should the business govern once and which records must stay separate?

Does this reach your products?

Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.

Check a product How a value is decided

Help someone else make sense of product passports.