What marketplaces ask for, and what that proves
Step 1
Establish the position
Step 2
Assemble the evidence
Step 3
Answer the platform request
Step 4
Keep both consistent
| Control | Evidence to retain |
|---|---|
| Scope | Entity, product, channel, stream and source |
| External action | Version, date, authorised filer and issued receipt |
| Maintenance | Source data, approval, invoice and next deadline |
The duty on the platform
Article 45(4) of the PPWR obliges online marketplaces to obtain registration information and a self-certification from sellers.
That is a duty on the platform. It does not replace or discharge the seller duty underneath it.
What we do not publish
Amazon and bol.com each control their own onboarding fields, evidence and acceptance decisions, and their seller pages are behind a login.
We do not publish a platform field name, fee or blocking behaviour without dated primary evidence from the platform itself, so the live seller account remains the reference.
The order of work
Establish the packaging position first, then satisfy the platform request with evidence that matches it.
A number supplied to satisfy a form, without a position behind it, creates a second problem rather than solving the first.
Conclusion
Scope comes before a form. Connect the legal entity, product, sales channel and EPR stream to the rule that actually applies.
Evidence must remain traceable. Keep source data, versions, approvals, filings, receipts and every record issued by an external body.
Third-party decisions are never guaranteed. CONAI, public registers, collective systems and marketplaces control their own procedures, timing and decisions.