FAQDPPEU

EU Digital Product Passport Who must create a Digital Product Passport?

For a covered product, the manufacturer must ensure a DPP is available. The product-specific delegated act then identifies who creates the passport and who may update each data set.

This FAQ helps separate DPP creation, passport updates, supplier data, service-provider hosting, and importer or distributor checks.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Overview

Under EU ESPR, product-specific delegated acts identify which actors create a Digital Product Passport or update its data. The placing the product on the market carries the back-up duty, while the operator placing the product on the market or putting it into service carries the registry duty. Manufacturers, importers, and distributors have separate obligations for covered products.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

Who is responsible for creating an EU Digital Product Passport?

For an ESPR product covered by a delegated act, start with the that places the product on the EU market or puts it into service. ESPR Article 10 requires the operator placing the product on the market to make available a back-up copy of the DPP through a DPP service provider. Article 13 requires the operator placing the product on the market or putting it into service to upload the required registry data.

For manufacturers, Article 27 adds a direct duty to ensure that a DPP and its current back-up copy are available for covered products. Article 9 then requires the product-group delegated act to specify the actors that create the DPP or update passport data, what they may change, and the arrangements for doing so.

  • Manufacturer: ensure the covered product has the required DPP and current back-up copy, and keep the passport data accurate, complete, and up to date.
  • Imported product: the importer must check before placing the product on the EU market that a DPP is available in accordance with ESPR Article 9 and the applicable delegated act.
  • Distribution: the distributor must verify, before making a covered product available, that it is labelled or linked to a DPP where the delegated act requires it.
  • Authorised representative: a manufacturer may appoint one by written mandate, but Article 28 says the manufacturer's Article 27(1) obligations, including DPP availability, cannot form part of that mandate.
  • Updates: do not give write access broadly; follow the delegated act's rules on which actors may introduce or update which data.
Question 2

How do manufacturer, importer, and distributor duties differ?

The manufacturer obligation is the strongest anchor in ESPR. For covered products, Article 27 requires manufacturers to ensure the product is accompanied by required information and that a DPP is available, including a back-up copy of the most up-to-date passport version stored by a DPP service provider.

Importers and distributors are not passive. Before placing a covered product on the market, importers must ensure that the manufacturer has handled conformity assessment, required information, and DPP availability. Before making the product available, distributors must verify that the product is labelled or linked to a DPP where the delegated act requires it, and they must stop making it available if the product or manufacturer is not compliant.

  • Assign manufacturer accountability to the legal manufacturer named for the product; do not use 'brand owner' as a substitute unless that entity is also the manufacturer under the applicable facts.
  • For non-EU manufacturers, require the EU importer file to show that the passport exists, is accessible, and has the required back-up copy before market placement.
  • Give distributors and dealers a checkable acceptance rule: no required DPP link, data carrier, documents, or instructions means the product should not move forward.
  • Keep marketplace and distance-selling teams supplied with the data carrier copy or unique product identifier so customers can access required passport information before purchase where ESPR requires it.
Question 3

What responsibility do suppliers and service providers have?

Suppliers are usually data contributors, not the default public owner of the final-product passport. ESPR Article 38 says that, when the delegated act specifies it, supply-chain actors must provide relevant information free of charge to manufacturers, notified bodies, and competent national authorities, allow manufacturer assessment when information is absent, and enable verification of information related to their activities.

DPP service providers are different from suppliers. They may store or process passport data for the , but ESPR Article 11 limits their processing to what is necessary for the service unless specifically agreed with the operator placing the product on the market or putting it into service.

  • Put supplier evidence in contract and onboarding records: material composition, substance data, component identifiers, production or environmental data, and verification access where the delegated act requires those data.
  • Give suppliers clear data ownership and correction paths so the manufacturer can keep passport data accurate, complete, and up to date.
  • Treat service-provider hosting as governance infrastructure: back-up copy, availability, access control, security, privacy, and continuity after insolvency or cessation of activity.
  • Separate 'can contribute data' from 'is legally responsible for creating the passport' unless the delegated act assigns that creation or update role.
Recommended next step

Turn DPP responsibility into an accountable evidence workflow

This DPP responsibility FAQ helps assign the market-placement owner, supplier data controls, service-provider governance, and delegated-act watchlist before passport publication.

Question 4

What governance record should a company keep?

A useful DPP responsibility record should identify the legal trigger, the product group, the market-placement actor, the delegated-act rule, and the teams allowed to create or update passport data. It should also show how supplier data is requested, checked, corrected, and locked before publication.

