BEYOĞLU PROFESSIONAL PPWR-EPR COMPLIANCE SERVICES
Free Workspace Check My EU Scope
PPWR-EPR  ·  Marketplaces  ·  Amazon
PPWR applies · Amazon packaging-EPR rollout active

Amazon Packaging EPR after PPWR.

Amazon can ask for your packaging EPR registration number, verify it against a national register and restrict offers when required compliance information is missing. But Amazon is only the marketplace verification layer. Your real obligation still begins with the Producer, the destination Member State and the national EPR system.

Check My Amazon EU Scope → Open Amazon Checklist Prepare Evidence Pack

The legal architecture

Amazon verifies a country compliance record. It does not create that record.

Article 45 places marketplace obligations on top of the Producer's underlying EPR duties. Keep those two layers separate and Amazon becomes much easier to manage.

Direct answer

What does Amazon actually need from a packaging-EPR seller?

Under the PPWR marketplace framework, Amazon must obtain relevant Producer registration information, the registration number for the Member State where the consumer is located, and a Producer self-certification concerning EPR compliance. Amazon must also make reasonable verification efforts.

That does not turn Amazon into the Producer's national register, PRO, system operator or EPR Authorised Representative. Registration, system participation, reporting, payment and representation remain separate legal layers.

COUNTRY

The customer destination matters.

Do not use only the Amazon storefront or inventory-storage country to determine packaging-EPR scope. Cross-border and non-store destination countries can matter.

PRODUCER

The correct legal entity needs the correct number.

Do not upload a supplier's registration number simply because obtaining your own number would be inconvenient. First determine whether you are genuinely non-Producer for that destination-country transaction.

AMAZON

“Approved” is a marketplace status.

It indicates that Amazon accepted or validated the submitted compliance information. It does not prove that every report was filed, every contribution paid or every AR obligation fulfilled.

Important transition point: there is still no single new EU27 Amazon EPR number.

PPWR Article 44 creates a future harmonised national-register architecture, but the Commission's Article 44 registration/reporting format act remains a draft as of this regulatory review. Amazon therefore continues to work with the currently recognised country-specific registration identifiers and national systems. Do not wait for a fictional “EU PPWR number”.

Current Article 45 law and later legislative proposals must not be mixed.

The page applies the law in force on 30 August 2026. A pending EU legislative proposal may change parts of the Article 45 representation architecture, but a proposal is not treated as adopted law until the legislative process is complete.

Amazon EU packaging status

Legal obligation and Seller Central availability are two different statuses.

Amazon's public PPWR material currently gives specific packaging registration resources for nine countries and operates Austria through a separate EPR route. Additional Seller Central country submissions are still being activated.

Country Current national reference used by Amazon Amazon operational status Pay on Behalf / special route Beyoğlu note
Germany
DE 		LUCID / ZSVR registration number ESTABLISHED

Mature Amazon verification workflow. 		Current Amazon PPWR materials direct sellers to independent compliance rather than packaging Pay on Behalf. Registration alone is not enough: system participation + volume reporting also matter. Foreign direct sellers without a German branch have a new AR requirement from 12 August 2026.
France
FR 		National EPR registration / identifier used for the packaging stream ESTABLISHED

