Skip to content
DigitalProductPassport

Basics

What Data Goes Into a Digital Product Passport?

Product identity, materials, substances, repair, recycling and compliance evidence: a practical breakdown of the data a Digital Product Passport holds.

Reading time
9 min read
Last reviewed
Last updated
Written by
Techavtar editorial team
Reviewed by
Awaiting subject review

Short answer

Digital Product Passport data falls into four groups: product identity, material composition, sustainability and circularity data, and compliance evidence. In practice, teams split these into six working categories: identity, materials and components, substances of concern, durability and repair, end of life, and evidence. The exact fields are set for each product group, so treat any general list as a planning guide, not a legal list.

Key takeaways

  • A Digital Product Passport covers product identity, material composition, sustainability and circularity data, and compliance evidence.
  • The exact fields are set for each product group, so treat any general list as a planning guide, not a legal list.
  • Most of the data already exists, spread across ERP, PLM, supplier files and spreadsheets.
  • The hardest data to get usually sits with suppliers: substances, origin and evidence.
  • Start with a gap analysis on one product, then fix the gaps at their source.

Key facts

From our regulatory facts register, last reviewed 10 Nov 2026. Information only, not legal advice.

Digital Product Passport data falls into four groups: product identity, material composition, sustainability and circularity data, and compliance evidence. In practice, teams split these into six working categories: identity, materials and components, substances of concern, durability and repair, end of life, and evidence. This guide explains each category, where the data usually lives today and how to close the gaps.

The short answer: Digital Product Passport data in six categories

A Digital Product Passport (DPP) is a structured, machine-readable product record covering product identity, material composition, sustainability and circularity data, and compliance evidence. For a wider introduction, read what a Digital Product Passport is.

One caution before the detail. There is no single legal list of fields that applies to every product. DPP requirements reach each product group through its own delegated act, and the act sets the fields. The table below is a planning guide. It shows the product passport information you can reasonably expect to need, so that you can start finding it.

Data categoryExample fieldsTypical source systemWho provides it
IdentityModel, batch or serial number, GTIN, manufacturer, production siteERP, master dataProduct or master data team
Materials and componentsParts list, material of each part, weight or share, originPLM, bill of materials, supplier filesEngineering, sourcing, suppliers
Substances of concernSubstance name, where it is found in the product, amountSupplier declarations, compliance toolsSuppliers, compliance team
Durability, repair and maintenanceExpected lifetime, spare parts, repair instructions, care guidanceService manuals, PLM, after-sales systemsEngineering, after-sales
End of life and recyclingDismantling steps, recyclable parts, recycled content, disposal guidancePLM, supplier certificates, spreadsheetsEngineering, sustainability team
Compliance evidenceDeclarations of conformity, test reports, certificates, expiry datesDocument folders, quality systemCompliance and quality, laboratories

Whatever the category, a passport field is only useful if four things are true:

  • It has a value in a fixed format. "80" and "about 80 percent" are not the same thing to software. Agree the unit and the format.
  • It has a source. You can name the system or supplier the value came from.
  • It has an owner. One person is responsible for keeping it right.
  • It has evidence where a claim needs it. A document is linked to the field, with an expiry date.

Keep these four in mind as you read each category. A field that fails one of them is a gap, even if a number is sitting in a spreadsheet somewhere.

The sections below use three products as examples: a cotton jacket, an e-bike battery and a washing machine.

Identity data

Identity data answers the first question any reader has: which product is this, and who is responsible for it?

Expect to need:

  • a unique product identifier, at model, batch or item level
  • the product name and model
  • the manufacturer and, where relevant, the importer
  • the place and date of production

For a washing machine, this is the model number and serial number on the rating plate. For a jacket, it is usually the style, colour and production batch. For an e-bike battery, it is the serial number of that one battery.

Identity data is usually the easiest category, because it already lives in your enterprise resource planning (ERP) system. The common problem is duplication. The same product has one code in ERP, another in the web shop and a third at the factory. Decide which code is the master before you build anything on top of it.

Materials and components

This category describes what the product is made of. It is the material composition part of the passport.

The natural source is the bill of materials (BOM) in your product lifecycle management (PLM) or ERP system. A passport needs more than a production BOM usually holds:

  • The material of each part, not only the part number. "Zip, 60 cm" becomes "zip, brass teeth, polyester tape".
  • The weight or share of each material. A jacket might be 80% cotton and 20% recycled polyester by weight.
  • Where each part or material came from, at the level the rules for your product ask for.
  • The supplier behind each part.

For an e-bike battery, the breakdown runs from the pack to modules, cells, casing and electronics. For a washing machine, it covers the drum, motor, pump, housing and control board.

Intermediate products matter here too. If you buy a steel beam or a roll of fabric, your passport data depends on what that supplier can tell you about its own inputs.

Substances of concern

A substance of concern is a substance that harms health or the environment, or hinders recycling, and must be tracked in a product.

