DPP registry: EU technical guidelines are out
The Commission has published the technical documentation for the EU Digital Product Passport registry. What it contains, who it affects first and what to do now.
Oskar CornelissenCo-Founder & CLO, RegulyPublished 18 Nov 2026 · 8 min read
Contents
On 16 November 2026 the European Commission published the full technical documentation for the EU registry of Digital Product Passports. It explains how companies and their service providers connect their systems to the registry, how they authenticate, and how passport data is described and validated in machine-readable form. It creates no new obligations. But for the first time it shows in detail how the requirements of the Ecodesign Regulation (ESPR) and the implementing regulation on the registry are to be met technically. Battery manufacturers need it first: from 18 February 2027, certain batteries must carry a digital battery passport.
- Who
- European Commission, DG Internal Market (GROW)
- Published
- 16 November 2026, documents dated 30 October 2026
- Scope
- Five guides and specifications plus semantic data resources
- Audience
- Economic operators, DPP service providers, developers and IT teams
- Legal basis
- Art. 13 ESPR (Reg. (EU) 2024/1781), Implementing Regulation (EU) 2026/1778
- First use case
- Battery passport under Art. 77 Batteries Regulation (EU) 2023/1542
- Key date
- 18 February 2027
- Test environment
- Available, features are added gradually
What the registry is and what it is not
The Digital Product Passport is decentralised. The actual product data stays with the company or with a service provider it appoints. The EU registry, by contrast, is an index: it records which passports exist for products on the EU market and stores at least their unique identifiers. For customs clearance the commodity code is added. Delegated acts or other Union law may require further registration data. This is set out in Art. 13 ESPR. The Commission had to set up the registry by 19 July 2026. Organisations can now enrol.
- Registration: the company uploads the identifiers and registration data and automatically receives a unique registration identifier.
- No proof of conformity: the registration identifier only confirms that a passport is registered. It says nothing about whether the product meets the requirements.
- Customs: customs authorities use the EU Single Window Environment for Customs to check whether imported goods have a registered passport with a matching commodity code. If not, the goods cannot simply be released for free circulation.
- Authorities: the Commission, market surveillance and customs have access to the registry data.
- Public: the Commission is also building a public web portal (Art. 14 ESPR) where passport data can be searched and compared within the applicable access rights.
The documents at a glance
The Commission has bundled the technical guidelines on its Digital Product Passport page. All documents are dated 30 October 2026. In addition there is the user guide for economic operators, available in its third version since September 2026.
| Document | Content | Relevant for |
|---|---|---|
| API Integration Guide for Economic Operators | Connecting your own systems to the registry APIs: authentication, passport registration, API usage, error handling | IT teams and service providers registering passports automatically |
| OpenAPI Specifications | Machine-readable description of the public registry APIs with operations, request and response structures | Developers |
| Service Account Technical Integration Guide | System-to-system access via service accounts, sign-in with private_key_jwt, key and token handling | Anyone working through automation rather than the web interface |
| Self-Hosted Authentication Guide | Securing self-hosted passports: validating access tokens (JWT, JWKS, audience), authorisation, error cases | Companies running passports on their own infrastructure |
| Semantic Data Guide and Semantic Data Artifacts | Taxonomies, validation schemas (SHACL), JSON-LD contexts and versioning, initially for the battery passport | Data owners and service providers structuring passport data |
Document
API Integration Guide for Economic Operators
- Content
- Connecting your own systems to the registry APIs: authentication, passport registration, API usage, error handling
- Relevant for
- IT teams and service providers registering passports automatically
Document
OpenAPI Specifications
- Content
- Machine-readable description of the public registry APIs with operations, request and response structures
- Relevant for
- Developers
Document
Service Account Technical Integration Guide
- Content
- System-to-system access via service accounts, sign-in with private_key_jwt, key and token handling
- Relevant for
- Anyone working through automation rather than the web interface
Document
Self-Hosted Authentication Guide
- Content
- Securing self-hosted passports: validating access tokens (JWT, JWKS, audience), authorisation, error cases
- Relevant for
- Companies running passports on their own infrastructure
Document
Semantic Data Guide and Semantic Data Artifacts
- Content
- Taxonomies, validation schemas (SHACL), JSON-LD contexts and versioning, initially for the battery passport
- Relevant for
- Data owners and service providers structuring passport data
For batteries, the Commission has also published an overview of data points per battery category, currently version 3.2 of 19 October 2026. The semantic resources turn these data points into testable rules. A passport that does not match them is rejected at registration.
What the implementing regulation lays down
The guidelines implement Implementing Regulation (EU) 2026/1778. The Commission adopted it on 16 July 2026, and it has been in force since 6 August 2026. It covers all products for which Union law requires a registered passport: besides the ESPR product groups, batteries and in future, for example, construction products, toys and detergents. These are the key points for companies:
- Verification first: only verified economic operators may register. Identity is proven, for instance, with qualified electronic signatures or seals or an electronic identification at assurance level high. Verification is valid for at most three years. Once it expires, no new registrations or changes are possible.
- Right level: registration happens at the level set by the applicable law, i.e. per model, batch or item. Where several requirements apply, the most granular one counts.
- Automatic checks: the registry checks, among other things, semantic conformity, the level, the commodity code and, where relevant, the link to the backup copy held by the service provider.
- Proof: on request the registry issues an electronically sealed document confirming the registration. It can be retrieved for 90 days and regenerated.
- Responsibility: the company is liable for the accuracy, completeness and currency of its data, even if a service provider registers on its behalf. The provider must itself be verified in the registry.
- Retention: all changes are versioned. Unless sector law says otherwise, the registry deletes registration data after ten years.
Self-hosting or service provider: what the guidelines say
The guidelines leave both routes open. If you host your passports yourself, the Self-Hosted Authentication Guide requires you to check who may access restricted data, such as market surveillance authorities or recyclers. The registry issues tokens for this, which your own server must validate. Regardless of that, Art. 10(4) ESPR requires a backup copy with a Digital Product Passport service provider when the product is placed on the market, so the passport stays available even after insolvency. Nobody can do entirely without a service provider. We compared which option suits which company in a separate article.
Timeline
18 July 2024
ESPR enters into force
Art. 13 obliges the Commission to set up a registry for Digital Product Passports.
16 July 2026
Implementing regulation on the registry
The Commission adopts Regulation (EU) 2026/1778. In force since 6 August 2026.
19 July 2026
Deadline for the registry
By this date the Commission had to set up the registry. Organisations can now enrol.
16 Nov 2026
Technical guidelines published
API guide, OpenAPI specification, guides on service accounts and authentication, semantic resources.
18 Feb 2027
Battery passport becomes mandatory
For light means of transport batteries, industrial batteries above 2 kWh and electric vehicle batteries. By then Member States also appoint their national registry administrators.
later
Further product groups
A product group only becomes subject to the obligation with its delegated act under the ESPR or its own sector law.
For all other sectors the registry sets no deadline of its own. When a passport becomes mandatory for textiles, furniture, steel or electronics is decided by the respective legal act. Which dates are fixed and which are only planned is shown in our roadmap to 2030.
What companies should do now
- Check whether you are affected. Anyone placing batteries of the categories above on the market needs registered passports from February 2027. Everyone else should check whether a legal act already exists for their product group.
- Enrol your organisation in the registry. Start verification, appoint responsible people and assign permissions, including for service providers that will register on your behalf.
- Decide on the operating model. Self-hosting with token validation as per the Authentication Guide, or a service provider. The backup copy with a service provider is mandatory either way.
- Prepare master data. For each product, define the commodity code, the registration level (model, batch, item) and the unique identifiers for product, operator and facility under Art. 12 ESPR.
- Use the test environment. The Commission runs an acceptance environment with a separate EU Login account. Registration and validation can be tried there without creating live data.
- Validate data against the schema. Anyone preparing a battery passport should check their data against the semantic rules early. Otherwise errors only surface at registration.
Talk it through in person
Set up a passport that is ready to register
We show you which product data your passport needs and how to structure it so that registration and validation run smoothly. Talk to us about where you stand.
Book a callWritten by
Oskar CornelissenCo-Founder & CLO, Reguly



