ENATIV Logo
ENATIV
Back
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl
  1. Knowledge hub
  2. ›
  3. E-commerce
  4. ›
  5. Multi-vendor marketplace

Multi-vendor marketplace

One site with many sellers: commissions, order splitting and payouts as decisions to make before launch.

E-commerceUsing since 2025

Category
E-commerce
Using since
2025

In practice

A multi-vendor marketplace is one site where many independent sellers sell their goods and you usually earn on commission. It differs from an ordinary store in that the cart splits into per-seller orders and the money has to be settled and paid out. Before the first seller joins, settle the commission and who answers for complaints.

What is Multi-vendor marketplace?

In a multi-vendor marketplace one site offers the goods of many independent sellers. In one payment model, Stripe Connect for example, the customer pays the marketplace, which pays the sellers and keeps a commission. An ordinary store has one catalogue owner and one order per cart. Here each of those is a separate decision.

Four decisions come back in every project: who runs the catalogue, how you calculate the commission, how you split payment and payouts, and how you admit and moderate sellers. In the starter model the marketplace is also the merchant of record: it is legally responsible for the goods and covers the negative balances of its sellers. Count that burden before launch.

How I approach the marketplace model

I start a marketplace with the rules and choose technology afterwards. An engine implements only the rules someone has written down, so I begin by writing them. I open with three questions, in this order.

  1. Who sells and on what terms

    I write down who can open a seller account, who approves an offer and what happens when a seller breaks the rules. The scope of the seller panel and of moderation follows from that.

  2. How the money moves

    I settle who answers to the customer, how the commission is calculated and when a seller is paid out. Then I pick the payment provider, usually Stripe with Connect, which covers seller onboarding and payouts.

  3. What to build it on

    Last, I choose the technical base: a ready-made marketplace module, such as Mercur on Medusa.js, or custom modules on an open engine. I keep commission and payout data in a relational database, PostgreSQL for example, because those numbers must be reproducible. The front end is Next.js.

When it fits, and when it doesn't

A marketplace adds obligations towards sellers, so I count whether that model really pays off for you.

A good fit when

  • The goods come from independent sellers who run their own offers.
  • You earn on commission from sales, not on the margin of your own stock.
  • A cart with goods from several sellers should reach them as separate orders.
  • Data about sellers, offers and payouts should stay with you.

Not a fit when

  • You mainly sell your own goods and only now and then add third-party ones.
  • You have no sellers yet and no plan to find them.
  • Nobody will moderate offers and support sellers after launch.

If you sell your own goods, an ordinary store is enough, on Shopify for example. I write about the split into front end and engine in the headless commerce entry.

Frequently asked questions

In a store with suppliers you are the seller and the suppliers stay in the background. In a marketplace the sellers are visible, run their own offers and get paid out, while you set the rules and take a commission. The difference lies in who answers for the offer and whom you pay. Technically it means separate accounts, separate orders and separate settlements.
The customer keeps one cart, but a placed order splits into one order per seller. In Medusa.js a workflow creates an order for each vendor, and Mercur has a ready-made order group module for it. That way each seller sees and fulfils only their own part.
This is my opinion, not a rule. A hosted platform gives a faster start, but the commission rules and the seller data stay with the provider. An engine, such as Medusa.js with Mercur, gives control over the rules and the data, and in return somebody has to run it. I choose an engine when the marketplace rules are specific and a platform when the model is standard.
The commission rules and payout dates, because sellers ask about them straight away. Then who answers for complaints and returns, and the criteria for admitting and removing sellers. Without them the seller panel and moderation get built by feel, and changing the rules later touches every seller at once.

On this page

  • In practice
  • What is Multi-vendor marketplace?
  • How I approach the marketplace model
  • When it fits, and when it doesn't
  • Frequently asked questions

Related topics

  • Multi-vendor marketplace
  • Medusa.js
  • Stripe
  • Headless commerce
  • Next.js
  • PostgreSQL

Related services

  • E-CommerceHeadless Shopify, Medusa.js, and custom storefronts with Stripe.

Describe the rules of your marketplace

A marketplace usually starts with a conversation about rules, not technology. Tell me who is to sell on your site and how you plan to earn, and I will point out what a ready-made engine can carry. I describe the scope of a store in my [[service:ecommerce|e-commerce]] offer.

Describe your project