This is often the hardest category, for a simple reason. You usually do not know the answer yourself. The dye house knows what went into the jacket's colour. The cell maker knows the chemistry inside the battery.

For each substance you track, plan to record:

  • its name and a standard identifier
  • where in the product it is found, down to the part
  • the amount or concentration
  • the supplier declaration or test report behind the figure

Two practical tips. First, ask suppliers for full declarations in a fixed format, not a yes-or-no answer. Second, record the date of each declaration. A declaration from three years ago may not describe today's formulation.

Durability, repair and maintenance

This category helps a product last longer. It is aimed at owners and repairers.

Typical fields include:

  • expected lifetime or performance over time
  • care and maintenance instructions
  • repair instructions and the tools needed
  • available spare parts and how to order them

The washing machine is the clearest example. A repairer needs to know which pump fits which model, how to reach it and where to buy it. For a jacket, the same category holds care instructions and repair guidance, such as how to replace a zip. For an e-bike battery, it covers how the battery is expected to perform as it ages.

Much of this already exists in service manuals and after-sales systems. The work is to turn documents into fields that software can read. A good test is whether a repairer could find the right spare part from the passport alone, without phoning you.

End of life and recycling

This category is for the last stage of the product's life. Its readers are sorters, dismantlers and recyclers.

Expect fields such as:

  • how to dismantle the product safely
  • which parts and materials can be recycled
  • recycled content already in the product
  • how the owner should dispose of it

A recycler handling the jacket wants the fibre blend and anything that blocks recycling, such as a coating. A dismantler handling the battery needs safe removal steps. A recycler handling the washing machine wants to know where the valuable metals are.

Recycled-content figures need evidence. A percentage without a certificate is a claim, not a fact.

Compliance evidence

Evidence is what turns a passport from a description into something an authority can rely on. It is one of the four core parts of a DPP.

Evidence usually means:

  • declarations of conformity
  • test reports
  • certificates from third parties
  • supplier declarations

Store four things with each document: what it proves, who issued it, when it was issued and when it expires. Then link the document to the field it supports, not to the product as a whole.

Not every reader should see every document. Battery passport data, for example, is split into access tiers: the public, persons with a legitimate interest, and authorities. Our guide to EU battery passport requirements explains how that works for batteries. When you design your DPP data model, give every field and document a tier from the start.

Where this data lives today (ERP, PLM, suppliers, spreadsheets)

Very little passport data is new. Most of it exists somewhere. The problem is that it is scattered, in different formats, with no single owner.

Where it livesWhat it usually holdsCommon weakness
ERPProduct codes, suppliers, purchase data, production sitesSeveral codes for the same product
PLMBill of materials, drawings, specificationsPart numbers without material detail
SuppliersSubstances, origin, certificates, test reportsArrives as PDFs and emails, in many formats
SpreadsheetsSustainability figures, supplier lists, one-off studiesNo version control, owned by one person
Document foldersDeclarations, reports, manualsHard to link to a specific product or field

A useful first exercise is to take one product and write down, for each field in the first table, where the value comes from and who owns it. Where you cannot name a source, you have found a gap.

How to close the gaps

Work through the gaps in order. The steps below fit the six-step flow described in how a Digital Product Passport works.

  1. Pick one product. Choose one that is likely to be in scope and has a cooperative supply chain.
  2. List the fields you expect to need. Use the first table and any draft or final rules for your product group.
  3. Mark each field. Use three labels: have it, have it but in the wrong form, do not have it.
  4. Name the source and owner. Every field gets one source system and one person.
  5. Send supplier requests. Ask for data and evidence together, in one fixed template.
  6. Fix data at the source. Correct the BOM in PLM, not in a copy. Otherwise the gap returns with the next product.
  7. Validate and repeat. Check completeness and consistency, then move to the next product.

Keep the DPP data requirements for your product group under review. When the rules for your group are adopted, compare them with your field list and adjust.

The DPP readiness checklist puts this work into a ten-step plan, and the readiness quiz gives you a quick score for data, suppliers and systems.

Book a demo

If you would like to see how your own product data maps to a passport, including the gaps, book a demo. Bring one product and its bill of materials, and we will walk through it with you.

Frequently asked questions

Is a bill of materials enough?

No. A bill of materials is the best starting point for the materials and components part of a passport, but it was written for production. It usually lacks substances, origin, repair and end-of-life information, and it carries no evidence. Expect to enrich it with supplier data and documents.

Do we need supplier data?

Almost always. Your own systems hold what you buy and assemble, but your suppliers hold what their parts and materials are made of and the documents that prove it. Ask for the data in a fixed format, with evidence, and start early because suppliers need time to respond.

How is the data kept accurate?

Through ownership, validation and versions. Each field has a named owner and a source system, the record is checked for completeness and consistency before it is published, and every change creates a new dated version. Evidence carries an expiry date so that it is renewed before it lapses.

Find out how ready you are

The readiness quiz takes a few minutes and shows where your product data stands. When you want to see a passport built from your own products, book a demo.

Information only, not legal advice.