---
title: "What Is a Digital Product Passport (DPP)?"
canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/what-is-a-dpp"
source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/what-is-a-dpp"
author: "Sorena AI"
description: "A deep explainer of the EU Digital Product Passport (DPP) under ESPR (Regulation (EU) 2024/1781): definition, who uses it, what data it contains (Annex III)."
published_at: "2026-03-04"
updated_at: "2026-03-04"
keywords:
  - "what is a digital product passport"
  - "digital product passport definition"
  - "EU Digital Product Passport DPP"
  - "ESPR 2024/1781 DPP"
  - "DPP Annex III data"
  - "DPP QR code"
  - "data carrier"
  - "unique product identifier"
  - "DPP registry"
  - "DPP customs checks"
  - "DPP implementation"
  - "Digital Product Passport"
  - "DPP definition"
  - "ESPR 2024/1781"
  - "Annex III data"
  - "QR code"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# What Is a Digital Product Passport (DPP)?

A deep explainer of the EU Digital Product Passport (DPP) under ESPR (Regulation (EU) 2024/1781): definition, who uses it, what data it contains (Annex III).

*Artifact Guide* *EU*

## EU Digital Product Passport (DPP) What It Is (and Why It Matters)

A product-specific dataset accessible via a data carrier - built to support sustainability, circularity, and compliance.

Grounded in ESPR (Regulation (EU) 2024/1781) Articles 9-15 and Annex III.

A Digital Product Passport (DPP) is not a marketing microsite. Under ESPR (Regulation (EU) 2024/1781), it is a set of product-specific data - defined in product-group delegated acts - that must be accessible electronically through a data carrier (for example a QR/ID) and designed for differentiated access across the value chain. In practical terms, the DPP rollout is now shaped by the first ESPR working plan for 2025-2030 and the supporting EU registry and service-provider rules that are still being operationalised.

## The legal definition and where DPP requirements live

Under ESPR, a DPP is a set of data specific to a product that includes the information specified in the applicable delegated act adopted under Article 4 and that is accessible via electronic means through a data carrier.

In practice, DPP is a framework capability: the Commission sets product-group rules (delegated acts) that specify what data must be included, at what granularity (model/batch/item), who can access which fields, and who can create or update the data.

- ESPR Chapter III (Articles 9-15) sets core DPP obligations: availability, essential requirements, registry, web portal and customs controls.
- Product-specific delegated acts (Article 4) define the actual DPP content and access rights per product group.
- Annex III provides the universe of DPP data elements that delegated acts can require (IDs, compliance docs, manuals, operator IDs, facility IDs, etc.).
- The first ESPR working plan, released in April 2025 for the 2025-2030 period, is the current policy signal for which product groups will move first.

*Recommended next step*

*Placement: after the scope or definition section*

## Use EU Digital Product Passport (DPP) What It Is (and Why It Matters) as a cited research workflow

Research Copilot can take EU Digital Product Passport (DPP) What It Is (and Why It Matters) from clarifying scope and applicability with cited answers to a reusable workflow inside Sorena. Teams working on EU Digital Product Passport (DPP) can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

- [Open Research Copilot for EU Digital Product Passport (DPP) What It Is (and Why It Matters)](/solutions/research-copilot.md): Start from EU Digital Product Passport (DPP) What It Is (and Why It Matters) and answer scope, timing, and interpretation questions with cited outputs.
- [Talk through EU Digital Product Passport (DPP)](/contact.md): Review your current process, evidence gaps, and next steps for EU Digital Product Passport (DPP) What It Is (and Why It Matters).

## Who the DPP is for (and why access must be differentiated)

DPP is designed to serve many actors: customers, economic operators (manufacturer/importer/distributor/dealer), repair and circularity operators, market surveillance and customs authorities, and other stakeholders.

Because DPP data includes both public consumer-facing information and restricted compliance/technical information, DPP must support differentiated access rights by stakeholder type.

- Customers: easy, free access to the information they need before purchase (including distance selling).
- Circularity operators: repair/refurbish/recycle information and identifiers to support life extension and end-of-life operations.
- Authorities: faster compliance verification, authenticity checks, and improved traceability and market surveillance.

## What data is inside a DPP (Annex III, in plain language)

DPP data fields are product-group specific, but the regulation already enumerates the kinds of data that may be required.

A practical way to understand DPP data is to split it into four layers: identity, compliance, usage/circularity, and operator/facility metadata.

