Pay on Behalf pays your EPR fees. It does not register you.

By Jarmo Habakuk · 3 August 2026

✓ Last verified against primary sources: 3 August 2026

If you were automatically enrolled in Amazon’s EPR Pay on Behalf service, the compliance notices on your account probably went quiet, and it felt like the problem had been handled. It had not. Pay on Behalf pays your eco-contributions. It does not obtain your registration number. Those are two separate obligations, and under the PPWR the registration number is the one Amazon is required to check.

Amazon says so directly, on its own Pay on Behalf page:

If you’re a producer, even if you’re enrolled in EPR Pay on Behalf, you have to register in each EU country in which you sell packaging and packaged products and obtain an EPR registration number (ERN).

So the sellers most exposed right now are not the ones who ignored EPR. They are the ones who were enrolled, got quiet accounts for a year, and reasonably concluded they were covered.

Why the enrolment felt like a solution

Under the earlier regime, missing an ERN deadline meant Amazon enrolled you in Pay on Behalf, calculated your eco-contributions, paid the producer responsibility organisations and debited your seller account, plus an annual service fee per category. That is a real service and for a lot of sellers it was a relief — the fees got paid, nobody had to learn what Citeo was, and the notices stopped.

Nothing about that has been withdrawn. Pay on Behalf still does exactly what it always did. What changed is what Amazon has to verify, and the PPWR moved that to the registration itself.

The result is a gap that reads as a contradiction if you are looking at your account: you are paying eco-contributions through Amazon, in full, on time, and Amazon is simultaneously telling you that you are not compliant. Both are true.

What the obligation actually splits into

For packaging in any EU country you sell into, there are two things, and vendor content routinely blurs them:

Germany makes this split unusually easy to see, because the two steps are visibly separate: the LUCID registration is free, and the dual-system participation contract that costs money is a different contract with a different provider. Elsewhere the two arrive bundled from a compliance firm and the distinction disappears into a single invoice — which is why so many sellers cannot say which of the two they have actually bought.

What the notice looks like, and what it does not yet mean

In Account Health under Policy Compliance, an outstanding EPR requirement appears as an open issue naming the country and the stream — for example EPR: France Packaging and Printed Paper — with a date to address it, a count of affected SKUs, and an At-risk sales figure that Amazon calculates for you.

Two details worth knowing before you panic.

Check the Action taken and Account Health Rating Impact columns. While the issue is still a warning rather than an enforcement, both read No impact and the status says your submission is required. Nothing has happened to your listings yet. That is a meaningfully different state from a deactivation, and it is the state most sellers reading a scary banner are actually in.

The At-risk sales figure appears in more than one place, and the numbers are not the same. The priority-actions card on the Account Health landing page can show a much smaller figure than the Policy Compliance issue row, because the card is scoped to a single high-performing listing while the row totals the affected SKUs. If you are budgeting against this, use the issue row.

Submitting the number, if you have one

The submission itself is short, which is worth saying because the compliance industry is not incentivised to. From Account Health, open Policy Compliance, then Submit compliance information. You pick Extended Producer Responsibility (EPR) rather than GPSR, then choose the specific policy from a dropdown — in France that list runs to sixteen entries, one per stream, from France Batteries through France Packaging and Printed Paper to France Sanitary Textiles. Then there is a single field for the number.

There is no document upload and no form to argue your case in. It is a number, and it either validates or it does not.

Note that the streams are separate obligations. A seller who needs Packaging and Printed Paper may also need Textiles, and satisfying one does nothing for the other. Amazon raises a separate issue per stream, and it does not necessarily raise them all at once — so the absence of a notice for a stream is not evidence that you do not owe it.

There is no single EU deadline

This is worth stating plainly, because almost every guide currently running a countdown gets it wrong: 12 August 2026 is not an EU-wide EPR deadline. The dates are set per country and per stream, and in a real account they are months apart.

At the time of writing, a single seller account carries packaging notices with an address-by date of 12 August 2026 for France and 31 December 2026 for both Poland and Sweden — the same obligation, the same product, a gap of 150 days. Amazon’s own France page separately lists quarterly deadlines for WEEE, furniture and toys, semi-annual for sport and leisure goods, and annual for everything else including packaging.

The practical consequence is that “am I ready for the EPR deadline?” is not a question with an answer. You have a list of dates, one per country per stream, and the only authoritative version of that list is the open issues in your own Account Health. Anything you read that gives you one date to plan around, including this article, is a worse source than your own account.

What happens if it does become a deactivation

This is the part that is under-reported, and it is documented by Amazon rather than inferred. Once a listing carries the Listing removed status:

