Short answer: EPR reporting needs packaging data at the component level: every bottle, cap, label, carton, film and case for each SKU, with its material, format and weight, linked to evidence. Most brands have item masters and sales data but not this. Building it once, in a normalized structure, is what makes multistate reporting, fee forecasting and redesign decisions manageable.
Item master versus packaging bill of materials
An item master describes what you sell: SKU, description, size, case pack, price, maybe gross weight. It answers “what is this product?” A packaging bill of materials (BOM) describes what that product is packed in, broken down into each physical component. It answers “what packaging leaves with every unit, and how much of each material is that?”
Gross shipping weight minus net product weight is not a packaging BOM. It hides the split between materials, which is exactly what EPR programs charge on. A glass jar with a steel lid and a paper label is three different material categories, not one tare weight.
Packaging levels: primary, secondary, shipment and e-commerce
| Level | What it is | Example |
|---|---|---|
| Primary | Packaging in direct contact with the product, or the unit the consumer buys | Bottle, cap, label, pouch, jar |
| Secondary | Packaging that groups primary units for sale or display | Multipack carton, shrink sleeve, display tray |
| Tertiary / transport | Packaging used to move goods through distribution | Corrugated case, stretch wrap, pallet |
| E-commerce shipping | Packaging added to ship an order to a consumer | Mailer box, void fill, poly mailer, tape |
Which levels count depends on the program. Some focus on packaging that reaches households; others include more. Capture all levels in your data and let each state's rules decide what is reported. It is far easier to exclude a level later than to go back and collect it.
Component-level fields
Every component record should capture at least: the material, any material detail that affects classification (plastic resin, coatings, laminates, colorants), the physical format, the weight of one component, and how many of that component go with each sold unit. Recycled content and recyclability attributes are increasingly relevant for eco-modulated fees.
Sample field structure
The table below is an illustrative, non-client-specific example of a normalized packaging record. Values are made up for illustration.
| Field | Description | Typical source | Illustrative value |
|---|---|---|---|
| sku_id | Your SKU or item number | ERP / item master | SKU-1042 |
| sku_description | Product name and size | ERP / item master | Sparkling Water 12 oz, 12-pack |
| brand | Brand on the package | Item master | Example Brand |
| packaging_config_id | ID for a packaging configuration shared across SKUs | Built during normalization | CFG-CAN12-CTN |
| component_id | Unique component within the configuration | Built during normalization | CFG-CAN12-CTN-03 |
| component_name | What the component is | Spec sheet | Paperboard carton |
| packaging_level | Primary, secondary, tertiary/transport or e-commerce shipping | Spec sheet / operations | Secondary |
| material | Base material | Spec sheet / supplier | Paperboard |
| material_detail | Resin, coating, laminate or other detail | Supplier declaration | Clay-coated, unbleached |
| format | Physical form | Spec sheet | Folding carton |
| weight_value | Weight of one component | Spec sheet / measured | 86 |
| weight_unit | Unit as provided | Spec sheet | g |
| weight_g | Weight converted to grams | Calculated | 86.0 |
| components_per_sku_unit | How many of this component per sold unit | Spec sheet / BOM | 1 |
| recycled_content_pct | Postconsumer recycled content, if known | Supplier declaration | 35 |
| evidence_ref | Link to the source document or measurement record | Evidence register | EV-0217 |
| evidence_type | Spec sheet, supplier declaration, measured sample, estimate | Evidence register | Supplier declaration |
| assumption_note | Documented assumption where data is missing | Issue log | None |
| effective_from | Date this version took effect | Change log | 2025-03-01 |
| effective_to | Date this version was replaced, if any | Change log |
Supplier evidence and data provenance
A weight without a source is an assumption. For each value, record where it came from: a supplier specification, a signed supplier declaration, a measured sample, or an estimate with a documented method. Keep the document or measurement record in an evidence register and reference it from the component record.
Supplier outreach is often the slowest part of the work. Packaging suppliers, converters and co-packers each hold part of the picture, and requests stall without a clear template and follow-up. Ask for what you need in a structured format: component, material, resin or substrate, weight per unit, recycled content and the date the specification applies.
Unit conversions and quality-control rules
- Normalize units. Convert every weight to one unit (grams works well) and keep the original value and unit for traceability.
- Check plausibility. Flag components whose weight is far outside the range for similar items, such as a 12 oz can lid recorded at 120 g.
- Reconcile totals. Compare the sum of component weights to measured or published package weights where available.
- Require completeness. Every component needs material, format, weight and evidence type before it is used in a report.
- Watch per-unit counts. A case of 24 should allocate the case weight across 24 units, not charge each unit a full case.
SKU-to-packaging relationships and shared configurations
Many SKUs share packaging. Ten flavors in the same bottle, cap and carton use one packaging configuration with different labels. Model this explicitly: define packaging configurations once and link SKUs to them. When a supplier changes a cap, you update one configuration instead of ten SKUs, and every affected report updates consistently.
State sales allocation
Packaging weight per unit becomes reportable quantity only when multiplied by units supplied into each state. Direct shipments with ship-to states are straightforward. Sales to national distributors and retailers that move goods across state lines need an allocation method, such as distributor sell-through data or a documented proxy. Write the method down and apply it consistently.
Missing-data workflow and documented assumptions
Almost every brand starts with gaps. Handle them deliberately:
- Log the gap in an issue log with an owner and due date.
- Request the data from the supplier or measure a sample.
- If a deadline arrives first, use a documented estimate, for example from a comparable component, and mark it as an assumption.
- Replace the assumption with evidence when it arrives, and keep the history.
Versioning when packaging or suppliers change
Packaging changes during the year. A lighter bottle, a new label stock or a switch from plastic to paper all change reportable quantities. Give each component version an effective date range so the data reflects what was actually supplied in each period. Versioning is also how you prove source reduction over time.
What this foundation supports
- Reports. State-ready outputs generated from one source, consistent across programs.
- Fee forecasts. Quantities by material category are the input to every fee model. See packaging EPR fees.
- Redesign decisions. Compare the fee and compliance effect of packaging alternatives before you change suppliers.
- Audit readiness. Trace any reported number back to a SKU, component and source.
Next steps: learn how to request packaging specifications from suppliers, then how to connect SKU packaging to state-level sales. If you would rather hand the work off, see Managed Packaging EPR Operations.