- Identity layer: unique product identifier, commodity codes (e.g., TARIC), and (where applicable) a Global Trade Identification Number (GTIN).
- Compliance layer: declaration of conformity, technical documentation, and conformity certificates where applicable under EU law.
- Usage/circularity layer: user manuals, instructions, warnings and safety information (where required) and additional ecodesign information defined by delegated acts.
- Operator/facility layer: manufacturer/operator identifiers, importer info (including EORI), facility identifiers, and reference to the DPP service provider hosting the back-up copy.

## Model vs batch vs item level: why granularity is a key design decision

A DPP can be established at model, batch or item level depending on product-group rules. This directly affects architecture and cost: item-level DPP implies unique identifiers per unit; model-level implies shared identifiers with shared data.

Delegated acts must specify the level and the definition of that level for the product group.

- Model-level DPP: faster to implement; best when product units share identical regulated characteristics.
- Batch-level DPP: useful when manufacturing context affects compliance-relevant characteristics.
- Item-level DPP: strongest traceability; highest implementation complexity and lifecycle update needs.

## Data carrier + unique identifiers: the bridge between physical and digital

A DPP must be connected through a data carrier to a persistent unique product identifier. The data carrier must be physically present on the product, packaging, or accompanying documentation, as specified by product-group rules.

A DPP is designed to work with open standards and interoperability - to avoid vendor lock-in and to enable end-to-end traceability.

- Data carrier examples: QR/2D codes, RFID/EPC, or other standardised carriers depending on the product and context.
- Identifiers and carriers must comply with standards referenced in Annex III (or equivalent standards until harmonised references are published).
- Personal data: the regulation explicitly restricts storing customers' personal data in the DPP without explicit consent under GDPR.

## EU systems: registry, web portal, and customs controls

ESPR requires EU-level infrastructure to support DPP authenticity checks and automated controls.

For implementation teams, this translates into: (1) registry integration, (2) public and restricted data views, and (3) customs/market surveillance readiness.

- Digital product passport registry: the Commission must set up a registry that stores at least unique identifiers (with commodity codes for release-for-free-circulation products).
- Web portal: a public portal should allow searching and comparing DPP data consistent with access rights.
- Customs: for covered products placed under release for free circulation, the unique registration identifier must be provided when the registry is operational, and customs may verify it electronically.

## What is happening now: service-provider rules and rollout governance

The legal framework already allows DPP data to be stored by responsible economic operators or by DPP service providers, but the operating model is still maturing.

This is why storage architecture, backup access, continuity, and provider certification questions are not theoretical design issues. They are part of the Commission's active implementation agenda.

- On 9 Apr 2025, the Commission launched a public consultation on how DPP data should be stored and managed by service providers and on whether a certification scheme is needed.
- That consultation closed on 1 Jul 2025 and feeds the future rules for effective DPP system functioning.
- If you depend on a DPP platform vendor, you should treat provider controls and migration rights as part of core compliance design.

## How to start: week-one deliverables that de-risk implementation

A DPP program succeeds when it produces engineering-grade artifacts early: data maps, owners, identifier strategies, and evidence packages.

Use these deliverables to avoid building a portal that cannot satisfy delegated acts, access rights, and audit requirements later.

- DPP scope memo: product group(s), expected delegated act triggers, and the DPP granularity (model/batch/item) assumptions.
- Annex III data map: fields -> source systems -> owners -> update frequency -> retention policy.
- Identifier + carrier strategy: unique product identifier scheme, carrier choice, and fallback access for distance selling.
- Access control model: public vs restricted fields; actor types; authentication approach; audit logging.
- Evidence pack skeleton: declaration of conformity, technical documentation references, and how you keep DPP data accurate, complete and up to date.

## Primary sources

