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 for each product category. The DPP is accessed through a data carrier and must support access rights for different actor groups, depending on the applicable rules, including consumers, economic operators, repairers, recyclers, customs authorities, and market surveillance authorities.

Short version

The digital product passport is the product-specific data set required under ESPR, not the QR code, platform, website, database, standard, credential, or software system used to implement it.

Minespider working definition

A digital product passport is a structured electronic data set associated with a product, product model, batch, or item, depending on the applicable product rules. It contains or provides controlled access to information required by the relevant ESPR delegated act, including product identity, compliance or conformity information, sustainability characteristics, durability, repairability, circularity, and other product-specific information where required. The passport is accessed through a data carrier and linked to relevant identifiers. The digital product passport 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

Many discussions use digital product passport to mean the whole technical environment around product data. It is more precise to separate the passport from that environment. A QR code, RFID tag, or other data carrier can provide access to the DPP, but it is not the passport itself. A website can display passport data, but it is not the passport. A software platform can manage DPPs, but the platform is not the DPP. A database can store some passport data, but the passport may also provide controlled access to information held in other systems. A data standard can support interoperability, and a credential may support trust or access in a DPP implementation, but neither is the product-specific data set required by ESPR.

Digital product passport and DPP system

The digital product passport is the product-specific data set linked to the relevant product identity. The DPP system is the infrastructure around that data set. It may include identifiers, data carriers, registries, access-control rules, APIs, data exchange mechanisms, verification workflows, service providers, backup arrangements, and user interfaces. Keeping this distinction clear helps companies design for interoperability without reducing the passport to one vendor platform or one visible product page.

Static and dynamic data

The DPP framework can require information at different levels, including model-level, batch-level, and product-specific information depending on the delegated act. Some information may be stable, such as product model, manufacturer identity, material composition, and compliance or conformity information. Other information may change over time, such as repair information, software updates, maintenance records, durability-related data, or end-of-life handling information where required. A DPP implementation therefore needs to organize both relatively stable master data and product-specific or lifecycle-updated data without assuming that every data point must live in one database.

Access and permissions

A digital product passport is not one public page where every user sees the same information. ESPR requires access to be structured for different actors and purposes. Consumers, economic operators, repairers, recyclers, customs authorities, and market surveillance authorities may need different information or different levels of access. A useful DPP implementation needs authentication, authorization, field-level access where required, interoperability, and long-term availability.

Source context

ESPR Article 2, point 28 defines a digital product passport as a set of data specific to a product that includes 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. This means ESPR defines the framework, while product-category delegated acts determine the actual DPP content. European Commission ESPR guidance provides policy context. CIRPASS-2 provides implementation and interoperability context, not the legal source of the DPP definition.

What this means for implementation

DPP obligations will apply progressively as ESPR delegated acts are adopted for specific product groups. The timing, required fields, access rules, and update obligations will depend on the relevant delegated act. For companies, DPP preparation is a product-data infrastructure task: identifying required fields, linking data to product identifiers, collecting supplier evidence, managing access rights, supporting updates where required, and preserving 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

DPP obligations will apply progressively as ESPR delegated acts are adopted for specific product groups. Companies should treat DPP preparation as a product-data infrastructure task: identifying required fields, linking data to product identifiers, collecting supplier evidence, managing access rights, supporting updates where required, and preserving the record 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 hard part is keeping product identity, supplier data, evidence, access rights, and lifecycle updates connected as a product moves through the market and value chain. For Minespider, the DPP becomes valuable when it turns scattered compliance inputs into a governed record that different actors can trust and use.

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.
• Assuming the DPP is a document or PDF. It is a structured electronic data set accessible through a data carrier, not a static file.
• Treating the QR code, RFID tag, or other data carrier as the DPP. The data carrier can provide access to the passport, but it is not the passport itself.
• Treating a product webpage or public label as the DPP. A webpage may display selected passport information, but the passport is the underlying product-specific data set and access structure.
• Treating a platform or database as the DPP. Platforms and databases may create, store, serve, or manage passport data, but they are infrastructure around the passport rather than the passport itself.
• Assuming ESPR already fixes the same DPP fields for every product. Article 4 delegated acts determine the specific information required 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 rules, 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