Why Your SKU File Is Not an EPR Reporting File

The assumption is reasonable and usually wrong. Brands generally assume that existing SKU data, packaging specifications, and sales data can be assembled into a packaging EPR submission, but each of those datasets was built for a different function.

The SKU master exists to sell and ship product. Packaging specifications exist to source and manufacture. The ERP and sales warehouse exist to recognize revenue, fulfill orders, and forecast demand. Legal-entity and brand-licensing records sit in a separate system again.

None of them was designed to answer the filing question: how many pounds of each covered material, in each official category, a specific obligated legal entity supplied into a specific jurisdiction during a specific reporting period.

A defensible row in that file carries the material category mapped to the program's official taxonomy, the measured weight of the component, the units supplied into the jurisdiction, the obligated legal entity, the source evidence behind each value, and the version and effective date of the specification.

The common thread is not absence of data. In most cases each value exists somewhere. The difficulty is that no function has previously had to make these systems agree at component level, by jurisdiction, with retained evidence.

The reconciliation crosses every ownership boundary: material classification sits between packaging and sustainability; measured weights sit between packaging and procurement; jurisdiction volume sits between sales operations, supply chain, and finance; producer determination sits between legal and regulatory.

Implication: none of these are legal-interpretation questions. Each is a data-reconciliation question, and each has to be resolved before the SKU export becomes a number that can be filed and defended.

At catalog scale, the exposure is not one misclassified bottle. It is the absence of a system that can show which classifications, weights, and jurisdiction splits are correct.

Oregon converts classification into price. Oregon has been operating the fee model since mid-2025. Producers reported 2024 supply data, fees began July 1, 2025, and as of late May 2025 nearly 3,300 companies were registered and more than 3,000 had been invoiced.

California raises the granularity of the underlying file. CalRecycle's covered material category list contains 95 categories, and the program requires plastic-only weight and plastic component counts measured against a 2023 baseline.

Ontario shows where verification is heading. Blue Box reporting uses seven material categories and requires an annual supply report and brand supply list, and RPRA has issued public administrative penalties under the regulation.

The question has moved from submission to evidence. With the May 31, 2026 milestone passed for several CAA-administered states, the operative question is no longer whether a brand will report, but whether the file behind the submission can be reproduced.

A workable EPR file is a controlled dataset, not a one-time spreadsheet. The minimum schema, tied to the worked scenario above:

The operative standard is reproducibility. A reported weight is defensible when the underlying rows, component weights, source documents, and version history can be retrieved and re-derived on request.

The full model does not apply equally to every producer. Low-volume and de minimis rules reduce or remove the obligation in several programs: Ontario uses a gross Ontario revenue threshold, Oregon and Minnesota use revenue or tonnage thresholds, and Maine offers a lighter low-volume path.

Simplified or flat-fee options reduce category-level work. They change the file required rather than removing the need to prove the basis for the lighter treatment.

Registered-producer lists are not audit opinions. Appearance on a registry does not establish that a submission is correct, and absence from a registry does not by itself establish noncompliance.