Insights
Building a Multi-vendor Marketplace MVP
What makes a marketplace MVP different from a store — vendor onboarding, split payments, per-vendor ZATCA, and solving the cold-start problem.
A marketplace looks like a store with more sellers. It isn’t. It’s two products and a money-routing problem, and the thing that kills most marketplaces isn’t technology at all. If you’re considering one, go in knowing where the real difficulty lives.
A marketplace is two products
You serve buyers and sellers, and each needs its own product. Behind the storefront that buyers see sits a whole second application for vendors: onboarding, listing management, order handling, dashboards, and payouts. When you budget a marketplace MVP, you’re budgeting for both — a mistake founders make is scoping only the buyer side.
The hard part: money routing
When a buyer pays, that money can’t just land in your account. It has to split — the seller’s share to the seller, your commission to you — with payouts and settlement per vendor. Holding and distributing other people’s funds is often a regulated activity, which connects straight back to fintech. The rule of thumb: use a payment provider that supports marketplace or split payments; do not hand-roll a system that holds and disburses funds yourself.
Per-vendor compliance
Multiply the compliance work by your vendors. Each seller may need their own ZATCA-compliant invoicing, and you’ll run vendor KYC and onboarding. This is real integration work, not an afterthought — see ZATCA e-invoicing.
The real killer: cold start
Here’s what actually sinks marketplaces: the chicken-and-egg problem. No buyers come without sellers; no sellers stay without buyers. An empty marketplace is a dead one, and no amount of engineering fixes emptiness.
The tactics that work:
- Launch narrow — one category, one city.
- Solve the harder side first — usually supply. Seed vendors by hand.
- Do things that don’t scale — concierge onboarding, manual matching, even faking one side early.
- Prove liquidity in a niche before you spend on breadth. This is idea validation applied to a two-sided market.
Scope the MVP: go embarrassingly narrow
The right marketplace MVP is almost uncomfortably small: one category, one city, a handful of vetted vendors, and manual processes wherever you can get away with them. The single question to answer is: do transactions actually happen? Breadth comes only after the answer is yes. That restraint is the whole point of building an MVP before a full product.
The bottom line
Treat a marketplace as two products plus regulated money movement, lean on a provider for split payments, and — above all — launch narrow enough to beat the cold-start problem. Liquidity in a tiny niche is worth more than a beautiful empty platform.
Thinking about a marketplace? Book a free consultation and we’ll help you scope one that can actually reach liquidity — the way we approach every product.
FAQ
How is a marketplace MVP different from an online store?
A store sells your own products; a marketplace connects many independent sellers to buyers. That adds a whole second product — vendor onboarding, listings, and payouts — plus split payments that route money to each vendor minus your commission, and often per-vendor invoicing. It's meaningfully more complex than a single store.
How do split payments work in a marketplace?
When a buyer pays, the amount is divided between the seller and your commission, then paid out to each vendor. Holding and distributing other people's funds can be a regulated activity, so most marketplaces use a payment provider that supports marketplace or split payments rather than building fund-holding themselves. Plan this early — it shapes the architecture.
How do I solve the chicken-and-egg problem for a new marketplace?
Launch deliberately narrow — one category and one city — and solve the harder side first, usually supply. Seed early vendors manually, and don't be afraid to do things that don't scale, like concierge or manual matching, until you prove transactions happen. Liquidity in a small niche beats emptiness at scale.