Long-standing Amazon EPR verification route. 		Amazon Pay on Behalf available for eligible packaging operations, but ERN is still required under the PPWR workflow. Amazon evidence does not replace PRO participation, reports, eco-contributions or other national duties.
Spain
ES 		MITECO Producer registration identifier ESTABLISHED Amazon Pay on Behalf can cover eligible reporting/payment activity; registration number remains necessary. Non-Spanish sellers may have a representation route under the applicable Spanish packaging framework.
Belgium
BE 		Amazon directs sellers to Fost Plus for household packaging and Valipac for professional packaging. PPWR EXPANSION Amazon's current public rollout material directs sellers to independent compliance. Household and professional packaging routes must not be collapsed into one generic “Belgium EPR number”.
Italy
IT 		Current PRO / CONAI-related national route TRANSITION Amazon has published Pay on Behalf material for Italy, while the new national packaging-register workflow is still evolving. Verify the seller's live Account Health / POB status. Do not assume one old Amazon Italy workflow remains unchanged throughout the PPWR transition.
Netherlands
NL 		Verpact PPWR EXPANSION Amazon currently directs sellers to self-managed compliance. Amazon has reported verification issues where some lower-volume Verpact registrations are not publicly visible. A failed Amazon check does not automatically mean the underlying registration is invalid.
Ireland
IE 		Repak / applicable national packaging route PPWR EXPANSION Current Amazon material directs sellers to self-managed compliance. Check the actual Irish Producer/system route before treating an Amazon request as the whole obligation.
Poland
PL 		BDO PPWR EXPANSION Current Amazon material directs sellers to self-managed compliance. BDO registration, packaging-EPR fulfilment and marketplace proof are separate operational layers.
Sweden
SE 		Naturvårdsverket plus applicable PRO/system relationship PPWR EXPANSION Current Amazon material directs sellers to self-managed compliance. Amazon's own recent Seller Forum guidance confirms Swedish ERN submission is already appearing in Account Health for affected sellers.
Austria
AT 		Austrian packaging registration / VKS workflow SEPARATE AMAZON ROUTE Amazon currently operates a dedicated registration + Pay on Behalf route through ERP Austria for eligible sellers. Austria is unusual: Amazon's current service can include registration and an external authorised-representative arrangement. Read the current service terms before enrolling.
What about Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, Greece, Hungary, Latvia, Lithuania, Luxembourg, Malta, Portugal, Romania, Slovakia and Slovenia?

Do not read the absence of a visible Amazon submission field as an exemption from packaging EPR. Amazon states that distinct country-specific registration can be required for EU Member States where packaged goods are sold to customers, including non-store cross-border destinations, while Seller Central activation for additional locations is still ongoing. First resolve the country's legal obligation. Then retain the registration evidence until Amazon activates or requests the corresponding verification route.

Open EU27 Country Guides → Compare EU27 Check My Countries

Seller Central workflow

Obtain the number first. Submit it only when the underlying record is ready to verify.

Amazon has moved EPR submission into Account Health / Regulatory Compliance. The exact screen can vary by account and country, and some country fields appear only after Amazon activates verification.

01

Determine whether your legal entity is the Producer for that destination.

Do this before using a supplier ERN or registering unnecessarily. Amazon account ownership alone does not answer the PPWR Producer question.

02

Complete the underlying national registration.

Obtain the registration identifier recognised for the relevant country and packaging stream. Where a public register exists, wait until the record is actually visible before expecting automated marketplace validation.

03

Open the relevant Seller Central country context.

Amazon's interface is country-sensitive. Select the relevant marketplace / country where available rather than assuming one submission updates every European account.

04

Go to Account Health → Regulatory Compliance.

Current Amazon guidance routes EPR submissions through Product Policy Compliance / Regulatory Compliance and the “Submit compliance information” function.

05

Select or search the Packaging EPR requirement.

Enter the exact country-specific registration identifier. Do not alter spacing, entity name or identifier format simply to make it resemble another country's number.

06

Use the “non-producer” route only where it is factually correct.

Amazon's current PPWR help expressly provides a supplier-ERN / non-producer workflow in several markets. It is not a general permission to borrow an upstream registration number.

07

Submit and monitor the verification result.

Amazon currently advises that public-registry checks can take several working days. A newly issued number may also require time to propagate into a public register.

08

Keep the evidence after Amazon says “Approved”.

The ERN, PRO/system relationship, AR mandate where applicable, reports, payments and supporting evidence remain relevant after marketplace verification.

No Seller Central field visible?

Amazon's current operational guidance says the submission option can appear only in countries for which Amazon has activated compliance verification. If you already hold a valid national registration but no field is visible, keep the evidence. Do not conclude that the destination-country legal obligation disappeared.

What each record proves

One Amazon green check cannot replace the evidence file.

Build evidence according to the legal fact it proves. Do not call every document a “certificate”.

01 Registration / ERN

Proves the Producer registration record accepted for that country.

02 PRO / system evidence

Proves the relationship through which applicable EPR duties are fulfilled.

