BEYOĞLU PROFESSIONAL PPWR-EPR COMPLIANCE SERVICES
Free Workspace Check My EU Scope
PPWR-EPR  ·  Marketplaces  ·  Other Marketplaces
PPWR applies · marketplace verification varies by platform and Member State

Packaging EPR on Other EU Marketplaces.

Selling through a marketplace that is not Amazon, Etsy or eBay does not remove the PPWR Producer obligation. The platform may have a mature EPR portal, a country-specific registration field, a contractual self-certification, or no dedicated public EPR interface at all. The correct sequence does not change: determine the Producer, determine the destination Member State, establish the national compliance record, then provide the marketplace with the evidence it is legally entitled to verify.

Check My Marketplace Scope → Check Producer Status Build Evidence Pack

Article 45 scope

Not every website is automatically an Article 45 marketplace.

PPWR Article 45(4) refers specifically to online-platform providers falling within Section 4 of Chapter III of the Digital Services Act that enable consumers to conclude distance contracts with Producers.

Direct answer

When does the PPWR marketplace verification layer apply?

A platform must first fall within the relevant Digital Services Act online-platform framework and allow consumers to conclude distance contracts with Producers offering packaging or packaged products.

Where Article 45(4) applies, the platform must obtain the Producer's registration information and registration number for the Member State where the consumer is located, together with the Producer's EPR self-certification.

It must then make best efforts to determine whether the supplied information is complete and reliable.

TEST 01

Is this an online platform under the DSA?

A platform is generally a hosting service that stores and disseminates information provided by recipients of the service, subject to the DSA definition and exclusions.

TEST 02

Can the consumer conclude the sale through it?

Article 45(4) targets platforms that allow consumers to conclude distance contracts with Producers.

TEST 03

Does DSA Section 4 apply to the platform provider?

DSA Article 29 excludes qualifying micro and small platform providers from Section 4, subject to the rule's exceptions, including designated very large online platforms.

TEST 04

Is the seller the packaging Producer?

The marketplace requirement concerns Producers. Do not certify Producer status until the actual transaction has been analysed.

TEST 05

Which Member State is relevant?

For marketplace verification, Article 45 expressly looks to the Member State where the consumer is located.

TEST 06

What if Article 45(4) does not apply to the platform?

The platform-specific verification duty may differ. The Producer's underlying national EPR obligation does not disappear.

A marketplace's legal scope and your Producer scope are separate questions.

Even where a small platform provider falls outside DSA Section 4, or where a selling service does not fit the Article 45 marketplace model, you can still be the packaging Producer making packaged goods available for the first time in the destination Member State.

Your own online sales channel requires its own analysis.

Do not automatically copy the Amazon/eBay marketplace verification workflow onto a merchant's own webstore, hosted storefront or checkout service. First determine whether the service provider itself falls within the relevant DSA platform category. The seller's underlying Producer duties remain independently assessable.

No EPR field?

Use the national legal record as the source of truth.

Smaller, newly launched or less mature marketplaces may not yet expose a dedicated packaging-EPR portal. The absence of a marketplace interface is not a legal safe harbour.

01

Determine the Producer.

Manufacturer, importer, distributor, seller, dropshipper and fulfilment partner are not interchangeable legal conclusions.

02

Map every active consumer destination.

Use the final Member State served through the marketplace, not merely the marketplace's corporate country or the seller's warehouse location.

03

Complete the national Producer registration.

Use the authority, register, PRO or legally recognised national route actually applicable in that Member State.

04

Establish EPR fulfilment.

Complete PRO/system participation, EPR AR appointment, reporting and regulatory-funding arrangements where required.

05

Search the marketplace account for a compliance channel.

Check legal information, business information, seller verification, EPR, sustainability, environmental compliance and regulatory settings.

06

If no dedicated field exists, contact marketplace compliance support.

Ask where packaging registration information and EPR self-certification should be supplied for the relevant Member State.

07

Preserve the response.

Keep the marketplace ticket, email, help-centre instruction or seller-account screenshot with the national evidence file.

08

Control countries the platform can serve.

If a destination is not compliance-ready, disable it where the marketplace provides shipping, offer or country-availability controls.

