DPP data fields and template

What data does a Digital Product Passport carry?

Last updated · 2026-06-08

A Digital Product Passport is a structured set of product data, reached through a QR code or similar data carrier and tied to a unique product identifier. This page sets out, in plain English, the data a DPP is expected to carry, what is set at the framework level versus what waits for your delegated act, and gives you a free fill-in template to start gathering it.

TL;DR

A DPP carries identifiers (product, operator and facility) reached via a data carrier, plus composition and substances of concern, durability and reparability, recycled content, carbon and environmental footprint, and end-of-life information. Access is differentiated by audience. The exact fields are set per product group by its delegated act, so treat most as expected until yours is adopted.

How the passport is structured

The passport itself is data, not a document. A data carrier (a QR code, GS1 DataMatrix, or an RFID or NFC tag) sits on the product, its packaging or its documentation, and links to a record identified by a unique product identifier. Three levels of identifier are used: product, operator and facility. CIRPASS, DPP in a nutshell

Access is differentiated, on a need-to-know basis: consumers, repairers, recyclers and authorities each see the data relevant to them, while commercially sensitive information is protected. The data model is decentralised, so the data stays with operators or their solution providers rather than in one EU mega-database; a central registry holds the list of data carriers and identifiers so passports can be found. CIRPASS FAQ

New to these terms? See the glossary or the DPP explainer.

The data fields, grouped

What a DPP is likely to carry, by theme. Items marked framework-level follow from the regulation and its architecture; items marked expected are set by your product group’s delegated act and are not final until it is adopted.

Identifiers and the data carrier

How the passport is found and tied to your product, your business and your sites. This architecture is set at the framework level, though the exact identifier schemes settle with standards.

  • Unique product identifierFramework-level

    Identifies the product (model, batch or item level). GS1 GTIN is the leading candidate.

  • Unique operator identifierFramework-level

    Identifies the responsible economic operator.

  • Unique facility identifierFramework-level

    Identifies the production site or facility.

  • Data carrierFramework-level

    QR code, GS1 DataMatrix or RFID/NFC, physically on the product, packaging or documentation, linking to the passport.

Composition and substances

What the product is made of, and anything in it that matters for safety, recycling or repair. The exact fields and thresholds are set per delegated act.

  • Material compositionExpected, per delegated act

    Materials and their proportions.

  • Substances of concernExpected, per delegated act

    Presence and location of substances that affect reuse, recycling or safety.

  • Recycled contentExpected, per delegated act

    Share of recycled material, where the delegated act requires it.

Durability, reparability and end-of-life

The circular-economy story: how long it lasts, how to fix it, and what to do with it at the end. Scores and metrics are defined per delegated act.

  • Durability and reliabilityExpected, per delegated act

    Expected lifetime and reliability information.

  • ReparabilityExpected, per delegated act

    Spare-part availability, repair documentation, and a repairability score where defined.

  • InstructionsExpected, per delegated act

    Use, repair, maintenance and disposal instructions.

  • End-of-life and recyclingExpected, per delegated act

    Disassembly and recycling information for waste operators.

Carbon and environmental footprint

The climate and wider environmental impact of the product across its life cycle. Flagged especially for iron and steel and aluminium, and likely based on the EU PEF method.

  • Product carbon footprint (PCF)Expected, per delegated act

    Life-cycle greenhouse-gas emissions in CO2-equivalent, where required.

  • Environmental footprint (PEF)Expected, per delegated act

    Wider life-cycle impacts via the EU Product Environmental Footprint method.

Exact fields are set per delegated act

This is the realistic shape of a DPP, drawn from the regulation, the JRC data-requirements methodology and the emerging standards. But the precise fields, their granularity (model, batch or item level) and the access rules are fixed by each product group’s delegated act, and most are not yet adopted. The cross-sector standards (CEN-CENELEC JTC 24, EN 18000-series) are still being finalised, expected around 2026. CEN-CENELEC JTC 24

Free template

The DPP Data Field Template

A ready-to-fill CSV listing the data fields above, with a column marking each as framework-level or expected, so you can start gathering what your suppliers and systems hold without waiting for the final delegated act. The hardest fields to source, footprint and substances of concern, often sit with your suppliers, so starting early pays off.

Enter your email to download the DPP Data Field Template (CSV). Instant download — straight to your device, no waiting for an email.

The template lists the data a Digital Product Passport is likely to carry, marked “expected” where the delegated act has not set the field yet. Your CSV downloads instantly, and you join The ESPR Brief, our free plain-English newsletter, so you hear when the fields firm up. Unsubscribe any time, in one click.

The fields marked “expected” are not yet law for most product groups. Use the template to organise your data, not as a final compliance spec.

DPP data questions people ask

What data does a Digital Product Passport contain?

A DPP is a structured, machine-readable dataset reached through a data carrier (QR code, GS1 DataMatrix or RFID/NFC) linked to a unique product identifier. It typically carries product, operator and facility identifiers, material composition, substances of concern, durability and reparability, recycled content, carbon and environmental footprint, and end-of-life information. The exact fields are set per product group by its delegated act, so most fields are still expected, not confirmed.

Are the DPP data fields final?

Not for most products. ESPR is a framework regulation: the precise data fields, granularity and access rules for any product are set by that product group’s delegated act, and most are not yet adopted. The identifier and data-carrier architecture is set at the framework level, and the cross-sector standards (CEN-CENELEC JTC 24, EN 18000-series) are still being finalised, expected around 2026. Treat field lists as expected until your delegated act lands.

Who can see the DPP data?

Not everyone sees everything. The DPP uses differentiated, need-to-know access: consumers, repairers, recyclers and market-surveillance or customs authorities each see the datasets relevant to them, while commercially sensitive information is protected. The JRC methodology framework defines who can see which datasets.

Is there one big EU database for DPP data?

No. The DPP uses a decentralised data model: the data stays with economic operators or their solution providers, not in a single EU mega-database. The Commission must set up a central DPP registry before 19 July 2026, but it holds the list of data carriers and unique identifiers so passports can be located, rather than all the product data itself.

Keep going

Am I in scope, and when?

Check whether ESPR applies to your product and the expected DPP timing for your group.

What applies to me?

Your ESPR obligations by role, split into what applies now and what waits for the delegated act.

DPP software compared

A vendor-neutral comparison of Digital Product Passport platforms.

Readiness checklist

What you can do now versus what waits for your delegated act, on one free checklist.

Get the free DPP Readiness Checklist

Sources

  1. [1]Regulation (EU) 2024/1781 (ESPR), full text on EUR-Lexretrieved 8 Jun 2026
  2. [2]CIRPASS, Digital Product Passport in a nutshellretrieved 8 Jun 2026
  3. [3]CIRPASS, DPP FAQ (registry, decentralised model, identifiers)retrieved 8 Jun 2026
  4. [4]JRC, DPP data-requirements methodology (JRC145830)retrieved 8 Jun 2026
  5. [5]CEN-CENELEC JTC 24, Digital Product Passport standardsretrieved 8 Jun 2026

This is guidance to help you understand the Digital Product Passport, not legal advice. The exact data fields are set by each product group’s delegated act. For decisions specific to your business, confirm with the official sources we link or a qualified adviser.