Unique product identity
The passport must be linked to a persistent unique product identifier. The applicable delegated act determines whether the passport applies at model, batch or individual-item level.
ESPR manufacturer briefing
Digital Product Passport Requirements for Manufacturers
A practical, regulation-anchored explanation of what ESPR requires, what product-specific rules must still define, and what manufacturers should build now.
Reviewed 15 September 2026Based on primary EU legislationGeneral guidance, not legal advice
The essential distinction
ESPR creates the framework. Product-specific measures activate the detail.
The Ecodesign for Sustainable Products Regulation—Regulation (EU) 2024/1781—establishes the EU framework for Digital Product Passports. It sets core principles for identity, data carriers, access, interoperability, security and availability.
However, it does not impose one identical passport on every product from one universal date. Delegated acts for particular product groups determine the exact dataset, passport level, data carrier placement, permitted actors, update responsibilities and application date.
Core ESPR architecture
Six requirements every DPP programme should be ready to support
Accessible data carrier
A suitable data carrier—such as a QR code or another automatic identification medium—connects the physical product, packaging or documentation to the passport.
Structured, interoperable data
Passport information must use open, interoperable formats and be structured, machine-readable and searchable where required.
Defined access rights
Different actors may receive access to different data. Public, customer, supply-chain, auditor and authority views need governed permissions.
Accuracy, integrity and security
The economic operator must ensure the required information is accurate, complete and up to date, with appropriate protection against unauthorised alteration.
Availability and continuity
Passport data must remain available for the period specified in the applicable product rules, including where a service provider changes or ceases trading.
What the delegated act decides
The product-specific rule is your final specification
Before implementation is treated as compliance-ready, the responsible team must confirm these decisions in the measure covering the product group:
- Which products and economic operators are in scope
- The application date and transitional arrangements
- Whether the passport is model, batch or item-level
- The mandatory information fields and formats
- Where the data carrier must appear
- Who can access each category of information
- Who may create or update each data element
- How long the passport must remain available
Data preparation
What data may be required in a Digital Product Passport?
There is no universal final dataset. ESPR and Annex III establish categories that product-specific measures can draw from. Manufacturers should prepare a governed data inventory across the following domains without assuming every field will apply.
Product identity
Product, model, batch or item identifier; product classifications; basic characteristics and relevant identifiers.
Economic operators
Manufacturer, importer, authorised representative or other responsible-party information where required.
Manufacturing context
Manufacturing facility or location identifiers when included by the product-specific rules.
Materials and substances
Material composition, substances of concern, recycled content and sourcing information where applicable.
Sustainability performance
Durability, repairability, recyclability, resource use, environmental or carbon-footprint information where required.
Compliance evidence
Declarations, certificates, test evidence, instructions and conformity-related documentation.
Lifecycle and circularity
Repair, inspection, refurbishment, ownership, reuse, recycling and end-of-life information where applicable.
Operating responsibility
Who is responsible for the passport?
Software supports the operating model; it does not transfer the economic operator’s legal accountability. Responsibilities must be assigned across the value chain and confirmed against the applicable measure.
Manufacturer or placing operator
Creates or ensures creation of the passport, provides required data and maintains the information for which it is responsible.
Importers and distributors
Verify relevant obligations and passport availability where the applicable rules assign duties to them.
Suppliers
Provide trustworthy material, component, certificate and process data needed by the responsible economic operator.
DPP service provider
Provides technical hosting, access, security, continuity and interoperability capabilities under the agreed operating model.
Authorities and other actors
Access the data permitted for their role and use the passport for market surveillance, service, repair or circularity activities.
Manufacturer action plan
Seven steps to prepare without overbuilding
- 1
Confirm legal scope
Map product groups, markets and economic-operator roles. Track adopted delegated acts—not headlines or draft timelines.
- 2
Choose a pilot family
Select one representative product with real data, suppliers, evidence and a realistic lifecycle.
- 3
Define identity level
Prepare model, batch and item-level options until the applicable rule confirms the required passport level.
- 4
Build a data dictionary
Define each field, format, owner, source system, evidence, update frequency and access class.
- 5
Map systems and suppliers
Identify data held in ERP, PLM, PIM, MES, spreadsheets, document stores and supplier systems.
- 6
Design governance
Assign accountable owners, validation rules, publication approvals, corrections and retention responsibilities.
- 7
Test the complete chain
Validate product → identifier → data carrier → passport → role-based access → evidence → lifecycle update.
Assess your current readiness
Use the 30-point checklist to identify gaps in scope, data, identity, evidence, governance, systems and pilot planning.
Common questions
Digital Product Passport requirements FAQ
When do Digital Product Passport requirements become mandatory?
There is no single ESPR deadline for every product. ESPR establishes the framework, while product-specific delegated acts set the affected products, detailed requirements and application dates. Separate legislation, including the EU Battery Regulation, has its own timetable.
Which products will require a Digital Product Passport?
The answer depends on adopted product-specific measures. The ESPR working plan indicates priority product groups, but a working-plan priority is not itself a final legal obligation. Manufacturers should monitor the legislation that applies to their exact products.
What data must a Digital Product Passport contain?
The final dataset is defined by the relevant delegated act. ESPR provides a framework and possible information categories, including product identifiers, operator information, sustainability and circularity information, compliance documentation and other product-specific data.
Must the passport be created for every individual item?
Not necessarily. The applicable delegated act can specify the passport at model, batch or item level. The architecture should support the required level without duplicating or losing product history.
Does using DPP software guarantee ESPR compliance?
No. Software can provide the identity, data, evidence, access and governance infrastructure, but compliance also depends on applicable law, product design, data accuracy, supplier evidence and the economic operator’s processes.
Can commercially sensitive information remain restricted?
Yes, where the applicable rules provide differentiated access. A credible DPP architecture should expose only the information each stakeholder is permitted to see.
From requirements to pilot
Build a configurable, evidence-backed DPP foundation
UniQorn Trace™ connects product identity, structured data, evidence, permissions and lifecycle events for B2B manufacturers preparing for evolving product-passport requirements.
Primary legal source
See Regulation (EU) 2024/1781, particularly Articles 9–11 and Annex III. Always verify the current consolidated text and the delegated act applicable to your product.