Packaging EPR reporting is becoming a recurring data operation. Before you worry about a portal, make sure the underlying SKU, component, weight, supplier and evidence records can survive review.
See what records are missing, explore a synthetic worked example, or request a free 15-minute fit call before considering a paid assessment.
Explore the three-minute worked example → · For beauty and personal-care brands →
California now uses PEPRS for producer registration, data submission and compliance tracking. Circular Action Alliance also lists 2026 annual or interim producer reports across several state packaging EPR programs. The exact legal obligations vary by state and producer, but the operational pattern is clear: companies need repeatable packaging data that can be assembled, supported and reconciled.
This guide is about internal data control and reporting readiness. It does not determine whether your organization is an obligated producer or replace state, PRO or legal guidance.
Do not stop at a product or SKU name. A useful EPR data structure separates the package into its reporting-relevant components: bottle, cap, label, pouch, tray, carton, insert, film, pad and similar elements. For each component, retain the supplier, supplier part number, material description, effective date and supporting source.
California’s covered-material system is organized around combinations of material type and form. That makes component-level source data important even when final reporting categories are determined later under current program instructions.
Record finished component weights in a consistent unit and retain the source. A supplier specification, technical drawing or controlled physical measurement is stronger than an unexplained number copied into a spreadsheet. If an estimate must be used, identify it explicitly rather than allowing an estimate to look like measured data.
Packaging information often sits outside the team responsible for EPR reporting. Suppliers and converters may hold finished weights, material descriptions, recycled-content information, layer structures and technical specifications. Track who was asked, what was requested, when it is due, what was received and what remains unresolved.
This turns supplier follow-up from an inbox search into an auditable work queue.
Every reporting process develops gaps. The control question is whether those gaps are visible. Log the affected SKU or component, the field in question, the estimate or assumption, its basis, the reason better evidence is missing, the owner and the target resolution date.
An exception register also makes review easier: a manager can focus on unresolved judgments instead of rereading the entire dataset.
New products, discontinued SKUs, packaging redesigns, supplier substitutions and weight changes can all make last year’s data stale. Maintain effective dates and a change log so the reporting dataset can be updated during the year rather than reconstructed immediately before a deadline.
Before reporting, compare the current population and key packaging values with the prior year. Large changes should have an explanation: a new SKU, a discontinued item, a source correction, a material redesign or a supplier change. A prior/current-year reconciliation is one of the simplest ways to identify missing or duplicated records before submission.
A practical internal readiness standard is that active SKUs are represented, component weights and materials have supporting sources, unresolved assumptions are visible, current-year changes are incorporated, state-sales or other reporting populations are reconciled, exceptions have owners, and the final dataset has a documented review.
The Excel kit turns these six controls into a reusable workbook with a packaging BOM, supplier evidence tracker, assumptions register, change control, annual reconciliation and reporting-readiness checklist.
This article provides educational information about administrative data controls and is not legal advice.
