EPR compliance software for agencies: building a multi-client operation

Extended Producer Responsibility has quietly become one of the most operationally demanding areas of product compliance. Packaging, electricals (WEEE), batteries and, increasingly, textiles each carry their own registration and reporting obligations, and each EU member state implements them slightly differently. For an agency serving dozens or hundreds of producers across several countries, the combinatorial explosion is the whole problem.

Most agencies begin the same way: a spreadsheet per client, a shared mailbox, and a set of personal logins to national portals. This works until it doesn't — usually somewhere between the twentieth and fortieth client, when the number of moving parts outgrows the number of people who can hold them in their heads. EPR compliance software exists to carry that load, but only if it is built around how an agency actually works.

Multi-tenancy is the foundation, not a feature

The single most important architectural choice is multi-tenancy: one workspace in which every client's data is strictly isolated from every other's, enforced on every query rather than by convention. This is what lets you add a client in minutes, give a specialist access to only the accounts they handle, and answer an auditor's question about one producer without exposing another.

Agencies that adopt a tool designed for a single company — and then try to run all their clients inside it — inevitably rebuild isolation by hand, with naming conventions and folders. That is fragile, and it is the kind of fragility that surfaces at the worst possible moment. A purpose-built multi-tenant system removes the question entirely.

Standardise the obligations, automate the calendar

The leverage in an EPR operation comes from separating two things that spreadsheets tangle together: the rules of each country's regime, and the specific situation of each client. A well-designed obligation engine encodes the regime once — Germany's packaging rules, the UK's semi-annual packaging EPR returns, Poland's BDO reporting — and then resolves each client's countries and material flows into the exact obligations they carry.

The payoff is that the calendar maintains itself. When a rule's deadline changes, every affected client's schedule, reminders and export update at once, with no manual editing. This is the difference between software that stores your knowledge and software that applies it. It is worth confirming in any evaluation that changing a single rule genuinely propagates — ask to see it.

• Encode each country's regime once, version it, and keep it current as rules change.
• Derive per-client obligations automatically from countries and product flows.
• Let the calendar and reminders flow from the obligations, not from hand-maintained lists.
• Keep a tamper-evident audit trail so every filing and change is evidenced.

Where a white-label portal changes the relationship

The larger compliance networks learned long ago that a branded client portal is not a vanity feature — it is the mechanism that turns data collection from a chase into a workflow. When a client logs into a portal carrying your agency's brand, uploads their quarterly figures there, and sees their own status, two things happen: the data arrives in a structured, reviewable form, and the client experiences your agency as a modern software-enabled service rather than a mailbox.

For a mid-market agency, white-labelling that portal is also a competitive equaliser. It lets a fifteen-person agency present the same polished client experience as a network many times its size, without building and maintaining the software itself. That is often the single feature that moves an agency from evaluating to buying.

The data-sovereignty conversation

European buyers — German producers especially — will ask where their data lives, and increasingly they ask early. A credible EPR tool needs a clean answer: data stored and processed within the EU, a public subprocessor register, and a GDPR Article 28 data processing agreement ready for procurement. For the most demanding clients, the ability to self-host the system on your own infrastructure — with no subprocessors and no data leaving your environment — closes the conversation entirely.

A practical migration tip: don't try to move every client at once. Start with the handful whose renewals or filings are furthest away, get your team fluent in the system on those, then move the rest ahead of their next deadlines. A good vendor will run this migration with you rather than handing you an import template and wishing you luck.

Pricing that rewards consolidation

Finally, watch the pricing model. Per-seat pricing quietly penalises the behaviour you want — getting your whole team into one system — by charging you more for each person you onboard. Per-client pricing aligns the cost of the tool with the revenue it supports. Complywerk prices by managed client, not by seat, so a growing team never becomes a reason to keep people out of the system of record.

The product page shows the obligation engine and coverage across ten EU markets plus the UK; the pricing page lays out the three tiers and the per-client model in detail.