he Digital Product Passport (DPP) is a set of product data made available through a data carrier placed on the product, its packaging or accompanying documentation, as required by the EU Ecodesign for Sustainable Products Regulation (ESPR). The requirement does not take effect across all industries at the same time. It is being introduced for individual product groups through delegated acts, with the first covering iron and steel, textiles and tyres. For companies selling online, DPP is, in practice, a product data project rather than a legal compliance project. This is the aspect that is most often misunderstood.
Legal framework and key dates
The legal framework for the DPP is established by the ESPR, Regulation (EU) 2024/1781 of the European Parliament and of the Council on ecodesign requirements for sustainable products.
Two points are worth remembering from this table. First, the EU-level infrastructure is already in place, so the argument that “this is still a long way off” ceased to be valid in 2026. Second, the first actual passport obligation is not a DPP under the ESPR, but the battery passport under the Batteries Regulation, which becomes mandatory on 18 February 2027 for industrial and electric-vehicle batteries with a capacity greater than 2 kWh, as well as batteries for light means of transport.
Timeline by product group
Delegated acts specify exactly what the passport must contain for a given product group. The schedule below comes from the first working plan. These are the planned dates for adopting delegated acts, not the dates when the obligations begin to apply.
The interval between the adoption of an act and the start of the obligation is deliberate. Article 4(4) of the ESPR provides that a delegated act cannot start to apply earlier than 18 months after its entry into force, except in duly justified cases. This creates a real window for preparing product data. For textiles, it means, in practice, two to three years from now.
Who is responsible for the DPP?
The answer determines who takes ownership of the project within an organisation, and it is also a frequent source of confusion.
Responsibility lies with the economic operator placing a product on the EU market. The European Commission identifies manufacturers, authorised representatives, importers, distributors, dealers and fulfilment service providers in this context. Primary responsibility for creating the passport and ensuring the accuracy of its data rests with the operator placing the product on the EU market.
This translates into four operational responsibilities:
- Collect product data in digital form, in line with the requirements of the relevant delegated act.
- Register the passport in the EU DPP registry in accordance with the technical requirements.
- Place a physical data carrier on the product, its packaging or accompanying documentation.
- Maintain data accuracy throughout the product’s lifecycle.
The fourth point often comes as a surprise. The ESPR requires passport data to remain available for the expected lifetime of the product, including when the economic operator becomes insolvent, is liquidated or ceases trading. In practice, this means arranging a backup with an independent service provider. For a brand that currently keeps product data in spreadsheets and in descriptions entered manually into its online store, this is an architectural change, not a cosmetic one.
There is another important point that is rarely explained accurately: the ESPR does not impose an unconditional ban on including personal data in a passport. Article 10(1)(e) states that personal data relating to customers must not be stored in the passport without their explicit consent, in accordance with Article 6 of the GDPR. The condition is consent, rather than an outright prohibition. Nor does the regulation establish anonymous access as a general rule: Article 11(1)(b) grants customers free and easy access to the passport within the scope of their applicable access rights. In practice, designing a passport therefore means designing an access-permissions model, rather than assuming that all data is either public or completely restricted.
Normy techniczne, czyli co już jest rozstrzygnięte
To jest najbardziej pomijany element publikacji o DPP w Polsce, a jednocześnie najważniejszy dla zespołów technicznych. Komitet CEN/CENELEC JTC 24 opracował zestaw norm, które określają, jak paszport ma być zbudowany. Sześć z nich zostało opublikowanych 27 maja 2026, a 15 lipca 2026 przywołano je w Dzienniku Urzędowym UE, co nadało im status norm zharmonizowanych.
Two further standards in this set have not yet been referenced in the Official Journal: EN 18239, covering access-rights management, information-system security and trade secrets, and EN 18246, covering authentication, trustworthiness and data integrity. CEN and CENELEC state that six of the eight standards have been referenced.
The practical consequence is straightforward and useful for businesses. There is no need to invent a proprietary passport format or wait for a delegated act before starting work. The technical framework has already been defined, so organisations can begin with the most time-consuming task: getting their data into order.
Why DPP is a data project, not a compliance project
Many businesses approach DPP in the same way as GDPR or GPSR: as a legal department task that ends with a document and a declaration. This is a fundamental misunderstanding and one that can cost months of work.
The passport is an interface to data that an organisation either holds in one place, in a consistent structure, or does not. The passport itself can be generated in a matter of weeks. Getting the underlying data into a state where generating it makes sense takes months. The sequence is therefore the reverse of a typical compliance project: data first, passport second.
Six gaps that prevent DPP implementation in practice
The following list is based on projects involving product catalogue restructuring and PIM implementations. If three or more points sound familiar, preparing for DPP will take quarters rather than weeks.
- No single source of truth for product data. Information exists in parallel in ERP systems, spreadsheets, supplier files and descriptions entered into the online store. There is no reliable way to identify the authoritative version.
- No stable identifier at variant level. An identifier exists for the model, but not for a specific variant and batch, even though the passport requires a more granular level of identification than the model.
- Material composition stored in descriptive fields. Composition appears in marketing copy instead of attributes with defined controlled vocabularies, so it cannot be processed automatically.
- No structured data from suppliers. Information about material origins, carbon footprint or recycled content arrives in PDFs and emails.
- No version control or change history. It is impossible to reconstruct which data applied to a batch manufactured two years ago, even though the passport relates to that very batch.
- No ongoing maintenance process. Nobody owns attribute accuracy after implementation, so data becomes inconsistent again within a few months.
The role of a PIM system
A PIM (Product Information Management) system addresses five of the six issues above. By design, it provides a single source of truth for product data and supports attribute dictionaries, versioning and approval workflows. It does not solve the sixth issue: maintaining data is an organisational responsibility, not simply a system feature. That distinction matters.
Not every company needs a PIM system for DPP. For a catalogue of fewer than a few hundred items, with one supplier and a stable product range, a well-organised ERP structure and disciplined processes may be enough. PIM becomes practically unavoidable when a business combines multiple sales channels, multilingual content, many data suppliers and a catalogue running into thousands of items.
What a DPP preparation project looks like
Below is the structure we use at Strix in projects that organise product data for DPP and, more broadly, for automation.
Phase 1: data readiness audit — 2 to 4 weeks. Inventory data sources, assess the completeness of attributes required by the delegated act relevant to the industry, identify supplier-side gaps and evaluate the granularity of identifiers. The result is a prioritised gap list and a decision on whether a PIM system is needed.
Phase 2: data model — 3 to 6 weeks. Design an attribute structure with controlled vocabularies, assign ownership to each attribute and map the model to the identifier requirements of EN 18219 and the data exchange format of EN 18216.
Phase 3: implementation and migration — 2 to 4 months. Deploy a PIM system or restructure data in an existing system, migrate and enrich the information, integrate with ERP and the e-commerce platform, and introduce a process for obtaining data from suppliers.
Phase 4: passport layer — 4 to 8 weeks. Generate passports, implement data carriers, register passports in the DPP registry, arrange backup with an independent service provider and provide a public-facing passport interface.
The third phase takes the longest and accounts for most of the cost. Companies with an organised PIM system can move to the fourth phase almost immediately. That is the tangible value of implementing PIM earlier.
What the DPP does not require
This section is just as important as the preceding ones because much of the information circulating in the market overstates the scope of the obligation.
- DPP does not currently apply to all products. Requirements apply to groups covered by delegated acts. If your category is not included in the working plan, there is no specific deadline for you to prepare for.
- DPP does not require a single central EU database. The DPP registry stores identifiers and points to where the data can be found. The underlying data remains decentralised and under the responsibility of the economic operator.
- DPP does not require commercially sensitive information to be disclosed to everyone. Access differs for consumers, supply chain participants and market surveillance authorities. A separate standard, EN 18239, addresses the management of access rights.
- DPP does not replace declarations of conformity or labels. It adds another layer of information; it does not replace existing obligations.
How Strix approaches DPP
Strix is an e-commerce agency established in 2009, with offices in Poland, the Netherlands and Germany. We approach DPP from the product data perspective because this layer determines whether the project succeeds, and because it is where we have hands-on experience.
- home&you: implementation of Ergonode PIM and restructuring of the product catalogue for a multichannel home furnishings brand.
- Profix: a scalable Shopify e-commerce platform integrated with Ergonode, where the product data structure was a foundation of the project rather than an afterthought.
- Tatuum: a Magento e-commerce architecture rebuild with Ergonode PIM for a fashion brand, operating in an industry covered by the planned delegated act for textiles.
- Apteka Melisa: restructuring 21,000 product descriptions using AI, demonstrating the scale at which manual work stops being a viable option.
We are a Pimcore partner and also implement Ergonode, so we can compare PIM systems without being tied to a single platform. If a properly organised ERP system is sufficient in your case, we will say so.
Frequently asked questions
What is the Digital Product Passport?
It is a set of product data made digitally accessible through a data carrier placed on the product, its packaging or accompanying documentation. The required data is specified in delegated acts adopted under Regulation (EU) 2024/1781 (ESPR).
When does the DPP become mandatory?
There is no single date for all products. The EU’s first product-passport requirement is the battery passport, mandatory from 18 February 2027 for industrial and electric-vehicle batteries above 2 kWh. Under the ESPR, the first delegated acts cover iron and steel (adoption indicated for 2026), followed by textiles and tyres (2027). Requirements generally start applying around 18 months to two years after an act is adopted.
Who is responsible for creating the passport?
The economic operator placing the product on the EU market: a manufacturer, authorised representative, importer, distributor, dealer or fulfilment service provider. Responsibility for data accuracy lies with that operator, not the software provider.
Do I need a PIM system to meet DPP requirements?
Not always. PIM becomes practically essential when a catalogue contains thousands of items and the business has multiple sales channels, multiple languages and many data suppliers. With a small, stable catalogue, a well-organised ERP structure and disciplined processes may be enough.
Is passport data stored in a central EU database?
No. The DPP registry, which the Commission was required to establish by 19 July 2026 under Article 13(1) of the ESPR, stores unique identifiers and points to data locations. The underlying data remains decentralised, under the responsibility of the economic operator. The registry’s operating rules are set out in Implementing Regulation (EU) 2026/1778, in force since 6 August 2026.
Which technical standards define how the passport is built?
Six CEN/CENELEC standards published on 27 May 2026 and referenced in the Official Journal of the EU on 15 July 2026: EN 18216 for data exchange, EN 18219 for identifiers, EN 18220 for data carriers, EN 18221 for storage, EN 18222 for APIs and the passport lifecycle, and EN 18223 for interoperability. Two more, EN 18239 for access rights and security and EN 18246 for authentication and data integrity, have not yet been referenced.
Can the passport contain customers’ personal data?
Only with the customer’s explicit consent. Article 10(1)(e) of the ESPR states that personal data relating to customers must not be stored in the passport without their explicit consent, in accordance with Article 6 of the GDPR. This is a consent requirement, not an unconditional ban. The ESPR also does not establish anonymous access as a general rule: access depends on the rights assigned to the relevant user groups.
How long does it take to prepare an organisation for DPP?
The passport layer itself typically takes 4 to 8 weeks. Product data preparation is the decisive factor: where a catalogue needs substantial restructuring, it takes 4 to 8 months. Companies with an implemented PIM system can move to the passport layer almost immediately.
What should I do first if there is no delegated act for my industry yet?
Start with a product data readiness audit. It is valuable regardless of DPP because the same data structure supports content automation, multichannel sales, international expansion and product visibility in AI-driven channels.
Next step
If you want to know how ready your product data is for DPP, the starting point is a data readiness audit. The outcome is a prioritised list of specific gaps and an estimate of the effort required, rather than a generic recommendation.
Strix: an e-commerce agency established in 2009, with offices in Kraków, Utrecht and Frankfurt. Pimcore partner and Ergonode implementation specialist.