digital product passport

What does digital product passport mean?

Under ESPR, a digital product passport is a structured electronic data set specific to a product, product model, batch, or item, depending on the applicable product rules. Article 2, point 28 defines the term, while Article 4 delegated acts determine the required information, identifier level, access rules, and update obligations for each product category. The DPP is accessed through a data carrier and must support different access rights for different actor groups, including consumers, economic operators, repairers, recyclers, customs authorities, and market surveillance authorities where required.

Short version

The digital product passport (DPP) is the product-specific electronic data set required under ESPR, not the QR code, software platform, data standard, registry, database, or website used to host or access it.

Minespider working definition

A digital product passport (DPP) is a structured electronic data set associated with a product, product model, batch, or item, depending on the rules of its product category. It contains or provides controlled access to information required by the relevant ESPR delegated act, including compliance, sustainability, and circularity information. Accessed through a physical data carrier such as a QR code, barcode, or RFID tag and linked to unique identifiers, the DPP serves as an authoritative product record. It may store information directly or provide secure access to decentralized data held across different supply-chain systems. The DPP is the product-specific data set; the DPP system is the infrastructure used to create, access, update, exchange, verify, and preserve that data set.

Common boundary mistakes

Most DPP confusion comes from mixing up the regulated data set with the infrastructure around it. A QR code, barcode, RFID tag, or other data carrier provides physical access to the passport data, but is not the passport itself. A product website is a presentation layer. A software platform is a management tool. A registry or central database may be one storage or discovery component. Standards, schemas, and credentials provide interoperability and trust mechanisms. None of these is the product-specific electronic data set itself.

Digital product passport and DPP system

The digital product passport is the regulated product-specific data set. The DPP system is the infrastructure used to create, access, update, exchange, verify, preserve, and present that data set. A DPP system may include identifiers, data carriers, registries, APIs, data-exchange mechanisms, access-control rules, credentials, verification workflows, service providers, backup arrangements, and user interfaces. Keeping this distinction clear helps companies design interoperable architecture without reducing the passport to one vendor platform, one website, or one database.

Static and dynamic data

A DPP is not a static public webpage where every user sees the same information. Depending on the product category delegated act, information may be tracked at model-level, batch-level, or item-level granularity. The product-specific data set can combine stable master data, such as manufacturer identity, product model, material composition, and conformity information, with lifecycle-updated data such as repair history, software updates, maintenance records, durability information, or end-of-life handling information where required. Good implementations organize both stable and dynamic data without assuming that every field must live in one central database.

Access and permissions

A compliant DPP architecture needs granular access control. ESPR anticipates different information access for different actors and purposes, so consumers, recyclers, repairers, customs officials, market surveillance authorities, and economic operators may see different fields or assurance levels. In practice, this requires authentication, authorization, field-level permissions where needed, interoperability, and long-term availability rather than one universal public product page.

Source context

ESPR Article 2, point 28 defines a digital product passport as a set of data specific to a product that includes the information specified in the applicable delegated act adopted pursuant to Article 4 and that is accessible through a data carrier in accordance with Chapter III. ESPR therefore creates the legal framework, while product-specific delegated acts supply the required fields, timelines, identifier level, access rules, and update requirements. CIRPASS-2 and related EU-funded projects provide implementation guidance and interoperability context, but they are not the legal source of the DPP definition.

What this means for implementation

DPP preparation is not a web-design project; it is a product-data infrastructure task. Because obligations will roll out progressively by sector, companies need adaptable data value chains that can identify required regulatory fields, collect verified evidence from upstream suppliers, link information to the correct identifier level, manage multi-stakeholder access rights, support updates where required, and preserve the record across the product lifecycle.

Official definitions by source

Key deadline

Battery passport obligations under the EU Battery Regulation are the first DPP-type requirement already in force; ESPR delegated acts will phase in DPPs for other product categories from 2026 onwards.

Practical application

Companies should treat DPP preparation as a product-data infrastructure task rather than a webpage or label project. The practical work is to identify required regulatory fields, map them to model-, batch-, or item-level identifiers, collect supplier evidence, manage access rights for different users, support updates where required, and keep the record available across the product lifecycle.

Minespider commentary

Digital product passport is often reduced to the thing a customer scans, but the more useful definition is the structured product-specific data set behind the access point. The QR code or RFID tag is only the doorway; the passport is the governed record behind it. The hard part is keeping product identity, supplier data, evidence, access rights, and lifecycle updates connected as the product moves through the market and value chain. For Minespider, the DPP becomes valuable when it turns scattered compliance inputs into a trusted record that different actors can access according to their role.

Common confusions

• Treating digital product passport and battery passport as synonymous. The battery passport is a sector-specific battery obligation under the EU Battery Regulation; the ESPR digital product passport is the broader product-passport framework implemented through delegated acts.
• Treating the DPP as a document or PDF. It is a structured electronic data set accessible through a data carrier, not a static file or downloadable compliance document.
• Treating the QR code, barcode, RFID tag, or other data carrier as the DPP. The data carrier can provide physical access to passport data, but it is not the passport itself.
• Treating a product webpage or label as the DPP. A webpage may display selected passport information, but the passport is the underlying structured data set and access structure.
• Treating a software platform as the DPP. A platform can create, host, update, or manage DPPs, but the platform is infrastructure around the passport rather than the passport itself.
• Treating a central database or registry as the DPP. A DPP may store information directly or provide controlled access to data distributed across multiple systems.
• Treating data standards, schemas, or credentials as the DPP. Standards and credentials support interoperability, exchange, and verification; they are not the product-specific data set itself.
• Assuming ESPR already fixes the same DPP fields for every product. Article 4 delegated acts determine the specific information, access rules, update duties, and identifier level for each product group.
• Treating supplier traceability data as the whole DPP. Traceability data can feed a DPP, but the passport also depends on product identity, required fields, access permissions, verification, and preservation obligations.

Related regulations

• EU Battery Regulation
• ESPR

Related Minespider reading

External references

Related terms

• battery passport
• data carrier
• unique product identifier
• ecodesign requirement
• QR code
• traceability
• static data
• dynamic data
• product
• component
• intermediate product
• information requirement
• product group
• unique operator identifier
• unique facility identifier
• digital product passport service provider
• economic operator
• manufacturer