09

Monitor the platform for later PPWR implementation.

A marketplace can add a registration-number field, automated register check or new certification requirement after your national compliance file is already active.

Never manufacture a marketplace registration number.

If a country has no standardised public number format, use the identifier genuinely assigned by the competent authority, national register, PRO or legally recognised system. Do not convert a contract number, VAT number, company number or another country's EPR number into a fictional “PPWR number”.

Article 44 is still in transition.

The Commission published draft harmonised registration/reporting rules on 6 August 2026. The document remains a draft under stakeholder feedback at this regulatory review. Existing national registration systems therefore remain operationally relevant until the legally applicable transition is completed.

Verified implementation examples

The same PPWR rule can produce very different marketplace interfaces.

These examples are included to show the operating difference between marketplace implementations. They are not a substitute for the national Producer analysis.

Platform Current public implementation Packaging evidence examples Platform control Beyoğlu interpretation
Kaufland Global Marketplace DETAILED COUNTRY IMPLEMENTATION

Kaufland published a dedicated PPWR seller guide in June 2026 and maintains country-specific EPR onboarding rules. 		Current seller-registration materials include, among others:

Germany: LUCID.
Poland: BDO.
France: packaging registration evidence.
Spain: packaging registration evidence.
Austria: current compliance confirmation differs from markets requiring direct number upload. 		Marketplace/channel-specific EPR fields and seller compliance conditions. Do not assume one Kaufland marketplace country's workflow applies to another. The platform itself acknowledges transitional differences in registers and number formats.
Allegro PPWR WORKFLOW LIVE

Allegro announced its PPWR packaging-number workflow in April 2026 and redesigned its Legal obligations area in July 2026. 		Country-specific EPR number plus a platform packaging-compliance declaration. Germany example: LUCID. Poland: BDO. Allegro states that sales can be restricted where a valid EPR number required for the destination country has not been supplied. Buyers may be unable to see an offer or complete checkout. Strong example of destination-country enforcement being built directly into marketplace visibility and checkout.
Marketplace without verified public PPWR documentation VERIFY DIRECTLY

No dedicated public workflow confirmed from the platform's official seller documentation at the time of the seller's review. 		National Producer registration, system evidence, AR evidence and self-certification should still be kept ready. Platform may later request documentation, add an account field or apply country restrictions. Use the fallback protocol. Never interpret interface silence as legal exemption.
Platform terminology is not statutory terminology.

A marketplace may label its checkbox “declaration”, “certificate”, “compliance declaration” or “PPWR confirmation”. Do not automatically treat that interface statement as the formal PPWR Article 39 EU Declaration of Conformity. The Article 39 technical-conformity document and Article 45 EPR self-certification belong to different legal layers.

Compare Compliance Documents → Open EU27 Country Guides

Marketplace perimeter control

A new destination can create a new compliance file.

Cross-border marketplace programmes frequently expand seller availability. Compliance geography should be reconciled with commercial geography before the first shipment.

SELLING COUNTRY

Which Member States can currently order?

Review marketplace-level destination settings, not only the seller's preferred target countries.

FINAL DESTINATION

Do not stop at the logistics hub.

A fulfilment centre, consolidation warehouse or cross-border hub is not necessarily the consumer destination relevant to marketplace verification.

AUTO-EXPANSION

Check default international programmes.

Marketplace automation can make offers available to destinations the seller did not manually configure one by one.

COUNTRY EXCLUSION

Use restrictions deliberately.

Where the marketplace permits it, close destinations whose national compliance file is not yet operational.

REOPENING

Market activation is a controlled change.

Register, configure, evidence and test the country before switching sales back on.

MULTI-MARKETPLACE

Country totals belong to the Producer.

The national declaration may need quantities from several marketplaces and direct channels, not merely one seller portal.

Check My Countries → EU Market Entry Checklist

Marketplace Pay on Behalf

A marketplace can pay certain EPR costs for you. That does not make it your entire EPR operator.

PPWR Article 45 expressly permits a marketplace, on the basis of a written mandate, to meet the financial-contribution obligations in Article 45(2) on behalf of a Producer.

A marketplace mandate can cover

