Before anything technical
The hard part of a marketplace is not building it — it is solving the chicken-and-egg problem. Buyers will not come without sellers; sellers will not come without buyers. If you do not have a plan for that, the platform will not save you.
Marketplaces are among the most expensive things to build and the most likely to fail for non-technical reasons. This guide covers both — how to build one properly, and what to settle before you spend the money.
Solve supply first
Every successful marketplace solved the cold-start problem somehow. The common approaches:
- Start in one narrow niche or locality Easier to reach critical density in one Bengaluru neighbourhood than across a category nationally.
- Manually recruit the first sellers Sign them personally, onboard them yourself, and accept that this does not scale — it does not need to yet.
- Be the first supplier Some marketplaces begin by selling their own inventory, then open to third parties once buyers arrive.
- Aggregate existing listings Where legally and ethically appropriate, seed with publicly available supply and convert those sellers later.
The most common marketplace failure we see: spending ₹25 lakh on a comprehensive platform, launching, and discovering that acquiring sellers is a full-time business problem nobody had planned for. Validate that you can recruit twenty sellers before you commission the build — a spreadsheet and WhatsApp will prove it cheaply.
The pieces you actually need
| Component | What it covers | Complexity |
|---|---|---|
| Vendor onboarding | Registration, KYC, bank details, approval | Moderate |
| Vendor dashboard | Listings, orders, earnings, payouts | High |
| Catalogue & search | Listings, categories, filters, search | High |
| Cart & checkout | Multi-vendor cart, split orders | Very high |
| Split payments & payouts | Commission, settlement, reconciliation | Very high |
| Order lifecycle | Status per vendor, partial fulfilment | High |
| Ratings & disputes | Reviews, refunds, mediation | Moderate |
| Admin console | Approvals, moderation, reporting | High |
The multi-vendor cart problem
This is where marketplace complexity concentrates, and where naive builds break:
- One cart can contain items from several vendors, each with different shipping and availability.
- One payment must split into multiple vendor settlements plus your commission.
- Each vendor fulfils independently, so one order has several statuses at once.
- A partial cancellation must refund proportionally and adjust commission correctly.
- Returns may involve one vendor while the rest of the order proceeds.
A single-vendor store has one order with one status. A marketplace order is several orders wearing a trench coat, and every screen must handle that honestly.
Payments and payouts in India
- Use gateway split settlement Razorpay Route, Cashfree Easy Split, and equivalents handle vendor sub-accounts and automatic commission deduction. Do not build this manually.
- Collect vendor KYC properly PAN, GST where applicable, and bank verification. Gateways require it and so does your own risk position.
- Decide your payout cycle Weekly is common. Faster attracts vendors; slower protects you against refund exposure.
- Hold funds against returns Settle after the return window, or you will be recovering money from vendors who have already spent it.
- Handle GST correctly Marketplace GST treatment, including TCS obligations for operators, has specific rules — involve a CA before finalising your commission and invoicing model.
Reconciliation is a first-class feature, not an afterthought. You need a report that matches every customer payment against vendor settlements, commissions, refunds, and gateway fees. Marketplaces that skip this discover discrepancies months later that take weeks to unpick.
Trust and quality control
Marketplaces live or die on buyer trust, and one bad vendor damages the whole platform:
- Vendor approval before listings go live, at least initially.
- Listing moderation for prohibited items and misleading claims.
- Verified reviews tied to actual purchases.
- A dispute process with clear rules and a human decision-maker.
- Vendor performance metrics — cancellation rate, dispatch time, ratings — with consequences.
- A clear refund policy that says who pays in each scenario.
What to build first
Marketplace MVPs should be embarrassingly manual:
- Phase one Vendor listings, buyer browsing, single-vendor checkout, manual vendor onboarding, manual payouts. Yes, manual — it proves demand without building settlement infrastructure.
- Phase two Multi-vendor cart, automated split payments, vendor dashboard, ratings.
- Phase three Logistics integration, disputes, analytics, promotions, mobile apps.
Many marketplaces never need phase three. Almost none should start there.
Planning a marketplace and want the scope and payment architecture thought through properly? Tell us about your category and supply plan. See also our e-commerce cost guide and payment gateway guide.