• The listings are non-sellable until the required information is provided.
• Purchase orders are paused and no new inventory is accepted into fulfilment centres. In Send to Amazon you get: “This product is either prohibited, recalled, or requires compliance documentation to fulfill orders for this product in FBA.”
• Existing FBA inventory is deemed unfulfillable.
• If the information is not provided within 30 days of the deactivation email, outstanding purchase orders are cancelled and the inventory is returned to you or disposed of.
• To get it back you must create a removal order yourself within those 30 days — Amazon states explicitly that automatic removals do not apply here — and you are charged for the return. Miss it and the stock is disposed of.

So the exposure is not only the stopped sales that the At-risk figure counts. On a 30-day fuse it is the stock itself, and the default outcome of doing nothing is destruction rather than return.

That is also why the timing of the fix matters more than it looks. Registration is not instant anywhere, so “I’ll deal with it when they actually switch me off” quietly commits you to solving a multi-week problem inside a 30-day window.

Can you fix it in time?

Only one of these you can do yourself, for free, today.

Germany. The LUCID registration is free, self-service and takes about twenty minutes, and paying someone to do it is paying for typing. But the realistic timeline is not the afternoon it is often described as. A new number takes up to 72 hours to appear on the register, and submitting it before it appears gets it marked invalid by default. Amazon then validates it with ZSVR in up to five business days, and recommends checking the result on day six. Then you reinstate the listings — there is no automatic reinstatement, because other compliance checks are run manually. Realistically eight or nine days from a standing start, assuming nothing goes wrong.

Spain, and anywhere else you are not established. Amazon: “If you are not established in Spain, you must appoint an Authorized Representative (AR) established in Spain before registering for any EPR category.” This is the part that is usually described as a queue and is not one. It is a gate, and it has a price.

In practice a compliance firm will offer you two routes: send a company officer to the Spanish consulate to have the authorising documents signed and legalised, or pay the firm a one-off fee — in a recent case, €300 — to have their attorney act as your representative and complete that first step for you. Neither is a four-month queue. What they are is a dependency you cannot start the registration without, and the reason nothing else can proceed until it is done.

Amazon has also begun brokering this directly: on the open EPR issue there is a Do you need help getting an ERN? option in the sidebar that routes you to selected providers for both the number and the representative.

The traps, all documented

These are Amazon’s own stated failure modes rather than folklore:

• Do not resubmit a number that already shows as valid. Amazon: this counts as a resubmission, resets the validation process, and “will cause your listings to become inactive.” The most expensive mistake on the list, and it is made by people trying to be diligent.
• Do not submit a German number within 72 hours of registering. It will not be on the register yet and will be marked invalid.
• Match the entity, not just the number. Validation looks for a match on VAT number, tax or business registration number, legal business name and sometimes business address — and Amazon checks these against your storefront’s Detailed Seller Information. A registration in a slightly different legal name fails.
• Company names only. You cannot register under a personal name.
• Format is exact. A LUCID number is DE in capitals followed by 13 digits, no space. Wrong format is rejected by default, before anyone looks at it.
• Fix unrelated listing errors first. Amazon notes that existing listing issues prevent reactivation even when the compliance requirement has been met.

If a submission is rejected, Amazon gives one of six reasons: number not found, number expired, invalid producer name, invalid tax or VAT ID, invalid producer name and tax/VAT ID, or invalid product type. Four of those six are entity mismatches rather than anything wrong with the number itself.

Where this stands right now

As of 3 August 2026, live seller accounts carry an open Policy Compliance issue for EPR: France Packaging and Printed Paper with an address-by date of 12 August 2026, currently showing No impact and awaiting submission — while the packaging notices for Poland and Sweden on the same account are dated 31 December 2026.

What is genuinely unclear is what happens on that date, and the honest answer is that Amazon’s own surfaces do not agree. The France requirements help page still describes the consequence of missing an ERN deadline as automatic enrolment in Pay on Behalf. The priority action in Account Health describes the same deadline in terms of listings at risk. Those are different outcomes, and the help documentation appears to lag the notices.

Treat anyone telling you confidently which one it will be as guessing. We will update this section after the 12th with what actually happened.

What to do this week

1. Find out which streams you owe, per country, and do not assume the open issues are the complete list.
2. Check whether you already hold numbers through a brand owner, importer or an earlier registration that were never entered in Seller Central. This costs five minutes and occasionally ends the whole problem.
3. Register Germany yourself, now, if it is on your list. It is free and the clock starts at 72 hours.
4. Start the representative step for any country you are not established in, because nothing else can begin until it finishes.
5. Do not resubmit anything that already shows valid.