How to manage EPR in multiple countries in 2026
The hard part of a second EU market is keeping entity, register, category and period straight. Build one packaging record, then file each country on its own route.
Short answer: Once you sell into a second Member State, the hard part is not weighing another box. It is keeping the responsible legal entity, register, product category and reporting period correct for every market. PPWR Articles 44 and 45 provide for national producer registers. They do not issue one number for the Union. Build a record that can answer who owes what, where, for which pack, and during which dates.
What a multi-country EPR file has to hold
The unit of work is a country, an entity and a waste stream. A country list hides the legal decision. For each destination, name the company that first makes the pack available there, its place of establishment and the sales route. Repeat for packaging. If the SKU is electrical or contains a battery, those streams stay on other registers; do not fold them into the packaging row.
smbf.me is packaging EPR software with country workspaces, order import, destination mapping, packaging calculations, supported reports and evidence history. It is not legal advice, not a producer responsibility organisation, not an authorised representative, and not a single EU registration. Scheme fees, representative mandates and portal accounts remain separate unless a written proposal says otherwise.
| Field | Why it matters | Evidence example |
|---|---|---|
| Destination and first supply date | Selects the national rule and reporting period | Order export and shipping record |
| Responsible legal entity | Stops filing under the wrong group company | Invoice, import record, marketplace contract |
| Product or packaging stream | Selects the register | Bill of materials and classification |
| Local representation | Shows who may file or perform the duties | Written mandate and register confirmation |
| Registration and scheme ID | Proves participation or permission | Registry extract, certificate, PRO agreement |
| Reporting basis | Lets the declaration be reproduced | Component weights, quantities, mapping version |
The register matrix is an output of these facts. If an importer changes, or a seller moves from a marketplace to its own checkout, recalculate the row. A static "country done" tick cannot explain either change.
Why one shared "EU compliant" status breaks
Germany, Sweden and France already disagree on who clicks, what category is reported, and which calendar applies. A foreign direct seller without a German branch appoints a packaging representative, but the producer must create its own LUCID registration; the representative may handle later packaging duties, including volume reports. ZSVR representative guidance
Sweden's environmental agency's current packaging guidance requires a Sweden-established representative for specified EU-established packaging direct sellers from 12 August 2026, and the 2026 packaging data may need separate periods around that date because the producer definition changed. France splits household packaging from catering and a wider professional route still moving toward 2027 operations, with a stream-specific IDU. Those are three transforms of the same commercial evidence. Swedish 2026 packaging producer, ADEME IDU
If you collapse them into one status, you cannot reproduce a declaration when the scheme or the authority asks.
Shared drives and one January reminder
Many teams start with a shared drive of invoices, one LUCID PDF, and a spreadsheet of "annual EPR" dates. Someone pastes the same material codes into every portal. Someone else stores the representative flag as yes/no without the mandate.
Missed periods and wrong entities follow. Sweden's 2026 packaging data is due by 31 March 2027 and may need pre- and post-12-August producer periods. Germany wants LUCID quantities to match the system operator. A single "file everything in January" reminder will not catch both. This article is an EU-27 operations note; UK packaging EPR is a separate regime and is not this workflow.
How to run it here
Start from one measured SKU and shipping configuration. In smbf.me, keep country workspaces and versioned exports rather than overwriting last period's file.
- Build a row for each destination, legal entity and waste stream, and keep evidence for a no-obligation decision as well as for a yes.
- Keep one measured SKU and shipping record, then map components to each country's live reporting fields with a dated rule version.
- Separate the producer from the person who uses the portal, and store the written mandate where a representative is required.
- Put registration prerequisites, measurement period, filing date, submitter and owner on a calendar taken from that register's authority page.
- Before each filing, reconcile entity, period, categories and kilograms, then store the submitted file, receipt and calculation together.
Record material, empty weight and function of every packaging component. Store measurement date and specification version so a pack redesign updates every country that sells the SKU. Create a dated mapping rule: source component, reportable category, weight calculation, excluded cases. When a category changes, you can see which past periods need review.
Germany remains a useful filing-party example inside one country: LUCID is the producer's own act, while foreign WEEE and battery applications without a German establishment go through a German authorised representative in the ear-Portal. Save the actual mandate, not a general flag called "representative appointed". stiftung ear WEEE as a foreign company
A worked packaging example: a rechargeable lamp in a paperboard box with a plastic insert, sold from your own webshop to Germany, Sweden and France. The product record still has three packaging components plus the lamp and battery as other streams. That is nine decisions, not automatically nine registrations. For packaging, check LUCID and system participation in Germany, Naturvårdsverket and the 2026 transition in Sweden, and the relevant eco-organisation and IDU in France. Run the applicability test before you open each portal.
Checklist before you submit a national file
Use the five workflow steps above as the spine. A receipt uploaded later does not repair a wrong entity or last year's mapping rule.
For this filing window, confirm the row still matches the live portal fields, the mandate on file names the filer you are using, the calendar date came from the authority page (not a dual-system invoice), and kilograms reconcile to the same SKU specification version you export.
Mistakes that mix countries together
Teams reuse last year's mapping because the SKU name did not change. The pack did: a new mailer, a heavier insert, a pallet wrap that was never on the bill of materials. Version the specification, or the kilogram file will not match the warehouse.
Filing under the EU parent because "that is who pays the invoice" is a separate trap. The register wants the producer for that market. If a subsidiary first makes the pack available, the parent number will not defend the declaration.
One dual-system invoice is not a calendar for 27 countries. Open the authority link next to each date. Recheck it at filing, because PPWR transition texts and national portals still move.
Common questions about running several countries
Can one EU number cover every Member State? No. PPWR provides for producer registers in Member States and registration where the packaging is first made available. Keep a country-specific number and evidence pack. A German LUCID entry does not stand in for a French IDU or a Swedish producer record. PPWR
Should every country use the same packaging material categories? Use the same measured components. Translate them into the current national fields. LUCID asks for packaging types and matching system-operator quantities; Sweden's 2026 packaging report can split periods around 12 August because the producer definition changed. Those are different transforms of one bill of materials. ZSVR data reporting, Swedish agency
What changes when a marketplace listing becomes a direct webshop sale? Reassess producer identity, representative rule and registration before the first direct transaction. The sales channel is part of the legal fact pattern, not only a reporting filter. A number that was valid for marketplace supply can fail for direct-to-end-user sales. PPWR producer rules
Does one software workspace file every national portal automatically? No. smbf.me can import orders, map countries and keep packaging data, supported reports and evidence history. It does not replace the national register, the scheme or the authorised representative, and it does not claim auto-filing into every portal. You still submit through the live national route.
Open each destination from the 27-country packaging EPR guide. If a row is still blank, run the applicability test first. For the German packaging split of register, system and report, use the Germany country page.
Sources and review method
Register, representative and calendar facts were checked against the linked authority pages. Recheck the live form before you submit. This article is not legal advice.