A Digital Product Passport can do more than prove compliance
Use persistent product identity to connect products to services throughout their lifecycle.
A product that can be recognised can be served.
Returns, repair, resale and take-back all start with the same question: what exactly is this item?
One identity throughout the lifecycle
The passport is not a page per stage. It is one identity that each stage reads from and writes back to.
Sold
Passport handed over with the product
Used
Care, warranty and product information
Returned
Recognised on arrival
Assessed
Condition captured against the item
Repaired
Event recorded on the identity
Resold
Second life with history intact
Recycled
Material information still attached
Return & resell
The resale channel does not have to guess what it is holding — the item says so itself.
- 01Scan the product on arrival
- 02Identify the product or the individual item
- 03Determine eligibility against your own rules
- 04Capture condition and status
- 05Prepare it for resale with its information intact
Repair & after-sales
Repair history on the identity is a business capability, not a regulatory obligation — useful where it helps you, optional where it does not.
- 01Identify the product from the carrier on it
- 02Retrieve the relevant materials, components and care information
- 03Support the repair or after-sales request
- 04Record the event against the product identity
Take-back & circularity
The routing decision is only as good as the information available at the moment of sorting.
- 01Identify the returned product
- 02Capture its condition and status
- 03Route it toward reuse, repair, resale or recycling
- 04Keep the lifecycle information with the product as it moves
Granularity follows the use case
Circular services are one of the strongest reasons to consider item-level identity — but they are not a reason to apply it everywhere. Much of a circular proposition works perfectly well at model or batch level.
Compliance determines the minimum. Your business case determines the right level.
Enough when the service only needs to know what kind of product this is — care, materials, recycling guidance.
Useful when production runs differ in origin, materials or evidence, and that difference changes the handling.
Becomes valuable when the lifecycle of one physical unit matters — ownership, repair history, take-back value, resale.
Take-back and resale, running today
Filou & Friends is the clearest current example: item-level passports created inside seasonal production, then used for take-back and resale on the same identity. It is the reason the identity level was chosen in the first place.
Turn product identity into a lifecycle service.
Bring the circular service you want to run. We will work back from it to the identity level and the data it needs.