Marketplace Verification: The Platform Checks Your Packaging Position

The framework makes the marketplace the register's gatekeeper: platforms must verify that sellers offering packaged goods into a member state are registered for EPR there - checking the registration number against the register - and must not simply carry sellers who cannot show the position the law requires. National law in the largest markets built the pattern first (Germany's marketplace checks against LUCID, France's identifier discipline), and the platforms industrialised it: registration numbers collected in seller onboarding, validated against registers where interfaces exist, renewed on cycles, with listings restricted or accounts suspended where the position cannot be shown.

For sellers, verification converts EPR registration from a back-office duty into a trading licence. This guide explains the mechanics and the ladder.

The practical flow: the platform asks, per state of sale the seller activates, for the EPR registration number (or the representative's evidence), validates format and - where register interfaces allow - existence, and records the verification with an expiry or re-check rhythm. Sellers selling packaging-relevant categories feel it first; the questions arrive category by category as platforms extend coverage. The seller's disciplines are clerical and absolute: numbers entered exactly as issued, per state, with the representative's details matching the register's; renewals diarised against the platform's re-check, not the state's; and category scope understood (a seller whose range crosses from non-packaging into packaged goods mid-account meets the check at the listing, not at the annual review).

Platform enforcement ladders from notice to restriction to suspension, on the platform's timetable, with appeals that run on evidence: the register extract, the representative agreement, the scheme confirmation. Sellers should hold the evidence pack per state in the same readiness as the conformity file - the appeal is won by the seller who can produce the register entry in an hour. Two traps recur: the number that belongs to another entity (a distributor's, a former representative's) entered in good faith, which verification reads as no number; and the state activated for digital or exempt goods whose settings quietly extended to packaged lines. Both are configuration errors with suspension consequences, and both are prevented by the onboarding checklist in this station.

Platforms carry the duty because legislatures concluded the register alone could not see the tail - and the duty has a backstop logic the seller guides develop: where the seller cannot be made to comply, framework mechanisms look to the platform and fulfilment chain for the packaging's producer duties in defined cases. Platforms therefore verify conservatively, extend checks beyond the letter where their risk teams advise it, and publish seller requirements that are, in effect, a private restatement of the public law with the platform's margins of safety added. Sellers should read the platform's requirement page for their category as an operative compliance document - because for their account, it is one.

Verification quietly improves the market for the compliant: the free-riding seller's price advantage - the unpaid fees inside a lower price - is exactly what the check removes, and legitimate sellers have begun to say so in their trade associations' consultations. Treat the platform's number field as what it has become: the visible licence of the compliant, priced into the listing. Sellers who register early and display accurately are not bearing a cost their competitors avoid; they are holding an asset their competitors are about to be suspended without.

Verification's direction is expansion: more states' registers connected, more categories in scope, re-checks tightening from annual to event-driven as the interfaces mature. The seller's correct response is architectural rather than reactive - the mirror file, the reconciliation rhythm, the change triggers of the onboarding guide - because a system that keeps the account perpetually verifiable absorbs each widening as a non-event. Build for the check of 2028, not the check of this quarter.