03 EPR AR mandate

Proves representation where the national legal route requires it.

04 Reports & payments

Proves recurring fulfilment after registration.

05 Amazon approval

Proves only the marketplace verification status of the submitted information.

Do not upload an EU Declaration of Conformity as a substitute for packaging EPR registration.

The PPWR EU Declaration of Conformity belongs to the Manufacturer's technical-conformity chain. Packaging EPR registration belongs to the Producer / Chapter VIII chain. Amazon may separately request product or conformity evidence, but one document does not replace the other merely because both concern packaging.

Build Marketplace Evidence Pack → Understand Compliance Documents

Amazon rejection clinic

Fix the source record before repeatedly resubmitting the same number.

Amazon status / symptom Likely issue What to check What not to do
Number not found Registry publication delay, wrong identifier, wrong country, or non-public registration. Confirm the number in the competent national source. If newly issued, allow registry propagation before resubmission. Do not create alternative formatting or submit another entity's number.
Producer name mismatch Amazon legal entity and register legal entity differ. Compare exact legal name, company identifier, VAT/tax data where relevant, and account master data. Do not “fix” the register record by inventing a trading name unless the authority allows it.
Expired / invalid Registration, membership or underlying record is no longer valid. Renew or correct the underlying national status first. Do not treat an old Amazon approval screenshot as current legal evidence.
No country field visible Amazon verification portal not yet active for that country/account. Keep national compliance current and monitor Regulatory Compliance. Do not infer “Amazon does not ask” = “law does not apply”.
Pay on Behalf active but warning remains PPWR now requires the ERN even where POB handles reporting/payment. Obtain the relevant registration number and submit it when required. Do not assume POB substitutes for registration.
Supplier ERN rejected Supplier is not the correct Producer, country route does not support that evidence, or seller marked non-producer incorrectly. Re-run Producer determination for the actual destination transaction. Do not use supplier evidence solely to avoid your own registration.
Approved but listing still restricted Separate compliance requirement, propagation delay, ASIN/account issue or additional regulatory evidence. Review full Account Health and Product Policy Compliance, not only the ERN submission result. Do not assume every restriction is packaging EPR.

FBA, FBM and Pan-European FBA

Fulfilment changes packaging. It does not automatically change the Producer.

Separate the seller's product packaging, the seller-added shipment packaging and Amazon-added FBA transport packaging. Then determine the Producer and country obligation.

Amazon model What the seller must analyse Packaging point Amazon verification
FBA Seller / brand / importer Producer position, destination-country registration, AR where applicable, product packaging volumes. Amazon's current PPWR guidance keeps the seller responsible for product packaging that reaches the fulfilment centre. Amazon states that it handles EPR for transport packaging it later adds to fulfil the FBA order. Yes. FBA does not exempt the seller from Amazon's EPR verification.
FBM Producer status plus all packaging the seller or its fulfilment provider introduces. Seller-filled shipment packaging can become part of the seller's reportable packaging responsibility. Yes. Amazon expressly applies packaging-EPR verification to both FBA and merchant-fulfilled sellers.
Pan-European FBA Consumer destinations, not merely the Amazon store or warehouse location. Inventory placement and VAT geography are not the same legal test as packaging-EPR Producer geography. Amazon says a destination such as the Netherlands can require its own ERN even where the sale reaches the consumer through the Pan-EU network.
Cross-border non-store order Destination Member State. An Austrian, Danish or Luxembourg customer can matter even without a dedicated local Amazon storefront relationship. Amazon says compliance portal activation for additional non-store destinations is ongoing.
Germany deserves a separate check before excluding any FBA packaging volume.

Amazon's current general PPWR help says Amazon handles the EPR for transport packaging that Amazon itself adds during FBA fulfilment. Germany historically had Amazon-specific secondary-packaging reporting practices under the previous regime. For German declarations, use the current reporting-period Amazon data together with the current LUCID/system rules rather than relying on an old pre-PPWR assumption.

Pan-EU is changing again on 3 September 2026.

