Data architecture
Digital Product Passport data fields: what should you collect?
There is no single universal field list for every product. ESPR defines the architecture; product-specific measures define the final data.
Start with reusable data. Build a clean product-data foundation now, then map it to sector-specific requirements later.
Common categories
| Category | Examples |
|---|---|
| Identifiers | Unique product ID, SKU/model, GTIN where applicable, commodity code |
| Economic operators | Manufacturer, importer, facility and operator identifiers |
| Composition | Materials, components, substances, recycled content where applicable |
| Compliance | Declarations, certificates, test reports and technical documentation |
| Lifecycle | Durability, repair, spare parts, disassembly and end-of-life information |
Build once, reuse many times
Keep your internal source-of-truth separate from the public passport presentation layer. This makes it easier to reuse the same data across buyers, regulators, DPP providers and future APIs.