The assumption that fails
When small brands first hear about Extended Producer Responsibility, the next thing they usually hear is: "don't worry, there are exemptions for small businesses." That statement is true. What usually goes unsaid is what it takes to rely on one.
EPR exemptions exist across all seven active states. Six use a revenue threshold based on global gross revenue — the total worldwide revenue of the obligated producer entity: Oregon and Washington at $5M, Colorado at $5.5M (indexed to inflation), Maine, Minnesota, and Maryland at $2M. California uses a different base: California-specific sales, with a $1M threshold. Washington adds a second condition — both revenue and tonnage thresholds must be met. These thresholds are real, published, and verifiable. The difficulty is not finding the number. It is applying it correctly to a specific business.
The problem is that determining whether you qualify — in a way that can be documented and defended — is itself a compliance exercise.
Three structural reasons the calculation is harder than it looks
First: the threshold applies to the obligated producer, not to "your company" as you understand it. Before applying any revenue figure to any threshold, a brand must determine which legal entity is the obligated producer under the state's statutory hierarchy. That determination follows the same hierarchy that governs registration: brand owner first, then licensee, then importer of record. The threshold is measured against whichever entity that analysis produces — which may or may not be the entity whose revenue figures the brand's team reviews. The wrong entity produces the wrong number and the wrong conclusion.
Second: the revenue base is not uniform across states. Six states measure global gross revenue — total worldwide revenue of the obligated producer entity. California measures California-specific sales. A brand below Oregon's $5M global revenue threshold may simultaneously be above California's $1M California-specific threshold. A $3M brand is exempt in Oregon and fully obligated in Maryland at the same time. Each state's determination is independent. There is no single calculation that resolves all states simultaneously.
Third: Washington requires two conditions, not one. Falling below Washington's $5M revenue threshold is necessary but not sufficient for exemption. Tonnage of covered packaging introduced into the state must also fall below the applicable threshold. A brand that qualifies on revenue and has never measured its packaging tonnage does not have a complete exemption determination for Washington — it has half of one.
The three threshold traps
Six states measure global gross revenue — total worldwide revenue of the obligated producer, not US-only revenue. A brand that tracks US-only revenue may clear the threshold on the number it monitors but exceed it once global revenue is included. California applies a separate $1M threshold against California-specific sales, creating an independent obligation that co-exists with other states' thresholds.
Washington requires both revenue below $5M and tonnage of covered packaging below the applicable threshold. A brand that meets the revenue condition without having measured its packaging tonnage does not have a complete exemption determination. Revenue alone is not sufficient.
The threshold is applied to the obligated producer as determined by the statutory hierarchy — which may not be the entity whose revenue the team tracks. Until the producer determination is made, the revenue figure being evaluated may be the wrong one entirely.
Each trap has the same structure: a brand applies the right framework to the wrong input and reaches a conclusion that cannot be defended.
Amazon FBA and DTC sellers
Amazon FBA sellers remain individually responsible for their product packaging under all seven state EPR programs. Amazon's role as a fulfillment provider does not transfer the brand owner's producer obligation. The brand whose name appears on the packaging is the producer of that packaging — regardless of which warehouse it ships from or which platform processes the transaction.
Product packaging and shipping packaging are treated as separate obligations. The brand owner is the producer of the product packaging that arrives at Amazon's fulfillment center. Amazon may hold responsibility for the outbound shipping packaging it adds. FBA sellers face a narrower but real obligation: product packaging registration, reporting, and fee obligations in every active state where their products are sold.
DTC brands face the same obligation without the structural complexity. Sales are attributed directly to the brand as producer. A brand selling across multiple active states owns the threshold analysis, the registration, and the reporting for each state independently.
The documentation problem
An exemption is a conclusion that must be supportable by data. At minimum, a defensible exemption position requires:
- Identification of the obligated producer entity under each state's hierarchy
- The global gross revenue of that entity for the relevant fiscal year (or California-specific sales for California)
- For Washington: tonnage of covered packaging introduced into the state
- Documentation of when the determination was made and what data it was based on
An exemption position that exists only as an assumption — without underlying data — is not a compliance posture. It is a gap that becomes visible when the assumption is tested. Documentation created retroactively is harder to substantiate than records maintained at the time of the determination.
The data infrastructure problem
The uncomfortable truth: the data required to substantiate an EPR exemption is nearly identical to the data required to register and report under EPR.
To establish the revenue threshold, you need the global gross revenue of the obligated producer entity — by year. To establish the tonnage condition for Washington, you need packaging weight data by SKU and units sold into the state. To identify the obligated producer, you need to work through the producer hierarchy — the same analysis required for registration.
This is not meaningfully different from what a registering producer compiles for an annual EPR report. The difference is that a registering producer builds this infrastructure intentionally and maintains it year over year. A brand relying on exemption often builds it only when challenged — under time pressure and without a prior year's baseline.
By the time a brand is reconstructing this data retroactively, it is already operating in reactive compliance mode.
The companies that navigate exemption cleanly are the ones that treated it as a compliance question from the start: identified the obligated producer entity, gathered the relevant revenue data, applied it to each state's threshold, documented the reasoning, and set a calendar to revisit it annually.
When exemption status expires
EPR exemption thresholds are not permanent. Colorado's threshold is explicitly indexed to inflation and adjusts over time. All state thresholds are set by statute or rulemaking and are subject to revision as programs develop. A brand that establishes its exemption status and does not revisit it may be operating on a determination that no longer holds.
There is no automatic notification when a brand crosses a threshold. Revenue grows. Product lines expand. Distribution enters new states. The obligation to monitor belongs to the producer — not to the PRO, not to the state agency, and not to any party in the supply chain.
Exemption status is not a one-time determination. It is an annual compliance function.
"The exemption question is not 'are we small enough.' The exemption question is 'can we prove we are small enough, and will that still be true next year.'"
What to check now
If your brand currently relies on EPR exemption — or assumes it does — the following questions determine whether that position is substantiated:
If the answer to any of these is no, you are relying on an exemption you cannot yet substantiate. That is a different situation than not qualifying — but it carries the same risk if your status is ever questioned.
The brands that get surprised by EPR are not the ones that ignored it. They are the ones that made a reasonable assumption and never converted it into a documented position. The exemption trap is not a trap set by regulators. It is a gap between how compliance feels in year one and what it requires when the program matures.
Understanding where your company stands — before you are asked to explain it — is the difference between a compliance posture and a compliance liability.
Build a defensible exemption position before regulators ask for it
Our compliance workflow walks through threshold analysis by state, entity structure review, and packaging data requirements — so your exemption position is documented, not assumed.
Get Free EPR Compliance Check