---
title: "EU Digital Product Passport Product Group Readiness"
canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/product-group-readiness"
source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/product-group-readiness"
author: "Sorena AI"
description: "Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "EU Digital Product Passport"
  - "ESPR"
  - "product group readiness"
  - "delegated acts"
  - "data model"
  - "supplier data"
  - "unique product identifier"
  - "data carrier"
  - "DPP registry"
  - "Digital Product Passport"
---
**[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 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.

*DPP* *Product group readiness* *EU ESPR*

## EU Digital Product Passport Product Group Readiness

Prepare product lines for Digital Product Passport requirements before each product-specific ESPR delegated act fixes the final data fields and access rules.

This guide separates what is already clear in ESPR from what must wait for product-group rules: delegated-act monitoring, data ownership, supplier evidence, identifiers, carriers, access classes, and registry handoffs.

The EU Digital Product Passport is not a single universal spreadsheet. Under the Ecodesign for Sustainable Products Regulation, passport requirements are set at product-group level through delegated acts. A readiness programme should therefore build reusable DPP foundations while keeping every product group tied to its future rule text, data model, access rights, and registry obligations.

## Start with delegated-act status, not a generic passport launch

ESPR is framework legislation. The Commission sets concrete ecodesign and passport requirements product by product, or horizontally for groups with enough common characteristics. That means a product group is not ready because it has a QR code or a portal; it is ready when the team can show which delegated act applies, which passport level is required, which data fields are mandatory, and which actors can access or update them.

Use the first ESPR working plan and the priority list in ESPR as the watchlist, then maintain a product-group tracker for each affected portfolio. The tracker should distinguish adopted rules, consultations and preparatory studies, internal assumptions, and items intentionally left open until the product-specific delegated act is final.

- Record the product group and whether the expected rule is product-specific or horizontal.
- Track the current status: working-plan priority, consultation, draft delegated act, adopted delegated act, or not yet covered.
- Do not publish fixed passport field lists, deadlines, thresholds, or access promises until the relevant delegated act or implementing act supports them.
- For priority planning, flag iron and steel, aluminium, textiles including garments and footwear, furniture including mattresses, tyres, detergents, paints, lubricants, chemicals, energy-related products, ICT products, and other electronics because ESPR names them for the first working plan.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the product-group approach: ESPR delegates ecodesign and DPP details to acts adopted for specific product groups or horizontal groups, and Article 18 lists product groups to prioritise in the first working plan.
- [European Commission: Ecodesign for Sustainable Products Regulation](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) - Confirms ESPR is implemented through later concrete rules and that the first ESPR and Energy Labelling Working Plan was adopted in April 2025.

*Recommended next step*

*Placement: after registry section*

## Prepare product groups for DPP rule adoption

Use this guide to turn ESPR product-group monitoring into a maintained passport data, supplier evidence, identifier, access-rights, and registry readiness file.

- [Open Research Copilot](/solutions/research-copilot.md): Ask DPP readiness questions against cited ESPR and Commission source material.
- [Discuss DPP readiness](/contact.md): Review product-group tracking, data ownership, supplier evidence, identifiers, and registry preparation with Sorena.

## Build the data model around product-group fields and evidence

The binding passport field list is product-group specific, but ESPR already defines the architecture teams should prepare for. Data must be structured, searchable, transferable, based on open standards, and connected to a persistent unique product identifier. It must also be scoped to the model, batch, or item level specified in the delegated act.

A useful readiness model separates the regulated passport data from internal source evidence. For each candidate field, store the value, unit, source system, supplier or internal owner, criteria reference, assurance level, change trigger, and whether the field is public, restricted, authority-only, or withheld as confidential business information.

- Create a field catalogue with candidate sustainability, circularity, compliance, instruction, warning, and technical-documentation fields.
- Mark each field as confirmed by law, expected from preparatory work, voluntarily useful, or blocked until the delegated act is final.
- Define evidence URIs or document references for claims such as recycled content, carbon footprint, repairability, substance presence, or conformity.
- Keep model, batch, and item granularity explicit so ERP, PLM, supplier portals, and label systems do not mix values with different scopes.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the core DPP data requirements: open standards, machine-readable structured data, model/batch/item granularity, access rights, and product-group-specific data requirements.
- [ETSI ES 204 082: Information model for digital product information](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Provides a technical model for expressing product sustainability information as claims with criteria references, claimed values, evidence references, units, and assurance levels.

## Treat supplier data as controlled evidence, not a one-time questionnaire

Many DPP fields will depend on suppliers, component manufacturers, facilities, repairers, recyclers, or conformity bodies. Readiness therefore means knowing which supplier data is needed, where it originates, who can attest it, how it is refreshed, and how it remains available when a supplier, host, or product owner changes.

Supplier intake should collect more than values. For each submitted value, capture the supplier legal entity, facility, product or component identifier, measurement method, reference period, evidence document, assurance level, confidentiality class, and reuse permission. Fields that are useful for internal planning but not grounded in the final delegated act should remain labelled as assumptions.

- Map upstream fields to supplier contract clauses, purchase specifications, PLM records, and quality gates.
- Require suppliers to identify whether a value applies to a product model, batch, component lot, facility, or individual item.
- Store supplier evidence separately from public passport display text so restricted evidence can support public claims without over-disclosure.
- Plan update triggers for changed materials, changed facilities, new conformity evidence, repair or refurbishment events, and end-of-life data.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports supplier and value-chain readiness because ESPR expects DPP access, input, or updates by economic operators and other actors while protecting confidential business information.
- [ETSI ES 204 082: Information model for digital product information](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Supports supplier evidence design by describing claim data with criteria references, claimed values, evidence references, assurance level, and document or credential links.

## Choose identifiers and data carriers after deciding passport granularity

ESPR requires the passport to connect through a data carrier to a persistent unique product identifier. It also allows the delegated act to choose whether DPP data refers to the product model, batch, or item. That choice changes label design, supplier traceability, serialisation costs, recall handling, and whether lifecycle events such as repair or refurbishment can be attached to one physical product.

Readiness work should therefore avoid hard-coding a universal carrier pattern. Teams can still prepare carrier and resolver tests: whether the carrier will sit on the product, packaging, or accompanying documentation; whether a QR code, data matrix, RFID, NFC, or other carrier is appropriate; whether the carrier resolves to the correct product record; and whether it survives normal use, resale, repair, and recycling contexts.

- Maintain identifier rules for product identifiers, operator identifiers, facility identifiers, and future registry identifiers.
- Test carrier readability on real product surfaces, packaging, documentation, mobile devices, and warehouse or repair environments.
- Keep the resolver independent from page design so it can route public users, authorities, and restricted actors to the right data view.
- Do not encode large mutable datasets directly in the carrier when a stable identifier and resolver can point to maintained passport data.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the identifier and carrier requirements: ESPR requires a persistent unique product identifier connected through a data carrier, and delegates carrier placement and model/batch/item granularity to product-group rules.
- [ETSI ES 204 082: Information model for digital product information](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Supports the technical readiness topics for DPP implementations, including unique identifiers, data carriers, lookup mechanisms, access rights, interoperability, storage, authentication, and security.

## Define access classes before building the passport portal

ESPR expects differentiated access to DPP data. Consumers, businesses, repairers, recyclers, market surveillance authorities, customs authorities, and other actors may need different views of the same passport. Product-group delegated acts specify the access rights, so readiness should focus on classifying data and testing permission logic without pretending the final access matrix is already fixed.

A practical access model has at least four working classes: public product information, business-to-business or lifecycle partner information, authority and customs information, and restricted evidence or confidential business information. The classes should cover both read access and the rights to introduce, modify, or update data.

- Tag each data field with a proposed access class and the reason that class is needed.
- Separate public display text from audit evidence, supplier documents, and authority-only verification data.
- Design update permissions for manufacturers, importers, service providers, repairers, recyclers, and authorised internal roles.
- Verify that customer personal data is excluded from the passport unless a lawful, explicit consent basis is designed for a separate use case.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports differentiated access classes and update permissions: ESPR requires access and update rights to follow product-group-specific rights set in delegated acts.
- [European Commission: Digital Product Passport consultation](https://single-market-economy.ec.europa.eu/news/commission-launches-consultation-digital-product-passport-2025-04-09_en?ref=sorena.io) - Confirms the Commission was consulting on how DPP data should be stored and managed by service providers and on possible service-provider certification.

## Prepare for the registry and customs handoff

ESPR requires the Commission to set up a DPP registry that stores at least unique identifiers, and for products released for free circulation, the commodity code. The law sets 19 July 2026 as the registry setup date. Product-group rules and registry implementing arrangements will determine the detailed upload process and any extra registry data.

Teams can prepare now by aligning product identifiers, commodity codes, EORI and operator data, importer records, and customs-release workflows. Registry preparation should be treated as a master-data and border-control handoff, not as a marketing-page feature.

- Create a registry-ready payload design for unique product identifiers, operator identifiers, facility identifiers, commodity codes, and the future unique registration identifier.
- Align customs and trade-compliance ownership for imported products before the registry becomes operational for a covered product group.
- Test exception handling for mismatched commodity codes, missing identifiers, retired products, supplier data changes, and passport-host outage.
- Keep evidence that registry uploads are not treated as proof of compliance; they support traceability and controls alongside the underlying conformity record.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports registry and customs readiness: ESPR requires the Commission registry, unique identifiers, commodity-code storage for release for free circulation, and electronic customs verification once the registry and interconnection are operational.
- [European Commission: Ecodesign for Sustainable Products Regulation](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) - Confirms that the DPP will allow customs authorities to perform automatic checks on the existence and authenticity of DPPs for imported products.

## What teams can safely prepare before final product-specific rules

Before a product-specific delegated act is final, the defensible work is architecture and evidence readiness. Do not lock public claims, legal deadlines, penalty language, or mandatory field lists unless the applicable source already says so. Instead, create controls that can absorb the final rule without rebuilding product data from scratch.

The best output is a product-group readiness file that can be reviewed by product compliance, sustainability, master data, supply chain, IT, and customs teams. It should show what is known, what is assumed, what is waiting for the delegated act, and which systems or supplier workflows must change when the rule is adopted.

- A delegated-act watchlist for each product group and horizontal requirement area.
- A passport data catalogue with field owner, source system, supplier dependency, evidence reference, granularity, and access class.
- An identifier and carrier test record covering model, batch, and item scenarios.
- A supplier evidence intake template that captures method, reference period, facility, assurance level, and confidentiality class.
- A registry and customs readiness checklist for identifiers, commodity codes, importer data, EORI data, and exception handling.
- A change-control rule that prevents unsupported final claims until the product-group delegated act or implementing act is available.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the distinction between already-known DPP architecture and product-group-specific final requirements because ESPR leaves field lists, access rights, availability periods, carrier placement, and granularity to delegated acts.
- [European Commission: Digital Product Passport impact assessment surveys](https://single-market-economy.ec.europa.eu/news/take-part-our-impact-assessment-digital-product-passport-2025-07-25_en?ref=sorena.io) - Shows that system-level DPP service-provider requirements and certification feasibility were still being assessed through stakeholder surveys in 2025.

## Primary sources

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Primary legal source for ESPR product-group delegated acts, DPP data, identifiers, data carriers, access rights, registry, customs controls, and first-working-plan product group priorities.
  - Quote: "as specified in the applicable delegated act"
- [European Commission: Ecodesign for Sustainable Products Regulation](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) - Commission overview source for ESPR implementation, working-plan status, the DPP purpose, and customs checks for imported products.
  - Quote: "framework legislation that lays the foundation"
- [European Commission: Digital Product Passport consultation](https://single-market-economy.ec.europa.eu/news/commission-launches-consultation-digital-product-passport-2025-04-09_en?ref=sorena.io) - Commission source for ongoing DPP service-provider questions on data storage, management, and possible certification.
  - Quote: "how data should be stored and managed by service providers"
- [European Commission: Digital Product Passport impact assessment surveys](https://single-market-economy.ec.europa.eu/news/take-part-our-impact-assessment-digital-product-passport-2025-07-25_en?ref=sorena.io) - Commission source showing stakeholder surveys on future DPP service-provider requirements and certification feasibility.
  - Quote: "future requirements for DPP service providers"
- [ETSI ES 204 082: Information model for digital product information](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Technical source for DPP information-model concepts including claim data, criteria references, evidence, units, assurance level, identifiers, carriers, access rights, and interoperability topics.
  - Quote: "information model to describe environmental sustainability and circularity information"

## Related Topic Guides

- [Annex III Data Model Planning for EU Digital Product Passports](/artifacts/eu/digital-product-passport/annex-iii-data-model-planning.md): 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](/artifacts/eu/digital-product-passport/dpp-vs-digital-twin.md): 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](/artifacts/eu/digital-product-passport/dpp-vs-traditional-product-passports.md): 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](/artifacts/eu/digital-product-passport/customs-access-review-workflow.md): 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](/artifacts/eu/digital-product-passport/dpp-data-governance-raci-template.md): 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](/artifacts/eu/digital-product-passport/dpp-data-model-intake-workflow.md): A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness.
- [DPP Governance, Verification and Audit Controls](/artifacts/eu/digital-product-passport/governance-verification-and-audit.md): Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.
- [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.
- [DPP registry and web portal integration under EU ESPR](/artifacts/eu/digital-product-passport/dpp-registry-and-web-portal-integration.md): Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service providers, and lookup design.
- [DPP vs Battery Passport: ESPR and Battery Regulation Comparison](/artifacts/eu/digital-product-passport/dpp-vs-battery-passport.md): 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](/artifacts/eu/digital-product-passport/dpp-vs-eprel.md): 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](/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link.md): 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](/artifacts/eu/digital-product-passport/public-restricted-and-customs-access.md): 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](/artifacts/eu/digital-product-passport/api-and-resolver-architecture.md): Grounded 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](/artifacts/eu/digital-product-passport/applicability-test.md): 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](/artifacts/eu/digital-product-passport/architecture-and-integration.md): Grounded 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](/artifacts/eu/digital-product-passport/checklist.md): 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](/artifacts/eu/digital-product-passport/compliance.md): Grounded 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](/artifacts/eu/digital-product-passport/data-carriers-access-control-and-ux.md): 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](/artifacts/eu/digital-product-passport/data-requirements-and-fields.md): 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](/artifacts/eu/digital-product-passport/deadlines-and-compliance-calendar.md): Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts.
- [EU Digital Product Passport FAQ](/artifacts/eu/digital-product-passport/faq.md): 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](/artifacts/eu/digital-product-passport/unique-identifier-and-data-carrier-design.md): 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](/artifacts/eu/digital-product-passport/penalties-and-fines.md): What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts.
- [EU Digital Product Passport requirements under ESPR](/artifacts/eu/digital-product-passport/requirements.md): source-linked 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](/artifacts/eu/digital-product-passport/supplier-data-validation.md): 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 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.
- [EU DPP implementation playbook and vendor selection](/artifacts/eu/digital-product-passport/implementation-playbook-and-vendor-selection.md): 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](/artifacts/eu/digital-product-passport/product-group-readiness-checklist.md): A source-grounded 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](/artifacts/eu/digital-product-passport/dpp-qr-code-implementation-guide.md): Grounded 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](/artifacts/eu/digital-product-passport/supplier-data-validation-workflow.md): A grounded 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.
- [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.
- [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.
- [What is a Digital Product Passport under ESPR?](/artifacts/eu/digital-product-passport/what-is-a-dpp.md): A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.
- [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.
- [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.
- [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.


---

[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/product-group-readiness