A product passport starts with its sources, not its QR code.
Bring product information and evidence together from existing systems. Test the data path to a suitable passport solution for one product family.
Read the German originalStart with a specific product category
A digital product passport connects identifiers with information about a product. The relevant legislation determines the required content and dates. The EU Batteries Regulation specifies a battery passport for certain battery categories from 18 February 2027. This does not imply a general passport obligation for every product on that date.
First define the product family, responsible role and requirements profile. Only then can you assess which of your existing data are actually needed.
Every detail needs a source and an owner
A technical characteristic may be in the ERP, supporting evidence with a supplier and a change in a service process. Without clear origins, it is unclear who may correct inaccurate information. For a pilot, a small and fully traceable dataset is better than a large unchecked one.
Distinguish public information from data for authorised recipients. Access control must apply throughout the data path. A public QR code must not unintentionally expose restricted evidence.
Track changes to the product too
Use one example product to check how new information arrives, receives specialist approval and is published. Keep the original identifiers and relevant data versions traceable. A webpage created once is not enough for an ongoing lifecycle process.
The technical result of a pilot is a tested data handover with identified gaps. Demonstrating complete regulatory compliance also requires the appropriate specialist and legal assessment. A suitable platform can be connected once these requirements are clear.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
Digital product passports & battery passports · Packages