How to prepare product data for a Digital Product Passport
A practical source-data workflow for small brands, sellers and importers before product-specific DPP requirements apply.
Turn one product’s source data into a readiness score and reusable missing-data report.
1. Start with the product-specific rule
DPP requirements are not one universal checklist. The exact data points, access rights, timing and product scope come from the EU legislation that applies to the product category.
Before collecting data, write down the regulation, delegated act or other legal instrument that defines the DPP obligation for your product. This prevents teams from collecting impressive-looking data that is irrelevant while missing mandatory fields.
2. Build one source-of-truth product record
Collect the product name, model or family, stable identifiers, responsible economic operator and every required product-specific data field in one structured record. Avoid using marketplace titles as identifiers because they change easily.
Keep supplier data, internal technical records and environmental information linked to the same product record so different sales channels do not drift apart.
3. Store the source behind every important field
A value is more useful when you know where it came from. For each important DPP field, keep the source document, supplier statement, test result, bill of materials or internal owner responsible for maintaining it.
If a field has no verified source, mark it as missing instead of guessing. That missing-data list becomes a supplier request list and makes the work manageable.
4. Separate identifiers, data carriers and access rights
The identifier tells systems which product or unit is being referenced. The data carrier, such as a QR code where required, provides physical access to the digital record. Access rights determine who can see each data field.
These are related but different design decisions. Keeping them separate in your source data makes future implementation and registry work easier.
5. Plan for changes after launch
DPP work does not end when a passport is first created. Suppliers change, product compositions are revised, identifiers can be replaced and evidence can expire or need review.
Assign an owner, review date and change process. When shared supplier or operator information changes, identify every affected product rather than editing one passport and forgetting the rest.
Official sources
Frequently asked questions
Should I start with a QR code?
Usually no. Start with the applicable product law, stable identifiers and verified source data. The data carrier comes after you know what digital record it needs to resolve to.
Can one spreadsheet be enough?
For a very small catalog it can be a useful starting point. The harder part is maintaining evidence, field ownership, access classes and change impact as the catalog grows.
Does the planner list every legally required DPP field?
No. It is a generic preparation framework. Product-specific EU legislation determines the actual mandatory fields.