Authorised Representative software: what an AR agency actually needs

An Authorised Representative (AR) is the legal point of contact an EU market places on a non-EU manufacturer. Whether the obligation flows from Extended Producer Responsibility (EPR) schemes, the General Product Safety Regulation (GPSR), or product-specific rules for electricals and batteries, the pattern is the same: a manufacturer outside the Union appoints a representative inside it, and that representative becomes accountable to the authorities for a defined set of duties.

For the agencies that provide this service, the work is deceptively administrative. There is no single filing to get right; there is a rolling calendar of registrations, quantity declarations, fee payments and document retention obligations, multiplied across every client and every country. The agencies that struggle are rarely short of expertise — they are short of a system that keeps that expertise from living in one person's inbox.

The obligations you are actually managing

Before evaluating any tool, it helps to be precise about what an AR mandate contains. Most agencies are juggling some combination of:

• Registrations — enrolling each producer in the relevant national register (Germany's LUCID, France's system via CITEO, Poland's BDO, the UK's packaging EPR, and their equivalents) and keeping those registrations current.
• Quantity declarations — periodic reporting of tonnages or units placed on the market, at frequencies that differ by country and by material stream.
• Fee and contribution management — calculating, tracking and evidencing eco-contributions, which several registers tie directly to the declared quantities.
• Document retention — holding certificates, receipts and technical files for statutory periods, which for GPSR technical documentation can run to ten years.
• Being reachable — acting as the named contact for market surveillance authorities, which means being able to produce evidence on demand.

Any tool you consider should map cleanly onto this list. If it cannot represent a payment obligation as distinct from a filing obligation, or cannot express a country's specific reporting frequency, it will quietly push that complexity back onto a spreadsheet — which is exactly the failure you are trying to design away.

The three ways agencies lose control

Across the mid-market — agencies of roughly five to fifty people — the same three failure modes recur.

Deadline drift

When filing dates live in a shared spreadsheet, ownership blurs. A missed LUCID or CITEO deadline lands on the agency, not the client, and the reputational cost is high precisely because the service exists to prevent it. Software earns its place here by turning every obligation into a dated, owned item with escalating reminders — the traffic-light compliance calendar that clients already recognise from the larger networks.

Chasing data

Quarterly quantity data arrives late, in the wrong format, from the wrong person. The remedy is not a stricter email; it is a client portal that collects the data for you: a request becomes a magic link, the client uploads into a branded portal, and the submission lands as a review task rather than an inbox attachment to be transcribed by hand.

Key-person risk

The most dangerous spreadsheet is the one only one person understands. When the individual who knows how each client files is a single resignation away from taking the operation with them, the agency is carrying an unpriced risk. A shared system of record — clients, obligations, filings, documents and an append-only audit trail in one place — turns that tacit knowledge into something any team member can pick up.

Features that matter, and features that don't

Vendors compete on long feature lists. In practice, a short set of capabilities does most of the work: an obligation engine that derives duties from each client's countries and product flows; a calendar with genuine multi-tier reminders; a versioned document vault with expiry tracking; and submission-ready export that produces filings in each register's own structure with plausibility checks before anything leaves the building.

Two capabilities are easy to overlook and disproportionately valuable to an agency. The first is white-labelling: the ability to put your own brand and domain on the client-facing portal, so clients experience your agency rather than a third-party vendor. The second is a credible answer to the data-sovereignty question — EU data residency, a clean subprocessor register, and ideally the option to self-host on your own infrastructure.

A useful test when evaluating tools: ask the vendor to model one of your real clients — their countries, their flows — and show you the resulting obligation matrix and calendar. If the demo can only show generic screenshots, the obligation engine underneath may be thinner than the marketing suggests.

What this means for a growing agency

The agencies that scale past a few dozen clients without adding headcount linearly are the ones that stop treating each client as a bespoke folder of tasks and start treating compliance as a system. The right software makes that transition cheap. Complywerk is built specifically for AR and EPR agencies of five to fifty people, and prices per managed client rather than per seat — so bringing your whole team into one source of truth never costs you more.

If you are weighing up a move off spreadsheets, the product overview walks through the obligation engine end to end, and the pricing page sets out what per-client billing looks like across three tiers.