Before the product-specific delegated act exists, keep a product-group watchlist rather than assigning unsupported legal roles. Once the act defines product scope, passport level, data content, access rights, creation and update actors, registry data, and application details, turn those rules into named internal owners.

  • Product identity: model, batch, or item level required by the delegated act.
  • Responsible operator: manufacturer, importer, authorised representative, dealer, distributor, fulfilment service provider, or other actor identified for the product fact pattern.
  • Passport operations: creator, updater, approval owner, service provider, back-up copy location, registry upload owner, and access-rights owner.
  • Supplier controls: data fields requested, supplier source, validation method, correction owner, and evidence retained for authority or notified-body checks.
  • Review trigger: delegated-act changes, product design changes, supplier changes, importer changes, DPP service-provider changes, or non-conformity concerns.
Primary sources

References and citations

eur-lex.europa.eu5 citations
Referenced sections
  • Primary legal source for ESPR DPP creation and update actors, economic-operator duties, manufacturer/importer/distributor obligations, supply-chain information duties, service-provider rules, and delegated acts.
  • Articles 9, 10, 13, 27, and 28 identify creation and update rules, placing-on-market duties, manufacturer DPP availability, and the limit on an authorised representative's mandate.
  • Supports the distinct ESPR obligations of manufacturers, importers, and distributors for DPP availability, checks, and market availability controls.
Show 2 more
  • Supports supply-chain information duties when specified in a delegated act and the limits on DPP service-provider processing.
  • Supports using the delegated act to determine passport level, data content, access rights, creators, update actors, registry data, and market-placement duties.
"actors that are to create a digital product passport"
More quoted passages
"a digital product passport is available"
"provide, upon request and free of charge"
"accurate, complete and up to date"
cencenelec.eu4 citations
Referenced sections
  • Practical DPP design source for supply-chain information exchanges, market-compliance information flows, and product-group implementation choices.
  • Supports treating DPP design as a product-group and supply-chain implementation exercise rather than a single universal owner rule.
  • Supports practical supply-chain DPP information exchanges between raw-material suppliers, manufacturing suppliers, manufacturers, reuse operators, and recyclers.
Show 1 more
  • Supports maintaining a DPP design process that considers product-group requirements, supply-chain information exchanges, target audiences, and implementation choices.
"information generated and shared within supply chains"
More quoted passages
"based on a delegated act for each product group"
"model, product batch or product item level"
single-market-economy.ec.europa.eu
Referenced sections
  • Current Commission overview of economic-operator scope, registration, data compilation, lifecycle management, distance selling, and product-group dependence.
Show all related guides (37)

Annex III Data Model Planning for EU Digital Product Passports

Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts.

Digital Product Passport vs Digital Twin

Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits.

Digital Product Passport vs Paper Product Passports

Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability.

DPP customs access review workflow for ESPR products

Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence.

DPP Data Governance RACI Template for EU Digital Product Passports

Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence.

DPP data-model intake workflow for EU Digital Product Passports

An intake workflow for EU Digital Product Passport data models: product scope, legal status, field owner, evidence, access class, identifiers, carrier, registry mapping, and publication readiness.

DPP Governance, Verification and Audit Controls

Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.

DPP registry and web portal integration under EU ESPR

EU Digital Product Passport Registry and web portal integration guide based on official sources: identifiers, carriers, access rights, providers, and lookup design.

DPP vs Battery Passport: ESPR and Battery Regulation Comparison

Compare the ESPR Digital Product Passport framework with the EU Batteries Regulation battery passport by scope, timing, data, access rights, identifiers, registry, governance, and evidence.

DPP vs EPREL Comparison

Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits.

DPP vs GS1 Digital Link: Duties vs Standard

Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences.

EU Digital Product Passport access: public, restricted, and customs views

How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal.

EU Digital Product Passport API and resolver architecture

DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates.

EU Digital Product Passport Applicability Test

Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep.

EU Digital Product Passport architecture and integration

Guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance.

EU Digital Product Passport checklist

A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls.

EU Digital Product Passport compliance: ESPR requirements

EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence.

EU Digital Product Passport Data Carriers, Access Control, and UX

How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints.

EU Digital Product Passport data requirements and fields

How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation.

EU Digital Product Passport deadlines and compliance calendar

EU Digital Product Passport calendar covering the live DPP Registry, ESPR product-rule milestones, and fixed battery passport dates.

EU Digital Product Passport FAQ

Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance.

EU Digital Product Passport identifier and data carrier design

How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules.

EU Digital Product Passport penalties and enforcement

How EU Digital Product Passport breaches can lead to national penalties, corrective action, market restrictions, and customs holds under ESPR or battery law.

EU Digital Product Passport Product Group Readiness

Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs.

EU Digital Product Passport requirements under ESPR

Overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points.

EU Digital Product Passport supplier data validation controls

Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate.

EU DPP implementation playbook and vendor selection

Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence.

EU DPP Product-Group Readiness Checklist

A checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness.

EU DPP QR Code and Data Carrier Implementation Guide

Guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence.

EU DPP supplier data validation workflow

A workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records.

What is a Digital Product Passport under ESPR?

A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.