Somewhere after the compliance kickoff meeting, someone on the ops team gets handed a one-line task: "make sure we're EPR compliant in France, Germany, and Italy." No process, no owner, no software recommendation, just a deadline tied to a PRO's next filing window. That task only becomes tractable once you break it into a repeatable pipeline instead of a once-a-year scramble.
Who owns this after the kickoff meeting ends
EPR reporting fails most often not because the rules are unclear, but because no single team owns the full chain. Ops owns shipping data, finance owns the PRO relationship and payment, and nobody owns the handoff between them. Before building any process, assign one person as the pipeline owner, someone who can see shipment data and file the report, or who coordinates tightly with whoever does. And if you haven't confirmed which countries you're actually obligated to report in, settle that first via our producer-status guide before building a pipeline around an assumption.
The five-stage process map
Stage 1: Capture at the point of shipping
Every parcel that leaves the warehouse should log three things at minimum: destination country, the SKU(s) shipped, and the packaging profile used (see our BOM guide for how to define profiles). This is the one stage that has to happen automatically, at the moment of shipping, reconstructing it after the fact from order history is possible but painful, and it's where most merchants lose the will to keep the process accurate.
Stage 2: Aggregate by material and country
Monthly or quarterly, match your PRO's own reporting cadence rather than defaulting to the calendar year, sum shipment-level packaging data into material-category totals per destination country. This is a straightforward multiplication-and-sum job once Stage 1 data exists cleanly, a spreadsheet is genuinely fine here for most merchants below enterprise volume.
Stage 3: Match to the right PRO
Each country has its own registration and its own PRO relationship: LUCID plus a licensed dual system in Germany, CITEO in France, CONAI in Italy. Confirm the aggregated totals map to the material categories each PRO's declaration form actually asks for, they're not identical, and a category that's granular in one country's form might be one line item in another's.
Stage 4: Submit and pay
Submit the declaration through the PRO's portal and pay the calculated fee. Keep the submission confirmation and fee calculation together, not just the payment receipt, because an audit will ask for the basis of the number, not just proof it was paid.
Stage 5: Reconcile and archive for audit
Close the loop by reconciling declared totals against your actual shipment data for the period, and archive everything: the raw shipment export, the aggregation, the submission, and the payment confirmation. Most national schemes can request records going back several years; losing the underlying data between filing cycles is a common, avoidable failure.
Where this breaks in practice
- Packaging profile drift. A supplier swaps a component mid-quarter and nobody updates the BOM, so Stage 1 data quietly becomes wrong without anyone noticing until the totals look off.
- Returns and cancellations double-counted. Packaging on a returned order was still placed on the market once; don't subtract it from your totals unless the specific scheme's guidance says to.
- Multi-item orders under-weighted. A single packaging profile applied uniformly regardless of order size understates weight for bulk orders.
- Country mapping errors. A parcel routed through a fulfillment hub in one country but delivered to a consumer in another gets attributed to the wrong scheme.
- Deadline mismatch. Assuming every country reports on the same schedule; they don't, and missing one country's window while hitting another's is still a miss.
- No fallback when a system changes. A platform migration, a new 3PL, or a shipping software upgrade wipes out the custom fields you'd been using to capture packaging profile data, and nobody re-adds them to the new setup before the next reporting period starts.
Building it into existing shipping software
Most merchants don't need bespoke software for this, they need three additional fields captured wherever shipping labels are already generated: destination country (likely already captured), packaging profile ID, and a timestamp. If your platform or 3PL can export that alongside standard order data, Stage 1 and Stage 2 become a scheduled export-and-sum job rather than manual work. Where merchants get into trouble is trying to reconstruct this retroactively from generic order exports that were never designed to carry packaging detail, build the capture in before the reporting deadline is looming, not during it.
Once the pipeline produces reliable totals, the fee outcome itself depends partly on material choice, see our eco-modulation explainer for how that plays into what you actually pay per declaration. If you're changing fulfillment providers or shipping platforms this year, add "packaging profile field survives the migration" to the cutover checklist explicitly, it's exactly the kind of quiet dependency that gets dropped when a project's attention is on getting orders flowing again, not on compliance data that nobody notices missing until months later.
What a working pipeline looks like month to month
It's worth being concrete about what "done" looks like once the pipeline is running, because on paper this can sound heavier than it actually is in practice. A merchant with the pipeline built typically spends under an hour a month on it: an automated export drops shipment-level data into a shared folder, a scheduled spreadsheet formula rolls it into material-and-country totals, and the pipeline owner spot-checks the numbers against the prior period before filing season starts. The heavy lifting happens once, at setup, not every reporting cycle. Merchants who treat this as a recurring manual project, re-pulling and re-aggregating from scratch every quarter, are the ones who eventually miss a deadline or file a rushed, inaccurate number under pressure.
Build the pipeline once, not once a year
The merchants who find this manageable are the ones who treat it as infrastructure, three extra data fields at the shipping stage, a scheduled aggregation job, and a shared archive, rather than a quarterly fire drill. Set up Stage 1 capture this month even if Stages 2 through 5 are still manual; the earliest, cleanest data always comes from the point of shipping, and you can't go back and capture it later.
Frequently asked questions
Compliance glossary
Related reading
- Mastering Packaging Data: How to Build an Accurate Material BOM
- Eco-Modulation Explained: Why Your Packaging Materials Impact Your Fees
- France, Germany, Italy: Comparing EPR Requirements for Online Sellers
- Solving the Empty-Air Problem: PPWR Void Space and Dimensional Weight
- The Producer Trap: Does Your E-commerce Store Meet EU EPR Criteria?
