A digital product passport (DPP) is a set of product data, reached through a data carrier such as a QR code, that the EU Ecodesign for Sustainable Products Regulation (ESPR) will require product group by product group. Most of that data already exists in a company: in data sheets, certificates, the ERP and supplier files, and a PIM is the place to collect it, check it and publish it.
On this page 6 sections
Start with a review of the data you have, not with buying passport software, and choose a partner who can show the data model on your own products.
This guide describes the legal status as of 19 November 2026. We are not a law firm: which rules apply to your products is a question for your lawyer. We describe the data.
When does the digital product passport become mandatory?
Product group by product group. The passport comes from Regulation (EU) 2024/1781 (ESPR). Under it, the obligation for a product group arises only with a delegated act of the European Commission, from the date of application set in that act. The Commission's working plan of 16 April 2025 gives indicative adoption years: 2026 for iron and steel, 2027 for textiles and apparel, tyres and aluminium, and 2028 for furniture. These are planned adoption dates, not obligation dates.
Some products have a passport under separate EU rules. From 18 February 2027 every LMT battery, every industrial battery with a capacity above 2 kWh and every electric vehicle battery placed on the market or put into service must have a battery passport under Regulation (EU) 2023/1542.
ESPR also required the Commission to set up a digital product passport registry by 19 July 2026 (Article 13). The economic operator that places the product on the market uploads at least the unique identifiers to it.
What data does a digital product passport need?
The delegated act for each product group decides the exact list. ESPR Annex III sets the menu the Commission chooses from. Grouped the way a product data team would see it:
Area | What the passport can require | Where it usually sits today |
|---|---|---|
Identification | Unique product identifier, GTIN, commodity code such as TARIC | ERP, GS1 registration |
Composition | Materials, substances of concern with name, location in the product and concentration | R&D, supplier declarations, spreadsheets |
Origin and operators | Manufacturer and its unique operator identifier, facility identifiers, importer with EORI number, the responsible operator in the EU | ERP, supplier master data, legal |
Documents | Declaration of conformity, technical documentation, certificates | Shared drives, quality department |
Use and safety | Manuals, instructions, warnings, safety information | Technical writing, PDF files |
Performance and end of life | Where the act requires it: durability, repairability, carbon footprint, repair, disassembly and recycling information | Product management, external studies |
ESPR adds technical rules. The passport is linked to a persistent unique product identifier through a data carrier on the product, its packaging or its documentation. Its data must be machine-readable and based on open standards. The delegated act says whether the passport is kept per model, batch or item, and the passport must stay available for the period it sets, including after insolvency, with a back-up copy kept by a passport service provider.
How does a PIM prepare passport data?
A PIM does not make a product compliant. It makes the data findable, complete and the same in every place it is used. In the projects we plan for passport data, the PIM does five jobs:
- A data model per product group. Attributes, value lists and relations for composition, origin, documents and performance, built so they can grow when the delegated act for your group is published.
- Documents next to the product. Declarations of conformity, certificates and manuals linked to the right product and version in the DAM, instead of a shared drive.
- Supplier data in, with a person approving it. Composition and origin data often come from suppliers. Supplier PDFs and spreadsheets can be read by openProd, our AI import tool, or uploaded through a supplier portal.
- Checks before publishing. Validation and completeness rules stop a product with missing passport fields from going out.
- Publishing. The same data goes to the shop, to distributors and to a public passport page behind a QR code, fed from the PIM.
One limit is worth knowing early. A PIM holds data per product model well. If the delegated act asks for batch or item level, part of the data lives in production systems (ERP or MES), and the passport needs an integration with them.
Does LemonMind have a ready digital product passport product?
No. We do not sell a ready-made passport product, and we do not think a passport can simply be bought. In our projects the passport data is built as a data model in the PIM, with validation rules and a public passport page fed from it. The first step is a review of the product data you already have. When the review shows what is missing, the next step is a passport demo on your own data.
How to choose a DPP implementation partner
When we look at what companies are offered, the same questions separate the useful partners from the rest:
- Data or legal? A good partner says plainly which part is data work and which part is a legal question for your lawyer.
- Your products, not a demo catalogue. Ask to see the passport data model built on a sample of your own products.
- Supplier data. Ask how composition and origin data will be collected from suppliers, and who approves it.
- Model, batch or item. Ask how batch or item level data will reach the passport if your delegated act requires it.
- Standards. ESPR points to ISO/IEC 15459 for identifiers and data carriers. Ask how identifiers and the QR code will be generated and kept.
- A ready DPP solution. If someone offers one, ask what exactly is in it, which delegated acts it covers, and what it does with data that is not yet in your systems.
Who implements this: LemonMind
LemonMind is a Pimcore Platinum Partner, one of two in Poland, based in Gdańsk and working since 2010, with more than 35 PIM implementations. We build product data compliance into the PIM: the data model, checks before publishing and data for channels, in Pimcore, Akeneo or Ergonode. See our product data compliance page for GPSR, the passport and environmental claims.
Related work: for Marcopol we generate the catalogue, data sheets and declarations of conformity from Pimcore data, so a document always matches the product record. Background on the regulation: PXM and regulatory compliance.
If you already run Pimcore, our online Pimcore check includes readiness for the product passport. Otherwise talk to us about a review of your product data.
Sources
- Regulation (EU) 2024/1781 (ESPR), EUR-Lex · accessed 2026-11-19
- Ecodesign for Sustainable Products and Energy Labelling Working Plan 2025-2030, COM(2025) 187 · accessed 2026-11-19
- Regulation (EU) 2023/1542 on batteries, EUR-Lex · accessed 2026-11-19