Amazon has announced that all Pan-EU FBA products, including existing products, must have an active Netherlands offer from 3 September 2026. Belgium becomes an additional required offer from 26 February 2027. These are Amazon programme requirements; they do not replace the separate packaging-EPR analysis.

Producer before ERN

Should you upload your own number or an upstream supplier's number?

You are the Producer

Use your own destination-country compliance record.

  • Complete the required national Producer registration.
  • Establish PRO/system participation where applicable.
  • Appoint the required EPR AR where the legal route requires one.
  • Report packaging and pay regulatory contributions.
  • Submit your own correct registration identifier to Amazon.
You are genuinely not the Producer

Supplier evidence can be relevant — but only if the legal chain supports it.

  • Identify the actual upstream Producer for that Member State.
  • Confirm that its registration covers the packaging and transaction.
  • Obtain the correct national identifier and supporting evidence.
  • Use Amazon's non-producer field only where the country workflow provides it.
  • Keep the supplier declaration in the marketplace evidence file.
Run Producer Status Checker → Read Producer Guide Dropshipping?

Amazon EPR Pay on Behalf

Useful payment administration. Not a replacement for Producer registration.

PPWR changed the practical importance of the ERN: Amazon now says all sellers must obtain and provide the required registration number even where eligible Pay on Behalf is used.

What Pay on Behalf can do

Reporting and eco-contribution administration for eligible Amazon sales.

  • Calculate relevant Amazon marketplace sales data.
  • Submit eligible EPR reporting through the supported scheme.
  • Pay eco-contributions on the seller's behalf.
  • Debit the seller for the regulatory amount and applicable service charge.
  • Reduce manual reporting for the Amazon sales stream it covers.
What it does not automatically do

It does not make the rest of the EPR architecture disappear.

  • It does not remove the PPWR ERN requirement.
  • It does not decide correctly who the Producer is.
  • It does not automatically cover non-Amazon sales channels.
  • It does not universally provide statutory EPR AR services.
  • It does not prove every national obligation is complete.
Multi-channel seller? This is where marketplace-only compliance becomes dangerous.

If you sell the same packaged product through Amazon, Shopify, your own website, Etsy, wholesale orders or another marketplace, the national Producer declaration may need the total reportable quantity introduced by the Producer — not merely the quantity Amazon processed through POB. Maintain one country packaging ledger across all relevant channels.

Italy is currently a moving Amazon workflow.

Amazon has published Italy Pay on Behalf material, while the Italian packaging-register transition and Amazon implementation continue to evolve. Use the live Seller Central compliance status for the seller account rather than relying on an old screenshot or an earlier service-provider description.

Austria is different.

Amazon's current Austria service is broader than ordinary POB: eligible sellers can use a registration workflow involving ERP Austria GmbH, including registration and authorised-representative support. That special country service should not be extrapolated to the rest of the EU.

Beyoğlu managed Amazon workflow

Do not manage Amazon EPR as a folder of unrelated registration numbers.

We structure the work around the Producer, destination country, packaging master, declaration ledger and evidence file. Amazon becomes one verification endpoint inside that system.

01

Map the seller entity and Amazon operating model.

Legal seller, establishment, Amazon stores, FBA/FBM/Pan-EU, private-label position, supplier route and other sales channels.

02

Determine Producer status country by country.

We do not copy the German Producer conclusion into France, Spain or another destination without checking the actual transaction.

03

Activate only the Member States that require an operating file.

Each activated country receives its registration, system, AR, reporting, payment and evidence configuration.

04

Build one versioned packaging master.

SKU → packaging component → material → unit weight → effective date. The same factual packaging data can then map into different national reporting formats.

05

Route Amazon transactions into the correct country ledger.

Destination Member State, parcel, SKU and quantity drive the compliance event. Pan-EU inventory geography is not used as a shortcut for Producer scope.

06

Accrue regulatory exposure separately from Beyoğlu fees.

Authority / PRO / system contributions remain regulatory money. They are not mixed into our €1 declared-parcel fee.

07

Prepare the Amazon verification pack.

Registration identifier, underlying registration evidence, PRO/system evidence, EPR AR mandate where relevant, legal-name matching and supplier declaration where genuinely non-producer.

08

