Multi-Vendor Platform: Development from MVP to Scaling
A single error in payment splitting can send thousands of dollars to the wrong vendor. We've seen it happen on platforms with over 10,000 sellers and 250,000 products. For instance, on a project with 15,000 sellers and 500,000 products, we encountered N+1 queries when loading the cart. Our solution — materialized views and Redis cache — cut load time by 60% compared to a naive approach, which is 3 times faster. Our experience shows that getting the architecture right from the start saves up to 40% of the budget on later refinements. Financial losses from poor architecture can reach several million rubles.
Marketplace development: Why multi-vendor platforms are harder than single-vendor shops
Unlike a regular online store, a marketplace manages multiple parties: buyer, seller, and platform. This creates three critical issues: payment splitting, review verification, and dispute resolution. Each requires separate design and often external integrations. Typical marketplace commission ranges from 10% to 20% depending on product category. Key metrics: LCP < 2.5s, conversion rate > 3%.
Payment splitting
The buyer pays a single amount, which is automatically divided between the seller and the platform. Stripe Connect is the standard for Western markets. It offers three schemes: Direct (seller sees the customer), Destination (funds go through the platform), and Separate charges + transfers (maximum flexibility for multi-vendor cart). In the CIS, YooKassa with its split API or CloudPayments via agency scheme are used.
View Stripe Transfer Example
import stripe stripe.Transfer.create( amount=8500, # in cents currency="usd", destination="acct_1BuAYuBnMOckkSJp", # seller's connected account transfer_group="ORDER_95", ) Source: Stripe Connect Transfers documentation
Verified reviews and ratings
A review must be verified: only a buyer who actually received the product can leave a review. The trigger is a change in order status to delivered or completed plus N days. The seller can respond to reviews. Seller rating is computed using a sliding average, often with a recency weight (90-day cutoff, weight of recent reviews 0.4). Unverified reviews are filtered out to prevent manipulation.
Dispute resolution
A dispute is an entity that arises when there is a conflict: the buyer opens a dispute, the seller responds, and an operator makes a decision. Timeouts: the seller must respond within 3 days, the operator decides within 5 business days. The payment system executes the decision (refund or transfer). In our practice, 85% of disputes are resolved without operator escalation thanks to automatic rules: if the dispute amount is less than $50, the system refunds the buyer without operator involvement.
How to choose the tech stack for a marketplace
Stack choice depends on scale and performance requirements. For an MVP, Laravel + PostgreSQL + Meilisearch (product search) is sufficient. For a platform with millions of products, Django + PostgreSQL + Elasticsearch is better (Elasticsearch is up to 3x faster for complex full-text search). On the frontend, Next.js provides good SEO and fast TTFB. Queues and cache: Redis. Redis cache is 100x faster than disk-based storage for frequent queries, making it ideal for high-traffic marketplaces. File storage: S3-compatible (Cloudflare R2, MinIO).
| Component | Options |
|---|---|
| Backend API | Laravel, Django, Node.js/Nest.js |
| Frontend | Next.js, Nuxt.js |
| Database | PostgreSQL |
| Search | Elasticsearch, Meilisearch |
| Queues | Redis + Bull/BullMQ, RabbitMQ |
| Payments | Stripe Connect, YooKassa |
| File storage | S3-compatible (Cloudflare R2, MinIO) |
| Cache | Redis |
Comparison of payment approaches for multi-vendor marketplaces
| Criteria | Stripe Connect | YooKassa |
|---|---|---|
| Geography | International | CIS |
| Integration complexity | Medium | Low |
| Splitting flexibility | High (3 schemes) | Medium (agency scheme) |
| Multi-vendor cart support | Yes (Separate charges) | Limited |
| Commission | 2.9% + 30¢ | 2.99% + 35₽ |
Stripe Connect is more convenient for international projects and complex splitting schemes. YooKassa is simpler to integrate in the CIS and connects faster. Contact us for a consultation on selecting the right payment system for your project.
How we build a marketplace
Our team has 7+ years of experience in developing complex platforms, with 15+ marketplaces launched. Our engineers hold certifications in Stripe and AWS. The process includes:
- Analysis — gathering requirements, selecting the stack, prototyping payments.
- Design — database architecture, splitting schemes, role model.
- Implementation — API, admin panel, cart, payment, search, reviews, disputes.
- Testing — load testing, dispute simulation, security audit.
- Deployment — cloud deployment, CI/CD setup, monitoring.
What's included
- API documentation in Swagger
- Source code in a repository
- Access to admin panels
- Operation manual
- Administrator training (up to 2 hours)
- Technical support for one month after launch
Development timelines
MVP (seller registration, product catalog, cart, payment with splitting, personal accounts, admin panel) — 3–5 months. Full-featured platform with reviews, disputes, analytics, mobile apps — 6–12 months.
If you are planning to launch a marketplace, contact us for a preliminary estimate. Order an architecture audit of your marketplace and get a free optimization plan. Our architecture audit can save you up to $20,000 in avoidable costs.