Digital Product Passports are becoming a mandatory operational layer for products placed on the EU market.
For many fashion brands, the first question is how to implement a DPP.
In many cases, companies already manage product information through existing systems such as PIMs, PLMs, ERPs, supplier platforms, or e-commerce infrastructure. Extending these systems can therefore appear more efficient than introducing a dedicated DPP layer.
At the same time, brands are trying to avoid creating temporary or disconnected structures built only to satisfy compliance requirements.
The challenge is understanding whether existing infrastructure can realistically support the operational requirements Digital Product Passports introduce over time.
For many companies, the PIM is already the central environment for managing product information across channels.
It may already contain:
Using the existing system can therefore seem like the most logical path for managing Digital Product Passports without duplicating infrastructure.
In many cases, part of the required DPP information will already exist there.
Digital Product Passports introduce requirements that extend beyond traditional product enrichment.
From a technical perspective, DPPs will involve:
From an informational perspective, DPPs may also require:
The exact requirements will depend on the product group and future delegated acts.
This changes the role of the system managing the passport.
The challenge is no longer only storing product information, but maintaining structured product-level records connected to multiple actors and systems over time.
Traditional PIM environments are often designed around commercial product information:
Digital Product Passports introduce additional operational layers.
Product records may need to:
This does not automatically mean a PIM cannot support DPP requirements.
But it does mean brands need to evaluate whether the existing architecture was designed for this type of operational logic.
Some brands respond by building separate DPP workflows around existing systems without changing the underlying product infrastructure.
This can create:
The objective is therefore not simply adding another platform or duplicating existing infrastructure.
The challenge is building a structure where DPP requirements can integrate with existing systems while remaining maintainable as requirements evolve.
Before deciding how the DPP will be managed, brands increasingly need to evaluate:
The question is often less about replacing existing infrastructure, and more about whether current systems were originally designed for the operational requirements DPPs introduce.
As Digital Product Passport requirements become more specific, brands are increasingly evaluating how existing product systems fit into long-term DPP infrastructure.
For some brands, existing systems may support part of the DPP process. In other cases, brands may introduce dedicated DPP infrastructure designed to integrate with existing product systems rather than replace them.
Explore how Renoon helps fashion brands structure Digital Product Passports across existing systems, supplier data, and EU DPP requirements.
.png)
.png)
.png)
