Key Takeaways
- A digital product passport (DPP) is a structured data record attached to a physical product, required under EU law for an expanding list of product categories.
- Digital product passport requirements start with batteries in February 2027. Textiles, electronics, and construction products follow between 2027 and 2030.
- The digital product passport must be accessible via a data carrier on the product, typically a QR code or RFID tag, pointing to a hosted data record.
- Manufacturers are the primary responsible party. If you sell into the EU market, this applies regardless of where you manufacture.
- Non-compliance means losing access to the EU market.
- A PIM system is the most practical foundation for digital product passport data management. Manufacturers without one will struggle to meet data quality requirements.
- Most manufacturers are further behind on data preparation than they think.
What Is a Digital Product Passport?
A digital product passport is a structured digital record linked to a specific physical product. It holds data about that product across its full lifecycle: what it's made of, how it was produced, how it can be repaired, and what happens to it at the end of life.
The concept comes from the EU's Ecodesign for Sustainable Products Regulation (ESPR), which passed in 2024. The ESPR replaces the older Ecodesign Directive and significantly expands its scope. The digital product passport is one of its central instruments. (source: https://single-market-economy.ec.europa.eu/news/ecodesign-becomes-norm-products-european-union-2024-07-19_en)
The goal is to make product information machine-readable, standardised, and accessible to everyone in the value chain: regulators, recyclers, repair shops, business buyers, and consumers.
"The digital product passport will serve as a repository of product-specific information accessible to all actors in the value chain." — European Commission, ESPR Impact Assessment, SWD(2022) 82 final, p. 114
This is a regulatory requirement, not a voluntary sustainability initiative.
What a Digital Product Passport Contains
The exact data requirements vary by product category, but the ESPR defines a common framework across all of them.
Material composition is required: what the product is made of, including substances of concern. Component information covers key parts, their origin, and whether they are replaceable. Carbon footprint data must follow EU-defined lifecycle calculation rules. Repairability information includes spare parts availability, repair manuals, and disassembly instructions. Recycled content must show the percentage and source of recycled materials. End-of-life instructions tell recyclers how to disassemble and sort the product. Compliance documentation covers certifications and conformity declarations. Supply chain identifiers link the record to specific batches, production dates, and supplier references.
Not all of this is public. The ESPR defines access tiers. Consumers see a simplified view. Repair professionals and recyclers get more detail. Regulators and customs authorities get full access. Manufacturers control the data but must make the appropriate tiers available to each party.
Which Products Need a Digital Product Passport and When
If you manufacture or import products sold in the EU, the digital product passport requirement will apply to you. It is not limited to EU-based manufacturers.
The rollout follows a category-by-category schedule. The European Commission publishes delegated acts for each product group, specifying exact data requirements and deadlines.
Current confirmed timelines:
- Batteries (above certain capacity thresholds): Digital product passport required from February 2027. Technical requirements are already published in full. (source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023R1542)
- Textiles and apparel: As of early 2026, the delegated act remains in preparation, with adoption now expected in late 2026 or early 2027. Compliance for the textiles and apparel delegated act under the EU's ESPR is expected 12–24 months after its adoption
- Electronics and ICT equipment: Compliance expected from 2028 to 2029.
- Construction products: Digital product passport requirements expected from 2029 to 2030.
- Furniture, chemicals, and other categories: Further delegated acts planned through 2030.
The battery regulation is the clearest benchmark for what other sectors can expect. It requires a unique identifier per battery, a QR code data carrier, and a web-accessible data record hosted in an EU-compliant system. Manufacturers in other categories should treat it as a preview of what's coming for them.
How a Digital Product Passport Works Technically
Each digital product passport is linked to a physical product through a data carrier: a QR code, RFID tag, NFC chip, or other machine-readable format. The carrier must be physically attached to the product or its packaging and must remain scannable throughout the product's life.
The data is stored externally, not on the carrier itself. The carrier holds a unique product identifier that points to a hosted data record. The EU is aligning with the GS1 Digital Link standard for these identifiers, which means manufacturers choosing systems now should verify that their platform supports GS1 Digital Link to ensure long-term interoperability with EU registries. (source: https://www.gs1.org/standards/gs1-digital-link)
That hosted record must meet specific requirements. It must be accessible to authorized parties based on their access tier, support data updates without breaking existing links, and remain available for the full product lifetime, including after the product is sold or decommissioned. For EU market compliance, the hosting infrastructure must meet GDPR data residency requirements, which in practice means EU-based or adequacy-approved hosting.
Manufacturers do not all need to build their own hosting infrastructure. Third-party digital product passport platforms can manage this, provided they comply with technical standards set by GS1 and the EU Commission's own specifications. The EU is also developing a network of interoperable registries that these platforms will connect to.
What the manufacturer is responsible for:
- generating the unique identifier
- populating the data record accurately
- attaching the carrier to the product
- keeping the data current as the product or its components change.
What Manufacturers Need to Do Now
This is where most manufacturers are underprepared. The digital product passport is not a documentation task. It requires structured, accurate, machine-readable data about your product at a level of detail that most manufacturers have not previously needed to share externally.
A simple product with a short supply chain and well-maintained data can be DPP-ready in six months. A complex product with a global supply chain and fragmented internal data can take eighteen months or more. Starting late is the most common and most avoidable mistake.
Map your data gaps first.
Start with product categories that fall under the battery regulation or are likely to be regulated early. For each product, identify what data you currently hold, what format it's in, and where it lives. The gaps are almost always larger than expected.
Work upstream in your supply chain.
Much of the data a digital product passport requires (material composition, substance declarations, carbon footprint by component) sits with tier-1 and tier-2 suppliers, not with the manufacturer. Start requesting this data now. In projects we have implemented for industrial equipment manufacturers, the supplier data collection phase consistently takes longer than the technical integration. One manufacturer found that fewer than one-third of their direct suppliers could provide substance-level material declarations in any digital format.
Standardise your internal data.
Product data stored in PDFs, spreadsheets, and legacy system fields will not map cleanly to digital product passport data schemas. You need structured, typed data fields with consistent naming and controlled values. A PIM system is the most practical way to achieve this. It centralises product data, enforces attribute completeness, and creates a single source of truth that feeds directly into DPP output. Manufacturers who try to manage this in spreadsheets or ERP exports consistently hit data quality problems that delay compliance.
Choose a technical path.
The main options are: integrate with a dedicated digital product passport platform, build a fully independent solution on your own infrastructure, or extend existing product data systems to serve DPP output. Each has different cost and control trade-offs.
Build a process for ongoing updates.
A digital product passport is not a one-time filing. If a component changes, the data record must be updated. If a supplier revises a substance declaration, that change flows through to the passport. Clear internal ownership matters here. Without it, updates fall through the gaps.
Common Challenges in Digital Product Passport Implementation
Supply chain data availability is the biggest practical problem, by a significant margin. Carbon footprint calculations require activity data from suppliers. Material declarations require substance-level information. Many suppliers, particularly smaller ones in non-EU countries, do not have this data in a form that can be extracted and shared digitally. Some don't have it at all. It's a supply chain relationship problem that takes time to resolve regardless of which systems you use.
Legacy system limitations are real but more tractable. Most ERP and PLM systems were not designed to store or export the types of data a digital product passport requires. The more fundamental issue is that these systems often hold engineering and production data, not the commercial and compliance data a DPP needs. A PIM system fills that gap. It holds the structured product attributes, certifications, material declarations, and multilingual content that digital product passport schemas require, and it can export that data in formats that DPP platforms and custom solutions can consume.
Data governance is underestimated. Who owns the data record? Who updates it when something changes? Who is liable if it is wrong? Most organisations have not defined this yet, and it causes delays once implementation starts.
The cost of implementation varies widely. A full digital product passport rollout for a complex product with a global supply chain is not a small project. The range depends on supply chain complexity, existing data infrastructure, and whether a PIM system is already in place. Manufacturers with a well-maintained PIM consistently report faster and cheaper DPP implementations than those starting from scattered data sources.
What Happens If You Don't Comply
Products without a valid digital product passport cannot be placed on the EU market after the applicable deadline. This is a market access condition, not a tiered fine structure.
Customs authorities will verify digital product passport compliance at the point of import. Non-compliant products can be refused entry or recalled from the market. Member states designate market surveillance authorities with the power to require product withdrawal and publish non-compliance findings. Distributors and retailers in the EU are also required to verify that products they stock carry valid passports, which means non-compliant manufacturers risk losing EU distribution relationships before regulators act directly.
The practical consequence is straightforward: plan early or lose EU market access.
Software for Digital Product Passport Management
The digital product passport software market is still maturing. No single tool covers every industry and every requirement, but the landscape breaks down into a few practical categories.
PIM systems are the foundation. A product information management system is where digital product passport data preparation begins for most manufacturers. PIM platforms store structured product data: materials, components, attributes, certifications, multilingual content, and supplier references. This is exactly the data a digital product passport requires. A well-maintained PIM reduces the DPP data problem from a major project to a structured export. Manufacturers without a PIM who attempt digital product passport compliance from spreadsheets or ERP exports consistently find themselves rebuilding their data infrastructure anyway, just under more pressure and at higher cost.
A PIM system doesn't just support digital product passport compliance. It makes the underlying data good enough to comply with.
AtroPIM is particularly well-suited for digital product passport use cases, as it combines a structured product data repository with a publication-ready DPP output layer and a well-documented REST API that external passport platforms and custom integrations can consume directly.
Digital product passport platforms like Spherity and Minespider (source: https://minespider.com) handle the registry infrastructure: unique identifier generation, data hosting, access tier management, and integration with EU registry frameworks. Spherity has been involved in EU pilot projects for battery passport compliance. (source: https://spherity.com) These platforms sit on top of your data layer, not inside it. The quality of what they serve depends entirely on the quality of what feeds them.
Sustainability and LCA tools like Ecoinvent and SimaPro are used for lifecycle assessment and carbon footprint calculation. These feed specific data points into the digital product passport record but are not DPP management systems themselves.
Building an independent solution makes sense when product complexity is high, supply chain data flows are already digitised, or the business needs full control over data access and hosting. A custom digital product passport system built on standard web technologies and hosted on EU-compliant infrastructure avoids vendor dependency and gives complete flexibility over the data model. PLM systems can contribute engineering and component data to this layer, but they are a secondary source. The primary source is the PIM.
Extending existing web software is an option manufacturers often overlook. The same infrastructure that serves product pages in a web catalog or online store can be extended to serve digital product passport data to authorized parties. Access tiers, unique identifiers, and QR code generation can be added as modules on top of platforms like Magento or custom-built catalog systems. This works well when the product catalog is already well-structured, and data quality is high, which again points back to having a solid PIM in place first.
The consistent finding from manufacturers already working through battery digital product passport compliance: the technical platform matters less than the quality of the data going into it. Whichever approach you choose, verify that it supports the GS1 Digital Link standard before committing.