Skip to content
DigitalProductPassport

Basics

How a Digital Product Passport Works, Step by Step

From raw materials to recycling: a step-by-step look at how a Digital Product Passport is created, validated, published and scanned.

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

Short answer

A company collects structured data about a product, backs it with evidence, publishes it at a stable web address and prints a QR code on the product that leads to it. Anyone who scans the code sees the part of the record their role allows. The passport is the data; the QR code is only the link between the physical product and that data.

Key takeaways

  • A Digital Product Passport is built in six steps: identify, map, evidence, validate, publish and register, then scan.
  • The passport is the data. The QR code is only the link between the physical product and that data.
  • The EU DPP Registry stores identifiers that point to passports. The passport data stays with you or your DPP service provider.
  • Different readers see different data. The battery passport, for example, has three access tiers.
  • Most delays come from missing supplier data and missing evidence, not from the QR code.

Key facts

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

How does a Digital Product Passport work? In short, a company collects structured data about a product, backs it with evidence, publishes it at a stable web address and prints a QR code on the product that leads to it. Anyone who scans the code sees the part of the record their role allows. This guide follows that DPP process step by step, using an e-bike battery and a cotton jacket as examples.

How does a Digital Product Passport work? The short answer

A Digital Product Passport (DPP) is a structured, machine-readable product record. It covers product identity, material composition, sustainability and circularity data, and compliance evidence. It is reached through a data carrier such as a QR code.

The DPP data flow has six steps.

StepWhat happensWho usually does it
1. Identify the productThe product gets a unique identifierProduct or master data team
2. Map materials and componentsThe bill of materials is turned into passport dataEngineering, sourcing, suppliers
3. Attach evidenceDocuments are linked to the claims they proveCompliance and quality
4. Validate the dataThe record is checked for gaps and errorsCompliance, with a second reviewer
5. Publish and registerThe passport goes live and its identifier is registeredCompliance, DPP service provider
6. Scan and useReaders scan the code and see their tier of dataCustomers, repairers, recyclers, authorities

If you are new to the topic, start with what a Digital Product Passport is. You can also see the same flow in pictures in the how it works section of our home page.

Step 1: identify the product

Every passport starts with a clear answer to one question: which product is this?

You choose a unique identifier and the level it works at. There are three levels:

  • Model level. One passport for every unit of the same model. This suits products where every unit is identical.
  • Batch level. One passport per production batch. This suits products where materials or suppliers change between batches, such as a run of cotton jackets.
  • Item level. One passport per unit, tied to a serial number. An e-bike battery is a natural fit, because each battery has its own history.

The level is not always your choice. The rules for a product group can set it. Where you do have a choice, pick the level that matches how the data really varies. If you already use a Global Trade Item Number (GTIN) for retail, it is often the starting point for the model-level identifier.

Our guide to QR codes, data carriers and GS1 Digital Link covers identifiers in more detail.

Step 2: map materials and components

Next, you describe what the product is made of. The usual source is the bill of materials (BOM): the structured list of components and materials, with quantities.

A BOM is written for production, not for a passport. Mapping it means three things:

  1. Break the product down. An e-bike battery becomes cells, a casing, a battery management system and connectors. A jacket becomes shell fabric, lining, thread, zip and buttons.
  2. Describe each part. Record the material, its weight or share, and where it came from.
  3. Name the source. Note which supplier provided each part and its data.

Much of this data sits with suppliers. A jacket brand knows the fibre blend from its tech pack, but the dye house knows which chemicals were used. Ask suppliers in a fixed format, so that answers can be loaded without retyping.

For the full list of fields and where each one usually lives, see what data goes into a Digital Product Passport.

Step 3: attach evidence

A passport is more than a list of claims. Compliance evidence is one of its four core parts. Each important claim should point to the document that proves it.

Typical evidence includes:

  • test reports from a laboratory
  • certificates from a certification body
  • declarations of conformity
  • supplier declarations

Three habits keep evidence useful:

  • Link it to the field it proves. A recycled-content figure for the jacket lining should link to the certificate for that lining, not to a general folder.
  • Record the expiry date. Certificates run out. A passport with expired evidence is weaker than it looks.
  • Record who issued it. A reader should be able to tell a laboratory report from a self-declaration.

Step 4: validate the data