- [Regulation (EU) 2024/1781 (ESPR) - Official Journal](https://eur-lex.europa.eu/eli/reg/2024/1781/oj?ref=sorena.io) - Primary legal basis for DPP: Articles 9-15 (DPP requirements, registry, portal, customs) and Annex III (DPP data elements).
- [European Commission - Ecodesign for Sustainable Products Regulation (ESPR) overview](https://commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/ecodesign-sustainable-products-regulation_en?ref=sorena.io) - Plain-language description of ESPR and the Digital Product Passport concept and use cases (consumer information and customs checks).
- [CEN-CENELEC CWA 18186:2025 - Guidelines to create a Digital Product Passport](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Practical DPP design guidance for portal access, searchability, access rights, longevity/availability, security/trust, and procurement briefs.
- [CIRPASS DPP System Architecture (D3.2, March 2024) - product-centric architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Reference architecture guidance: product-centric identifiers, decentralised approaches, and interoperability principles.
- [GS1 - Digital Product Passport (standards and emerging regulations)](https://www.gs1.org/standards/standards-emerging-regulations/DPP?ref=sorena.io) - Identifier and data standards landscape relevant for DPP interoperability (e.g., GTIN and related GS1 building blocks).

## Related Topic Guides

- [DPP Applicability Test (ESPR Scoping) | EU Digital Product Passport](/artifacts/eu/digital-product-passport/applicability-test.md): A step-by-step applicability test for the EU Digital Product Passport (DPP): whether your product group is covered by an ESPR delegated act.
- [DPP Architecture & Integration (Open Standards, Registry, APIs) | EU Digital Product Passport](/artifacts/eu/digital-product-passport/architecture-and-integration.md): An advanced architecture guide for EU Digital Product Passport (DPP): product-centric identifiers and resolvers.
- [DPP Data Carriers, Access Control & UX | QR Code, Identifier, Public vs Restricted Views](/artifacts/eu/digital-product-passport/data-carriers-access-control-and-ux.md): A deep guide to DPP data carriers and UX under ESPR 2024/1781: physical data carrier requirements (Article 10), persistent unique product identifiers.
- [DPP Data Governance RACI Template | EU Digital Product Passport](/artifacts/eu/digital-product-passport/dpp-data-governance-raci-template.md): Copy/paste-ready governance templates for EU Digital Product Passport (DPP): RACI by Annex III field.
- [DPP Data Requirements & Fields (Annex III) | EU Digital Product Passport](/artifacts/eu/digital-product-passport/data-requirements-and-fields.md): A practitioner guide to EU DPP data requirements under ESPR (Regulation (EU) 2024/1781): what data fields can be required (Annex III).
- [DPP Governance, Verification & Audit Readiness | EU Digital Product Passport](/artifacts/eu/digital-product-passport/governance-verification-and-audit.md): An audit-readiness guide for EU Digital Product Passport (DPP): how to prove DPP data is accurate, complete and up to date (Article 9).
- [DPP Implementation Playbook & Vendor Selection | EU Digital Product Passport](/artifacts/eu/digital-product-passport/implementation-playbook-and-vendor-selection.md): A practical playbook for implementing EU Digital Product Passport (DPP): program steps, roles, supplier onboarding, data model and identifiers.
- [DPP QR Code Implementation Guide | Data Carrier + Identifier Design](/artifacts/eu/digital-product-passport/dpp-qr-code-implementation-guide.md): A practical implementation guide for using QR codes (and other data carriers) for EU Digital Product Passports: what ESPR requires (Article 10).
- [DPP vs Traditional Product Passports (Labels, PDFs, EPREL) | EU Digital Product Passport](/artifacts/eu/digital-product-passport/dpp-vs-traditional-product-passports.md): A deep comparison of the EU Digital Product Passport (DPP) vs traditional product information approaches: physical labels, PDFs/manuals.
- [ESPR / DPP Penalties & Fines | EU Digital Product Passport Enforcement](/artifacts/eu/digital-product-passport/penalties-and-fines.md): How penalties work for EU Digital Product Passport obligations under ESPR (Regulation (EU) 2024/1781): Member States set effective.
- [EU Digital Product Passport (DPP) Checklist | Audit-Ready Implementation Steps](/artifacts/eu/digital-product-passport/checklist.md): An audit-ready DPP checklist for ESPR 2024/1781: delegated act scoping, model/batch/item granularity, Annex III data mapping, data carriers (QR/ID).
- [EU Digital Product Passport (DPP) Compliance Guide | Implementation Playbook](/artifacts/eu/digital-product-passport/compliance.md): A practical compliance guide for EU Digital Product Passport (DPP) under ESPR 2024/1781: how to scope delegated acts, implement Articles 9-15 requirements.
- [EU Digital Product Passport (DPP) Deadlines & Compliance Calendar | ESPR 2024/1781](/artifacts/eu/digital-product-passport/deadlines-and-compliance-calendar.md): A calendar-ready timeline for EU Digital Product Passport (DPP) under ESPR (Regulation (EU) 2024/1781): entry into force (18 Jul 2024).
- [EU Digital Product Passport (DPP) FAQ | ESPR 2024/1781](/artifacts/eu/digital-product-passport/faq.md): Answers to the most searched EU DPP questions: is DPP mandatory, which products are in scope, model vs batch vs item, what data is required (Annex III).
- [EU Digital Product Passport (DPP) Requirements | ESPR Articles 9-15 + Annex III](/artifacts/eu/digital-product-passport/requirements.md): A detailed, execution-ready breakdown of EU Digital Product Passport (DPP) requirements under ESPR (Regulation (EU) 2024/1781): availability (Article 9).


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/digital-product-passport/what-is-a-dpp