Extended Producer Responsibility.

A different kind of sustainability reporting

EPR does not look like the rest of sustainability reporting. There is no single framework, no annual statement, and no double materiality assessment. Instead there is a growing set of separate jurisdictional obligations, each with its own registration requirements, data definitions, reporting calendar, and fee structure, all driven by the physical composition of what you put on the market.

The fees are calculated from the data you report, which changes the nature of the exercise. Reporting inaccurately is not only a compliance issue, it is a direct cost. Over-reporting a material category is money out the door; under-reporting invites correction with penalties attached.

The obligation mapping problem

The hardest part of EPR is usually not any individual report. It is knowing how many reports you owe. Obligations are triggered by placing products on a market, which means a company can accumulate reporting duties across many jurisdictions without any single team noticing, particularly where distributors and marketplaces are involved.

• Identifying every jurisdiction where obligations are triggered, including those reached indirectly
• Determining who the obligated party actually is in each case, which varies by jurisdiction and channel
• Mapping which product and packaging categories apply under each scheme's definitions
• Registration and producer responsibility organization membership where required
• Building a calendar of reporting deadlines that someone owns

The data problem

EPR reporting needs data about physical products: packaging weight by material type, product composition, units placed on each market, and increasingly recyclability and recycled content attributes. That information lives in product data systems, with suppliers, or in specifications that were never built for reporting, and almost never in finance.

Building this is a data governance exercise before it is a reporting exercise:

• Defining the product and packaging data model, aligned to the categories the schemes actually use
• Establishing collection from suppliers, including what to do about incomplete supplier data
• Setting a documented methodology for estimates where primary data does not exist
• Reconciling units placed on market against sales data, so the reported volumes tie to something
• Retaining evidence, because these submissions are auditable

Building it to repeat

EPR reporting recurs on multiple calendars simultaneously, so a process that depends on manual assembly does not survive contact with a second year. The target is a single governed product dataset, jurisdiction-specific mapping logic applied on top of it, and submissions generated from that rather than compiled from scratch each cycle.

That structure also makes new jurisdictions cheap to add, which matters because the number of schemes continues to grow.

Where this sits

EPR work often runs alongside broader sustainability reporting obligations, and the product data it requires frequently overlaps with circular economy disclosures under CSRD. Building the dataset once to serve both is the obvious efficiency, and it is easy to miss when the two efforts sit with different teams.