EPREL or Digital Product Passport: Where Should the Record Go?
Route an EU product-data question by product scope, legal instrument, data object, system and update event instead of treating EPREL and the ESPR passport as one database.
Signals to watch
- A supplier asks for a digital passport upload when the named product is currently governed by an energy-labelling EPREL registration duty
- A buyer treats the ESPR framework as if one universal passport schema and production registry already applied to every product
- Model identifiers, supplier role, placing-on-market date, public and restricted data, and the owning system are missing from the request
Use EPREL when the question concerns a covered energy-related product, its energy-labelling delegated act and the supplier’s product-database record. Use the ESPR digital product passport sources when a product-specific ESPR measure requires a passport and defines its data, carrier, access and update rules. Do not route by the words “product database” or “passport”; route by product scope, legal instrument, actor, data object and event.
This source-navigation answer is for a product-data service lead reading authorised energy-labelling, appliance, sustainability and product-data Telegram groups. “Need EU passport registration for new model” can be worth reviewing while the integration route is still open. It still does not reveal whether the model belongs in the European Product Registry for Energy Labelling (EPREL), a future ESPR passport, both through distinct duties, or neither.
Route 1: EPREL starts with an energy-labelling product group
Regulation (EU) 2017/1369 establishes the energy-labelling framework and its product database. Article 12 creates public and compliance parts, while Annex I lists the information to be stored. Product-specific delegated acts determine which products need labels and product information.
The EPREL interface is the operational entry point, and the Commission’s supplier information page explains supplier registration and product-model handling. A request should name the product group, delegated act, supplier, model identifier and date before the model is placed on the market.
EPREL is not a generic sustainability repository. It supports energy-labelling duties for covered groups. A model-registration error therefore needs the EPREL record, product-group rule and supplier account context, not a general passport strategy deck.
Route 2: ESPR defines a passport framework, then product acts activate it
Regulation (EU) 2024/1781, the Ecodesign for Sustainable Products Regulation (ESPR), establishes the digital product passport framework. Articles 9 to 12 address passport requirements, technical design and access, while Article 13 establishes a digital product passport registry.
That framework does not mean every product already has the same live passport obligation. A product-specific delegated act must identify the covered products, required data, data carrier, unique identifiers, access rights and applicable date. The Commission work plan and later acts matter, but a planned priority is not itself a filing duty.
The correct ESPR source chain is therefore: framework Regulation, current working-plan or preparatory source for context, adopted product-specific delegated act, technical standards or implementing rules where applicable, and the operational registry or interface when available for that duty.
EPREL and DPP compared by the question being asked
| Question | EPREL route | ESPR digital product passport route |
|---|---|---|
| Product scope | covered energy-labelling product group | product covered by an applicable ESPR delegated act |
| Primary legal source | Regulation 2017/1369 plus product delegated act | Regulation 2024/1781 plus product-specific ESPR act |
| Responsible actor | supplier as defined by energy-labelling law | economic operator identified by the product-specific rule |
| Data object | supplier and model information for public/compliance database parts | passport data set, identifiers, carrier and access rules |
| Operational system | EPREL supplier and public interfaces | DPP registry and relevant product/passport infrastructure as activated |
| Trigger | placing a covered model on the market, model/data change or correction | product-specific placing-on-market or other event defined by the act |
Neither column is a vendor-feature comparison. It is a legal-source and system router.
Five fields decide the route
Product. Capture the exact product group, model or family and intended EU market. “Appliance” is too broad.
Instrument. Name the framework and the product-specific act. Preserve its version and application date.
Actor. Identify supplier, manufacturer, importer, authorised representative or another economic operator. Do not transfer account duties because two entities share a brand.
Data object. Separate label parameters, product information sheet, technical documentation, passport data, unique identifiers and evidence behind each field.
Event. Record first placing on the market, model revision, data correction, ownership change, end of availability or another legal update event. A ticket without an event cannot establish priority or deadline.
These fields form the source-routing card. If any field is unknown, the service proposal should include discovery rather than promise a completed registration.
Example: one “passport correction” belongs in EPREL today
Illustrative composite, not a customer story: an authorised appliance group says, “EU passport has wrong annual consumption; launch next week.” A reply mentions an energy label, but no product-specific ESPR act or passport identifier.
The source clue points first to the energy-labelling route. The service lead asks for the product group, model identifier, EPREL record, delegated act, supplier and controlled test data. A broader ESPR data-readiness project may still be useful, but it should not replace the immediate EPREL correction or be sold as a live DPP filing without an applicable product rule.
The digital product passport pilot article explains how to recognise an early project without inventing a filing duty. The EU battery-passport data-owner handoff shows a product-specific ownership problem. When a forwarded claim lacks a stable legal source, use the official-source ladder.
Discovery must stop before registry access
Top Prospect can preserve relevant fragments from authorised Telegram sources the user has connected, including source, time and review context. The current matching-target interface saves configuration but does not automatically create new candidates. It cannot access EPREL supplier accounts, create a passport, change product records or determine that a delegated act applies.
The product-data service lead uses the fragment to choose the official route and ask for identifiers. The supplier, responsible economic operator and qualified advisers approve the record and any submission.
Key facts
- EPREL is the energy-labelling product database for covered product groups; it is not the general ESPR passport registry.
- ESPR creates a DPP framework, but product-specific acts determine coverage, data and dates.
- The same model data may feed several systems, yet field meaning, access and update events can differ.
- Product, instrument, actor, data object and event are the five routing fields.
- A Telegram message can expose a source-routing problem but cannot establish a registry duty or change a record.
FAQ
Is EPREL the EU digital product passport registry?
No. EPREL implements energy-labelling database duties; ESPR establishes a separate broader passport framework and registry architecture.
Does every product already need an ESPR passport?
No. Coverage and timing depend on an applicable product-specific act.
What should an EPREL request identify first?
The product group, delegated act, supplier, model identifier and placing-on-market date.
Can data be reused between the systems?
Possibly, but definitions, identifiers, access rights, evidence and update triggers must be mapped field by field.
Editorial review completed 22 August 2026 against Regulation (EU) 2017/1369, Regulation (EU) 2024/1781, EPREL and current European Commission supplier material. Qualified energy-labelling, ecodesign, product-data and legal specialists must confirm product coverage, actor, date and system route.
Frequently asked questions
Is EPREL the EU digital product passport registry?
No. EPREL is the product database established under the Energy Labelling Framework Regulation for covered product groups. ESPR establishes a broader digital product passport framework and registry architecture for products covered by product-specific measures.
Does every product already need an ESPR digital product passport?
No. The obligation and required data depend on applicable product-specific delegated acts and their dates.
What should an EPREL request identify first?
Identify the product group, applicable energy-labelling act, supplier role, model identifier and placing-on-market date, then determine the registration and update fields.
Can the same data be reused in EPREL and a future passport?
Some controlled product data may overlap, but field definitions, identifiers, access rights, legal purpose, update events and system interfaces must be mapped rather than assumed identical.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
