Why every reporting cycle starts with information held by parties the producer does not control — and what changes when the cycles repeat.
State packaging Extended Producer Responsibility laws in Oregon, California, Colorado, Maine, Maryland, Minnesota, and Washington are now in operating phases. Producers register, join Producer Responsibility Organizations, submit data on the packaging they place on the market, and pay fees calculated from that data. The framework is well-defined.
What the framework asks producers to report is more difficult than the act of reporting itself. The data that PROs and state agencies require — the weight of each material category, the count of plastic components, the recyclability classification of each item — is not the kind of information that sits, complete and current, inside a producer's internal systems. Much of it is created and held by packaging suppliers and external manufacturing partners.
The producer remains responsible for what gets reported, even though much of the underlying information may originate outside the producer's own organization.
This is not a one-time problem. It is the structural condition of every reporting cycle that follows.
Oregon's Plastic Pollution and Recycling Modernization Act establishes the obligation directly. A producer registered with a PRO must, per ORS 459A.869(5)(b):
"Upon request, provide the producer responsibility organization with records or other information necessary for the organization to meet the organization's obligations under ORS 459A.860 to 459A.975."
California's framework, implemented through the permanent SB 54 regulations and administered through the Circular Action Alliance, operates on the same architecture: the PRO submits aggregate reports to CalRecycle, but the underlying data must come from each participant producer, attributable to each producer's portfolio.
The legal weight is on the producer. The producer signs the participant agreement. The producer answers for the accuracy of the data. The producer pays fees that scale with reported volumes. None of these obligations are transferable to suppliers, manufacturers, or distributors.
The data fields are component-specific. California's permanent SB 54 regulation, 14 CCR §18980.6.8(a)(1), requires the PRO to maintain records — disaggregated by each participant producer — documenting, for the previous calendar year and for each covered material category:
"For the previous calendar year, for each covered material category, disaggregated by each participant producer: (A) The total weight of material sold, distributed, or imported in or into the state. (B) The total number of plastic components sold, distributed, or imported in or into the state. (C) The total weight of material that is recycled. (D) The total weight of material that is disposed of."
Two of those four figures describe what happened to the material downstream, and the PRO observes them. The other two describe what the producer placed on the market — and nothing in the chain can supply those except the producer.
A "component," per the same body of regulations, is defined as:
"a covered material item that has no physically distinct subparts, or a piece or subpart of a covered material item, if the piece or subpart is distinct with respect to its composition or function or is otherwise physically distinct from other pieces or subparts."
A single packaged product may contain multiple distinct components — bottle, cap, label, induction seal, secondary carton, and shrink wrap — each with its own material composition and weight. That detail is often not maintained at the component level inside the producer's enterprise systems. ERP records often track finished goods rather than packaging architecture at the level of detail required for EPR reporting. Specification documents live in product development files. Bill-of-materials records, where they exist with this level of resolution, often sit with the contract manufacturer or the packaging supplier rather than with the brand owner.
Industry practitioners have consistently described this asymmetry. Packaging-data platform vendors note that suppliers have rarely been asked to provide component-level information in structured form. Brand-side compliance teams describe the EPR reporting exercise as the first occasion on which a packaging line is fully characterized — at the component level, with weights and material designations — across the portfolio.
Run a directional fee estimate across CA / OR / CO.
Oregon's Department of Environmental Quality addressed this point directly. In its formal Q&A document supporting the rollout of SB 582, DEQ stated:
"Unfortunately, a lack of data visibility on the amount of product sold by distributors in or into Oregon does not relieve an obligated producer of the obligations to join a PRO, report sales data to the PRO and pay fees commensurate with those volumes."
The phrasing matters. The regulator acknowledged that the difficulty is real. It then asserted that the obligation persists.
There is no mechanism in the framework to suspend reporting because a supplier did not respond, or because a contract manufacturer's documentation is incomplete, or because the producer cannot fully verify what the upstream party reported. The same logic carries through every state framework. The producer registers, the producer reports, the producer pays. The supplier relationship — its responsiveness, its data quality, its willingness to provide what is requested — is a producer-side operating problem, not a regulatory exemption.
When a compliance team approaches the first packaging EPR report, the gap becomes operationally visible. Internal systems yield a portion of what is needed. Supplier outreach begins, and a significant fraction of suppliers do not respond on the required timeline. Of the responses received, formats vary, definitions drift, and some data is incomplete. The compliance team makes reasonable assumptions, documents methodology, and submits.
The first reporting cycle is, in this sense, an exposure event.
It reveals which suppliers respond and which do not. It reveals which fields the producer can populate internally and which it cannot. It reveals the difference between what the regulation requires and what the producer's normal operating processes are designed to deliver.
The second reporting cycle changes its nature.
Packaging EPR is not a single event. California's source-reduction framework, codified in PRC §42057, runs against a 2023 baseline and sets benchmarks at 2027, 2030, and 2032:
"By January 1, 2027, the PRO shall source reduce no less than 10 percent of plastic covered material sold, offered for sale, or distributed in the state..."
"By January 1, 2030, the PRO shall source reduce no less than 20 percent..."
"By January 1, 2032, a PRO acting on behalf of participants of the PRO's approved plan shall develop and implement a plan to achieve the 25-percent reduction by weight and 25 percent by plastic component source reduction requirement..."
Oregon's PRO submits an annual report by July 1 of each year. CalRecycle data reporting begins in 2026 and continues annually. Colorado, Maine, Maryland, Minnesota, and Washington each operate on their own annual cadences within their statutory schedules.
For the producer, this means the supplier-data exercise begins again. New product launches arrive between cycles. Existing products undergo packaging changes — material swaps, weight reductions, format adjustments — and each change alters component-level data. New suppliers enter the portfolio. Existing suppliers' contacts turn over. The dataset assembled for the first cycle is not the dataset required for the second.
If the first cycle was a project, the second is the same project — with the additional burden of explaining what changed and why.
Reported data is not, in these frameworks, accepted on the basis of the producer's submission alone. The Circular Action Alliance Participant Producer Agreement, §7.1(d), requires producers to warrant that their reports are:
"...(i) accurate and complete, (ii) provided to CAA with any necessary consent, right, permission, license, clearance, or authority (including any further reasonable proof thereof (if requested by CAA))..."
The CAA Oregon Program Plan formalizes this further. Under "Duty to Comply with Requests for Documentation":
"Upon written request from CAA, participant producers shall provide documentation in support of their reports to CAA. This may include specific data, calculation methodologies, and/or audit reports, among other items."
Under "Duty to Provide Access":
"Participant producers will be required to grant access during business hours to CAA or its authorized representatives to inspect and review records relevant to information submitted in their reports..."
And under "Retention of Records":
"CAA members will be required to retain records to substantiate and verify the accuracy of the information submitted in their reports for a to-be-determined period following the submission, and such records will be subject to inspection by CAA."
These provisions change what the producer must keep, in addition to what the producer must submit. The supplier email confirming a material substitution, the supplier specification sheet listing component weights, the methodology note describing how a recyclability designation was reached — each becomes a record that may need to be produced on request, possibly years after the reporting cycle has closed.
Validation does not introduce a different kind of work. It increases the operational value of records the producer was already, in principle, responsible for. The standing of a reported number now depends not just on whether the number was submitted, but on whether the producer can show how it was derived.
When the data sources are external, the requirements are component-level, and the cycles are annual, the coordination cost of ad hoc supplier outreach accumulates over time. Each cycle that begins with a fresh round of supplier emails, custom spreadsheets, and inconsistent format reconciliation pays the same coordination cost as the cycle before it. Each cycle that closes without a structured supporting record set may leave the producer less prepared to respond to a subsequent validation request.
The arithmetic does not require a sharp inflection. It requires only that the work recur. Over the course of the 2027 → 2030 → 2032 California milestone schedule alone, a producer can expect to run five or six reporting cycles, with similar supplier interactions, similar data requirements, and similar validation exposure, applied each time.
The form of the response is a producer-by-producer decision. It can be informal — a shared spreadsheet maintained year-round, a standing supplier check-in process, a routine product-launch checkpoint. It can be formal — a dedicated packaging-data process embedded in a compliance function. What the regulatory framework does not allow is for the question to be deferred indefinitely. The recurring nature of the obligation gives information processes time to compound their value if they exist, and to compound their absence if they do not.
Packaging EPR places legal responsibility on the producer while much of the required information originates outside the producer's control. The first reporting cycle is what reveals this asymmetry. The recurring nature of the framework is what makes it operationally consequential.
Organizations that treat supplier information as an annual collection exercise will likely repeat much of the same work every reporting cycle. Organizations that build repeatable information processes are more likely to reduce that recurring coordination burden over time.
A state-by-state map of where you owe — and which next step fits the shape of your data.
Get your EPR Compliance BlueprintThis article is for informational purposes only and does not constitute legal advice. Regulatory timelines and program requirements are subject to change. Always verify current obligations with state authorities, PROs, and qualified legal counsel directly. Orbitlex is not a law firm.