Continue after Amazon says “Approved”.

Recurring declaration, regulatory payment, evidence retention, renewal and country changes continue after marketplace verification.

Build My Amazon Compliance Map → Discuss Managed Amazon EPR

Data & automation

Amazon data should enter the compliance ledger once, not be retyped into 27 spreadsheets.

The data layer is designed around order/shipment events, country routing and packaging profiles. Integration method depends on the customer's production setup.

IMPORT

Amazon reports and structured files

Existing Amazon order, shipment and EPR-related exports can be normalised into the compliance ledger without manually rebuilding each order.

API

Commerce-event ingestion

Beyoğlu's managed integration layer can accept normalised order and shipment events from the customer's commerce stack where the production connector is enabled.

PACKAGING MASTER

SKU data is reused; legal conclusions are not.

One packaging master can feed several countries, while national material mapping, tariff treatment and reporting logic remain country-specific.

ROUTING

Destination creates the country event.

Germany-bound parcels enter Germany. France-bound parcels enter France. A non-store destination is not discarded merely because it has no dedicated storefront.

EXCEPTION ENGINE

Compliance-changing transactions stop ordinary automation.

New country, new packaging, supplier change, unusual fulfilment route or missing Producer status can be routed for review instead of silently producing a wrong declaration.

EVIDENCE

Submission status becomes evidence, not the legal conclusion.

Amazon approval, rejection, national registration, reporting and payment evidence remain separately identifiable.

Public technical disclosure

This page does not claim that a universal native Amazon SP-API connector is active for every Beyoğlu customer today. Managed integrations are enabled according to the customer's production setup. Where direct connector access is not activated, structured Amazon exports can be used as the transaction source. We disclose an integration as live only when it is actually configured.

Beyoğlu pricing

Amazon does not create a separate hidden pricing model.

The standard Beyoğlu service structure remains country activation + declared parcel. Regulatory money is additional and separately identified.

Country activation
€25 + applicable VAT

Once per newly activated country. Non-refundable after the country compliance file is opened and configuration work begins.

Declared parcel
€1 + applicable VAT

Per parcel entering the relevant declaration ledger. Multiple SKUs in one declared parcel do not create multiple Beyoğlu parcel fees.

Regulatory EPR
At cost

Authority, PRO, system, levy, tax, deposit or legally required third-party amounts remain separate from Beyoğlu Professional revenue.

Amazon seller service-fee example

Beyoğlu service subtotal
€350

€100 country activation + €250 parcel fees · plus applicable VAT.

Regulatory EPR contributions and any applicable authority / PRO / system / third-party costs are excluded.

Already activated a country?

The €25 activation fee is not charged again simply because another Amazon reporting period begins. The recurring Beyoğlu operating component is the declared-parcel fee, while actual regulatory charges follow the applicable country system.

Full Pricing → Estimate Regulatory Cost

Guide vs checklist

This page tells you what the Amazon system means. The checklist tells you what to do next.

Keep the legal explanation and the execution sequence separate. That way a workflow change does not require rewriting the entire regulatory analysis.

Amazon operating guide

Understand the system.

  • Producer vs non-producer logic
  • Amazon country rollout status
  • FBA / FBM / Pan-EU implications
  • Pay on Behalf limits
  • Evidence and rejection logic
Amazon EPR checklist

Execute the work in order.

  • Confirm seller and destinations
  • Determine Producer
  • Complete national registration
  • Prepare Amazon evidence
  • Track approval and ongoing duties
Open Amazon Checklist →

Amazon packaging EPR FAQ

Questions that actually change the Seller Central workflow.

Do I need one EPR number for Amazon Europe or one number per country?

Packaging EPR is country-specific. Amazon's current PPWR guidance states that sellers can need a distinct registration number for each Member State where packaged products are sold to customers. There is no single Amazon EU packaging-EPR number.

I already submitted a valid German, French or Spanish packaging number before PPWR. Do I submit it again?

Amazon's published PPWR guidance states that, as of March 2026, existing valid packaging ERNs such as LUCID and existing Spain/France numbers did not need to be resubmitted. Amazon also warns that this can change as implementation develops. The underlying national registration must remain valid and current.