Before anything is published, the record is checked. Validation answers three questions.

  1. Is it complete? Every required field has a value. Missing fields are listed as gaps, each with an owner.
  2. Is it consistent? Material shares add up to 100%. Dates are in order. Units are the same throughout.
  3. Is it supported? Each claim that needs evidence has a valid document attached.

Some checks can be automatic. Others need a person. A second reviewer who did not enter the data should approve it, in the same way that a second engineer signs off a drawing. Keep a record of who approved what and when. That audit trail matters if an authority later asks how a figure was reached.

Step 5: publish and register

Publishing does two things. It makes the passport reachable, and it fixes a version.

  1. The passport goes live at a stable web address. The passport data is held by the economic operator or its DPP service provider. It is not uploaded in full to the EU.
  2. The identifier is registered. The EU DPP Registry is an index. It stores unique identifiers and key data that point to passports.
  3. The data carrier is produced. The QR code is generated from the identifier and sent to label or packaging artwork.

Registration becomes mandatory as each product group's DPP obligation takes effect. Until then, you can still prepare your identifiers and process. Read how the EU DPP Registry works for what it stores and what it does not.

One practical point: the web address in the QR code must not change. Print the code once, and change the data behind it when needed.

Step 6: scan and use

Now the product is in the world. Someone scans the product passport QR code with a phone and the passport opens in a browser. No app should be needed.

What they see depends on who they are. Battery passport data, for example, is split into three access tiers: the public, persons with a legitimate interest, and authorities.

ReaderExampleWhat they need
PublicA cyclist buying an e-bikeWhat the battery is and how to use and dispose of it
Legitimate interestA repair workshop or recyclerDetail needed to repair, dismantle or recycle safely
AuthoritiesA market surveillance authorityThe evidence that the battery meets the rules

A good passport page shows restricted fields as locked, not hidden. The reader can see that more data exists and how to request access.

What happens when the product changes (repairs, resale)

A product does not stand still after sale. A battery is repaired. A jacket is resold. A washing machine gets a new pump.

A passport is built to handle this, because the QR code points to a record that can gain new versions. Three kinds of change are common:

  • Corrections. An error in the published data is fixed. The old version stays in the history.
  • New evidence. A certificate is renewed and the new document replaces the old one.
  • Life events. A repair, a change of owner or a change of use is added to the record.

Which life events must be recorded, and who may record them, depends on the rules for your product group. For most groups those rules are not final. Plan for the capability now: version history, named roles and a clear record of who changed what. Confirm your obligations with your legal advisor.

Common pitfalls

  • Treating the QR code as the project. Printing a code takes a day. Collecting clean data takes much longer. Start with the data.
  • Starting supplier requests late. Suppliers need time, and some will not have the data. Ask early and ask for evidence with it.
  • Choosing the wrong identifier level. A model-level passport cannot hold serial-level history. Changing level later means relabelling.
  • Publishing a PDF behind the code. A PDF is not machine-readable. Software cannot compare or check it.
  • Letting evidence expire. Track expiry dates and renew before they pass.
  • Making everything public. Decide the access tier for each field before you publish. Restricting a field afterwards is harder.
  • Changing the web address. If the address in the code changes, every printed label breaks.

To see how ready your own data is for these steps, take the DPP readiness quiz.

See a sample passport

The easiest way to understand the flow is to look at a finished passport. See a sample passport on our home page, scan its QR code and open each access tier. If you would like to walk through the six steps with your own product, you can book a demo.

Frequently asked questions

Can a DPP be updated after sale?

A passport is designed as a living record with versions, so a correction or a new document can be added without reprinting the QR code. Which changes are allowed or required after sale depends on the rules for your product group. Keep a dated history of every change so that readers can see what changed and when.

Who updates the DPP after a repair?

That depends on the rules for the product group, and for most groups those rules are not final. As a working assumption, the business responsible for the passport stays in control of the record and decides who else may add to it, such as an authorised repairer. Confirm your obligations with your legal advisor once the rules for your product are known.

What happens if the manufacturer goes out of business?

The passport should stay reachable for as long as the product is in use, so plan for continuity from the start. Ask your DPP service provider how the passport stays available if either of you stops trading, and keep your own export of the data. We do not state a legal rule here because we have not yet confirmed one against a primary source.

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.