DPP BUYER GUIDES
Digital Product Passport Data Requirements: A Checklist
Digital product passport data requirements depend on the product rules that apply to you. For project planning, start with a data register: what each field means, where its evidence comes from, who approves it and who may see it. The working method below helps you turn scattered files into a reviewable pilot dataset.
Separate legal requirements from pilot choices
ESPR Article 9 and Annex III set the framework; applicable delegated acts specify the product-group data and whether the passport is at model, batch or item level. Do not copy a generic field list into a compliance declaration. Identify the current rule for your product and keep its reference beside each required field.
The register in this guide is an original DPP Atlas planning tool. Its columns are suggested controls for your team, not a claim that every listed data category is legally required. Add fields for a pilot only when you can explain their purpose. Label optional brand content separately from required product information.
For a fictional table manufacturer, care instructions and repair parts could be useful pilot content. That does not make them the final legal schema for every furniture product. Keep the business decision and the legal requirement in separate columns, with a reviewer for each.
References: EU Regulation 2024/1781 — Articles 9–11 and Annex III
Create a field register your team can maintain
Use one row per field definition, then keep product values in a linked table. This avoids repeating a changing definition across hundreds of rows. Give each definition a stable internal key so a renamed label does not break the connection.
Before collecting values, agree the expected type and unit. “Recycled content” is incomplete as a request: which component, which basis, which period and which evidence? Put those boundaries in the definition. Ask a colleague outside the project to read the row and explain what they would enter.
| Register column | What to record | Illustrative example |
|---|---|---|
| Field and meaning | Stable key plus plain definition | care_instructions; care for the finished item |
| Product scope | Model, batch or individual item | Chair range A; blue fabric variant |
| Value format | Type, unit and allowed values | Text; approved language codes |
| Evidence | Source, date and exact location | Supplier sheet; revision 3; page 2 |
| Responsibility | Collector and approver | Buyer collects; product lead approves |
| Access and status | Audience plus review state | Public; awaiting approval |
| Change trigger | When to review the value | New fabric supplier or revised care sheet |
Map product data without losing its context
As a working inventory, group candidate fields into identity, materials, supply-chain references, use and repair, and supporting documents. Then review each group against your product rules. These groups help locate owners; they are not a prescribed EU schema.
A fictional jacket record illustrates the difference. A composition value may describe the outer fabric, while a certificate covers only a supplier facility. Attaching both to one product page does not prove the certificate covers that finished jacket. Preserve the document’s scope and ask the reviewer to check the relationship.
Keep an identifier map across your systems. A supplier’s product code, an internal stock code and a public identifier may differ. Record the mapping explicitly and test two similar variants. Avoid matching records by a shortened product name alone; use a key the owner has checked.
Make missing and conflicting data visible
Use explicit review states. We suggest “not requested”, “awaiting evidence”, “under review”, “approved” and “conflicting”. Keep “not applicable” as a reasoned decision, with its reviewer, rather than an easy way to clear a blank cell.
Trace4Value’s pilot report identifies inconsistent availability and standardisation of data as practical challenges. Our recommendation is to measure the unresolved rows by cause and owner, rather than report a single completion percentage that can hide weak evidence.
For example, if 90 of 100 candidate fields have values, that is only a populated-field count. It does not mean 90 percent of the required work is approved. Ten missing optional photos and ten unresolved product identifiers have very different consequences. Track completeness, evidence review and release blockers separately.
References: Trace4Value — Pioneering Digital Product Passports (2025), section 4.4, PDF
Send suppliers a bounded request
Ask for the smallest evidence pack that can settle the open issue. Include the exact product or batch, the field definition, the unit, the preferred format and a reply date. Show an example row with fictional data. State who can answer questions about the request.
On receipt, preserve the original document and its version. Check that the response refers to the requested item, then record any transformation into your own format. If a supplier sends kilograms and your field expects grams, keep both the source value and the conversion. A later reviewer should be able to reproduce the result.
Do not make suppliers guess which information will become public. Describe the intended audience and have the owner approve access. Test that public exports and pages omit evidence marked private. Avoid including personal contact details in a product record merely because they appear in an email signature.
Validate meaning as well as file format
The Commission’s Semantic Data Guide addresses resources such as taxonomies, validation schemas, SHACL shapes and JSON-LD contexts. Use the current applicable resources with your technical team. A file that passes a structural check can still contain a value attached to the wrong product.
For your pilot, add a human review of a small record sample after import. Compare the displayed value, its unit and its source with the original. Include a missing field, a rejected value and a corrected record in that sample. Keep a record of which version you reviewed.
Use these digital product passport data requirements questions in the next planning meeting: which fields are actually required, which remain assumptions, and who can resolve each gap? Once the answers are in the register, use the implementation checklist to agree the tests before public release.
References: European Commission — DPP Registry resources, API and Semantic Data Guides (30 October 2026)
Sources and review context
Sources were reviewed for this editorial guide on 4 November 2026. Provider descriptions are attributed public statements. This guide does not report hands-on software testing or certify regulatory compliance. Check the current original source when a detail affects your decision.
How DPP Atlas reviews evidence