19 questions to the European Commission on real-world DPP implementation

DPP: the questions begin where theory ends.
The questions below were prepared on the basis of our hands-on experience implementing DPP, our work on the Veridi solution and our participation in standardisation work.
The questions have been submitted to the CEN-CENELEC Secretariat as part of the work of JTC 24. We hope they will be presented to representatives of the European Commission and addressed at the next plenary meeting of CEN-CENELEC JTC 24, which will take place on 7-9 October 2026 and in which we are taking part.
We do not treat this list as a catalogue of theoretical problems. Most of the questions arise directly from decisions that companies building and deploying DPP solutions already have to make today: they concern architecture, product identification, data granularity, access rights, the role of providers and backup providers, the relationship with the DPP Registry and the responsibilities of the individual participants in the DPP ecosystem.
1. DPP backup before the requirements for DPP Service Providers are adopted
How is an economic operator to meet the obligation to provide a DPP backup during the period in which the requirements for DPP Service Providers have not yet been adopted, in particular for the Battery Passport, which becomes mandatory on 18 February 2027?
2. Independence of the backup provider
Can the entity hosting the primary DPP and the backup provider be the same entity, or does the Commission interpret the backup obligation as requiring the use of an independent second provider?
3. The role of contributors and supply chain actors
How does the Commission see the involvement of supply chain actors that supply data to the DPP but are not the economic operator responsible for creating the passport? Can they directly update the data assigned to them without obtaining the status of an entity publishing the DPP?
4. Access rights to non-public data
How are access rights to the non-public parts of the DPP to be implemented technically? Does the Commission envisage a common model for credentials and authorisation, or will this remain dependent on the implementation of individual DPP systems?
5. A new DPP or an update to an existing passport
Which events should result in the creation of a new DPP rather than an update to an existing one? How should one proceed in the case of refurbishment, remanufacturing, a change of the responsible economic operator, a significant repair or a substantial modification of the product?
6. Integration of decentralised DPPs with the EU portal
What will the target model look like for integrating decentralised DPPs with the EU portal for searching and comparing data? Will DPP implementations have to expose specific APIs, discovery endpoints or other interfaces for the Commission's portal?
7. Stability of the current technical baseline
Following the publication of the first harmonised standards, can an implementation compliant with EN 18216 and EN 18219-18223 be treated as a sufficiently stable technical baseline for designing systems today, or should implementers expect additional requirements that may call for significant architectural changes?
8. Authentication, reliability and integrity of DPP data
How should the requirements concerning the authentication, reliability and integrity of DPP data be understood in practice? Will documenting provenance or supporting evidence be expected at the level of individual data items, or is the main concern ensuring the technical integrity of the record?
9. Identification systems and issuing agencies
Does the Commission plan to publish clear compliance criteria for identifier schemes and issuing agencies, so that an implementer can objectively verify whether a given identification solution meets the DPP requirements?
10. DPP Registry - API stability and versioning
When will the schema and API of the DPP Registry be considered production-stable, and what mechanism for versioning and backward compatibility does the Commission envisage for future changes?
11. Product model versus product variant
How does the Commission understand the distinction between a product model and a product variant for the purposes of the DPP?
In many industries, particularly in the textile sector, the natural structure of a product may look as follows:
model → colour → size
Should different combinations of colour and size be treated as separate models for the purposes of the DPP, or can they remain variants of a single parent product model?
12. The place of the variant in the DPP structure
The ESPR refers to the following levels of granularity:
model → batch → item
In practical product systems, however, there is often an additional intermediate level - the variant.
Does the Commission envisage that the variant may function as an additional level in the product structure, even if it does not constitute a separate level of DPP granularity within the meaning of the ESPR?
Could the following structure therefore be correct:
model → variant → batch → item
where the relevant delegated act specifies, or will specify, one of the levels provided for by the ESPR as the legally required level of DPP granularity?
13. What determines the existence of a separate model?
What criteria should determine whether two product variants are to be treated as two separate models for the purposes of the DPP?
Should the deciding factor be:
- technical properties relevant to ecodesign requirements,
- a separate product identifier,
- material differences,
- design differences,
- or a combination of these elements?
For example, should a difference solely in colour or size result in a separate DPP at model level?
14. Data at different levels of granularity within a single product structure
Does the Commission envisage that information relating to a single product may exist simultaneously at different levels of granularity?
For example:
- general design and product data → model,
- colour and size → variant,
- place or date of production → batch,
- serial number, usage or repair history → item.
Can the DPP refer to such information hierarchically, without the need to duplicate all information at every lower level?
15. Model-level DPP versus batch-level and item-level data
If a delegated act requires a DPP to be established at model level, will it still be possible to technically link that DPP to more detailed information on specific batches or individual items?
Does the Commission envisage a model in which the model-level DPP serves as a common information core, while batch-level or item-level data are linked to it as additional records?
16. DPP granularity versus the unique product identifier
Should the level of DPP granularity always correspond to the level of uniqueness of the identifier to which the data carrier refers?
If a DPP is required at model level, but the product has a more detailed identifier at variant or item level, can the data carrier identify that more detailed object and then lead to the corresponding model-level DPP?
Or does the Commission envisage the principle:
one level of DPP granularity = one corresponding level of product identification?
17. Product change versus the creation of a new model
How should an update to an existing DPP be distinguished from the creation of a new product model requiring a new DPP?
This is particularly important when the product remains essentially the same, but there is a change in, for example:
- the material supplier,
- a small share of one of the materials,
- a design element,
- an environmental parameter,
- the production process.
Does the Commission envisage common criteria for determining when such a change still falls within the same model and when it results in a new model?
18. Different levels of granularity in different sectors
Does the Commission envisage a common, interoperable mechanism enabling DPP systems to handle different levels of granularity in parallel?
For example, one product group may require a DPP at model level, another at batch level and yet another at item level, while in the battery sector some information may relate to the battery model and some to a specific unit.
Should the target DPP architecture allow for a common representation of the relationship:
model → variant → batch → item
regardless of which level has been designated as mandatory by a particular sectoral act?
19. Textiles as a practical case of granularity
In the Commission's current work on requirements for textiles, is the problem of a potential mismatch between the regulatory concept of a “model” and the way products are identified in the textile industry being analysed?
In particular, we are interested in the structure:
model / style → colour → size
and which of these levels the Commission currently considers as potentially corresponding to the concept of a “model” for the purposes of the DPP.
In summary
We are not asking the Commission to determine, at this stage, the content of future delegated acts for specific product groups; rather, we would like to better understand the Commission's general approach to the relationship between the regulatory architecture of the DPP, its granularity, product identification and the actual product structures and processes used by industry.
The DPP is increasingly moving from the level of general assumptions to a stage at which concrete architectural, product and organisational decisions have to be made. And that is exactly when questions emerge that were not visible before.
It is no longer just a matter of whether the DPP will be mandatory, but of exactly how it is supposed to work: at what product level, with what identifier, who can supply and update data, who is responsible for publication, how to ensure backup, how to manage access and how to connect decentralised systems with the EU infrastructure.
These are questions that need to be asked today, because the answers will have a direct impact on how DPP systems are designed and on implementation costs for businesses.
That is why it is good that they are now being brought into discussion with the European Commission. The sooner these issues can be clarified, the lower the risk that the market will build several different interpretations of the same system and later have to correct them at great cost.
And perhaps this is what matters most today: it is not about having an answer to every question right away. It is about making sure the right questions are asked before solutions become widespread and difficult to change.
