Guide chapters
§ - Important Disclaimer Regarding the Nature of the Material00 - How to use the guide01 - First choose the business and responsibility model, then build the marketplace02 - Construction plan: what must exist and when03 - Responsibility Matrix: Operator, Seller, and Suppliers04 - Seller Onboarding: Whom to Allow to Sell05 - Product card: information without which an offer cannot be published06 - GPSR: Product Safety in Practice07 - Product Category Gates08 - Packaging and EPR: who is actually responsible09 - Consumer Law: Sale, Withdrawal, and Complaint10 - Prices, Promotions, Ranking, Advertising, and Reviews11 - Payments, Payouts, VAT, and Sales Documents12 - GDPR without myths: what to record, where, and on what basis13 - DSA: reporting, moderation, and seller traceability14 - P2B: fair rules for business users15 - DAC7: seller data and annual reporting16 - E-commerce accessibility from June 28, 202517 - Cybersecurity and NIS218 - Retention: How long to store data and evidence19 - Post-launch operations: calendar and owners20 - Four business models - specific decisions21 - Document and Procedure Package to Prepare22 - GO / NO-GO Checklist Before Launch23 - Most Common Misconceptions24 - Sources and Update Principle

Responsibility Matrix: Operator, Seller, and Suppliers

AreaMarketplace OperatorSellerExternal Supplier
Seller IdentityCollects or obtains only data required for its own obligations from the PSP source, verifies remaining elements, and archives proofProvides true, up-to-date data and documentsPSP performs KYC and may be a data source; the operator does not duplicate it unnecessarily but remains responsible for missing DSA/DAC7 elements
Sales AgreementIndicates the party to the agreement, forwards the order and proofIs a party, carries out delivery, withdrawal, and complaint handlingCourier carries out transport according to its role
Product ComplianceDesigns mandatory fields, checks, reacts, blocks, and cooperatesProvides information and proof; is responsible according to the role of manufacturer/importer/distributorLaboratory or representative may provide proof; does not automatically assume responsibility
Price and PromotionEnsures correct interface, price history, consistency, and markingsSets the correct price and declares promotions according to the rulesPricing tool operates within the limits set by the operator
Personal DataController of its own processes; limits access, fulfills rights, and ensures securitySeparate controller for data needed for its salesProcessor or separate controller according to the actual role
PaymentIntegrates PSP, reconciles refunds and information flowUndergoes PSP onboarding, receives payouts, and bears agreed costsLicensed PSP handles accounts, settlement, payment KYC, and part of fraud
EPR and packagingChecks seller's declaration and EPR registration; responsible for its own goods, imports, or fulfillmentDefines its role and accounts for packaging/products it is responsible forFulfillment must report packaging consumption to the relevant responsible entity
DAC7Determines operator status, collects, verifies, reports, and informsProvides data and updates itPSP may be a source of some data based on the agreement and agreed integration
Moderation and ReportsManages the reporting channel, decisions, justifications, and appeal pathReacts, corrects the offer, provides proofModeration tool supports, but responsibility for the decision remains with the operator
Need to implement these processes in a real marketplace?

I design multi-vendor platforms with onboarding, payments, moderation, and operational workflows.

Explore marketplace development