Textile EPR Explained: What Apparel Operators Need to Track

It is late October and a wholesale operations lead is trying to close the books on Q3 for a French PRO filing. She has 4,200 active SKUs across two brands. Fiber composition lives in a shared Google Sheet the design team last updated in July. Garment weight lives in the tech pack PDFs on Dropbox. Units shipped into France live in the 3PL export, but the 3PL reports by carton, not by SKU, and the wholesale orders into French retailers live in a separate order management tool. She is stitching four exports together in Excel, calling the design assistant to confirm whether style FR-2411 is 68 percent cotton or 72 percent, and the filing is due Friday. This is not a sustainability problem. This is a product data problem that arrived with a legal deadline attached.

What is textile extended producer responsibility for apparel brands?

Textile extended producer responsibility apparel regulation, usually shortened to textile EPR, is a family of laws that make the brand that places a garment on a national market financially and administratively responsible for what happens to that garment at end of life. The brand pays a per-unit fee to a national Producer Responsibility Organisation, or PRO, and that PRO funds collection, sorting, reuse, and recycling infrastructure. France was first, live since 2007 and significantly tightened in 2023 with eco-modulation. The Netherlands went live in 2023. Sweden, Spain, and the EU-wide framework under the revised Waste Framework Directive are on the runway.

The fee itself is not the operational problem. For most mid-market brands the annual bill lands in a range that finance can absorb. The operational problem is the reporting basis. To file, you need to declare, per SKU, per market, per period: units placed on market, fiber composition by percentage, unit weight, country of manufacture, and increasingly a set of eco-modulation criteria such as durability, recycled content percentage, and presence of hazardous substances. A brand doing 4,000 active SKUs into three EPR markets is producing 12,000 data points per filing period, and the filing periods are quarterly or annual depending on jurisdiction.

If that data does not live in one place with one owner, you rebuild it every quarter from spreadsheets and PDFs. That is where the cost is.

Why does textile EPR break at Breakpoint 1?

The 6 Breakpoints framework locates this problem precisely. Breakpoint 1 is where product data starts fragmenting: fiber content in the tech pack, HS codes in the customs spreadsheet, weight in the sample room notes, sustainability attributes in a separate ESG tracker, country of origin in the PO system. Each attribute has a different owner and a different update cadence. Nobody is wrong individually. The system is wrong collectively.

EPR is the first regulation that forces a brand to reconcile all of those data points against actual units shipped, per market, on a legal timeline. Before EPR, fragmented product data cost you time and margin. Under EPR, it costs you filing accuracy, and inaccurate filings in France now carry penalties that can exceed the fee itself.

When I am sitting across from a buyer comparing vendors, the EPR conversation almost always exposes the same thing: they have a PLM that holds design intent, a spreadsheet that holds compliance data, and an ERP or order system that holds shipped units, and nothing joins them on a SKU key. The vendor demos all look impressive in isolation. The buyer’s actual question is whether the fiber composition on the tech pack in module A will appear on the EPR export in module B without a human retyping it. That is a Breakpoint 1 question, not a sustainability module question.

What data do you actually need to track per SKU?

The defensible answer, based on the current French Refashion declaration, the Dutch Stichting UPV Textiel intake, and the draft EU harmonised approach, is the following per-SKU attributes:

• Fiber composition, expressed as a percentage list summing to 100, aligned with the ISO 1833 fiber names used on care labels
• Unit net weight in grams, measured on the finished garment excluding hangtags and polybag
• Product category, mapped to the PRO’s category taxonomy (which is not the same as your internal merchandising category)
• Country of manufacture, at the finishing stage, not the fabric mill
• Recycled content percentage by fiber, with documentation of the certification standard (GRS, RCS)
• Presence of hazardous substances declaration, usually a boolean tied to your REACH and Prop 65 attestations
• Durability indicators, which in France now include a physical durability score based on abrasion, pilling, and dimensional stability tests
• Units placed on market, per SKU, per jurisdiction, per reporting period

That last one is where wholesale and DTC diverge and where the 3PL blind spot at Breakpoint 5 leaks into the Breakpoint 1 problem. A DTC unit sold from a UK 3PL to a French consumer counts as placed on the French market. A wholesale unit shipped to a French retailer counts as placed on the French market on the shipping date, not the retail sell-through date. A unit shipped to a Belgian retailer who then transships to France counts as placed on the Belgian market. Your order system has to know the destination country of the first commercial placement, not the ship-to on the sales order.

The objections I hear most often in evaluations are around this exact seam. Brands assume their 3PL report will give them units by country. It gives them units by ship-to address, which is close but not the same, and it does not join to fiber composition on the SKU. Two exports and a VLOOKUP is how most brands are filing today. It works until the PRO audits you.

