The more we know about the DPP, the more questions we have

Recently, as members of CEN-CENELEC JTC 24, we were tasked with preparing questions for the European Commission that may be raised at the upcoming plenary meeting. We are certainly not short of questions - I prepared several myself, and most of them are no longer about what the Digital Product Passport is, but about who we are within its structure, how we are supposed to navigate it, and how to correctly understand the concepts it contains.
The most important questions begin where regulation, standards and the reality of a specific industry have to meet in a single system.
As we know, the Battery Passport and the DPP under ESPR are not the same legal regime - but they are meant to operate within one architecture. That is why one of the most interesting areas for me today is the relationship between the Battery Passport arising from the Battery Regulation and the DPP being developed under ESPR, as well as the diversity built into ESPR itself.
In principle, the Battery Regulation is already very specific: from 18 February 2027, the relevant LMT batteries, industrial batteries >2 kWh and EV batteries must have a passport. Nothing suggests this date will change - so it appears the regulator will expect batteries sold after that date to have passports. The battery passport covers both information relating to the battery model and information relating to the individual battery, and access to some of the data depends on the role and, in certain cases, on a legitimate interest. That much we know for sure. ESPR, by contrast, builds a horizontal model and says: the relevant delegated act for a product group will determine “whether”... or rather “how” the DPP is to be created at the model, batch or item level, and what (or who) will define those levels. On the surface this assumption sounds logical - until we sit down with a specific industry and try to issue a passport (which is something we have been doing at Veridi for a while now).
For example: in the commercial practice of the textile industry, we see identification going down to, for instance, the combination of style/model → colour → size, and this is the normal way of identifying a product (e.g. a GTIN for a women's polo shirt/white/XS); sometimes further variants come into play as well, such as seasons.
Since we do not yet have a sector-specific definition of a model for textiles, a point of reference may be recital 33 of the preamble to the ESPR, according to which a “model” usually refers to a version of a product of which all units share the same technical characteristics relevant for the ecodesign requirements and the same model identifier.
But... are we working with an unambiguous understanding of this concept? Is every model the same? Let's look at how it works in practice.
Batteries take precedence (a separate regime, but harmonised standards): “battery model” means a version of a battery, all units of which share the same technical characteristics relevant to the requirements of the Regulation on sustainability, safety, labelling, marking and information, and the same model identifier.
Toys (TSR - it applies later, but the text is already known): a “toy model” is a group of toys that share a common manufacturer, the same design and technical characteristics, the same materials and production processes, and a common identification element.
CPR: not a model but a “product type”, which means the abstract model of individual products, defined by the intended use and a set of characteristics which preclude differences with respect to performance or compliance with product requirements (...), whereby identical products of different manufacturers belong to different product types.
Iron and steel (JRC, working proposal within the ESPR preparatory study for iron & steel, March 2026): in the document, the model level is described as a specific configuration of a steel product, defined by a set of technical specifications that affect the properties of the material and its intended use. The JRC specifically points to: steel grade according to EN 10027-1, steel number according to EN 10027-2, product form according to EN 10079 and treatment condition according to EN 10027-1.
Detergents and surfactants: “model” means a group of detergents or surfactants which have the same manufacturer and are placed on the market under the same trade name, have the same content in accordance with Part A, point 1(h) of Annex V and are manufactured using the same production processes, where relevant are covered by the same CLP classification, and are defined by a type number or other element allowing their identification as a group.
And now, coming back to fashion: what in this arrangement is a “model” within the meaning of the future DPP? Is a model a single style regardless of colour and size? Does a colour already create a new model? What about size? Or perhaps the business-natural concept of a variant should find its place in the regulation, between a very broad model and a very detailed item? Because a production batch answers a completely different question than a product variant. And while the individual item level is the most precise, in some sectors it would potentially mean tens of millions of individual identifiers and passports. This is exactly where theory meets production.
ESPR deliberately leaves the decision on the DPP level to sectoral acts. For textiles, the final delegated act has not yet been adopted; the Commission currently indicates its planned adoption for Q4 2027, and the JRC's preparatory work and consultations are already under way. In other industries waiting for their delegated acts, too, the question is not “what does ESPR say today?” but how to translate the passport architecture into the real product structure used by a specific industry, while preserving the integrity of the norms and standards being implemented.
Here another layer appears, or level of business decisions. “Shall”, “should” and the question: “what do I need to have today?” (because it is increasingly clear that the implementation of legal acts is deliberately split into stages), and a similar problem arises when implementing standards.
In standards, the difference is clear-cut:
- shall = requirement
- should = recommendation.
But from the perspective of a company preparing a production system, another distinction matters more:
- what is mandatory today?
- what will be required once the sectoral act comes in?
- what follows from the standard?
- what gives a presumption of conformity?
- and what is good practice worth implementing right now?
These are not academic questions. The answers determine the system architecture, the data model, integrations, and the money companies are spending today.
Six of the eight standards prepared by CEN-CENELEC JTC 24 have already been cited as harmonised standards; two more - on access rights/security and on authentication, reliability and integrity - complete this architecture. Plus a whole handful of regulations and directives that I informally call “sister” acts - they are closely related or connected, they can easily slip by in this sheer volume of information, and it is worth following the progress of work around these solutions.
And that is precisely why the deeper we go into implementation, the more questions arise at the interface between individual documents.
Providers? That is a separate topic and quite an interesting paradox. We are already building DPP solutions and preparing for the role of DPP service providers - that is what the market and the regulator itself expect - but the European framework for providers is not yet complete. The Commission currently indicates the adoption of the relevant acts on DPP Service Providers for 2027. At the same time, the DPP Registry has been live since 20 July 2026 and by default allows providers to be registered (so far designated as vendors, subcontractors), but there are still no concrete solutions in sight; it remains a theoretical solution, and the entire regulatory and technical ecosystem around it is still being filled in.
As providers, we are implementing systems whose subsequent regulatory and technical layers are still being created. This is not a criticism of the regulator - it is simply the reality of building new regulatory infrastructure in real time. And the closer you are to the work, the less simple the answers become.
People who are close to the regulation, who follow the work of CEN-CENELEC, take part in technical groups, work at the W3C (incidentally, Veridi has joined the family of organisations working in W3C working groups), or who are actually trying to build a working DPP, have a great many questions, because these questions are born of practice. A certain stir is already noticeable, our calendar is genuinely packed, organisations are starting to discover that the “regulatory ecosystem” is enormous, and that working through the documents can take months. In my view, this is a sign of this market maturing, not of its weakness.
Manufacturers have concerns about data access and voice them loudly during consultations. Concerns about years of their work, and about making sure no one steals their experience and know-how. While access to public information is obvious to most, non-public information causes real unease. Supply chains, logistics chains, B2B, subcontractors. The question arises: who and how. Who will have access, and in what way.
Both ESPR and the Battery Regulation provide for different levels of access and permissions, and ESPR explicitly provides for the possibility of establishing procedures for issuing and verifying digital credentials for economic operators and other authorised entities. With the development of the European identity infrastructure (where we hope to join the group of those testing the solutions), credentials and authentication, the direction seems fairly clear: authorities will receive the appropriate digital permissions, providers will be obliged to ensure access, and inspection will be automated. Not everyone will see everything - but an entity with the appropriate role and authentication will be able to obtain access to the information it is entitled to.
In practice, individual providers will probably implement this architecture in the various ways indicated in the standards and guidelines, but the key will be for the result to be interoperable. Now we need to connect the worlds - regulatory, industry and IT. Ahead of us lie further work in JTC 24 WG1, the JTC 24 plenary meeting, the CROSS area, and an analysis of how individual regulations intersect with the common DPP architecture. But some of these questions should not remain purely European. We are also taking them to ISO/IEC JTC 5, whose task is to build the international foundations of the DPP, ensuring interoperability across sectors and systems.
This is particularly important because, through liaison roles, I am today at the interface of the work of five committees in total. From this perspective it is very clear that the next stage cannot be developing each piece of the DPP separately. We have to start testing them together. Regulation with regulation. Standard with standard. Identifier with data carriers. Access rights with the user's actual role. The data model with a real product. And legal requirements with the production line.
And I think we all need proper workshops rather than yet another meeting about what a DPP is. Workshops where we put on the table: a battery, a T-shirt, a steel product, a component, a real supply chain and a real economic operator case. And try to take them end-to-end through regulation, standards and the system.
Interested? Write to us: contact@veridi.pl