I use Amazon EPR Pay on Behalf. Do I still need an ERN?

Yes under Amazon's current PPWR workflow. Amazon states that all sellers must obtain and provide the relevant packaging EPR registration number even when Pay on Behalf is used for eligible reporting and eco-contribution payments.

Does FBA remove my packaging-EPR responsibility?

No. Amazon's current PPWR guidance keeps the seller responsible for the product packaging that reaches the Amazon fulfilment centre. Amazon states that it handles EPR for transport packaging it adds during FBA fulfilment. Country-specific reporting treatment should still be checked for the relevant reporting period.

Does packaging EPR apply to FBM sellers?

Yes. Amazon states that it must confirm packaging-EPR compliance for sellers regardless of whether the order is FBA or merchant fulfilled. FBM can additionally make seller-added shipment packaging relevant to the seller's packaging ledger.

I do not have an Amazon storefront in a country. Can that country still matter?

Yes. Amazon's current guidance expressly addresses cross-border sales into EU non-store countries. The destination of the packaged goods can create an EPR obligation even where Amazon has not yet activated a dedicated Seller Central submission field.

Can I submit my supplier's EPR number instead of registering?

Only where you are genuinely not the Producer and the relevant national/Amazon workflow permits upstream evidence. Amazon's current PPWR help provides a non-producer route for several countries. It is not a universal exemption for resellers or dropshippers.

Amazon approved my ERN. Am I fully compliant?

Not necessarily. Amazon approval concerns the marketplace verification layer. National PRO/system participation, EPR AR requirements, reporting, regulatory payment, renewals and evidence retention remain separate obligations.

I am outside the EU and sell directly to German consumers. Can Beyoğlu handle everything including LUCID registration?

Germany now requires qualifying foreign direct sellers without a German branch to appoint an authorised representative. However, current German rules expressly keep LUCID Producer registration as the Producer's personal duty. A representative can assume the other EPR duties within its lawful mandate, but cannot replace the Producer for that personal registration act.

Can Beyoğlu manage Amazon sales together with Shopify, Etsy and my own website?

Yes, that is the intended operating architecture. The country compliance ledger should aggregate all reportable transactions attributable to the Producer rather than treating Amazon as the whole business. Integration method depends on the customer's enabled data connectors and available structured imports.

Source record

Marketplace policy changes faster than the underlying Regulation.

This page therefore carries two dates: regulatory review and Amazon operational review. Both were completed on 30 August 2026.

EU LAW Regulation (EU) 2025/40

Articles 44–47, including Producer registration, Article 45 marketplace verification and EPR representation.

EU COMMISSION PPWR application notice · August 2026

Confirms general application from 12 August 2026.

EU TRANSITION Draft Article 44 implementing regulation · Ares(2026)7688068

Draft harmonised registration/reporting format. Not treated as final law on this page.

AMAZON New EU Packaging and Packaging Waste Regulation · G22AA5MS5P7TLNYM

Current Amazon packaging EPR help: ERNs, country resources, Seller Central submission, FBA/FBM, non-store countries and POB.

AMAZON OPERATIONS Account Health / Regulatory Compliance guidance

Current submission path and confirmation that country verification fields are being activated progressively.

AMAZON PROGRAMME Pan-European FBA updates · August 2026

Netherlands offer requirement from 3 September 2026 and Belgium requirement from 26 February 2027.

GERMANY PRIMARY ZSVR / LUCID current PPWR guidance

Registration, system participation, reporting and foreign-Producer AR rules after 12 August 2026.

BEYOĞLU EU27 Official Sources Directory

Country authorities, registers and recognised EPR systems used for national verification.

Open Official Sources Directory → Knowledge Hub
Amazon is one sales channel. Your EPR obligation is larger than the marketplace.

Build the country compliance record first. Then give Amazon the evidence it is entitled to verify.

Start with the legal seller, Producer status, Amazon destinations and fulfilment model. We will turn those facts into the countries, registrations, system relationships, reporting work and evidence your business actually needs.

Build My Amazon EU Scope → Amazon Checklist Work With Beyoğlu