Trace every carton
back to the yarn lot.
EU brands started sending Digital Product Passport questionnaires two years before the textile rules apply. We built the supplier evidence hub and batch genealogy that turns an 11-day scramble into a two-day answer.
This is a composite scenario built from how we deliver this kind of work. The client is fictional and the figures are targets, not measured results. We will replace it with a named engagement when a client agrees to be quoted.
A knitwear group near Dhaka with four factories and about 6,000 workers, supplying three EU fashion brands, with yarn from 14 upstream suppliers
- Three EU brands sent DPP readiness questionnaires in 2026, each with different templates. The group's data stopped at the factory gate: fibre composition came from supplier declarations, recycled-content certificates sat in email, and facility identifiers were typed differently in every file.
- Batch-level questions had no answer. Nobody could link a carton of finished goods to the yarn lots inside it. The sustainability team was answering each questionnaire by hand in about eleven days, and expiring certificates were found only when a brand asked.
How we approached it.
Build to the JRC proposal
The EU textile act is expected in late 2027. We built to the three levels the JRC study proposes now: model, batch and item, so the data is ready whichever way the act lands.
Supplier evidence hub
All 14 yarn and fabric suppliers upload declarations and certificates against a shared facility identifier list, with expiry dates captured on upload.
Batch genealogy
Yarn lot to knitting batch to dye lot to cutting order to carton, recorded from the existing ERP events and the floor's lot cards.
Certificate registry
Every certificate has an owner, a scope and an expiry. Thirty days before expiry the supplier and the merchandiser get a task.
Questionnaire export
One data model, exported into each brand's template, with the evidence attached.
Try it yourself.
A simplified illustration with made-up data. It plays once when it scrolls into view, and you can pause it or step through.
Step 1 / 10 A finished garment lot with nothing traced yet.
What we built.
- Facility and supplier master data with one identifier per site
- Evidence hub with upload, scope, expiry and reminder tasks
- Batch genealogy from ERP events and lot cards, with a coverage dashboard
- Certificate registry and expiry alerts
- Template export for three brand questionnaires
- Data quality dashboard: missing fields by supplier and style
Outcomes (targets).
These are the results we would aim for. They are not measured results from a named client.
- Target14 / 14suppliers onboardedwith a shared facility identifier
- Target92%pilot cartons with full genealogytwo product lines, one season
- Target3certificate expiries caught before shipmentin the first season
- Target11 days to 2questionnaire response timeper brand request
Timeline and stack.
12 weeks, piloted on two product lines
What we learned.
- Do not wait for the delegated act. The data gap is at batch level, and closing it takes a season.
- Certificate expiry is a silent failure. A registry with reminders is the cheapest fix.
- One supplier identifier list prevents half the questionnaire errors.
How we would deliver it.
Want this
for your business?
Message an engineer on WhatsApp or send a brief. We agree scope and price before work begins and build in small working steps you can test.