Article 45(2) financial contributions.

  • Covered regulatory contributions under the marketplace service
  • Calculation of marketplace sales where the service provides it
  • Remittance of covered regulatory money
  • Supporting reporting to the extent expressly included
  • Marketplace-specific evidence generated by the service
Do not assume it covers

The complete Producer legal architecture.

  • Producer determination
  • All national registrations
  • EPR Authorised Representative
  • Non-marketplace sales
  • All packaging streams
  • All reporting periods
  • Technical PPWR conformity
Read the written mandate.

A marketplace service marketed as “EPR service”, “Pay on Behalf” or “compliance service” should be assessed according to the actual contractual scope. Do not infer a transfer of statutory responsibility that the mandate does not contain.

EPR AR remains a separate question.

The Article 45(3) EPR Authorised Representative architecture remains part of the Regulation in force at this review date. A Commission proposal to suspend aspects of that mechanism remains in an ongoing legislative procedure and is not treated here as adopted law. Marketplace UI should never be used as the legal test for whether an AR is required.

Marketplace evidence file

Build evidence that survives a marketplace migration.

The compliance file should still make sense if the seller stops using the current marketplace tomorrow.

01 Producer assessment

Legal reasoning for the seller's Producer status.

02 Registration

National Producer number and official/public record.

03 AR / PRO

Representation mandate and EPR-system evidence.

04 Reports & payment

Recurring fulfilment after registration.

05 Marketplace record

Submission, certification, approval, support ticket or restriction evidence.

Marketplace approval is not authority approval.

A green tick, accepted number or unrestricted listing proves only what the marketplace's verification process actually checked. It does not establish that every report, contribution, AR obligation, PRO relationship or national rule has been fulfilled.

Verification and restriction

Platform enforcement and statutory enforcement are not the same thing.

Event Legal / operating layer Possible consequence Correct response
Missing marketplace EPR number Marketplace verification Warning, blocked onboarding, hidden offer, checkout restriction or request for evidence, depending on platform. Establish the underlying national record before correcting the marketplace account.
Information appears inaccurate DSA / marketplace trader-information layer Platform can require correction and applicable DSA rules provide for suspension where required information is not corrected. Correct the source data and maintain matching legal-entity information.
Producer unregistered nationally National packaging EPR Country-specific statutory consequences, sales restrictions, penalties or other enforcement. Use the relevant country page and primary national source.
Marketplace accepts number but PRO/reporting absent Underlying EPR file Marketplace may remain operational while statutory compliance is incomplete. Complete the national reporting/payment/system layer.
One marketplace blocks a country, another does not Platform implementation difference Different commercial visibility. Do not interpret the more permissive platform as the legal authority.

GDPR-by-design

Packaging reporting does not require a copy of the customer's private life.

Transaction automation should process only the information required to determine the compliance event and maintain legally necessary evidence.

Standard packaging ledger

Data that can be operationally relevant

  • Marketplace / channel identifier
  • External order or shipment ID
  • Transaction / shipment date
  • Final destination Member State
  • SKU and quantity
  • Parcel count
  • Packaging-profile version
  • Fulfilment route
  • Paid / cancelled / shipped / returned status
Not standard EPR ledger data

Personal data we should not retain without a reason

  • Buyer name
  • Personal email address
  • Telephone number
  • Marketplace message content
  • Payment-card credentials
  • Bank-account credentials
  • Marketing-profile information
  • Unnecessary full delivery-address history
Beyoğlu standard: minimise before retention.

The standard packaging-EPR ledger is designed around transaction identifiers, destination, SKU, packaging and fulfilment status. It is not designed to require buyer names, private communications or payment credentials for ordinary packaging-EPR calculation.

Full personal-data rules depend on the actual integration.

Where a marketplace connector, structured import or customer system exposes personal data, controller/processor roles, purposes, lawful basis, access controls, retention, deletion and international-transfer safeguards must be documented for that production setup. This page does not invent a universal GDPR lawful basis for every customer integration.

Beyoğlu marketplace-neutral architecture

The compliance engine should survive a change of marketplace.

Producer, country, packaging and regulatory records belong to the business. Amazon, Etsy, eBay, Kaufland, Allegro or another marketplace is merely a transaction source and an evidence-verification endpoint.

