Skip to content
DigitalProductPassport

How-to

DPP Readiness Checklist: 10 Steps to Prepare Your Company

A practical 10-step Digital Product Passport checklist to get your products, data, suppliers and systems ready, with an owner and output for each step.

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

Short answer

Preparing for a Digital Product Passport takes ten steps across your products, data, suppliers and systems, and each step names an owner, an effort level and the output you should have at the end. DPP readiness is mostly data and supplier work; the QR code is the easy part. Work through the steps in order, and finish with a pilot on one product before you scale.

Key takeaways

  • DPP readiness is mostly data and supplier work. The QR code is the easy part.
  • Start with scope and ownership, then identifiers, data, suppliers and evidence.
  • Each of the ten steps has an owner, an effort level and a concrete output.
  • After a delegated act is adopted, companies get a transition period of at least 18 months, so the basics are worth starting before the final rules.
  • Finish with a pilot on one product before you scale.

Key facts

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

This Digital Product Passport checklist sets out ten steps to prepare your products, data, suppliers and systems. Each step names an owner, an effort level and the output you should have at the end. Work through them in order, and finish with a pilot on one product.

How to use this Digital Product Passport checklist

The checklist is written for an operations or compliance manager who has been asked to prepare for the Digital Product Passport (DPP). If the topic is new to you, read what a Digital Product Passport is first.

Three things to know before you start:

StepOwnerEffortOutput
1. Map products in scopeComplianceLowScope list
2. Assign an ownerSenior managementLowNamed lead and working group
3. Choose identifier granularityProduct and master dataMediumIdentifier decision per product family
4. Inventory data sourcesIT and dataMediumData source map
5. Map BOM and materialsEngineeringHighMaterial breakdown for priority products
6. Engage suppliersSourcingHighSupplier data requests sent and tracked
7. Organise evidenceQuality and complianceMediumEvidence register with expiry dates
8. Define access tiersCompliance and legalMediumTier for every field
9. Pick a DPP platform or providerIT and complianceMediumShortlist and decision
10. Pilot one productDPP leadMediumOne passport, published end to end

You do not have to finish one step before starting the next. Steps 1 and 2 come first. Steps 3 to 8 can then run side by side, as long as the DPP lead keeps them joined up. Steps 9 and 10 use the results of everything before them.

Keep the outputs simple. A shared spreadsheet is enough for a scope list or an evidence register at this stage. What matters is that each output exists, has an owner and is kept up to date.

If you prefer a quick score before you begin, the DPP readiness quiz covers the same ground in a few minutes.

The 10 steps

1. Map products in scope

List every product you place on the EU market and match each one to a product group. Mark each as fixed in law, expected, or not yet known. The DPP timeline by product group shows which dates are fixed and which are indicative.

  • Owner: compliance manager
  • Effort: low
  • Output: a scope list with product, product group, status and expected date

2. Assign an owner

DPP implementation crosses compliance, engineering, sourcing, quality and IT. Without one accountable person, it stalls between departments. Name a lead, give them a small working group and agree how often they report. The lead does not need to be a lawyer or an engineer. They need the authority to ask other departments for data and time.

  • Owner: senior management
  • Effort: low
  • Output: a named DPP lead, a working group and a reporting rhythm

3. Choose identifier granularity

Decide whether each product family needs a passport at model, batch or item level. A washing machine with a serial number suits item level. A run of cotton jackets may suit batch level. The rules for your product group may set the level for you, so check them first. Our guide to QR codes, data carriers and unique identifiers explains the options.

  • Owner: product and master data team
  • Effort: medium
  • Output: an identifier decision for each product family, with the reason

4. Inventory data sources

Write down where product data lives today: ERP, PLM, supplier files, spreadsheets and document folders. For each source, note what it holds, who owns it and how reliable it is. This shows you which data exists, which is duplicated and which is missing. Where the same value lives in two places, decide which one is the master.

  • Owner: IT and data team
  • Effort: medium
  • Output: a data source map with an owner for each source

5. Map BOM and materials

Take the bill of materials (BOM) for your priority products and add what a passport needs: the material of each part, its weight or share, and its supplier. The guide to what data goes into a Digital Product Passport lists the fields to look for.

  • Owner: engineering or product development
  • Effort: high
  • Output: a material breakdown for each priority product, with gaps marked

6. Engage suppliers

Much of the data you lack sits with suppliers. Tell them what is coming, send one fixed template and ask for evidence with the data. Track who has answered. Start with the suppliers behind your priority products. Some suppliers will not have the data, and a few will not want to share it. Find that out early, while you still have time to help them or to look at alternatives.

  • Owner: sourcing or procurement
  • Effort: high
  • Output: supplier requests sent, a response tracker and a list of suppliers who need support

7. Organise evidence

Collect the documents that back your claims: declarations, test reports and certificates. For each one, record what it proves, who issued it and when it expires. Link each document to the product and field it supports. A certificate that covers a supplier in general is weaker than one that covers the exact material in your product.

  • Owner: quality and compliance
  • Effort: medium
  • Output: an evidence register with issuer, scope and expiry date

8. Define access tiers

Decide who should see each field: the public, businesses with a legitimate need such as repairers and recyclers, or authorities. Follow the rules for your product group where they exist. Mark commercially sensitive fields clearly. Do this before the pilot, because a field that has been published to everyone is hard to pull back.

  • Owner: compliance, with legal input
  • Effort: medium
  • Output: an access tier for every field in your data model

9. Pick a DPP platform or provider

You need a place to hold, validate, publish and version passports. Compare options against a short list of needs:

10. Pilot one product

Build one passport from start to finish. Choose a product that is likely to be in scope and has a cooperative supply chain. Publish it, print the QR code, scan it and ask a colleague outside the project to read it. Write down what was hard.

  • Owner: DPP lead
  • Effort: medium
  • Output: one published passport and a list of lessons for the roll-out

Common mistakes

  • Starting with the label. The QR code depends on the identifier, and the identifier depends on the data. Do steps 3 to 7 first.
  • Leaving it to one department. Compliance cannot fix a BOM, and engineering cannot chase certificates. Step 2 exists for this reason.
  • Asking suppliers once, by email. Free-text replies cannot be loaded or compared. Use one template and follow up.
  • Collecting data without evidence. A figure with no document behind it will need to be collected again.
  • Fixing data in a copy. If you correct a spreadsheet and not the source system, the error returns.
  • Waiting for certainty. Final field lists come with the delegated act. Scope, ownership, identifiers and supplier engagement do not depend on it.
  • Scaling before the pilot. Problems found on one product are cheap. The same problems found across a full range are not.

Next steps

To prepare for DPP requirements, start with the first two steps this month. They need little effort and unlock everything else. Then put dates against steps 3 to 10, working back from the date that applies to your product group.

This checklist is general guidance, not legal advice. Confirm your obligations with your legal advisor.

When you are ready, take the readiness quiz to see your score across products, data, suppliers and systems. Then book a demo to walk through the gaps with one of your own products.

Frequently asked questions

How long does DPP readiness take?

It depends on how many products you have, how clean your product data is and how quickly your suppliers respond. Supplier data and evidence usually take the longest, so start those steps first. Use the transition period of at least 18 months after a delegated act is adopted as your outer planning window, not as the time to begin.

Should we wait for the delegated act?

No, not for the basics. The delegated act for your product group will set the exact fields and dates, but scope, ownership, identifiers, a data inventory and supplier engagement are needed whatever the final text says. Wait for the act before you fix the final field list and labels.

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.