For many eCommerce brands, the biggest uncertainty around the Digital Product Passport (DPP) is not whether it will be required, but what data actually needs to be provided. The good news is that the DPP does not introduce completely new information out of nowhere. Most of the required data already exists somewhere in your organization. The challenge is structure, consistency and accessibility.
This article explains which data is required for a Digital Product Passport in eCommerce, how it is typically sourced, and how brands should think about it strategically.
The core principle behind DPP data requirements
The Digital Product Passport is built around one central idea:
product data must be machine readable, verifiable and available throughout the entire product lifecycle.
That means the DPP is not limited to what customers see on a product detail page. It combines regulatory, operational and sustainability data into a single digital product profile that can be accessed by different stakeholders for different purposes.
For eCommerce brands, this shifts product data from being “shop content” to being regulated infrastructure.
Mandatory vs. extended data in a Digital Product Passport
Not all data in a Digital Product Passport is public, and not all data is mandatory from day one. The EU defines a minimum required dataset per product category, which can be extended voluntarily by brands.
In practice, DPP data falls into three layers:
legally required data defined by EU regulation
product and supply chain data needed for verification
optional data used for customer communication and brand differentiation
Understanding this separation is crucial for eCommerce brands, because it prevents overengineering while still enabling future expansion.
Core data required for a Digital Product Passport
At a minimum, a Digital Product Passport requires clear product identification and traceability. This includes information that uniquely defines what the product is and where it comes from.
Typical required data includes:
product name, model or SKU
product category and type
manufacturer or brand placing the product on the EU market
country of manufacture and production sites
For eCommerce brands, this data often already exists in a PIM, ERP or supplier database. The DPP requires it to be structured and linked to a persistent digital identifier.
Material and composition data
One of the most important aspects of the Digital Product Passport is transparency around materials. This is especially relevant for fashion, apparel and textile eCommerce brands.
Material data usually covers:
material types and percentages
information on recycled or bio based content
presence of restricted or hazardous substances
This data is essential not only for compliance, but also for recycling, reuse and circular economy processes. Over time, material transparency will become a baseline expectation for customers as well.
Sustainability and environmental data
Depending on the product category, the Digital Product Passport may require environmental indicators. These are designed to make sustainability claims measurable and comparable.
Examples include:
CO₂ footprint or emissions data
water usage or energy consumption
durability or expected product lifespan
For eCommerce brands, this data often comes from suppliers or external assessments. The DPP does not require perfection, but it does require consistency and traceability.
Lifecycle and end-of-life information
A key difference between the Digital Product Passport and traditional product information is its lifecycle perspective. The DPP must support what happens after the sale.
This includes data such as:
care and maintenance instructions
repairability information
reuse, resale or recycling guidance
For eCommerce brands, this opens the door to post-purchase engagement, reduced returns and longer product lifespans.
Access control and visibility of DPP data
Not all DPP data is visible to everyone. One of the most misunderstood aspects of the Digital Product Passport is that data access is role based.
Customers see simplified, user friendly information. Authorities, recyclers or service partners may access deeper technical data. eCommerce brands remain in control of how information is presented, while still meeting regulatory requirements.
This makes the DPP fundamentally different from a public sustainability label or static disclosure.
Where does this data live in an eCommerce stack?
For most eCommerce brands, DPP data is distributed across multiple systems:
PIM systems for product attributes
ERP systems for suppliers and production
external tools for sustainability metrics
A Digital Product Passport does not replace these systems. It connects them and exposes the relevant data through a standardized digital interface.
This is why early alignment between product, tech and compliance teams is critical.
Conclusion
The data required for a Digital Product Passport in eCommerce is not exotic or new. What is new is the expectation that this data is structured, accessible and lifecycle aware.
For eCommerce brands, the DPP turns product data into regulated infrastructure. Brands that invest early in clean data models and clear ownership will not only meet compliance requirements, but also gain a long term advantage in transparency, trust and scalability.
