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

Four business models - specific decisions

A. Bootstrap with handicrafts, like Artovnia#

Recommended start: only entrepreneurs from the EU, no shipping from outside the EU, no operator fulfillment, no high-risk categories. The seller is the party to the sale, PSP handles payment separation.

What to build first:

  • onboarding of the manufacturer-artisan and their EPR and packaging duties;
  • simple but mandatory GPSR documentation and batch identification;
  • separate gateways for food-contact ceramics, candles, cosmetics, and children's products;
  • manufacturer and warning cards;
  • checkout, withdrawal, complaint, and a fast security channel;
  • proof of terms and conditions and separate marketing consents;
  • export of orders, commissions, and DAC7 data.

Do not allow at the start: cosmetics 'without papers', toys without CE marking, mugs without food-contact proof, dropshipping imports, and claims that 'handicrafts are not subject to GPSR or EPR'.

B. Sports store adding a marketplace#

The most important thing is to separate the two roles. For own goods, the operator is the seller; for partner offers, an intermediary. The customer must see this on the listing, product page, in the cart, on the confirmation, and in the complaint process.

What to build:

  • a "sold by: store" or "sold by: partner" marker in every relevant place;
  • separate sales documents and VAT/commission settlement;
  • routing of complaints and withdrawals according to the seller;
  • category gates for helmets/PPE, electronics, supplements, and children's products;
  • control over favoring own offers in ranking and P2B description;
  • a shared checkout, but separate orders, refunds, and payouts;
  • own EPR obligations for goods/operator, independent of partners.

C. Medium-sized general product marketplace#

Do not launch 'everything' with a single control. The platform creates a category program with owners and risk levels. It automates DSA/DAC7 onboarding, document repository, EPR, moderation, pricing, recalls, and notifications.

Once the threshold is exceeded, readiness for full DSA platform obligations is required. As a medium-sized online platform operator, one must formally check the national NIS2 status and registration deadline. PAD applies unless a micro-enterprise exemption is in place. P2B requires a complaint/mediation system within the scope defined by the regulation.

D. Marketplace 1000 florists, each with its own storefront#

Each florist is a separate seller. The storefront displays their data, delivery terms, and local reach, but the operator maintains consistent minimum rules.

Key functions:

  • onboarding and re-verification of 1000 entities without manual data re-entry;
  • local order routing to the correct florist and a clear contract page;
  • cut-off times, availability, and substitution of flowers confirmed before purchase, not after;
  • proof of photo/description of the arrangement and the scope of permissible changes;
  • information on price, delivery, freshness, and withdrawal – an exception for perishable goods applied only to products actually meeting the criteria;
  • quality complaints and prompt proof of condition upon delivery;
  • EPR and packaging assigned to the florist responsible for packing, or a fulfillment model described in the contract;
  • category of additional gifts separately: alcohol, food, cosmetics, candles, and toys cannot pass the 'flowers' gateway.
Need to implement these processes in a real marketplace?

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

Explore marketplace development