What has changed and its scope
Implementing Decision (EU) 2026/1736 published references to six DPP harmonised standards. For the requirements they cover, Article 41(2) ESPR provides a presumption of conformity for passports complying with those standards. Implementing Regulation (EU) 2026/1778 sets the operational rules for the EU DPP Registry, which entered into force on 6 August 2026; the Commission made the Registry operational on 20 July 2026. [1] [2] [3]
This can simplify technical conformity evidence for matters covered by the standards, but it does not remove sector-specific duties, economic-operator responsibility or checks required by applicable legislation.
Guide contents
Six harmonised standards: a common technical foundation
Decision (EU) 2026/1736 publishes six standards: EN 18216:2026 for data exchange protocols; EN 18219:2026 for unique identifiers; EN 18220:2026 for data carriers; EN 18221:2026 for storage, archiving and persistence; EN 18222:2026 for lifecycle-management and search APIs; and EN 18223:2026 for system interoperability. [1]
The key legal effect is the presumption of conformity with Articles 10 and 11 ESPR to the extent those requirements are covered by the harmonised standards. This provides a clearer technical reference without turning a standard into automatic product certification.
EU Registry: central index, decentralised product data
The DPP Registry is the European indexing service for product passports. It stores unique identifiers, registration data and high-level metadata; detailed product data remains decentralised, except where applicable legislation requires additional Registry data. [3]
Regulation (EU) 2026/1778 also covers registration APIs, passport existence and completeness checks, unique registration identifiers, customs-related components, a semantic repository and identification and authorisation systems. [2]
Verified operators, electronic identity and responsibility
DPP registration in the Registry is reserved to verified economic operators. The Regulation defines identity-verification requirements and, for legal persons, qualified eIDAS instruments; it also covers delegation, profile management and transfer of registered passports. [2]
For businesses, operator master data, powers, roles and responsibilities are therefore part of the DPP registration and maintenance process rather than a separate administrative detail.
Lower burden means more standardisation, not less responsibility
Harmonised standards can reduce technical duplication and make conformity evidence more straightforward for the requirements they cover. The Registry also provides a common European point for identification and registration. These changes should not be read as a blanket reduction of all controls.
Product-specific legislation, mandatory data, access levels, operator responsibilities and authority checks still apply. The operational benefit comes from building a standards-aligned architecture once and reusing it across sector profiles.
The NexusDpp approach
A cross-sector structure. A dedicated profile.
NexusDpp is designed to connect product identity, data, records, responsibilities and access. Preparation starts from this foundation: the proposed process translates the regulatory topic into a project configuration to validate against the customer's product and organisation. Platform architecture.
Align identity and data carriers
Map product, operator and physical-carrier identifiers for the applicable profile.
Structure data and APIs
Organise datasets, versions, data exchange, search and integrations for interoperability.
Prepare the verified operator
Define authorised users, delegations, identity evidence and registration responsibilities.
Connect the EU Registry
Manage registration, registration identifiers, metadata and completeness checks in the DPP workflow.
Configuration example / illustrative
From requirements to daily work
A manufacturer managing several product families can maintain a shared foundation for identity, roles, APIs and audit trail, then apply the dataset required by each sector act. EU Registry registration becomes a controlled workflow stage rather than a separate manual activity.
What needs configuration and validation
NexusDpp is designed to support unique identifiers, data carriers, APIs, interoperability, versioning, roles, audit trails and Registry integration flows. Actual conformity depends on configuration, the product, applicable sector legislation and tested integrations. The platform does not replace case-specific legal or technical assessment.
Available features, integrations and acceptance tests must be specified in the agreed service scope. An information page is not a conformity certificate. Project status and transparency.
Primary sources and editorial method
Editorial review: 30 September 2026. Regulatory references are distinguished from NexusDpp organisational proposals. Always consult the applicable text and any subsequent updates.
- EUR-Lex / Implementing Decision (EU) 2026/1736
Six DPP harmonised standards and presumption of conformity for covered ESPR requirements.
- EUR-Lex / Implementing Regulation (EU) 2026/1778
DPP Registry implementation, operator verification, registration, access and architecture.
- European Commission / The DPP Registry
Registry indexing role, stored data and decentralised product-data model.
- European Commission / Digital Product Passport
Official timeline, operational Registry and technical resources for economic operators.
General information, not legal advice on an individual product. Requirements, exemptions, transitions and responsibilities depend on the specific case.