The DPP Cost Gap: Why Asian-Made Garments Cost €1.80–3.50 to Certify — and How Factory Data Closes It
There's a number circulating in sourcing offices that should worry every factory owner in Asia more than any tariff: what it costs a buyer to assemble Digital Product Passport data for a garment depends heavily on where it was made. Not because the garment is different — because the records are.
I own a CMT factory in Nepal. This post is the economics of that gap, from the factory side of the table: why it exists, what the buyer will actually ask you for, and which part of the cost your own data systems can remove.
The Gap: €0.40–1.20 vs €1.80–3.50 per Piece
Fibre2Fashion reports that assembling DPP data runs €0.40–1.20 per piece for Portugal-sourced product, against €1.80–3.50 per piece for Asian-sourced product — with the difference driven by fragmented, paper-based records at Asian tier-1 and tier-2 suppliers. At the top of that range, the compliance cost on an Asian-made garment can exceed the CMT charge for sewing it.
Sit with what that gap is made of. It is not testing fees or certification bodies. It is people: someone at the buyer or their agent chasing the factory for cutting records, matching a paper register against an invoice, phoning to ask which fabric roll fed which lot, and re-checking numbers that don't reconcile. Paper records don't just slow the factory down — they bill the buyer, per piece, every season. And buyers can read a per-piece cost table as well as anyone: the same Fibre2Fashion piece frames the gap as a potential sourcing edge for the cheaper-to-verify supply base.
The timeline makes this concrete rather than theoretical: the textile delegated acts under the EU's ESPR are expected in 2027, with implementation from around 2028 after a transition period. Buyers are building their data pipelines now, which means they are also deciding now which suppliers are cheap to plug into them.
What a Buyer Will Actually Ask Your Factory For
Strip away the regulation language and the request that lands in your inbox looks like this:
| Request | What It Means in Factory Terms |
|---|---|
| Material traceability | Which fabric (supplier, invoice, ideally roll) went into this lot; certificates your fabric supplier issued |
| Production records | Where and when this lot was cut, sewn, and finished — with dates and quantities that reconcile |
| Per-lot data | Pieces cut vs pieces shipped, quality outcomes, A/B grading, rework — tied to a specific lot, not a monthly total |
Every one of those is data your factory already generates. The only question is whether it exists as structured records that export in an afternoon, or as registers and memory that someone has to reconstruct — at €1.80–3.50 a piece, on your buyer's ledger, next to your name.
How Scan-Based Records Shrink the Verification Cost
In a scan-based factory, the audit trail is a side effect of running production. On our floor, every bundle carries a QR code from the cutting room, and its journey writes itself: cutting batch (lot, article, sizes, colors, fabric used) → each sewing operation scanned with operator, machine, and timestamp → A/B grade receipt at finishing → challan when the goods leave the gate. When a buyer asks "show me lot 8082," the answer is a structured export, not a week of chasing paper — the same trail we described in our QR production tracking guide.
The honest boundary matters, so here it is plainly. Our piece-level trail runs to finishing; after that, data is at lot and article level. And no software inside a CMT factory conjures fibre origin or mill-level chemistry — that data lives upstream with your fabric suppliers, and getting it still takes their cooperation. What the factory-side system removes is the verification labour on the part of the chain you actually own: the production records that today make up most of the chasing.
What to Start Capturing Now
You don't need to wait for the delegated acts to know what to record. Start with what you already touch daily:
- Cutting batch records per lot — article, size set, colors, fabric consumed, cutting date.
- An operation scan trail — who did which operation on which machine, when, per bundle.
- Quality outcomes at finishing — pass/repair with defect types, A/B grading per lot.
- Dispatch records that reference lots — the challan should say which lots it carries, closing the loop from cut to shipped.
- Supplier paperwork filed against lots — fabric invoices and any certificates linked to the lot they fed, so upstream data has somewhere to attach when you get it.
If you want the full readiness walkthrough — the five-step path from paper to a continuous digital trail — that's our earlier post on becoming DPP-ready as a garment factory. This post is the economics of why it's worth doing: the readiness work is the same work that moves your factory from the expensive-to-verify column toward the cheap-to-verify one.
Scan ERP by Country
Production Records That Export in an Afternoon
Scan ERP writes the audit trail as a side effect of production: QR-coded bundles from cutting, every operation scanned with operator and timestamp, A/B receipts, and challans tied to lots — 50,000,000+ pieces tracked in a working CMT factory. Operators use their own Android phones; go live in 2 weeks. From $39/month — $5/machine or $0.001/piece, whichever bills lower.
Request a Free DemoFrequently Asked Questions
What is the DPP cost gap between European and Asian garment sourcing?
Fibre2Fashion reports that assembling Digital Product Passport data costs €0.40–1.20 per piece for Portugal-sourced product versus €1.80–3.50 per piece for Asian-sourced product. The gap is not the garments — it is the records. Asian tier-1 and tier-2 suppliers largely keep fragmented, paper-based production records, so every DPP data point has to be chased, transcribed, and verified by hand, and that labour lands on the per-piece cost of the garment.
When does the Digital Product Passport become mandatory for textiles?
The textile delegated acts under the EU's ESPR are expected in 2027, with implementation from around 2028 after a transition period, according to Carbonfact's policy tracking. That sounds distant, but buyers are building their data pipelines now — the sourcing decisions that determine which factories are in those pipelines are being made before the regulation is in force.
Can factory software alone make a garment DPP-compliant?
No. A full DPP also needs upstream data — fibre origin, mill certificates, dyeing and finishing chemistry — that lives with your fabric suppliers, and software inside a CMT factory cannot conjure it. What factory software does control is the production-record layer: which lot, which operations, which operator and machine, when, with what quality outcome, shipped on which challan. Digitizing that layer removes the verification labour on the part of the chain the factory actually owns.
What DPP data should an Asian garment factory start capturing now?
Start with what you already touch daily: cutting batch records per lot (article, sizes, colors, fabric used), a scan trail of sewing operations with operator, machine, and timestamps, quality outcomes with A/B grading at finishing, and dispatch records that reference the lots they contain. Keep supplier invoices and any fabric certificates filed against the lot they fed. None of this requires waiting for the delegated acts — it is the same data that answers any buyer audit today.
The DPP conversation is usually framed as a burden coming for Asian factories. Read the cost table the other way: the €1.80–3.50 is not a fixed tax on being Asian — it's the price of paper. The factory that shows up with structured production records isn't just compliant earlier; it's cheaper for the buyer to keep. That's the version of this regulation worth getting ahead of.
Santosh Rijal is the founder of Scan ERP, a garment manufacturing ERP system designed for factory floor operations. He works directly with sewing lines, cutting rooms, and production supervisors across Nepal's garment manufacturing sector.