Every EPR compliance customer starts in the same place: a spreadsheet. Usually shared between Finance, Operations, and whoever drew the short straw on the compliance ticket. This article is an honest breakdown of what that spreadsheet costs you across a year — and when switching to purpose-built software is obviously the right move.
We are not going to argue that Excel is worthless. It is genuinely the cheapest possible option up to a point. The question is where that point is.
The 30-second answer
- Up to 1 country, ~500 orders/year, annual filing, stable packaging: Excel is fine. Maybe even optimal.
- 2+ countries, monthly or quarterly filings, or a changing product catalog: Excel costs more than it saves — it's the kind of cost that only shows up as "we spent our Friday reconciling numbers for CITEO" rather than as a line item on the P&L.
This article breaks down the numbers behind that cutover.
What Excel-based compliance actually looks like
Typical tabs in a real spreadsheet we've migrated from:
- Products: SKU, name, selling price.
- BOM / Packaging: packaging components per SKU, weights in grams, material type.
- Sales Q1 / Q2 / Q3 / Q4: one tab per quarter (or month), exported from Shopify / WooCommerce / the Amazon Seller Central report.
- Country-splitter: VLOOKUP from country code to country name, pivot by country.
- Material totals: SUMIFS summing packaging weights per country per material.
- Declaration templates: one per PRO — ECOEMBES in one format, CITEO in another, LUCID in a third. All with different column orders, units (kg vs g), and decimal separators.
When a well-run spreadsheet like this is at its best, it works. The problems arrive when anything changes.
The hidden costs nobody measures
1. Time spent per filing
From customer interviews, the median time to prepare a single country's declaration from scratch in a spreadsheet is 6–10 hours. Multiply by country count and filing frequency:
- 1 country, annual: ~8 hours/year. Fine.
- 3 countries, quarterly: ~96 hours/year. That's 3 full weeks of founder time.
- 5 countries, mixed monthly + quarterly: ~180+ hours/year. A part-time job.
At a conservative €75/hour internal cost, that's €7,200–€13,500/year for 3 countries. Pack Declare's paid plans run from €120 to €590 a year.
2. Error rate
Across declarations we've re-computed for customers migrating from Excel, the baseline error rate is 3–5 material-level errors per declaration. The most common:
- Unit mismatches: grams reported in a kg-denominated column, or vice versa. Results in numbers off by a factor of 1,000.
- Stale BOM: the spreadsheet reflects the packaging as of January; a supplier swap in March is not back-propagated.
- Missing subtype mapping: ALUMINIUM subtype should map to ECOEMBES "Metales No Ferrosos" (vs. the default STEEL → "Metales Ferrosos"). Spreadsheet formulas rarely handle this.
- Returns not netted: sales are gross; returns aren't netted out of the packaging total. PROs typically want net.
- B2B / B2C mix not separated: e-commerce B2C packaging declares differently from wholesale-to-retailer B2B in several countries (BE, FR). Many spreadsheets collapse both.
Most of these don't get caught until a PRO audit asks for reconciliation. At that point, reconstructing the error from scratch is usually more expensive than the fine itself.
3. No audit trail
An Excel file at submission time is a snapshot. If you ever need to answer "what were the exact sales lines and BOM that produced this number", you're rebuilding the answer from scratch — hoping the source data still exists and that no one has edited the master spreadsheet in between.
Pack Declare stores every compute run as an immutable ledger. You can replay the exact calculation from 2024 even after your Shopify catalog and your BOM have both changed in 2026.
4. Format drift
ECOEMBES, CITEO, LUCID and the others update their required CSV formats periodically. If you hand-build declarations in Excel, you have to:
- Notice the format change (often buried in a PRO circular).
- Download the new template.
- Rebuild your pivot / VLOOKUPs / column order.
- Re-validate against the new spec.
Pack Declare's country adapters are versioned. When a format changes, we ship a new adapter version; your declaration packs pick it up automatically. You don't notice the change because we've already noticed it.
5. Cross-country expansion cost
In a spreadsheet, adding a new country (say PL, SE, DK — the three we just added to Pack Declare) is a full copy-paste-modify of the pivot + template. Plan on 4–8 hours of setup per country, plus a full filing cycle before you trust it.
In Pack Declare, you click "Add Poland". The mapping, validation, and CSV format are all there on day one. Same for Sweden, Denmark, and the next country we add.
Cost comparison: a realistic SMB scenario
Imagine a Shopify brand selling to ES + FR + DE, 50 SKUs, monthly compute and quarterly filings:
| Excel DIY | Pack Declare | |
|---|---|---|
| Software cost/year | €0 | €2,388 |
| Hours spent on compliance/year | ~80 hours | ~10 hours |
| Time cost (€75/h internal rate) | €6,000 | €750 |
| Estimated fine risk/year (3–5 errors × avg PRO fine) | €500–2,000 | <€100 |
| Total annual cost | €6,500–8,000 | €3,238 |
Even excluding fine risk, Pack Declare saves ~€3,000 in real money per year for a company at this scale. That's before counting the opportunity cost of founder time.
When Excel is still the right answer
We'll talk you out of switching if:
- You sell in exactly one country, with an annual filing (not monthly or quarterly), fewer than ~500 orders/year, and a stable packaging spec. For that customer, 8 hours/year in a spreadsheet is genuinely cheaper than a SaaS subscription.
- You're below every PRO threshold and only need a basic registration, not a full declaration. At that stage you're tracking whether you crossed the threshold, not computing declarations.
- Your packaging is radically non-standard and the Pack Declare data model doesn't fit it yet (e.g. some refill / return-pool / industrial cases). Our data model is optimized for e-commerce — niche B2B industrial packaging may still be easier in Excel.
A clean migration path
For the 80% of spreadsheet users who will graduate, the migration is straightforward:
- Export your BOM tab to CSV and upload it via Pack Declare's BOM bulk import.
- Connect your Shopify / WooCommerce / Amazon store (or upload sales CSVs if you prefer).
- Run a compute job for the last closed quarter and compare numbers with your spreadsheet version. Discrepancies almost always reveal bugs in the spreadsheet, not in the software.
- From then on, Pack Declare replaces every tab. Your spreadsheet becomes historical reference.
Most migrations take under 2 hours of working time, usually completed in a single afternoon. Customers on any paid plan can do it with our done-with-you onboarding (€499 one-time) if they prefer.
The honest bottom line
Spreadsheets are an excellent starting point and a terrible permanent system. The switching moment arrives earlier than most SMBs expect — typically the first time you're asked to file in a second country, or the first time a PRO audit lands on your desk.
If you're reading this and recognize yourself in the "80 hours a year in a spreadsheet" scenario, the switch literally pays for itself in about 4 months. And the first month is the Free tier, so you can evaluate it without spending anything.
Run the free PPWR Compliance Check →
Or start free with Pack Declare →
Related reading: Pack Declare vs. Coolset · Pack Declare vs. PPWR Copilot · Pack Declare vs. Eldris
Frequently asked questions
Can I manage EPR compliance in a spreadsheet?
Yes, and for some sellers it is the right answer. A well-run spreadsheet with tabs for products, packaging bills of materials, quarterly sales, a country splitter and per-scheme declaration templates genuinely works. The problems begin when something changes.
When is Excel still the better choice for EPR?
When you sell in exactly one country, file annually rather than monthly or quarterly, ship fewer than roughly 500 orders a year, and your packaging specification is stable. At that scale eight hours a year in a spreadsheet is cheaper than any subscription.
At what point does a spreadsheet stop being worth it?
At two or more countries, at monthly or quarterly filing frequency, or with a changing product catalogue. Past those thresholds Excel costs more than it saves — but as Friday afternoons spent reconciling figures rather than as a line item on the profit and loss.
Why is multi-country EPR hard to do in a spreadsheet?
Because each scheme wants a different shape. ECOEMBES, CITEO and LUCID use different column orders, different units — kilograms against grams — and different decimal separators. Every added country multiplies the templates you maintain and the ways a transcription can go wrong.
What does a typical EPR spreadsheet contain?
Usually a products tab, a packaging bill of materials tab with component weights and materials, one sales tab per quarter or month exported from your storefront, a country splitter built on VLOOKUP, material totals built on SUMIFS, and a separate declaration template for each scheme.
Are there cases where software is the wrong fit?
Yes. If your packaging is radically non-standard — some refill, return-pool or industrial cases — a data model optimised for e-commerce may not fit it, and a spreadsheet remains easier. Being below every scheme threshold is another: you are tracking a threshold, not computing declarations.
What are the hidden costs of spreadsheet-based compliance?
They rarely appear as costs at all, which is the difficulty. They surface as reconciliation time, as errors found late, and as a dependency on whoever built the workbook. None of that is visible in a budget line, so the comparison is usually made against a subscription price alone.
How do you migrate from a spreadsheet without losing history?
Keep the spreadsheet as the record of past filings and move forward from a clean period boundary. Your packaging bill of materials is the asset worth carrying across; the sales tabs can be replaced by connecting the storefront the exports came from in the first place.