A Digital Product Passport is a structured digital record linked to a physical product through a data carrier. Under EU rules, it gives consumers, businesses and authorities access to defined product, sustainability and compliance information. Exact data fields, passport granularity and start dates are set product by product — not by one universal deadline.
What is a Digital Product Passport?
The EU describes the DPP as a digital identity card for products, components and materials. It connects a unique product identifier to information that different users need across a product’s lifecycle.
The passport is not a single EU database containing every product file. The intended architecture is decentralised: the responsible company or a service provider maintains the passport data, while defined identifiers and metadata are registered centrally. Access rights can differ for consumers, commercial partners, repairers, market-surveillance authorities and customs.
Why is the EU introducing DPP?
The DPP is an information layer for the EU’s circular-product policy. Its purposes include making sustainability claims verifiable, supporting repair and recycling, improving supply-chain information and helping authorities check compliance.
For businesses, this turns product data into regulated infrastructure. Information that may currently sit across ERP, PIM, PLM, laboratory files and supplier spreadsheets must be connected to a stable product identity and kept available for the required period.
What information does a DPP contain?
There is no universal DPP field list. The ESPR defines the framework; each product-specific act determines the required data. Depending on the product, fields may cover:
- product, model, batch or item identity;
- manufacturer and responsible economic operator;
- materials, substances of concern and recycled content;
- performance, durability and repair information;
- environmental indicators and supporting documentation;
- conformity documents, instructions and end-of-life guidance;
- lifecycle events or other sector-specific information.
Which products require a DPP?
The ESPR can establish DPP requirements for a broad range of physical goods placed on the EU market, but obligations are activated through product-specific rules. The Commission’s 2025–2030 working plan prioritises work including iron and steel, aluminium, textiles and apparel, furniture, tyres and mattresses, alongside horizontal measures.
Batteries are the clearest near-term case under separate sector legislation. From 18 February 2027, the EU Battery Regulation requires a battery passport for each LMT battery, each industrial battery above 2 kWh and each electric-vehicle battery placed on the market or put into service.
When does DPP become mandatory?
There is no single date when every company needs a DPP. A practical timeline has three layers:
- Framework: the ESPR entered into force in July 2024.
- Infrastructure: the European Commission launched the DPP Registry and a testing environment on 20 July 2026.
- Product obligations: sector or delegated acts specify affected products, data, granularity, transition periods and application dates.
See the DPP deadlines guide for the difference between adopted dates and planning milestones.
How does a DPP work?
A typical flow starts when an economic operator assigns the required unique identifier, assembles validated product data and publishes the passport through its own system or a DPP service provider. The identifier and required metadata are registered, and a data carrier is placed on the product, packaging or accompanying documentation as the applicable rule requires.
When someone scans or resolves that carrier, the system identifies the user context and returns the information they are allowed to access. Public sustainability information can coexist with restricted compliance or commercially sensitive data.
QR codes and Digital Links
A QR code is a likely data carrier in many deployments, but it should not be confused with the passport itself. A robust implementation also needs a persistent identifier, a resolver or URL strategy, hosting, permissions and a way to keep records available even when systems or providers change.
Standards-based web identifiers can make a carrier resolvable to several destinations: a consumer view, a repair manual, a compliance record or an API representation. The exact carrier and identifier rules remain product-specific.
The DPP Registry
The EU Registry is central infrastructure for registering unique identifiers and associated metadata. The Commission states that registration is available through a user interface and an API. It is an index and control layer, not a substitute for the operator’s complete product-data environment.
Companies therefore need two connected capabilities: create and maintain compliant passport records, and perform required registry interactions.
Who is responsible for creating the passport?
Responsibility normally sits with the economic operator placing the covered product on the EU market or putting it into service — for example a manufacturer, importer or another party identified in the applicable legislation. A software vendor can operate the technology, but outsourcing the platform does not automatically transfer legal responsibility.
Internally, DPP delivery usually spans compliance, sustainability, product, procurement, IT and operations. A named business owner and field-level data ownership are more important than starting with a software purchase.
DPP software and providers
DPP platforms can help collect supplier data, connect product systems, generate passport views, manage access and register identifiers. The correct architecture depends on scale, data maturity, sector rules and how much of the capability already exists in ERP, PIM, PLM or traceability systems.
Use our DPP software guide to create a requirements list, then review the provider landscape by category rather than treating every vendor as interchangeable.
A practical implementation sequence
- Map products to adopted and planned EU rules.
- Define product identity and the likely passport granularity.
- Inventory required data and evidence across internal and supplier systems.
- Classify public, restricted and authority-only information.
- Design governance, validation and update processes.
- Test a small representative product set.
- Select technology after the data and workflow gaps are visible.
- Monitor delegated acts, standards and registry guidance for change.
Frequently asked questions
Is the Digital Product Passport already mandatory?
The ESPR framework is in force, but it does not make a DPP immediately mandatory for every product. Obligations apply when product-specific rules set the scope, data and application date. A separate battery passport requirement applies from 18 February 2027 to covered batteries.
Is a QR code the Digital Product Passport?
No. A QR code or another data carrier is the physical access point. The passport is the structured digital record and the systems that make authorised information available.
Where is DPP data stored?
Under the ESPR model, product data is generally stored in a decentralised way by the responsible economic operator or its service provider. Required identifiers and metadata are registered in the EU DPP Registry.
Does DPP apply to products made outside the EU?
Product rules apply to covered products placed on the EU market, regardless of where they were manufactured. The responsible EU economic operator must ensure compliance.
What should a company do first?
Confirm which product rules and timelines apply, create a product and supplier data inventory, assign data owners, test identifier and data-carrier choices, and run a limited pilot before committing to a platform.