Insights
Building a Multi-vendor Marketplace MVP
A marketplace is two products plus a money-routing problem, and what kills most of them isn't technology. Split payments, per-vendor compliance, and cold start.
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. Go in knowing where the real difficulty lives.
Two products, not one
Behind the storefront buyers see sits a whole second application for vendors: onboarding, listing management, order handling, dashboards, payouts. Founders routinely scope and budget only the buyer side, then discover the vendor side mid-build. Price both from the start.
The hard part: routing money
When a buyer pays, the money can’t just land in your account. It has to split, the seller’s share to the seller and your commission to you, with settlement per vendor. And holding or distributing other people’s funds is often a regulated activity, which puts you near fintech territory.
The rule: use a payment provider that supports marketplace or split payments. Don’t hand-roll a system that holds and disburses funds.
Compliance multiplies by vendor
Each seller may need its own ZATCA-compliant invoicing, and you’ll run vendor KYC and onboarding. This is real integration work that scales with your seller count, so it belongs in the plan, not in the surprises.
The real killer: cold start
No buyers without sellers; no sellers without buyers. An empty marketplace is a dead one, and no amount of engineering fixes emptiness.
What works: launch narrow (one category, one city). Solve the harder side first, usually supply, by recruiting vendors by hand. Run concierge and manual operations without shame. And prove liquidity in the niche before spending anything on breadth. It’s the marketplace version of validating before you build.
Scope: embarrassingly narrow
The right marketplace MVP feels uncomfortably small. One category, one city, a handful of vetted vendors, manual processes wherever you can get away with them. It exists to answer one question: do transactions actually happen? Breadth waits for a yes, which is the MVP discipline applied to a two-sided market.
Liquidity in a tiny niche is worth more than a beautiful empty platform. If you’re scoping a marketplace, we’ll help you find the narrow version that can prove itself.
FAQ
How is a marketplace MVP different from an online store?
A store sells your products; a marketplace connects many independent sellers to buyers. That adds a second product for vendors (onboarding, listings, payouts) plus split payments that route money to each seller minus your commission, and often per-vendor invoicing. Budget for all of it, not just the storefront.
How do split payments work in a marketplace?
A buyer pays once; the amount divides between the seller and your commission, then settles out to each vendor. Holding and distributing other people's money can be regulated activity, so most marketplaces use a payment provider with marketplace or split-payment support instead of building fund-holding themselves.
How do I solve the chicken-and-egg problem?
Launch deliberately narrow — one category, one city — and solve the harder side first, usually supply. Seed early vendors by hand, and use manual or concierge operations until transactions actually happen. Liquidity in a small niche beats emptiness at scale.