Single-facility EPR compliance is a documentation problem. Multi-facility EPR compliance is a documentation architecture problem. The distinction matters because the challenges that appear when a manufacturer operates production facilities across multiple EPR-active states aren't simply a scaled-up version of the single-facility challenge — they're qualitatively different problems that require a different approach to infrastructure design.
This article is for sustainability directors and compliance managers at manufacturers operating four or more production facilities across states with differing EPR frameworks. If you're trying to build a compliance architecture that works at scale without creating separate, incompatible documentation systems for each state, the decisions you make in the next 12 months will determine whether that's achievable.
The Multi-State Documentation Problem
Consider a manufacturer with production facilities in Michigan, Ohio, Indiana, and Illinois. Michigan has the Clean Products Initiative. Illinois has passed EPR legislation with rulemaking ongoing. Ohio and Indiana have no enacted EPR framework as of 2025, though Indiana manufacturers in the automotive supply chain face OEM documentation requirements that function as de facto compliance obligations.
The Michigan facility needs documentation meeting Michigan's specific requirements: closed-loop percentage by material grade, chain-of-custody to recycler, quarterly reporting on defined schedules. The Illinois facility will need documentation that meets Illinois's framework once implementation rules are final. The Ohio and Indiana facilities need documentation that satisfies OEM supplier qualification criteria — which, in practice, means documentation equivalent to what Michigan requires, even without a state regulatory driver.
If each facility builds its documentation system independently — using local MES exports, local spreadsheet workflows, and local recycler certificate filing practices — the manufacturer ends up with four disconnected data stores that cannot be consolidated into a coherent company-wide EPR disclosure without significant manual reconciliation work at each reporting cycle. Corporate sustainability leadership can't see the consolidated picture. Finance can't easily audit the numbers. And when the first cross-state OEM sustainability questionnaire arrives asking for company-wide recycled content data, somebody has to manually extract and reconcile data from four different local systems under deadline pressure.
Why State Framework Differences Make Consolidation Harder Than It Looks
The first instinct is to build a consolidated compliance database and then customize the reporting output for each state's specific requirements. In principle, this is the right architecture. In practice, it's complicated by three factors that manifest differently at each facility:
Reporting period mismatches. State EPR frameworks define reporting periods differently. Some require quarterly reporting; some require annual; some have both periodic and event-triggered reporting requirements. A single consolidated database needs to handle different reporting calendars for different facility-state combinations without requiring custom database configurations for each state.
Material category definitions. States define material categories for EPR reporting in different ways. Michigan's framework has specific grade categories for ferrous and non-ferrous metals. California's SB 54 focuses on plastic materials with resin-level categories. GRI 306 uses its own hazardous/non-hazardous split. A consolidated tracking system needs to capture material data at sufficient specificity to satisfy all the category definitions the manufacturer must report against — which means the most granular category set, not the least granular.
Recycler certification requirements. States recognize different recycler certification schemes. Michigan recognizes state-registered recyclers and ISO 14001-certified facilities. Other states may specify different certification criteria. A multi-facility manufacturer using a regional recycler network needs to verify that each recycler holds the certifications required by each state where the relevant facilities are located — which may be different certifications for the same recycler, depending on which facility's scrap they're receiving.
Building a Consolidated Compliance Architecture
The foundational principle for multi-site EPR compliance architecture is: one source of truth for material flow data, multiple views for state-specific reporting. This means designing the data collection layer to capture the most granular data required by any framework the manufacturer must comply with, so that state-specific reports can be generated as filtered views of that common data set rather than as separately collected data.
For a manufacturer in the scenario described above, the data collection layer needs to capture at minimum:
- Generation weight by container, with source facility, source line, production order reference, and timestamp
- Material grade at the container level (not just material type — grade-level specificity satisfies both Michigan's framework and GRI 306)
- Carrier handoff record per container with weight, timestamp, and carrier identity
- Recycler receipt confirmation per batch with received weight and certificate reference
- Recycler certification status by facility and period
From this common data foundation, Michigan's quarterly closed-loop percentage report for the Michigan facility is a filtered, aggregated view. Illinois's eventual reporting requirements are a different filtered view of the same data. The OEM sustainability questionnaire response is another view. The GRI 306 disclosure is another. The sustainability team doesn't need to run a separate data collection project for each reporting obligation — they need one data collection system and multiple report templates.
The Integration Layer Challenge
Multi-facility manufacturers rarely have uniform MES and ERP environments across sites. A facility acquired in 2018 may run Epicor Kinetic. The flagship Michigan plant runs SAP S/4HANA. An Indiana stamping operation runs Plex Manufacturing Cloud. Each has different data structures for production orders, material lots, and scrap generation records.
The material tracking layer has to normalize data from these different source systems into a common schema — translating each system's native field structures into the standardized data model required for consolidated EPR reporting. This normalization work is typically the most technically complex part of a multi-site implementation. It's also where most multi-site projects underestimate effort: the first site's integration is relatively clean; the second and third sites reveal that the "standard" integration approach doesn't work the same way on different source systems.
We're not saying ERP homogenization is required before EPR compliance architecture can work. We're saying the integration design needs to account explicitly for system heterogeneity rather than assuming it away. The integration design that works for four systems with different data models is more complex than the design that works for one — but it's the design that actually supports multi-site compliance at scale.
Governance: Who Owns What in a Multi-Site System
Multi-facility compliance architecture is as much a governance question as a technical one. When material flow data is collected centrally and reported at both facility and corporate levels, clear ownership structures need to exist for several decisions:
Data quality for each facility. If a facility's scale integration goes offline or a container ID scan is missed, who is responsible for identifying the gap and resolving it? The facility's operations team or the corporate sustainability function? Ambiguity here creates compliance gaps that surface at filing time.
Recycler certificate receipt and matching. Recycler certificates are typically addressed to the facility, not to corporate. In a multi-site system, certificates need to be uploaded centrally and matched against the facility's generation and handoff records. The workflow for certificate receipt, upload, and validation needs clear ownership — typically the facility-level environmental compliance coordinator, with corporate sustainability providing oversight and exception handling.
State filing sign-off. Each state's EPR filing is typically submitted by the facility or by the company as a legal entity registered with that state's program. The sign-off authority needs to be defined — who has authority to certify the accuracy of a facility-level EPR filing, and what review process does the corporate sustainability team require before filing?
These governance questions are best resolved before the first multi-site implementation is complete, not when the first filing deadline arrives and the process is unclear. The manufacturers who build governance frameworks alongside technical implementation are the ones who sustain compliance quality across reporting cycles, rather than finding that the technical system works but the organizational process produces inconsistent outputs.
