A Digital Product Passport is not a free-form document. It carries a defined set of data, drawn from the same families across every product group, with the exact fields fixed per group by an ESPR delegated act. Here is what actually goes inside one.
Who the product is and who is responsible for it: a unique product identifier (via GS1 Digital Link / GTIN), batch- or item-level identifiers where the group requires them, the model and type, the commodity code (CN / TARIC), and the identity of the responsible economic operator and, where applicable, the manufacturing site.
The regulatory paperwork: the EU declaration of conformity, CE marking where relevant, applicable certificates and test reports, and the standards the product was assessed against. Each is a document with traceable provenance, not just a checkbox.
What the product is made of: material composition, recycled content, and any substances of concern — aligned with the REACH candidate list and, for some groups, SCIP notification. This is often the hardest data to assemble because it lives with upstream suppliers.
How to keep the product in use and recover it: durability and expected lifetime, reparability (including spare-part availability and, for electronics, a repairability index), disassembly and recycling instructions, and end-of-life or take-back information.
The product's impact: carbon footprint and, for some groups, wider lifecycle indicators and an environmental-performance class. For steel and other CBAM goods, the embedded-carbon figure overlaps with CBAM reporting.
A passport field is only as good as the evidence behind it. "70% recycled aluminium" needs a supplier declaration or test report a market-surveillance authority can inspect. The bulk of a DPP project is not building the passport — it is collecting, structuring and evidencing the data. That is the layer PassPer builds from documents you already hold.
Answer 10 questions and get a personalised DPP readiness report — free, no account.