What the EU's Digital Product Passport Means for Brands Sourcing From Vietnam
- Proto Insights

- 3 hours ago
- 3 min read
On 19 July 2026, the EU's Ecodesign for Sustainable Products Regulation came into full effect for large enterprises operating in the bloc. Two changes matter immediately for any brand manufacturing apparel in Vietnam and selling into Europe: unsold clothing can no longer be destroyed, and textile products require a Digital Product Passport, tied to a public registry, before they can legally be sold.
Most of the coverage since has framed this as a compliance story, something for legal and sustainability teams to handle. That framing misses where the actual work happens. A Digital Product Passport is a documentation problem first, and it starts in the same place every garment does: the tech pack.
What the Digital Product Passport actually requires
A Digital Product Passport is a structured, traceable record attached to a product that captures, at minimum: the materials used and their proportions, where those materials came from, how the garment was made and finished, and information relevant to its recyclability or end-of-life handling. It has to be accessible digitally, typically via a QR code or similar, and it has to be accurate enough to survive an audit, not just plausible enough to publish.
That's a higher bar than most brands' internal documentation currently clears. A tech pack that lists a fabric as "cotton blend" or a supplier as "TBC" was fine when it only had to satisfy an internal design team. It is not fine when it has to satisfy a regulator.
Why this starts with the bill of materials, not the compliance team
Every Digital Product Passport is only as good as the bill of materials behind it. If a brand's tech packs already capture exact fibre percentages, named and traceable suppliers, certified fabric origins, and finishing processes, building a compliant passport is a matter of formatting that data correctly. If that information doesn't exist in a usable form, because it was agreed verbally with a factory, or buried in an email thread from eighteen months ago, someone has to go and reconstruct it, product by product, under time pressure.
This is the distinction that matters: compliance teams can build the passport, but they can't invent the underlying data if it was never captured properly during development. That's a production and product development responsibility, not a legal one.
What a compliant tech pack needs to capture
A tech pack built with the Digital Product Passport in mind should include, as standard, rather than as an exception:
Exact fibre composition by percentage, not a general category
Named suppliers for fabric, trims, and any finishing processes, with traceability documentation on file
Certification records where relevant (organic, recycled content, and similar)
A clear record of any wash, dye, or finishing treatments applied after the base fabric is sourced
Country of origin at each stage of production, not just final assembly
None of this is complicated to capture. It's only difficult to reconstruct after the fact, which is the position a lot of brands will find themselves in over the next two seasons as enforcement extends from large enterprises toward the wider market.
What happens if a brand isn't ready
The immediate risk isn't a fine on day one, enforcement is rolling out in stages, and large enterprises are the current focus. The practical risk is timeline. Building a Digital Product Passport for a product line with incomplete underlying documentation takes real time: tracking down suppliers, verifying claims, and in some cases re-testing fabric composition where records don't exist. Brands that leave this until a shipment is blocked at customs are working against a much shorter clock than brands who treat it as part of ongoing development now.
There's also a quieter cost. Buyers and retail partners in the EU are starting to ask sourcing questions earlier in the relationship, before a PO is placed, because they don't want to inherit a compliance gap from a supplier. A brand that can answer those questions cleanly moves faster through that conversation than one that can't.
The practical takeaway
If your brand ships into the EU, the useful exercise right now isn't a compliance audit, it's pulling three or four of your best-selling tech packs and checking whether the material, supplier, and origin data in them is specific enough to build a Digital Product Passport from directly, with no follow-up questions. If it is, you're in good shape. If it isn't, that's the gap worth closing before the registry expands beyond large enterprises.
This is also, not coincidentally, what good tech pack development has always looked like, specific, traceable, and complete. The Digital Product Passport didn't invent a new standard. It just made the old shortcuts visible.




Comments