--- title: "EU Digital Product Passport FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq" source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/items/page/2" author: "Sorena AI" description: "Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "EU Digital Product Passport" - "ESPR" - "DPP registry" - "customs access" - "product passport data carrier" - "unique product identifier" - "Digital Product Passport" - "data carrier" --- **[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) --- # 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. *FAQ* *DPP* *EU ESPR* ## EU Digital Product Passport questions answered Concise answers on how the EU Digital Product Passport works under the Ecodesign for Sustainable Products Regulation. Covers who creates and updates passports, which product groups are first in scope, what goes into the registry, how customs access works, and how public and restricted data should be separated. The EU Digital Product Passport is the ESPR mechanism for making product sustainability, circularity, traceability, and compliance information available electronically. The exact passport content, access rights, data carrier, and product level are set in product-specific delegated acts, so implementation starts with the applicable product group rule rather than a one-size-fits-all passport template. ## Browse sub-FAQ modules ### [DPP QR code vs NFC data carrier choices under EU ESPR](/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices.md) How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier. - 4 items ### [EU DPP customs access: registry, portal, and restricted data](/artifacts/eu/digital-product-passport/faq/customs-access.md) FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data. - 4 items ### [EU DPP unique identifier requirements: product, operator and facility IDs](/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements.md) FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence. - 4 items ### [Public vs restricted EU Digital Product Passport data](/artifacts/eu/digital-product-passport/faq/public-vs-restricted-passport-data.md) How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules. - 5 items ### [What is the EU Digital Product Passport registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md) FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming. - 4 items ### [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md) FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts. - 4 items ### [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md) DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together. - 4 items Browse all indexed questions: [/artifacts/eu/digital-product-passport/faq/items](/artifacts/eu/digital-product-passport/faq/items.md) ## All FAQ items *Page 2 of 2. Showing 9 of 29 items.* ### [What should teams not assume about the registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md#what-should-teams-not-assume-about-the-registry) *Module: [What is the EU Digital Product Passport registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md)* Do not assume the registry is a public passport page, a compliance certificate, or a complete product-data store. ESPR makes the registry a secure identifier record, while the passport itself remains distributed across economic operators and service providers. - Registry acknowledgement is not proof of compliance. - The registry is not the same thing as the public web portal. - Additional registry fields depend on delegated acts, not on page-level convenience. - Passport storage can remain decentralised even when registry data is centralised. Sources for this answer: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 13 to 15 distinguish the secure registry, the web portal, customs checks, and the limits on what registry communication proves. ### [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md#which-products-come-first-for-the-eu-digital-product-passport) *Module: [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md)* For binding passport planning, separate the battery passport from the ESPR Digital Product Passport. The Batteries Regulation says that from 18 February 2027 each LMT battery, each industrial battery with a capacity greater than 2 kWh, and each electric vehicle battery placed on the market or put into service must have an electronic battery passport. - Treat covered batteries as a separate first-passport workstream under Regulation (EU) 2023/1542. - Treat ESPR priority product groups as a watchlist for upcoming ecodesign and DPP requirements, not as automatic passport obligations. - Do not publish a product-group DPP launch date unless the applicable delegated act or official working-plan material supports it. Sources for this answer: - [Regulation (EU) 2023/1542 on batteries and waste batteries](https://eur-lex.europa.eu/eli/reg/2023/1542/oj/eng?ref=sorena.io) - Supports the separate battery passport obligation, the covered battery categories, and the 18 February 2027 date. - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports that ESPR DPP requirements are tied to product-specific delegated acts rather than a single across-the-board passport date. ### [Which ESPR product groups are priority candidates?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md#which-espr-product-groups-are-priority-candidates) *Module: [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md)* ESPR Article 18 sets the first working-plan priority list. The listed groups are iron and steel; aluminium; textiles, especially garments and footwear; furniture, including mattresses; tyres; detergents; paints; lubricants; chemicals; relevant energy-related products; and information and communication technology products and other electronics. - Start inventory work for products that fall into the Article 18 priority groups. - Keep batteries in a separate regulatory tracker because their passport rule is in the Batteries Regulation. - For each ESPR product group, link the watch item to the future delegated act rather than copying a generic DPP deadline across all products. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the Article 18 first working-plan product groups and the point that working-plan priority is a planning step. - [European Commission 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) - Supports the Commission framing of ESPR as the product-sustainability framework behind future product-specific measures. ### [Why does the delegated act matter?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md#why-does-the-delegated-act-matter) *Module: [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md)* Under ESPR, the delegated act is where the general framework becomes product-specific. ESPR Article 9 says products can be placed on the market or put into service only if a digital product passport is available in accordance with the applicable delegated acts, and Article 9 also says those acts specify which data must be included, the data carriers to be used, and how the carrier is presented and positioned. - Create one tracking row per product group and delegated act, not one generic DPP row for every SKU. - Record the affected product models, market role, passport data owner, carrier decision owner, and supplier-data dependencies. - Update the row when the delegated act defines the product scope, data elements, carrier layout, access rights, conformity assessment route, and application timing. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports that ESPR passport availability, data content, carriers, layout, and positioning are specified through applicable delegated acts. ### [What should teams do now?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md#what-should-teams-do-now) *Module: [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md)* For batteries, build against the grounded Batteries Regulation passport scope if the business places covered LMT, industrial greater-than-2 kWh, or electric vehicle batteries on the EU market or puts them into service. That work should include the battery category decision, the responsible economic operator, QR-code access, and the information set in Annex XIII. - Segment the portfolio into battery-passport products, ESPR Article 18 priority groups, and products not yet matched to a grounded DPP priority source. - Assign a regulatory owner for delegated-act monitoring and a data owner for each product family likely to need passport data. - For public pages, customer notices, supplier questionnaires, and internal roadmaps, label unfinalised ESPR product-group timing as dependent on the delegated act. Sources for this answer: - [Regulation (EU) 2023/1542 on batteries and waste batteries](https://eur-lex.europa.eu/eli/reg/2023/1542/oj/eng?ref=sorena.io) - Supports the battery categories, QR-code link to the battery passport, responsibility for passport information, and Annex XIII information structure. - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the need to wait for product-specific delegated acts before treating ESPR DPP details as binding for a product group. ### [Who is responsible for creating an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md#who-is-responsible-for-creating-an-eu-digital-product-passport) *Module: [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md)* For an ESPR product covered by a delegated act, start with the economic operator that places the product on the EU market or puts it into service. ESPR Article 10 requires that operator to make available a back-up copy of the DPP through a DPP service provider, and Article 13 requires that operator to upload the required registry data. - Manufacturer-led placement: the manufacturer normally owns the product conformity file, DPP availability, and current passport content for products it places on the EU market or puts into service. - 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. - Updates: do not give write access broadly; follow the delegated act's rules on which actors may introduce or update which data. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports that ESPR delegated acts specify the actors that create or update DPP data and that the placing-on-market operator has DPP back-up and registry duties. - [CEN-CENELEC CWA 18186:2025 DPP design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports treating DPP design as a product-group and supply-chain implementation exercise rather than a single universal owner rule. ### [How do manufacturer, importer, and distributor duties differ?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md#how-do-manufacturer-importer-and-distributor-duties-differ) *Module: [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md)* 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. - Assign product accountability to the manufacturer or brand owner that controls design, technical documentation, declaration of conformity, and passport content. - 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. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the distinct ESPR obligations of manufacturers, importers, and distributors for DPP availability, checks, and market availability controls. ### [What responsibility do suppliers and service providers have?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md#what-responsibility-do-suppliers-and-service-providers-have) *Module: [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md)* 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. - 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. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports supply-chain information duties when specified in a delegated act and the limits on DPP service-provider processing. - [CEN-CENELEC CWA 18186:2025 DPP design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports practical supply-chain DPP information exchanges between raw-material suppliers, manufacturing suppliers, manufacturers, reuse operators, and recyclers. ### [What governance record should a company keep?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md#what-governance-record-should-a-company-keep) *Module: [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md)* 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. - 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. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports using the delegated act to determine passport level, data content, access rights, creators, update actors, registry data, and market-placement duties. - [CEN-CENELEC CWA 18186:2025 DPP design guidance](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports maintaining a DPP design process that considers product-group requirements, supply-chain information exchanges, target audiences, and implementation choices. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/digital-product-passport/faq/items](/artifacts/eu/digital-product-passport/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 2 of 2 Pages: [1](/artifacts/eu/digital-product-passport/faq/items.md) | [2](/artifacts/eu/digital-product-passport/faq/items/page/2.md) [Previous page](/artifacts/eu/digital-product-passport/faq/items.md) *Recommended next step* *Placement: after governance section* ## Prepare the Digital Product Passport evidence model Use the applicable delegated act to map passport fields, access rights, registry data, identifiers, data carriers, owners, and update controls before publishing a DPP endpoint. - [Open Research Copilot](/solutions/research-copilot.md): Check DPP source requirements and product-group delegated acts with cited external sources. - [Discuss DPP implementation](/contact.md): Review passport fields, identifiers, access rights, and evidence ownership for covered EU products. --- [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/faq/items/page/2