How to offboard an EPR client without leaving liabilities behind (DE & FR checklists)

Plenty has been written about onboarding an EPR client. Almost nothing has been written about the other end — and the other end is where agencies get burned. A producer stops selling into a market, the commercial relationship winds down, someone archives the folder… and six months later there is a missed filing, a registry warning, or an invoice from a scheme nobody remembers being party to. Offboarding an EPR client is not a date; it is a phase with country-specific duties, and two opposite failure modes: stopping too early, and not stopping everything.

Failure mode one: stopping too early (the nil-return tail)

In Germany's WEEE regime the sequence is explicit. Registration with stiftung ear is an administrative act, not a contract you can walk away from: ending it means applying for revocation in the ear portal, which can be requested at the earliest two months in advance and never retroactively. Crucially, the reporting obligation does not end when the application is submitted — it ends when the market-leaving date is published in the register. Until then, a producer that has stopped selling must keep filing, reporting zero. Those nil returns are not busywork; they are the legal difference between an orderly exit and a compliance breach during the tail.

This is the single most common offboarding mistake we hear from agencies: the team stops generating filings the day the client says goodbye, because 'they're not selling any more'. The obligation says otherwise. The operational answer is that offboarding should be a status in your system that changes how obligations are labelled — 'nil return' — rather than a deletion that makes them disappear.

Failure mode two: not stopping everything (the German dual track)

German packaging law splits a producer's duties across two separate legal relationships: registration in the LUCID register, operated by the Zentrale Stelle, and a system-participation contract with a dual system (a PRO), which are distinct obligations with separate counterparties. The exit mirrors the structure: deregistering from LUCID is one track; terminating the system-participation contract with the PRO is another. They do not trigger each other. An agency that files the LUCID deregistration and forgets the PRO contract leaves the client paying participation fees for capacity they no longer use — and an agency that cancels the contract but leaves the registration active leaves a registered producer with no system participation, which is its own violation while any sales continue.

Both tracks should end with a verification step, not an action step: the registry's or scheme's written confirmation — in German administrative practice, the Verwaltungsakt or equivalent confirmation document — archived against the client record. 'We sent the letter' is not evidence; the confirmation is.

France: the eco-organisme owns the exit

France routes EPR through approved eco-organismes, and the unique identifier (IDU) that proves a producer's compliance is managed accordingly: in the collective system, the eco-organisme registers the producer in SYDEREP, communicates the IDU, and is the party that can withdraw it — producers do not self-manage the identifier. Offboarding a French client therefore runs through the eco-organisme relationship, not around it.

The contractual layer is where the money is. Membership contracts of the Citeo type commonly renew by tacit annual renewal, with termination requiring notice — commonly by registered letter before 31 October — ahead of the next contract year. Miss the window and the client is typically committed, and paying, for another full year. The exact clause varies by contract and by year: treat the 31 October date as a planning default and check your contract terms for every client before relying on it. The operational point stands regardless of the precise date: the French exit window belongs on a calendar with reminders, months ahead, because it is the one offboarding deadline that silently costs a year's fees when it slips.

The checklists

Condensed to the steps that recur, per regime:

Germany — WEEE (stiftung ear)

1. Agree the market-leaving date with the client; apply for revocation in the ear portal no earlier than two months ahead.
2. Keep filing until the market-leaving date is published — as nil returns once real volumes stop.
3. Archive the revocation confirmation and the published delisting against the client record.

Germany — packaging (LUCID + PRO, two tracks)

1. Track A: file the LUCID deregistration; archive the administrative confirmation.
2. Track B: terminate the system-participation contract with the dual system per its notice terms; archive the termination confirmation.
3. Verify both confirmations exist before closing the client — one without the other is an unfinished exit.

France — eco-organisme (Citeo-type)

1. Locate the termination clause and notice deadline in the membership contract — check your contract terms; do not assume the default.
2. Send the required notice (typically registered letter) inside the window; archive proof of dispatch and any acknowledgement.
3. Confirm the final declaration and the IDU status with the eco-organisme before closing.

Making the phase visible in your system

Every step above is unglamorous, and that is exactly why it fails in spreadsheets: offboarding work has no revenue attached, no client pushing for it, and a time horizon of months. It survives only if the system carries it. Complywerk models offboarding as a client status with consequences: filings keep generating through the tail with an explicit 'Nil return' title until the market-leaving date, the German dual-track checklist creates both exit tracks with their archive-the-confirmation verification steps, the French exit window lands on the calendar as its own dated item — flagged to check your contract terms — and every status transition is written to the append-only audit trail. The goal is simple: when a client leaves, the last thing your agency files for them should be a deliberate zero, not an apology.

Country processes evolve and contract clauses differ. This guide describes the recurring structure; confirm current registry procedures and your specific contract terms — the legal conclusions belong with your licensed review.