01

Map every sales channel.

Marketplace, own store, B2B orders, distributors, fulfilment providers and dropshipping routes.

02

Determine Producer status by route.

A conclusion reached for one transaction is not blindly copied to every marketplace.

03

Establish the EU country perimeter.

Compare actual destination availability against the countries in which the compliance file is ready to operate.

04

Activate national compliance files.

Registration, PRO/system, EPR AR, tariffs, reporting, payment and evidence.

05

Build one packaging master.

SKU, component, material, unit weight and version are maintained once and mapped into country rules.

06

Normalise marketplace orders.

Different marketplace schemas are converted into one controlled compliance-event model.

07

Calculate one Producer-level country position.

Quantities from different marketplaces can be aggregated where they belong to the same Producer and national reporting perimeter.

08

Generate marketplace-specific evidence.

The same legal source record can feed different platform registration fields, self-certifications and evidence packs.

Build My Marketplace Map → Discuss Managed Marketplace EPR

Integration-neutral automation

Different APIs. One compliance event model.

We do not require every marketplace to expose the same API. The integration layer accepts the best authorised data route actually available.

NATIVE API

Approved marketplace connector

Where an authorised production API exposes the required order and fulfilment fields, events can be ingested directly.

WEBHOOK

Event-driven ingestion

Paid, shipped, cancelled or returned events can update the ledger without unnecessary polling where supported.

CSV / XLSX

Structured marketplace export

A marketplace without a suitable API can still feed the ledger through controlled structured files.

ERP / OMS

Central commerce source

If the customer's ERP, OMS or marketplace aggregator already consolidates transactions, the compliance layer can operate from that controlled source.

EXCEPTION

Unknown route stops automation.

New country, new legal seller, missing packaging data or uncertain Producer status should be escalated rather than silently declared.

MARKETPLACE EPR FIELD

We automate only authorised interfaces.

A marketplace regulatory field is not screen-scraped merely because the platform has not published an authorised API for it.

Connector transparency

A marketplace connector is described as live only when the relevant production integration, permissions and data access are actually configured. If a bespoke connector or mapping layer is required, its implementation scope is agreed separately. This page does not invent a universal connector fee.

Beyoğlu pricing

The marketplace changes. The pricing architecture does not.

Professional service fees remain separate from authority, PRO, system and other regulatory money.

Country activation
€25 + applicable VAT

Once per newly activated country. Opens and configures the relevant country compliance file.

Declared parcel
€1 + applicable VAT

Per parcel entering the relevant declaration ledger. Marketplace brand does not alter the standard parcel fee.

Regulatory EPR
At cost

Actual authority, PRO, EPR system, levy, tax, deposit and legally required third-party amounts remain separately identified.

Multi-marketplace service-fee example

Beyoğlu service subtotal
€525

€125 country activation + €400 parcel fees · plus applicable VAT.

Regulatory EPR and other country-specific charges are excluded.

One parcel is not multiplied by the number of marketplaces.

The €1 professional fee follows the declared parcel entering the compliance ledger. The fact that your business uses several marketplaces does not itself create several parcel fees for the same declared parcel.

Full Pricing → Estimate Regulatory Cost

Other marketplaces FAQ

What to do when the platform has not written the compliance manual for you.

Does PPWR Article 45 apply to every marketplace or website?

No. Article 45(4) refers to providers of online platforms falling within Section 4 of Chapter III of the Digital Services Act that allow consumers to conclude distance contracts with Producers. DSA Article 29 contains a micro/small-enterprise exclusion subject to its exceptions. The seller's underlying Producer and national EPR duties, however, remain a separate question.

What must an Article 45 marketplace obtain from a packaging Producer?

The platform must obtain information on the Producer's registration in the Member State where the consumer is located, including the registration number, together with a self-certification confirming compliance with the applicable extended producer responsibility requirements.

Does the marketplace have to verify my registration number?

Article 45 requires the online-platform provider to make best efforts to assess whether the information received is complete and reliable. Member States may also provide automated reconciliation with the national Producer register.

My marketplace has no EPR field. Do I still have to register?

