One obligation engine, from national rule to filed evidence
Complywerk turns the messy reality of multi-country EPR into a single, dependable flow. You maintain clients; the engine maintains the obligations, mandates, deadlines, reminders and audit trail that hang off them — from onboarding to the last nil return of an offboarding.
Rules → obligations → calendar → reminders → evidence
A versioned rules base encodes each country's regime. Every client's countries and material flows are resolved into the exact obligations they carry — and everything downstream follows automatically.
Ten EU markets and the UK, with EU-level rules on top
Country regimes are researched, encoded and versioned — from Germany's LUCID to the UK's packaging EPR. Change a rule's deadline once and every affected client's calendar, reminders and export update. No per-country spreadsheets to keep in sync.
LUCID / EPR
EPR (CITEO)
EPR
CONAI
RPD (pEPR)
BDO
EPR
EPR
EPR
EPR
Filings in the register's own structure — checked before they leave
The hardest part of a filing isn't the maths, it's the transcription. The UK RPD packaging return is generated in its exact category structure, with plausibility checks that catch the errors humans make when copying tonnage between systems.
- Category-level tonnage mapped to the RPD return structure
- Plausibility checks flag outliers and zero-value anomalies
- Every figure carries a source tag — measured, spec sheet or estimate — and estimated values are disclosed on every export, so your methodology is self-evidencing in an audit
- Receipts archived and linked to the filing on the audit trail
- The same engine extends to LUCID and other registers
Authorised-representative mandates as records, not PDFs in a folder
An AR mandate is a legal relationship with formal requirements, validity dates and a registry-facing status — not just a signed document. Complywerk tracks every mandate per client, country and stream, from draft through active and expiring to terminated.
- Country-specific formal-requirements checklists — Germany's WEEE (ElektroG §8) and packaging (VerpackG §35) regimes ship first; a mandate cannot go active until the required items are ticked, recorded per your licensed review
- Expiry reminders through the same four-tier engine as filings — 30/14/7/1 days ahead by default, offsets configurable per workspace
- Termination checklists: terminating a mandate automatically creates the registry-notification task, and every transition lands on the append-only audit trail
- The client portal clearly marks obligations the producer must complete themselves (e.g. LUCID registration under VerpackG §9), so the delegation boundary stays visible on both sides
Client offboarding, done right — down to the last nil return
Losing a client is not a date, it is a phase with country-specific duties — and the tail is what nobody budgets time for. Complywerk models offboarding as a status with its own checklists, so nothing stops silently and nothing runs on forgotten.
- Nil-return tail: filings keep generating until the registry publishes the market-leaving date, each one explicitly titled “Nil return” — visible in the calendar, the task list and the client portal
- Dual-track German packaging checklist: LUCID deregistration and the PRO system-participation contract are two separate exits, each with an “administrative confirmation archived” verification step
- France: the registered-letter exit window of Citeo-type contracts lands on the calendar as its own item — always flagged “check your contract terms”, because clauses differ
- Every status transition is recorded on the append-only audit trail
The system tracks the tail-period obligations; the legal judgement of when duties actually end stays with your licensed review — see the responsibility boundary in our Trust Center.
One ZIP for the marketplace compliance desk
Marketplaces verify EPR compliance and delist sellers who cannot produce proof. When Amazon asks, the answer should be one click: a pack of registration numbers and certificates assembled to the marketplace's own country template.
- Amazon templates for Germany (LUCID number + proof of system participation) and France (IDU) available today — Spain (ENV) and Austria (GLN/VKS) coming soon
- Each pack contains the registration-number listing (CSV), the linked certificate files and a gap list — expired or missing items are named, never silently omitted
- Certificates such as the annual Teilnahmebescheinigung (proof of system participation) inherit the vault's expiry reminders, so next year's refresh is already on the calendar
Want to see the engine on your book of clients?
We'll set up a demo tenant with the countries and flows you actually operate in.