Buyer guide
Digital Product Passport software: what actually matters.
A DPP platform should manage structured product data and long-term access — not just generate a QR code or PDF.
Core capabilities to evaluate
| Capability | Why it matters |
|---|---|
| Product data model | Must support the fields and product level required by applicable product-specific rules. |
| Identifiers & data carriers | ESPR requires a persistent unique product identifier linked through a data carrier. |
| Machine-readable data | DPP data should use open, interoperable formats and be structured, searchable and transferable where applicable. |
| Access control | Different actors can have different access rights to passport data. |
| Back-up & continuity | ESPR requires a back-up copy through a DPP service provider for products covered by applicable delegated acts. |
| Bulk import / API | Critical when product count grows beyond manual entry. |
| Supplier workflow | Much of the required data will originate upstream. |
Questions to ask vendors
- Can I export all passport data in a portable machine-readable format?
- How are identifiers, model/batch/item levels and version history handled?
- What happens if I stop using the platform?
- Can suppliers submit data without seeing sensitive fields?
- Is the platform ready to adapt to product-specific delegated acts?
Avoid lock-in: ESPR explicitly requires open standards and an interoperable exchange network without vendor lock-in for DPP data.