Potentially yes. Marketplace interface availability is not the legal Producer test. Determine your national EPR obligation first. If registration is required, complete it and retain the evidence, then ask the marketplace how the information should be supplied.

Can the marketplace pay my EPR fees for me?

PPWR Article 45 permits the financial obligations in Article 45(2) to be met by the online-platform provider on behalf of the Producer where there is a written mandate. The exact marketplace service scope must be read from the mandate.

Does marketplace Pay on Behalf remove my need for an EPR Authorised Representative?

Not automatically. Financial-payment administration and statutory EPR representation are different legal functions. The EPR AR requirement must be assessed under the applicable PPWR and Member-State route.

Does one marketplace registration number cover the whole EU?

No. Producer registration is organised by Member State. A seller operating across several EU destinations can therefore require several national registration records.

What should I do before adding a new EU destination to a marketplace?

Confirm the Producer, determine whether registration is required, complete the national system and AR route where applicable, build the packaging data, establish reporting/payment and preserve evidence. Then activate the marketplace destination.

Is marketplace approval proof that I am fully EPR compliant?

No. Marketplace approval proves only the status of the marketplace's verification process. National registration, PRO/system participation, authorised representation, reporting, regulatory payment and evidence retention remain separately assessable.

Can Kaufland or Allegro have different EPR requirements for different countries?

Yes. Current Kaufland materials use different EPR evidence mechanisms across its national marketplace channels. Allegro also uses destination-country EPR numbers and can restrict sales where required information is missing. Always use the current marketplace and national source for the specific Member State.

Do I have to send buyer personal data to Beyoğlu for packaging EPR reporting?

The standard packaging-EPR ledger is designed around order or shipment identifiers, destination Member State, SKU, quantity, parcel count, packaging profile and fulfilment status. Buyer names, private messages, payment credentials and other unnecessary personal data are not standard packaging-ledger requirements.

Can Beyoğlu work with a marketplace that has no native connector?

Yes where an appropriate authorised data route exists. Depending on the production setup, structured marketplace exports, an ERP/OMS feed, a marketplace aggregator or another approved integration can provide the transaction data. A bespoke connector is not represented as live until it is actually implemented.

Source record

Law first. Marketplace interface second.

Regulatory review: 31 August 2026. Marketplace implementation review: 31 August 2026.

EU LAW Regulation (EU) 2025/40

Producer definition, Article 44 registers and Article 45 marketplace/EPR framework.

EU LAW Digital Services Act

Section 4, Article 29 scope exclusion, Article 30 trader traceability and Article 31 compliance by design.

COMMISSION GUIDANCE C/2026/3084

Commission PPWR guidance published 10 June 2026.

EUROPEAN COMMISSION PPWR FAQ

Commission FAQ published 3 August 2026.

ARTICLE 44 TRANSITION Draft Producer Register Implementing Regulation

Ares(2026)7688068. Published for stakeholder feedback on 6 August 2026. Draft — not treated as final law.

LEGISLATIVE PROPOSAL COM(2025) 982

Proposal concerning suspension of EPR AR appointment rules. Legislative procedure remains ongoing at this review date.

KAUFLAND PPWR Seller Guidance

Current marketplace-country packaging registration architecture and transition information.

KAUFLAND Seller Registration / EPR Requirements

Current EPR upload requirements by Kaufland national sales channel.

ALLEGRO PPWR EPR Registration Numbers

April 2026 packaging-number and compliance-declaration workflow.

ALLEGRO EPR Information for Sellers

Country-specific EPR numbers, verification and potential sales limitations.

BEYOĞLU EU27 Official Sources Directory

National authorities, Producer registers, PROs and recognised systems.

BEYOĞLU PPWR-EPR Knowledge Hub

Producer, EPR AR, PRO, documents, costs and cross-border operating explanations.

Marketplaces change. The underlying Producer record should not.

Build one defensible EU compliance system, then connect every marketplace to it.

Start with your legal seller, Producer status, active EU destinations, packaging data and fulfilment routes. Beyoğlu can convert those facts into country operating files, registrations, EPR-system relationships, representation, declarations, payments and marketplace evidence.

Build My EU Marketplace Scope → All Marketplace Guides Work With Beyoğlu