Fulfilment providers and the PPWR: the Article 45(7)-(8) suspension duty

Most PPWR commentary talks to marketplaces. But the Packaging and Packaging Waste Regulation hands fulfilment service providers (FSPs) their own obtain-assess-suspend duty, and it is arguably harder to operate: an FSP's clients are bound by contract and physically present in its warehouses, so "swiftly suspend" is not a button, it is an offboarding. If you run fulfilment, 3PL or warehousing services for sellers reaching EU consumers, Article 45(7) and 45(8) are your paragraphs. Here is what they say and what an operable compliance process looks like.

Article 45(7): what your clients must hand you

At the moment of concluding the fulfilment contract, producers must provide the FSP with the same package a marketplace collects: information on their registration in the producer register of each relevant member state, the registration number or numbers, and a self-certification that they only offer packaging complying with the EPR requirements of Article 45(1) and (3). The regulation is explicit on one point that matters for liability allocation: producers are responsible for the accuracy of the information they provide, as itemised in EUROPEN's compilation of PPWR obligations. Accuracy is the producer's problem; assessment is yours.

Article 45(8): assess, demand remedy, then suspend

Upon receiving that information, the FSP must make best efforts to assess whether it is reliable and complete. Where the FSP has reason to believe an item is inaccurate, incomplete or outdated, it must request that the producer remedy it. And if the producer fails to correct the information, the FSP must swiftly suspend its services to that producer for offers to EU consumers, stating the reasons. That is a three-stage machine: assessment, remediation request, suspension. Each stage produces a decision a regulator can later second-guess, which is why each stage needs a record.

Separately, Article 20 of the PPWR imposes packaging-handling care duties on fulfilment providers, per ecosistant's PPWR guide for e-commerce, so the registration duty is not the only PPWR surface an FSP carries. Both apply from 12 August 2026.

Germany got there four years earlier

None of this should feel exotic to an FSP with German operations. Since 1 July 2022, German law has prohibited the distribution of packaged goods from producers not registered in LUCID, and that prohibition binds fulfilment providers as well as marketplaces, per GvW's briefing on the German Packaging Act. A German warehouse shipping a client's goods while that client's LUCID registration is missing or revoked has been a compliance failure for years. The PPWR takes that model EU-wide and adds the explicit suspension duty.

Why best efforts points at the registers

The best-efforts standard in 45(8) mirrors the platform standard in 45(4)-(6) set out in the marketplace-side Article 45 explainer, and both inherit their meaning from the verify-before-onboarding discipline the DSA's trader-traceability rules normalised, as the US ITA's EU regulatory briefing describes in the adjacent GPSR context. Meanwhile, PPWR Article 44(13) requires every national producer register to be publicly accessible, free of charge and machine readable, per DIHK's PPWR guidance. When the authoritative source is public, free and machine readable, best efforts that stop short of checking it are difficult to defend. The reference standard of care for an FSP is therefore concrete: check the registers a client's obligations map to, record what they showed, re-check on a schedule, and be able to show the trail.

An operable process, stage by stage

The duty resolves into four stages, each of which should leave a record a regulator could later inspect:

At contract signature

Collect registration numbers per member state and stream, plus the self-certification. Validate formats immediately; a malformed number is a remediation case on day one.

Before first shipment

Verify each number against the relevant national register (existence, holder match, active status) and store the point-in-time result. This is the record that proves your assessment happened before services began.

Continuously

Re-check the portfolio. Registrations lapse and get revoked, and a client compliant at signature can be a liability by spring. Register update rhythms support this: LUCID updates daily, stiftung ear daily via an automated interface, and ADEME's IDU dataset daily (see the EU producer register map).

On failure

Issue the remediation request, date it, and if the client does not fix the gap, suspend with stated reasons, keeping the whole sequence in the file. Under 45(8) the suspension is not optional once remediation fails.

EPR Clear turns the Article 45(8) sequence into an API: verification at contract signature, continuous monitoring with revocation alerts, and a timestamped evidence log covering assessment, remediation and suspension. You can run a free exposure scan across your client book, or read the marketplace-side Article 45 explainer for the full platform picture.

FAQ

Run the verification workflow as a service

Registration checks per seller, stream and member state, continuous revocation monitoring, and a timestamped evidence log that is your best-efforts record.