Every year, the same ritual plays out: just before the reporting deadline, data gets pulled from ERP exports, supplier portals, and aging spreadsheets, manually stitched together, and submitted to the compliance system with fingers crossed. One mistake and you're not just looking at back-payments - [1] fines can reach €200,000.
EPR reporting is no longer a niche concern. With the PPWR, which becomes binding across all EU member states on August 12, 2026, the requirements for packaging data, documentation, and evidence are rising sharply. Companies still relying on manual processes are building on a foundation that simply won't hold up.
The Problem: Why Manual EPR Quantity Declarations Break Down
Data Scattered Across Too Many Sources
The real work in EPR reporting rarely lies in filling out the declaration form itself - it lies in tracking down the data. [2] show that 30-70% of the necessary data is typically missing when packaging specifications are first digitized. Material weights, component structures, sales volumes - this information is spread across ERP systems, inventory management tools, supplier portals, and local spreadsheets.
The result is what compliance experts call "manual, non-auditable Excel chaos": [3]. Every reporting cycle generates new rounds of reconciliation, broken data handoffs, and manual audit trails.
Error-Prone and Impossible to Audit
Field reports from the ZSVR show that audit guidelines are frequently violated and under-reporting often goes undetected. This is no accident: when material weights are calculated by hand, component quantities are aggregated manually, and changes are never versioned, inconsistencies are inevitable.
Particularly critical: [4]. Discrepancies between the two declarations can be treated as a regulatory violation. Anyone who can't produce airtight documentation will find themselves in a difficult position during a ZSVR audit.
Doesn't Scale with Your Portfolio
For a company with 50 SKUs, Excel might just about work. For FMCG companies managing thousands of articles, multiple packaging components per product, and sales across several EU countries, it simply doesn't scale. [2]
Warning – Risk of Fines: Late or incorrect data reporting can result in fines of up to €10,000. If the completeness declaration is missing entirely or submitted too late, further sanctions may follow — and the ZSVR consistently pursues violations.
What EPR Reporting Actually Involves
Before talking about automation, it's worth taking a clear-eyed look at the full scope of reporting obligations - because many companies underestimate just how many processes sit behind the term "quantity declaration."
1. System Participation and Ongoing Quantity Declarations
Every company that places packaged goods on the German market must register in the LUCID packaging register and enter into a licensing agreement with a dual system (e.g., Grüner Punkt, Reclay, Interseroh). [5]. The same quantities must also be reported in parallel to the LUCID register.
Licensing fees are based on the material type and weight of the packaging placed on the market. That means: companies that don't know their material weights precisely will either overpay - or underpay and risk back-payments.
2. Annual Final Declaration
At the end of each calendar year comes the annual final declaration: the definitive actual-quantity report covering all packaging placed on the market. [6]. It forms the basis for the final fee settlement.
3. Completeness Declaration (VE)
Larger companies face an additional obligation: the Completeness Declaration (Vollständigkeitserklärung, or VE). Companies that placed more than 80,000 kg of glass, 50,000 kg of paper/cardboard, or 30,000 kg of plastics, metals, or composites on the market in the previous year must file an audited Completeness Declaration with the ZSVR annually by May 15. [7].
4. Multi-Country Reporting for EU-Wide Distribution
Companies placing packaging on the market not just in Germany but also in other EU countries must meet separate EPR obligations in each target country. [8]. France additionally requires the Triman label and operates a mature eco-modulation system; Spain and Austria have their own reporting requirements and in some cases require the appointment of an authorized representative.
What a Professional EPR Reporting Solution Needs to Deliver
Not every piece of software with "EPR" in the name actually solves the underlying problem. [8]. Here's what a professional EPR reporting solution must be capable of:
| Anforderung | Warum wichtig | Ohne Software |
|---|---|---|
| Zentrale Verpackungsdatenbank | Einheitliche Datenbasis für alle Meldungen und Länder | Daten verteilt in ERP, Excel, E-Mail |
| Automatische Mengenberechnung | Materialgewichte pro Komponente korrekt aggregieren | Manuelle Berechnung, fehleranfällig |
| Audit-Trail & Versionierung | Nachvollziehbarkeit bei ZSVR-Prüfungen | Keine Änderungshistorie |
| Multi-Country-Fähigkeit | Länderspezifische Regeln und Meldeformate | Separate Prozesse je Land |
| ERP-Integration | Absatzmengen direkt aus dem System | Manueller Export und Abgleich |
| Export für Systembeteiliger | Direkte Übergabe an duales System und LUCID | Manuelle Aufbereitung je Empfänger |
A Central Packaging Database as the Foundation
At the heart of any EPR reporting solution is a structured, versioned packaging database. [9]. Only companies that maintain this data centrally and consistently can generate quantity declarations in an automated, error-free way.
Automatic Quantity Calculation and Aggregation
From the packaging database, material weights per component can be calculated automatically and multiplied by sales volumes pulled from the ERP system. The result: a complete quantity declaration broken down by material type and packaging category - with no manual steps in between.
An Audit-Ready Documentation Trail
[10]. Every change to specifications or quantities is versioned and timestamped. This isn't just valuable for internal processes - it's a prerequisite for a defensible Completeness Declaration.
How Packa Supports EPR Reporting
Packa is an EU-native platform for digital packaging management, built from the ground up for exactly these requirements. The approach: capture packaging data once in a structured way - then use it across every downstream process, from quantity declarations to PPWR declarations of conformity.
See how Packa automates your EPR reporting — from quantity declarations to completeness statements.
Talk to a Packaging ExpertCentralized Packaging Specification Management
Packa uses AI to digitize packaging specifications from PDFs, Excel exports, and ERP data - transforming them into a structured, auditable data foundation. [11] - that's the baseline that makes automated EPR reporting possible in the first place.
Every packaging component - carton, film, label, closure - is captured with material type, weight, and recyclability. Changes are versioned. Supplier data is collected in a structured format and integrated directly into the platform.
Automatic Material Quantity Aggregation
From the stored specifications and sales volumes, Packa automatically calculates the reportable material quantities - broken down by material type, packaging component, and target market. [8].
That means: no manual calculations, no transcription errors, no discrepancies between the LUCID declaration and the dual system declaration.
Export Functions for Dual System Operators and LUCID
The aggregated quantities can be exported directly in the formats expected by dual system operators and the LUCID register. [9] - without expensive custom development.
Audit-Ready Documentation
Packa provides a central, versioned packaging database with a complete audit trail. Every change to specifications, quantities, or material data is transparently documented. This creates the foundation for the Completeness Declaration - and for a solid response to any inquiry from the ZSVR or a dual system operator.
Looking Ahead: The PPWR Raises the Stakes for Reporting
What today might still feel like a "nice to have" becomes mandatory from August 2026. The PPWR doesn't just introduce new packaging design requirements - it fundamentally tightens the demands on EPR reporting.
Eco-modulation becomes mandatory across the EU. Under Article 45 of the PPWR, EPR fees will be directly tied to recyclability grades - packaging with better recyclability pays less. [12]. That means: companies that don't know their material composition precisely won't be able to take advantage of eco-modulation savings.
More granular data requirements. [10]. A simple weight figure per material class will no longer be sufficient.
Declaration of Conformity becomes mandatory. [13], confirming that the packaging meets PPWR requirements. This Declaration of Conformity (DoC) is based on the same specification data needed for EPR reporting - another strong argument for a unified data foundation.
Multi-country reporting gets more complex. [14]. Companies active in multiple markets need a solution that maps country-specific requirements centrally.
Go digital before the pressure mounts: Companies that structure their packaging data and automate EPR reporting today will already be prepared for PPWR requirements from August 2026 onwards — while also saving significant manual effort in every reporting cycle.
Conclusion: EPR Reporting Is a Data Problem - and It's Solvable
Manual EPR quantity declarations in Excel aren't a compliance process. They're a symptom of missing data structure. [3] are the direct consequence.
The good news: the problem is solvable. Companies that capture packaging specifications in a structured way just once can automate quantity declarations, unlock eco-modulation savings, and produce audit-ready Completeness Declarations - for Germany and every other EU market.
Packa is the only EU-native platform that links EPR reporting directly to a complete packaging portfolio: specifications, material weights, and sales volumes flow automatically into the declaration. The result: less effort, fewer errors, more control.
See in a live demo how Packa automates your EPR quantity reports and makes your reporting audit-proof.
Book a DemoWhat is a quantity report in the EPR context?
A quantity report is the mandatory declaration of the amount of packaging placed on the market — broken down by material type and weight. It must be submitted both to the dual system (e.g. Grüner Punkt, Reclay) and to the packaging register LUCID. The quantities reported must be identical in both cases.
Who is required to submit a completeness declaration?
Companies that exceeded certain quantity thresholds in the previous year: 80,000 kg of glass, 50,000 kg of paper/cardboard, or 30,000 kg of plastics, metals, or composites. The completeness declaration must be filed annually with the ZSVR by May 15th and confirmed by a registered auditor.
What is the difference between LUCID and the dual system?
LUCID is the public packaging register operated by the Zentrale Stelle Verpackungsregister (ZSVR) — this is where companies register and report their quantities. The dual system (e.g. Grüner Punkt, Reclay, Interseroh) is the private-sector contractual partner that organizes and finances the collection and recycling of packaging. Both reports must be identical.
What does the PPWR change about EPR reporting?
The PPWR, which takes effect on August 12, 2026, harmonizes EPR requirements across the EU and introduces mandatory ecomodulation: EPR fees will be tied to the recyclability of the packaging. In addition, more detailed material data and a Declaration of Conformity (DoC) for each packaging type will become mandatory. Companies that do not maintain structured packaging data will be unable to meet these requirements.
Can I cover EPR reporting with my ERP system?
ERP systems like SAP provide important sales and quantity data, but are not designed to manage packaging specifications and country-specific EPR rules. In practice, a specialized packaging management platform like Packa is recommended as a complementary data layer — it handles specifications and compliance logic, while the ERP supplies the transactional data.
