The first practical step was creating a minimum viable DPP schema before talking to suppliers. We defined a short, non negotiable set of fields and mapped them to existing supplier documents so it didn't feel like "new work." The hardest field to standardize was material origin and processing location, especially when suppliers relied on sub tier partners they didn't fully control. What actually worked for onboarding was a simple script plus incentive: "We're starting with only three required fields. If you share them, you'll stay on our preferred supplier list for next season." Framing it as limited scope and tying it to future volume unlocked cooperation much faster than compliance language ever did.
The first practical step we took was locking a minimum viable DPP schema and piloting it with one cooperative supplier before scaling. We started with product ID, material composition, country of origin, and care attributes, then wired those fields to SKUs so data stayed attached as products moved systems. The hardest field to standardize was material provenance at the tier-2 level, where suppliers used inconsistent naming and percentages. What worked for reluctant vendors was an onboarding script that tied compliance to upside: "Share these four fields once, and we'll reuse them for future orders and regulatory reporting." Pairing that with a small PO preference for compliant suppliers unlocked participation quickly Albert Richer, Founder, WhatAreTheBest.com
I'll be completely transparent here: at Fulfill.com, we're primarily focused on the logistics and fulfillment side of the supply chain rather than upstream product passport implementation. Digital product passports are really a manufacturing and brand-level initiative that happens before products reach our warehouses. However, I've had extensive conversations with our fashion and apparel clients who are wrestling with DPP requirements, and I can share what I'm seeing from the fulfillment perspective. The most practical first step I've observed successful brands taking is starting with a single product line or collection rather than their entire catalog. One of our clients, a sustainable activewear brand, began with their bestselling legging line. They mapped backwards from finished goods in our warehouse to identify every supplier touchpoint: fabric mills, dye houses, cut-and-sew facilities. This narrow focus let them test systems and workflows without drowning in complexity. From what they've shared, the hardest data field to standardize was material composition percentages. It sounds simple, but different suppliers use different testing methods and report at different precision levels. One mill reports cotton content as 95.2 percent, another rounds to 95 percent, a third says "approximately 95 percent." When you're trying to create a standardized digital record that needs to be legally compliant across EU markets, those inconsistencies become massive headaches. The onboarding challenge is real. What I've seen work isn't actually about incentives, it's about reducing friction. One brand we work with created a simple mobile-friendly form that took suppliers under five minutes to complete. They pre-filled every field they could with existing data from purchase orders and certifications already on file. The key message to suppliers was: "We're not asking for new information, just confirming what we already have in a standardized format." That reframing changed the conversation from "more work" to "quick verification." They also made it clear this wasn't optional for future orders. No traceability data meant no new purchase orders once DPP requirements kicked in. That business reality motivated faster adoption than any incentive could. The brands succeeding at this are treating it like a data infrastructure project, not a compliance checkbox.