How is eco-modulation changing what you need to store?

Eco-modulation is the reason a compliance spreadsheet is no longer sufficient. Under the flat-fee model that ran in France through 2022, you paid roughly the same per garment regardless of composition. Under eco-modulation, the fee is bonused down for garments that meet durability, recyclability, and recycled content thresholds, and penalised up for garments that fail them. In practice, the fee can vary by a factor of three or more between a 100 percent recycled polyester tee with a durability score above threshold and a mixed-fiber garment with elastane above 5 percent and no durability testing.

That means the eco-modulation criteria have to be stored per SKU at the product data layer, not derived at filing time. If a merchandiser cannot see the projected EPR fee delta between a 95/5 cotton-elastane construction and a 100 percent cotton alternative during line planning, that decision is being made blind. This is where PLM stops being a design tool and starts being a commercial planning tool. The line plan needs to carry projected landed cost including EPR fee, and the tech pack needs to carry the durability test results before the style is committed to production.

Brands that hold this data in a PLM with a proper attribute model, with tech packs syncing bidirectionally from Illustrator so that fiber composition and construction details are captured at the source rather than retyped, are the ones that can forecast their eco-modulated fee before the season ships. Brands that hold this data in PDFs and spreadsheets will find out what the fee was after the filing.

What does a working EPR data flow look like?

The defensible architecture has four layers, and each layer has to have a single owner and a single system of record.

At the product data layer, every SKU carries the eight attributes listed above as first-class fields, not free-text notes. Fiber composition is a structured list, not a string. Weight is a number in grams, captured at sample approval and locked at bulk approval. Country of manufacture is captured from the PO at production commit. Durability score is captured from the physical test report and attached to the style before the style is released for order intake.

At the transaction layer, every sales order, wholesale invoice, and DTC shipment carries the destination country of first commercial placement. Wholesale orders inherit the ship-to country from the retailer account. DTC orders inherit from the consumer ship-to. Transshipments and returns adjust the count.

At the reconciliation layer, units placed on market per SKU per jurisdiction per period are calculated from the transaction layer, not from the 3PL export. The 3PL export is a check, not the source. If your 3PL disagrees with your order system on units shipped, you have a Breakpoint 3 inventory truth problem that EPR is now surfacing on a legal timeline.

At the filing layer, the PRO’s declaration format is generated directly from the product data and reconciliation layers, per market. For a $15M brand running wholesale plus DTC plus 3PL, we already see 6 to 9 hours per week going to inventory reconciliation across Shopify, 3PL, and wholesale, and one FTE effectively doing data plumbing. Adding EPR filings to a fragmented stack adds another 20 to 40 hours per quarter of the same kind of work. Adding it to a unified product data and order layer adds a report.

When should apparel brands start treating EPR as a data project?

The honest answer: before you sell your first unit into a regulated market, but at the latest during the season before your first filing period. Brands that wait until the filing deadline to organise their product data end up filing on estimates, and estimates are the audit trigger.

Here is the point of view I will defend: EPR compliance is a product data problem, not a sustainability team problem. Handing it to a sustainability lead who does not own the PIM is setting that person up to spend their quarters chasing designers for fiber percentages. Handing it to the head of operations, who owns the flow from PLM through order to shipment, is how it becomes a report instead of a project. The sustainability team should own the strategy, the targets, and the eco-modulation trajectory. The operations team should own the data.

The brands I have seen struggle most are the ones running four or five point tools with a compliance consultant bridging them. The consultant produces a beautiful filing once and then leaves, and the brand cannot reproduce it the next quarter because the underlying data still lives in the same fragmented places. The brands that file cleanly are the ones where fiber composition, weight, country of origin, and units placed on market all resolve to the same SKU key inside the same system, and the filing is a query against that system.

What this means for an apparel operations team

If your product data cannot output, on demand, a per-SKU report of fiber composition, weight, country of manufacture, and units placed on market by jurisdiction for the last quarter, you are not ready for EPR. That readiness gap does not go away by hiring a compliance analyst. It goes away by fixing Breakpoint 1.

The practical near-term move is to audit your current SKU master against the eight attributes above and identify which attributes live outside your PLM or PIM today. Any attribute that lives in a spreadsheet, a PDF, or a colleague’s inbox is an attribute that will not be defensible under audit. Get those attributes into the product data layer with a clear owner and a clear capture point in the development calendar.

The practical medium-term move is to make sure your order and warehouse layers carry destination country at the right grain. If your 3PL cannot report units shipped by SKU by destination country, that is a warehouse execution problem that will bleed into every EPR filing you do. Fix that seam before it becomes the reason a filing fails.

FAQs