When a product enters the EU’s Digital Product Passport system, the first technical question is simple: what does the central registry actually hold? The answer is less than most people expect. The DPP Registry User Guide for Economic Operators defines the DPP Registration Record as a minimal set of data stored in the registry, binding the Unique Product Identifier (UPI) with a Unique Registration Identifier (URI). Understanding what each of those identifiers does, and where the actual product data lives, is the foundation of any compliant unique product identifier DPP registry implementation.
What the DPP Registration Record Contains
The Registration Record is intentionally small. It holds the UPI, the URI returned by the registry, and two optional fields: a Model Identifier and a Batch Identifier. That is the complete list. The registry does not store product specifications, material declarations, carbon footprint data, or any of the other information that makes up a full Digital Product Passport. Those data sets live elsewhere, under the economic operator’s control.
There is one additional mandatory field for a specific category of products. Under Regulation (EU) 2024/1781, Article 13(1), the registry must also store the commodity code for any product intended to be placed under the customs procedure “release for free circulation.” If your product crosses an EU border under that customs procedure, the commodity code is not optional.
Article 13(1) of Regulation (EU) 2024/1781 also specifies that the registry shall store “the unique identifiers for batteries as referred to in Article 77(3) of Regulation (EU) 2023/1542.” Batteries therefore have their own identifier obligations layered on top of the general framework.
The Unique Product Identifier: Format, Length and Who Supplies It
The UPI is the identifier you, as the economic operator, create and supply at registration. It is URL-based and must conform to a URL format compliant with JTC 24 standards. It has a maximum length of 50 characters and is mandatory at registration. You cannot register a product without it.
The URL-based format is not arbitrary. A URL-structured identifier can be resolved directly, meaning a scanner, customs system, or market surveillance authority can follow the identifier to the product data without needing a separate lookup table. This connects to the broader question of how identifiers and data carriers work in practice, where standards like GS1 Digital Link use URL syntax to encode product identity in a scannable format.
The 50-character limit is strict. If your current internal product identifiers are longer, or if you are building a URL that includes domain names, product codes, and version numbers, you need to plan your identifier structure before registration, not after. A UPI that exceeds 50 characters will be rejected.
The Unique Registration Identifier: What the Registry Returns
The URI is not something you create. It is returned by the DPP Registry as the result of a successful registration. Once the registry accepts your UPI and creates a record, it issues a URI that identifies that specific record held centrally. The URI connects to the DPP Data via the UPI.
Think of the relationship this way: the UPI is the address you give the registry so it can find your product data. The URI is the receipt the registry gives you confirming that the record exists. Both are needed for the system to function. A market surveillance authority querying the registry will use the URI to locate the record, then follow the UPI to reach the actual DPP Data.
Where the DPP Data Actually Lives
This is the point most often misunderstood. The registry does not host your product passport data. The DPP Registry User Guide states clearly that DPP Data is created and stored by economic operators, held in the economic operator’s or a service provider’s database, and must be resolvable at all times.
“Resolvable at all times” is a real operational requirement, not a vague aspiration. If a customs authority, a recycler, or a market surveillance body queries your UPI and the data endpoint is down, you are not compliant. Uptime, data availability, and endpoint maintenance are your responsibility.
Using a service provider to host your DPP Data does not change who is responsible for it. The User Guide is explicit: registering with a service provider does not transfer that responsibility to the provider. You remain the economic operator of record. If the data is wrong, missing, or inaccessible, the obligation sits with you.
Model Identifier and Batch Identifier: Optional but Useful
Two optional fields can be supplied at registration alongside the mandatory UPI: the Model Identifier and the Batch Identifier. Neither is required to complete a valid registration, but both serve practical purposes.
The Model Identifier allows you to group individual product registrations under a common model reference. This matters when you are registering large volumes of individually serialised products that share the same design, material composition, and repair documentation. Querying by Model Identifier can return all registrations for that model without requiring a separate lookup for each unit.
The Batch Identifier links a registration to a specific production batch. For sectors where batch traceability is already standard, such as food contact materials or chemicals, this field maps naturally onto existing internal systems. For sectors new to batch-level tracking, it is worth building the batch reference into your identifier architecture from the start rather than retrofitting it later.
Battery-Specific Obligations Under the Unique Product Identifier DPP Registry Framework
Batteries face a more specific set of obligations than most product categories. Article 13(1) of Regulation (EU) 2024/1781 requires the registry to store the unique identifiers for batteries as defined in Article 77(3) of Regulation (EU) 2023/1542. That cross-reference means battery identifiers must meet the requirements of both regulations simultaneously.
Article 78 of Regulation (EU) 2024/1781 goes further. It amends Regulation (EU) 2023/1542 by adding Article 77(10), which requires the economic operator placing the battery on the market to upload the unique identifier into the registry. The upload obligation sits with the economic operator placing the product on the market, not with the manufacturer, the importer, or any upstream party unless they are also the entity placing the battery on the EU market.
If you distribute batteries into the EU under your own brand, you are likely the economic operator responsible for the upload. If you are a retailer selling batteries manufactured and branded by a third party, the obligation may sit with the brand owner. The distinction matters and should be confirmed in your supply chain contracts.
The EU Central Registry and What Registration Actually Triggers
The EU Central DPP Registry is the single point of registration for products covered by the Ecodesign for Sustainable Products Regulation. When you submit a UPI and receive a URI back, you have created a Registration Record. You have not submitted a product passport. You have not verified that your DPP Data is complete or accurate. Registration confirms only that the registry has a record linking your identifier to your data endpoint.
The practical implication is that registration and compliance are not the same thing. A product can be registered and still fail a market surveillance check if the DPP Data at the resolved endpoint is incomplete, outdated, or formatted incorrectly. Registration is the first step, not the final one.
Deadlines for when registration will be required depend on the product category and the relevant delegated act under the Ecodesign for Sustainable Products Regulation. For most product categories, the specific compliance dates are expected around 2026 to 2030, pending the adoption of the relevant ESPR delegated acts. No single confirmed date applies across all categories. Check the delegated act for your specific product group to confirm when your obligation begins.
What to Prepare Before You Register
Before you submit a UPI to the registry, four things should be in place.
- Your UPI structure is finalised. It must be URL-based, JTC 24 compliant, and no longer than 50 characters. Test it against those constraints before building it into your labelling or ERP systems.
- Your DPP Data endpoint is live and resolvable. The registry will accept a UPI that points to a broken endpoint, but your compliance obligation requires the data to be accessible at all times after registration.
- You have decided whether to include Model Identifier and Batch Identifier. Adding these at registration is easier than amending records later, particularly if you are registering at volume.
- You have confirmed who the economic operator of record is. For batteries especially, the upload obligation under Article 77(10) of Regulation (EU) 2023/1542 (as inserted by Article 78 of Regulation (EU) 2024/1781) sits with the entity placing the product on the market. Confirm this in writing with your supply chain partners.
If you are ready to build your registration workflow and want to see how Traceable handles UPI generation, data hosting, and registry submission, visit traceable.digital/pricing to start a free trial. Plans are available for single-product pilots through to enterprise-scale multi-category programmes.
