A single EPR number is not enough
A single EPR number is not enough
How we resolved a compliance gap in selling across multiple Amazon EU marketplaces
CLIENT | CHALLENGE | OUTCOME |
|---|---|---|
Ryor | German LUCID assumed to cover EPR in every EU market | Clear CONAI registration path + reusable guide |
Ryor was selling across multiple EU marketplaces with a German LUCID registration already in place — and assumed that covered their environmental compliance obligations everywhere they sold. It didn't.
1 Initial Situation
Ryor held a valid LUCID Packaging Register number, satisfying Germany's Extended Producer Responsibility (EPR) requirements under the German Packaging Act.
But Ryor also sold into Italy — and LUCID only covers the German market. Each EU country runs its own separate EPR scheme, and a registration in one does not carry over to another. Without realizing it, Ryor had a compliance gap on a second, active marketplace.
THE GAP
One EPR registration does not equal EU-wide coverage. A German LUCID number carries no legal weight in Italy — leaving active sales exposed on a marketplace the client didn't realize was uncovered.
2 Chosen Strategy
Rather than simply flagging the gap, we identified the correct path forward: Italy's own EPR system, CONAI, and confirmed that registration there — not an extension of LUCID — was the right fix.
We then went a step further than a one-off answer. Instead of only telling Ryor what to do, we built a short, standalone manual explaining how to register with CONAI — something the client's team could follow directly, and something we could reuse for any future client selling into Italy.
THE APPROACH
Don't just diagnose — equip the client. A reusable CONAI registration manual turns a single fix into repeatable capability for every future EU market.
3 Implementation
1 Confirmed LUCID (Germany) status
Verified Ryor's existing German registration and clarified that it does not extend to Italy.
2 Identified CONAI as the correct scheme
Pinpointed CONAI as the separate registration required for the Italian market.
3 Produced a dedicated CONAI registration guide
Tailored for Ryor and reusable as a general reference for future EPR cases.
4 Result
RESOLVED
Ryor moved from an unnoticed compliance gap in Italy to a clear, actionable registration path — backed by documentation the client's team could act on directly.
Environmental compliance on Amazon EU isn't a single checkbox: each market runs its own EPR system, and staying compliant means knowing which registration applies where — not assuming one covers them all.
DISCLAIMER
This document is a summary case study prepared for illustrative and marketing purposes. Details reflect the case as managed by amabrands.
How we resolved a compliance gap in selling across multiple Amazon EU marketplaces
CLIENT | CHALLENGE | OUTCOME |
|---|---|---|
Ryor | German LUCID assumed to cover EPR in every EU market | Clear CONAI registration path + reusable guide |
Ryor was selling across multiple EU marketplaces with a German LUCID registration already in place — and assumed that covered their environmental compliance obligations everywhere they sold. It didn't.
1 Initial Situation
Ryor held a valid LUCID Packaging Register number, satisfying Germany's Extended Producer Responsibility (EPR) requirements under the German Packaging Act.
But Ryor also sold into Italy — and LUCID only covers the German market. Each EU country runs its own separate EPR scheme, and a registration in one does not carry over to another. Without realizing it, Ryor had a compliance gap on a second, active marketplace.
THE GAP
One EPR registration does not equal EU-wide coverage. A German LUCID number carries no legal weight in Italy — leaving active sales exposed on a marketplace the client didn't realize was uncovered.
2 Chosen Strategy
Rather than simply flagging the gap, we identified the correct path forward: Italy's own EPR system, CONAI, and confirmed that registration there — not an extension of LUCID — was the right fix.
We then went a step further than a one-off answer. Instead of only telling Ryor what to do, we built a short, standalone manual explaining how to register with CONAI — something the client's team could follow directly, and something we could reuse for any future client selling into Italy.
THE APPROACH
Don't just diagnose — equip the client. A reusable CONAI registration manual turns a single fix into repeatable capability for every future EU market.
3 Implementation
1 Confirmed LUCID (Germany) status
Verified Ryor's existing German registration and clarified that it does not extend to Italy.
2 Identified CONAI as the correct scheme
Pinpointed CONAI as the separate registration required for the Italian market.
3 Produced a dedicated CONAI registration guide
Tailored for Ryor and reusable as a general reference for future EPR cases.
4 Result
RESOLVED
Ryor moved from an unnoticed compliance gap in Italy to a clear, actionable registration path — backed by documentation the client's team could act on directly.
Environmental compliance on Amazon EU isn't a single checkbox: each market runs its own EPR system, and staying compliant means knowing which registration applies where — not assuming one covers them all.
DISCLAIMER
This document is a summary case study prepared for illustrative and marketing purposes. Details reflect the case as managed by amabrands.
More case studies
Explore all the projects and get a feel for our work.
More case studies
Explore all the projects and get a feel for our work.


