Registration is only the visible step. The real burden is maintaining packaging, sales, channel, and reporting data across seven separate state systems.
This article focuses on the operational fragmentation that emerges when packaging EPR obligations stack across multiple states. For the broader thesis on why packaging EPR is an operational function rather than a filing task, see the companion perspective below.
Learn more:Why a Managed EPR Service Is Becoming More Practical Than Both Spreadsheets and Software
Once a brand sells across multiple active EPR jurisdictions, the compliance picture changes shape. Registration is the visible step. The operational burden is what comes after — spanning packaging data infrastructure, sales geography attribution, fulfillment channels, reporting calendars, and state-level definitions that share almost nothing in common.
The most common operational misunderstanding in multi-state EPR is treating producer enrollment as the compliance finish line. Register with the Circular Action Alliance. Receive confirmation. Move on.
That sequence describes administrative access — not operational compliance.
The Circular Action Alliance currently administers programs in six of the seven enacted states. For brands, this looks like consolidation. Operationally, it isn't. Each CAA agreement is separately negotiated under a different state statutory framework. Fee structures differ. Covered material definitions differ. Reporting templates differ. Contractual terms differ. A CAA membership in Oregon is not the same legal instrument as a CAA membership in Colorado, Maine, Minnesota, Maryland, or Washington — even though they share the same administrator.
After enrollment, each state program generates its own obligations:
None of these obligations transfer across states. Oregon's 2024 annual report does not satisfy Colorado's 2024 annual report, even though the underlying products and packaging may be identical. The reporting infrastructure for each state must be built and maintained separately.
The visible part of multi-state EPR is enrollment. The operational burden begins after enrollment — and it compounds with every additional state. (For a detailed overview of how PROs work and what producers are actually joining, see What Is a Producer Responsibility Organization?)
A common assumption among national brands is that the underlying EPR programs are structurally similar — that compliance in Oregon provides a template for Colorado, which provides a template for Maine, and so on.
They are not structurally similar. They are seven independently designed systems with incompatible operational requirements.
Producer status rules differ. California's statute uses a three-tier producer hierarchy: brand owner, exclusive licensee, then seller/distributor. Oregon uses a different structure with no standalone brand owner tier. A foreign brand with a U.S. distributor but no U.S. licensee faces a different legal producer status analysis in California than in any other state — and a different compliance exposure profile as a result.
Revenue thresholds are incompatible. Oregon exempts producers below $5M global gross revenue. California covers producers above $1M in California-specific sales. Maine, Minnesota, and Maryland set the threshold at $2M global gross. The trigger metric itself differs: California measures state-specific revenue; every other state measures global revenue. A brand with $4M global revenue and $2.5M in California sales is exempt in Oregon but obligated in California. The same brand, the same products, two different compliance statuses — because the thresholds measure different things.
Covered materials diverge sharply. California currently covers only single-use plastic packaging and plastic food service ware. Colorado, Oregon, Maine, Minnesota, Maryland, and Washington all cover paper products: catalogs, directories, promotional mailers, inserts. A paper catalog mailed to consumers is a reportable covered material in six states and entirely outside California's program scope. Minnesota is the only state that covers boat wrap. Oregon requires life cycle assessments from the top 25 producers by covered material weight — an obligation with no analog in any other state.
Program structures vary. Maryland is currently the only state permitting multiple competing PROs, a model that will require brands to evaluate enrollment options that don't exist elsewhere.
Run a directional fee estimate across CA / OR / CO.
Washington mandates a $5M annual reuse financial assistance fund beginning in 2029 — a PRO obligation with no equivalent in any other program. These are not minor variations in implementation. They are structural differences that create distinct compliance workflows for the same national brand.| State | Exemption Threshold | Paper Products | Fee Operative |
|---|---|---|---|
| California | >$1M CA sales | Not covered | 2027 (est.) |
| Oregon | >$5M global | ✓ Covered | Operative |
| Colorado | >$5M global | ✓ Covered | Operative |
| Maine | >$2M global | ✓ Covered | ~2027 |
| Minnesota | >$2M global | ✓ Covered | 2029 |
| Maryland | >$2M global | ✓ Covered | 2029 |
| Washington | TBD | ✓ Covered | 2030 |
Multi-state EPR is not one national framework replicated seven times. It is seven separate and evolving systems with different definitions, timelines, reporting structures, and operational requirements.
This is where most multi-state EPR compliance programs encounter their first serious operational breakdown — not at the registration stage, but at the data stage.
State EPR programs require producers to report covered packaging by material type, material weight, recyclability designation, and in some cases component-level hierarchy — organized by the state into which those materials were introduced. Standard enterprise resource planning systems were not designed to capture this information. They track packaging as a procurement cost center: unit cost, supplier, inventory quantity, lead time. The material composition record that EPR requires — resin type, layer structure, weight by component, recyclability classification under each state's specific criteria — is almost never stored in an ERP system in usable form.
Colorado's first annual reporting cycle in 2024 was the first real-world stress test of this gap at scale. Brands attempting to file 2024 supply data discovered that the information they needed was distributed across supplier specification sheets, packaging engineering records, product lifecycle management systems, and in many cases was simply absent — had never been captured in a centralized, queryable format. The reporting problem was a symptom. The root cause was a packaging data architecture problem that predated EPR by years.
Most companies do not have an EPR reporting problem. They have a packaging data architecture problem that EPR has made visible.
The practical scope of what must be built is broader than most compliance timelines assume:
Packaging data gaps that EPR programs expose:
Paper and promotional materials present a structural challenge that extends beyond packaging data systems entirely. All six non-California states cover catalogs, directories, promotional mailers, and inserts as covered materials. These materials are procured and distributed by marketing departments — not supply chain, not procurement, not logistics. Most packaging compliance platforms don't ingest marketing print procurement data. Most marketing teams don't know they have an EPR reporting obligation. The data gap is organizational before it is technical.
Building the packaging data layer needed for multi-state EPR reporting is not a one-time project. Material classifications evolve as state definitions change. New SKUs must be onboarded with complete material records. Supplier specifications must be validated and updated. The dataset must be maintained continuously across seven state-specific taxonomies with no shared standard between them.
For brands selling through multiple channels — retail, Amazon FBA, direct-to-consumer, and wholesale — the same physical product generates different EPR obligation profiles depending entirely on how it was shipped. This is not a theoretical edge case. It is the operational reality for a large share of national consumer brands, and it is not modeled in most compliance frameworks.
Under Oregon, Colorado, Minnesota, and Washington, the entity that physically packages an item for shipment is the statutory producer for that shipping packaging. When a brand's product is fulfilled through Amazon FBA, Amazon packs and ships the outer box. In those states, Amazon is the statutory producer for the FBA shipping packaging. The brand is the producer for the product packaging inside the box.
The practical consequence: the same SKU sold through retail, through Amazon FBA, and through the brand's own DTC website generates three different EPR obligation profiles for the packaging in that transaction.
| Sales Channel | Product Packaging | Shipping Packaging | Producer Structure |
|---|---|---|---|
| Retail | Brand | Retailer / carrier | Single — brand only |
| Amazon FBA | Brand | Amazon | Split — brand + Amazon |
| Direct-to-Consumer | Brand | Brand | Unified — brand for all layers |
Most existing compliance workflows were not designed to model this channel-level fragmentation consistently — particularly across states with different shipping-packaging rules.
Amazon has not publicly disclosed its EPR enrollment or fee pass-through structure for FBA sellers. If Amazon enrolls as a producer for shipping packaging and passes costs through FBA fee adjustments, brands pay indirectly. If Amazon does not enroll, the unregistered shipping packaging obligation may create regulator inquiries that flow back to brand producers. Neither scenario is currently resolved or predictable.
Franchise structures create a parallel complexity. In Maine, Colorado, Minnesota, Maryland, and Washington, a franchisor with even one franchisee location in the state is the statutory producer for all covered materials flowing through every in-state franchisee — regardless of whether the franchisor controls packaging decisions at the store level. A national restaurant or retail franchise with thousands of locations across those states faces EPR obligations that scale with network size, not with the franchisor's direct operational control.
Private-label and co-manufactured products create a different attribution problem. Without a signed, state-compliant written assignment agreement between the brand owner and the contract manufacturer, both parties can be treated as co-producers in Maine, Minnesota, and Washington. Most existing co-manufacturing supply agreements do not contain EPR assignment language. The compliance exposure exists in contracts signed before EPR was a consideration — and those contracts typically have not been reviewed or updated.
EPR liability increasingly follows packaging control and fulfillment structure — not simply product ownership. Brands that haven't mapped their channel-level packaging responsibility across all active EPR states are operating with an incomplete picture of their actual compliance exposure — including penalty exposure that can reach $50,000 per day per violation in California and equivalent ranges in other operative states. (See EPR Penalties by State for a full breakdown.)
The difficulty of multi-state EPR compliance is often framed as a legal interpretation problem: complex regulations, evolving definitions, state-specific nuance. That framing mislocates the source of most compliance failures.
The harder operational problem is that the data required for EPR compliance exists across multiple internal functions that were never designed to coordinate with each other for regulatory reporting purposes.
Product packaging is typically managed by supply chain or procurement. Shipping and fulfillment packaging belongs to logistics. Promotional paper — catalogs, mailers, directories, inserts — sits with marketing. Retailer-exclusive SKU specifications may sit with a dedicated trade team. Contractual assignments for co-manufactured products sit with legal. Fee modeling sits with finance. State-specific regulatory monitoring may sit with legal, compliance, or no one in particular.
Every one of these functions generates or controls data required for multi-state EPR reporting. State laws generally do not specify a single responsible owner for this workflow. In most organizations, EPR compliance is managed across functions through manual coordination and point-in-time data pulls — assembled under deadline pressure rather than maintained as a continuous operational process.
Oregon is the only state that currently publishes a public list of compliant and non-compliant producers on the CAA website. Reporting failures in Oregon create public reputational exposure, not just regulatory risk. Maryland is the only state with a statutory third-party audit requirement for PRO-level data — meaning producer submissions in Maryland face implicit audit scrutiny that flows back upstream from the PRO. As more programs mature and enforcement frameworks develop, the tolerance for fragmented, manually assembled compliance data will narrow.
Sustainability teams often receive initial EPR assignments because the law is framed as environmental policy. But the actual workload — packaging data collection, SKU-level classification, supplier coordination, annual reporting, fee modeling, state monitoring — spans operations, procurement, finance, legal, and marketing. Sustainability functions are rarely structured to coordinate across all of them.
EPR compliance rarely fails because companies ignore the law. It fails because the required operational data was never designed to function as a unified regulatory reporting system — and the internal structure to assemble it across functions on an annual basis doesn't exist.
The real burden of EPR is not registration. It is building packaging, sales, fulfillment, and reporting data systems capable of surviving continuous regulatory variation.
As of May 2026, two of the seven enacted state programs — Oregon and Colorado — have issued producer invoices and are fully operative. The remaining five are at various stages of rulemaking, stewardship organization selection, or regulatory finalization, with no operative fee obligations and, in several cases, no finalized reporting requirements.
Sell-prohibition dates — the date after which brands without valid PRO enrollment face potential sales restrictions — are staggered across seven years: Oregon and Colorado in July 2025, Maine approximately in 2027, Minnesota in January 2029, Washington in March 2029, and California in January 2032. No two states share the same trigger date, and several remain contingent on regulatory milestones that haven't yet been reached.
Eco-modulation fee schedules — the mechanism that charges higher fees for non-recyclable packaging and lower fees for recyclable materials — are included in all seven state laws but are not yet operative at scale. Oregon has initiated a framework; Colorado is in development; the remaining five states have not published schedules.
Brands investing in packaging redesigns to reduce long-term EPR cost exposure are doing so without a published fee differential to validate the return. The packaging change may be complete before the applicable fee schedule exists — or the schedule may differ from what was anticipated when the redesign decision was made.
California's regulatory situation shifted materially in May 2026. After CalRecycle withdrew its draft implementing regulations in January 2026 and restarted the rulemaking process, SB 54 implementing rules were finalized on May 1, 2026. The May 31, 2026 reporting deadline is now confirmed — covering the 2023 baseline report, annual supply report, and annual source reduction report. Brands that delayed compliance planning pending regulatory clarity now face a compressed window. California remains the largest and most operationally demanding EPR market in the U.S.
Multi-year EPR cost modeling for national brands is currently speculative for five of the seven states. That is not a compliance gap in the traditional sense. It is a structural planning problem: brands must maintain compliance infrastructure for programs whose fee structures, reporting requirements, and covered material definitions are still being written.
The brands that are managing multi-state EPR most effectively are not managing it as a compliance function. They are managing it as an operational data function — with the same discipline applied to financial reporting or supply chain traceability.
The foundation is a centralized packaging data layer — a single system of record for packaging composition at the SKU and component level, covering material type, weight, recyclability classification, and layer structure, maintained continuously and mapped to each state's specific reporting taxonomy. On top of that sits a sales geography transformation workflow: a methodology for converting DC-level inventory data into state-of-introduction volume calculations, since standard logistics systems were not built to produce state-attributed covered material volumes.
Beyond the data layer, multi-state EPR requires structured channel-level attribution — a mapping of which packaging layers carry which producer obligations across retail, FBA, DTC, and franchise channels — along with a separate data feed from marketing procurement systems that captures catalog, mailer, and insert volumes distributed into each covered state. Paper and promotional materials are among the most commonly missed covered material categories precisely because they have never been part of packaging compliance workflows.
The operational layer includes:
Building this infrastructure internally requires cross-functional ownership structures that most organizations don't currently have, data systems that span procurement, logistics, marketing, and finance, and regulatory monitoring capacity across seven evolving programs simultaneously.
For many brands, the cost of building and maintaining that infrastructure is not trivial relative to year-one fee obligations — particularly in states where fees are still years away. Brands operating in Oregon, the most mature program, can use that experience as a reference point for what other state programs will eventually require. (See our Oregon EPR Compliance Guide for a state-specific breakdown.) That cost calculus will shift as programs mature and enforcement pressure increases. But the brands that build compliance operations infrastructure early will be positioned to scale it as new states activate, rather than rebuilding it reactively under deadline pressure.
As EPR programs mature, the differentiator will not be whether brands registered. It will be whether they built systems capable of maintaining compliance across multiple evolving jurisdictions simultaneously.
Multi-state packaging EPR has crossed a threshold. For national brands selling packaged goods across the U.S. market, the question is no longer whether to register — it's whether the operational infrastructure exists to sustain compliance as seven programs simultaneously mature, diverge, and expand their covered material scope.
The brands that adapt to this environment early are treating compliance data as infrastructure, not paperwork. They are building centralized packaging data systems, cross-functional reporting workflows, and ongoing regulatory monitoring processes that treat EPR as a permanent operational function — not a periodic filing exercise.
The brands that don't will encounter the same pattern: data reconstruction under deadline pressure, fragmented cross-functional coordination at the point of submission, and structural rework as each new state program goes operative. The compliance gap accumulates quietly, and becomes expensive at the moment it's hardest to address.
Run a free EPR Status Check to see which states your brand is exposed to — and what compliance actions apply to your specific situation.
Get Free EPR Compliance CheckThe build-vs-buy question for this operational infrastructure — internal capability vs managed service — is explored in the companion perspective below.
Learn more:Why a Managed EPR Service Is Becoming More Practical Than Both Spreadsheets and Software
This 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 the relevant state agency and producer responsibility organization directly. Orbitlex is not a law firm.