When fashion brands evaluate Digital Product Passport providers, they typically ask the wrong questions. They ask about user interface design, consumer engagement features, and QR code aesthetics. What they should be asking is: how many data fields can your platform actually handle, and how do they map to the regulatory requirements that will define DPP compliance under ESPR?

Symolem's proprietary DPP methodology maps 814+ discrete data fields across 36 domains. This is not an arbitrary number, it represents the full scope of data that a genuinely comprehensive Digital Product Passport must be capable of containing, based on our analysis of ESPR delegated act requirements, existing voluntary standards (GRS, OEKO-TEX, GOTS, Higg), retailer data requirements, and emerging industry consensus on best practice.

Why field coverage matters

ESPR delegated acts will specify mandatory data fields for each product category. For textiles, the current trajectory suggests these will cover materials and fibre composition, chemical compliance and restricted substances, carbon footprint and environmental impact, durability and reparability metrics, recyclability and end-of-life information, supply chain traceability, and economic operator identification.

But mandatory fields are the floor, not the ceiling. Retailers, particularly large European retailers subject to Article 25 verification obligations, will increasingly require data beyond the regulatory minimum. Brands that can only provide the minimum will find themselves at a competitive disadvantage when retailer scorecards begin to weight DPP data quality alongside price and margin.

The 36 domains

Our 814+-field methodology spans 36 distinct data domains. These include product identification and classification, materials composition (fibre-level detail), chemical management and REACH compliance, water usage and water stress indicators, energy consumption across production stages, carbon footprint (Scope 1, 2, and 3), biodiversity impact indicators, labour standards and wage data, working conditions and health and safety, supply chain mapping (Tier 1 through Tier 4), manufacturing process documentation, quality and durability testing results, care and maintenance instructions, reparability scoring, recyclability and disassembly assessment, end-of-life pathway documentation, packaging materials and recyclability, transport and logistics data, certifications and third-party audits, consumer care guidance, product warranty information, take-back and collection programme data, circular business model data, digital twin and 3D model references, regulatory compliance declarations, economic operator information, unique product identifiers, DPP access and resolution metadata, data quality and provenance indicators, and temporal versioning and update history.

How to use this framework

When evaluating a DPP provider, ask them to map their platform's data model against these 36 domains. How many of the 814+ fields can they currently support? How many are on their development roadmap? What is their data ingestion architecture, can they integrate with your existing PLM, ERP, and sustainability reporting systems, or do they require manual data entry?

A provider that covers 200 fields may be sufficient for initial compliance. A provider that covers 500 or more is building for the retailer and investor expectations that will follow. A provider that cannot tell you their field coverage has not done the regulatory analysis required to serve you well.

Beyond compliance: the data quality dimension

Field coverage is necessary but not sufficient. The quality of data within each field matters as much as the field's existence. Our methodology includes data quality indicators for each of the 814+ fields, assessing whether the data is primary or secondary, whether it is verified or self-declared, whether it has temporal currency (how recently it was updated), and whether it has supply chain provenance (which actor in the chain generated it).

Brands that invest in data quality now, not just data quantity, will be better positioned when ESPR verification requirements come into force. A DPP full of unverified, outdated, or self-declared data is technically compliant but practically vulnerable to challenge.

The benchmark opportunity

We developed this 814+-field methodology not as an academic exercise but as a practical tool for fashion brands and retailers navigating the DPP landscape. It provides a common language for evaluating providers, a framework for prioritising data collection efforts, and a benchmark against which to measure progress toward comprehensive DPP readiness.

The brands that treat DPP data as a strategic asset, not a compliance burden, will be the ones that extract commercial value from the ESPR era. The 814+-field framework is designed to help them get there.