In most organisations the digital product passport discussion starts with "when will it be mandatory". A more useful question: when it is, which data will we be able to produce retrospectively?
The answer is usually "very little". Which batch a product came from, which raw material it was made with, which plant it passed through — if none of that was recorded at the time, it cannot be reconstructed later. A document can be produced; data cannot.
The four layers a passport carries
- Identity: the unique number of the product and the mark that makes it readable.
- Composition: raw materials, material ratios, share of recycled content.
- Origin: production site, batch, date and, where relevant, the supply chain.
- Life cycle: maintenance, repair, reuse and disposal guidance.
Without the first layer the other three have nothing to attach to. A passport binds to the UNIT, not the product model: two batches of the same model can carry different material ratios, and showing exactly that difference is what a passport is for.
A passport binds to the unit, not the model; a record kept at model level is not an answer to the question being asked.
Three things you can do now
First, start unit identity. Even if the label carries only a barcode today, giving every unit a unique number is the layer that costs most to add later.
Second, bind batch information to that identity. It already exists in your production records; what is missing is the link to the number on the product.
Third, match supplier documents to the batch. Analysis reports, certificates of origin and declarations of conformity sit in a folder today; a passport wants them behind a machine-readable link.
What starting early buys you
An organisation that starts collecting early faces a format conversion, not a software project, when the obligation arrives. Turning data you hold into a required schema takes weeks; producing data you never captured is not possible.
Where the data comes from
Most of what a digital product passport asks for already exists in the plant: raw- material origin, production date, component list, certificates. The problem is not absence but scatter. The same fact sits separately in the quality file, the supplier contract and the label approval, and one day those three diverge.
The first step in preparing is not collecting new data but tying together what is already there. Unlinked data gets compiled by hand when the passport becomes mandatory, and every hand-compiled file goes stale within a month.
At which product level
Whether the passport attaches to the product model, the batch or the individual unit is a decision to take early. A model-level passport is cheap but cannot express batch differences; a unit-level passport expresses the most but requires every unit to carry its own identity.
- Model level: sufficient for facts that do not change across a product.
- Batch level: needed once raw material or production conditions vary.
- Unit level: needed if recall and ownership tracking are wanted.
- The level can be raised later; it cannot be lowered.
When a passport is updated
A passport is not published once and left. Some facts change across a product's life: repair, resale, recycling. Unless who may update it and how earlier versions are retained is settled at the start, the passport drifts away from the actual state of the product.
The data you will collect when passports become mandatory is the data you are not collecting today.