The proposed Article 45(3) suspension is not silently treated as law.
The engine records procedure 2025/0395(COD) as a proposal status and keeps current Article 45(3) logic active until an adopted legal act changes the applicable rule.
EU27 EPR Authorised Representative Appointment Engine
Assess the current PPWR Article 45(3) route, apply destination-country formalities, prepare the Producer and representative data, collect evidence and generate a country-aware appointment preparation pack without presenting a draft as a legally effective appointment.
For the PPWR Chapter VIII EPR role, the Producer appoints a person or entity established in the relevant Member State to fulfil specified extended-producer-responsibility obligations. Article 45(3) currently requires certain cross-border EU Producers to make that appointment by written mandate in each destination Member State other than their Member State of establishment; Member States may also impose the requirement on third-country Producers.
COM(2025) 982 / 2025/0395(COD) proposes suspending Article 45(3) until 2035. A legislative proposal is not applied here as current law unless it is adopted and enters into force.The engine stores structured data in the site's local Public Workspace and evidence files in this browser's IndexedDB. It does not treat generated files as submitted or accepted.
Legal boundary
Article 45(3) concerns the EPR Authorised Representative for Chapter VIII producer-responsibility obligations. Article 17 concerns a manufacturer's separate technical/conformity authorised representative. The principals, tasks and documents are not interchangeable.
The engine records procedure 2025/0395(COD) as a proposal status and keeps current Article 45(3) logic active until an adopted legal act changes the applicable rule.
A generated appointment draft, a signed document, a portal-accepted appointment and a legally effective representation are separate states.
EU27 execution map
This matrix combines current EU-law logic with the national execution/formality status verified for each Member State. A review state is deliberate: it prevents the engine from inventing a national form or legal effect where the primary-source procedure is not yet mapped.
How it works
Identify the Producer, establishment and route to final users before deciding representation.
Separate EU cross-border obligations from third-country national requirements and transitional execution issues.
Keep the Producer and destination-country representative as separate entities with signatory authority.
Use the official form, certification, portal request, acceptance or authority approval required for that Member State.
Store extracts, signatory authority, signed appointment, acceptance and confirmations as hashed browser-local evidence.
Do not advance the lifecycle to legally effective without the evidence required by the applicable route.
Use official forms where controlling; otherwise export a country-aware draft, portal pack or portable preparation record.
Natural questions
Not every sales situation has the same result. Under current PPWR Article 45(3), a Producer covered by Article 3(15)(c) or (d) appoints an EPR Authorised Representative by written mandate in each other Member State where it first makes packaging or packaged products available. Third-country obligations depend on national rules. Producer status and route to the end user must be established first.
Article 3(20) ties the EPR Authorised Representative to establishment in the Member State where the relevant EPR obligations are fulfilled. A legal or service group can operate across countries, but the appointment and national establishment must satisfy each destination-country rule.
No. Some national routes add certification, portal acceptance, register confirmation or authority review. The engine therefore separates signature-ready, signed, accepted, confirmed and legally-effective states.
No. Article 17 is a technical/conformity role appointed by the manufacturer. The Article 45 EPR role concerns Chapter VIII producer-responsibility obligations. The documents and delegated tasks must remain separate.
A Commission proposal, COM(2025) 982 / 2025/0395(COD), proposes suspension. The engine does not treat a proposal as current law before adoption and entry into force.
No. The German route keeps the initial LUCID registration as a personal Producer obligation. The appointment engine marks that registration task as non-delegable and separately tracks the representative's LUCID confirmation.
The producer-register route sends an appointment request to the representative using its Danish CVR. The representative must accept the request; current DPA guidance gives a seven-day acceptance window before the request expires.
Where the competent body publishes a controlling form or official appointment example, that output takes priority over a Beyoğlu draft. Malta and Portugal are examples of routes where the official document layer must be surfaced explicitly.
Structured draft data is stored in the site's browser-local Public Workspace. Evidence files are stored in IndexedDB with SHA-256 hashes. Nothing becomes submitted merely because it is stored or exported.