Multi-Vendor Marketplace: Commissions, KYB, Multi-Currency

A customer adds items from three vendors to the cart. The system must process payment as a single transaction, split the order into sub-orders in real time, calculate commissions for each seller, and notify the warehouses. Our marketplace architecture uses event-driven design to avoid deadlocks. We specialize in multi-vendor marketplace development with order splitting into sub-orders, flexible commission management, KYB vendor verification, and multi-currency support. With over 5 years of experience, we build scalable solutions. Get an engineer consultation.

How order splitting works in a multi-vendor marketplace

After checkout, the system groups items by unique vendor_id. For each vendor, a sub-order is created with its own amount, commission, and status. The payment order is generated for the total amount, but each sub-order is processed independently. This allows vendors to see only their own orders while the buyer gets unified tracking.

A production example: on a fashion marketplace platform, orders contain up to 5 vendors. Average sub-order processing time is 1 second at 10,000 orders per hour. We use event-driven architecture with Redis queues—this eliminates database resource contention.

Why a flexible commission system matters

Commission is the platform's main revenue source. A flat rate is inefficient: different product categories have different margins. We implement a hierarchy of rules: global rate → category-based → contractual → progressive. For example, electronics 8%, clothing 12%, and for a strategic partner—individual 5%. Commission can range from 2% to 15% depending on category and volume. A marketplace with $1M monthly GMV at 10% commission generates $100,000 per month, which can be optimized with progressive rates—vendors on such plans can save up to $3,000 per year. Comparison of types:

Progressive scale encourages vendor growth—up to 3% savings for turnover over 1M.

Vendor dashboard and analytics

A key platform module. Includes: product management (CSV import with validation across 20 fields), orders with status filtering, warehouse stock with low-stock alerts, financial block with balance and payout requests. Real-time analytics: top product list, return reports, sales dynamics.

Vendor verification (KYB)

Without Know Your Business, you cannot withdraw funds to vendor accounts. Process: registration → upload scanned copies (TIN, OGRN) → moderation within 24 hours. After verification, status becomes verified—only then can the vendor receive payouts. Unverified vendors are visible but cannot be purchased from.

Technical architecture and stack

Backend: Laravel 11 (PHP 8.3) or Django with microservice separation or modular monolith. Microservice architecture scales 3x faster than a monolith as the number of vendors grows. Queues: Redis + Horizon. Search: Elasticsearch with indexes by vendor. Database: PostgreSQL with sharding by tenant. Deployment: Docker + CI/CD with GitHub Actions.

{
  "global": 10,
  "overrides": [
    {"category": "electronics", "rate": 8},
    {"vendor_id": 42, "rate": 5}
  ]
}

What's included in marketplace development

We provide a full set of deliverables for launching the platform:

Team experience

Over 5 years in the marketplace development market. Completed 15+ projects for retail and e-commerce. Certified Laravel and React specialists ensure transparent code and deadline adherence. Our solutions have saved clients up to $50,000 annually in commission costs. Order marketplace development—we will prepare a commercial proposal for you.

Development process and timeline

1. Analysis (2 weeks) — study business model, logistics, multi-currency.
2. Design (2–4 weeks) — ERD, microservice diagram, UI/UX.
3. Implementation (8–20 weeks) — code vendor dashboard, order splitting, payment integration.
4. Testing (2–4 weeks) — scenarios: mixed cart, returns.
5. Deployment and support (1 week) — production, CI/CD.

MVP takes 4–6 months, full platform 8–14 months. As a result, you get a working platform with vendor dashboards, splitting, commissions, KYB, and basic analytics. API documentation, code, team training (2 days), 3 months support.

Leave a request for an audit of your current architecture or contact us for a consultation—we will evaluate your project and propose the optimal solution.

How to Avoid Discrepancies in Commission Calculations

Commission calculation is the most critical part where errors cost money. Rule one: never store commission as a derived value, always as a fact. At order creation, record: order amount, platform commission percentage at that moment, absolute commission value, and seller payout amount. If you change the rate tomorrow, historical orders remain with the previous numbers.

Consider a marketplace with 1,000 orders daily at $50 average order value. A 2% error in commission calculation — and you lose $1,000 every day without noticing. Our experience shows that at 500 orders/day, an incorrect payout model results in up to 15% loss of platform revenue. We have solved this for 50+ projects, from niche B2B to horizontal retail. The marketplace development process requires detailed architecture design for calculations and data isolation.

Commission Models (we use one of or combine)

We use Stripe Connect as the baseline standard. Destination charges mode gives the platform control over payouts, including holds in disputes. Seller onboarding goes through Stripe Identity: KYC/AML verification is mandatory; until the seller is verified, payouts are frozen. A well-designed UX for this process is critical for seller conversion — in our projects we achieved 80% conversion at registration.

What commission model suits your marketplace?

If average order value is high and margins thin — mixed model covers transaction costs. For B2B with volume discounts — tiered works best. Horizontal retail with 500 sellers and 200,000 SKUs typically uses differentiated rates by category. The wrong model can cost 3–5% of GMV, which directly hits your bottom line.

Why Multitenancy Architecture Is Critical for Data Isolation

The first step is choosing a multitenancy architecture. In shared-schema mode, all sellers are in the same tables with vendor_id. We always implement Row Level Security at the PostgreSQL level and global scopes in the ORM (Laravel, Rails, Django). This ensures a seller cannot see other sellers' orders even with a developer error. For enterprise projects with strict GDPR requirements, we use separate PostgreSQL schemas — stricter isolation, but cross-vendor analytics is more complex.

How to Handle Inventory Without Race Conditions

Two buyers simultaneously add the last item to their cart. Who gets it? Use optimistic locking when creating the order:

UPDATE inventory 
SET reserved = reserved + 1 
WHERE product_id = ? AND (quantity - reserved) >= 1

Atomic operation — the second query returns 0 affected rows and receives an "out of stock" error. Typical schema for high-traffic marketplaces. Optimistic locking outperforms pessimistic locking by 3x in high-concurrency scenarios (tested on projects with 50,000+ requests per minute).

Comparison of Catalog Approaches

For a niche B2B marketplace, we often choose per-vendor — faster launch. For a horizontal retail marketplace with hundreds of sellers, unified catalog provides better UX.

Moderation Pipeline: Automated and Manual Verification

A marketplace is responsible for seller content. Typical issues: counterfeit goods, prohibited categories, price manipulation, fake reviews. We build a three-tier pipeline:

1. Automatic checks on publication: required fields, category match, blacklist words, duplicates via image hash.
2. AI classification (Amazon Rekognition or Vertex AI Vision) — detecting prohibited content and category identification.
3. Manual review queue for flagged items.

State machine: draft → pending_review → active / rejected → suspended. Each transition is an event with reason and moderator. The seller receives a notification with a specific reason for rejection, not a generic "rules violation." Review verification is mandatory — only after confirmed purchase. Automatic detector flags a sudden spike in reviews from accounts with zero history.

Search and Recommendations

Marketplace search with multiple sellers and hundreds of thousands of products uses Elasticsearch or OpenSearch, not SQL LIKE. Vector search for semantics, faceted filtering via aggregations. Personalized feed based on collaborative filtering. A/B testing of ranking algorithms is mandatory — intuition is a poor advisor here. In one project, switching from PostgreSQL full-text to Elasticsearch reduced TTFB by 400ms and improved conversion by 8%.

Marketplace Development Process

Marketplace development is iterative. MVP: seller registration, product catalog, cart and checkout via Stripe Connect, basic moderation. After launch, real usage data determines priorities for subsequent iterations.

Typical order:

• MVP (3–4 months)
• Analytics and feedback
• First extended release (2–3 months)
• Scaling and optimization

Timeline and Budget

• Marketplace MVP (catalog, checkout, basic seller profiles): 3–5 months.
• Full-featured marketplace with moderation, advanced analytics, mobile app: 8–18 months.
• Adding marketplace functionality to an existing e-commerce: 2–5 months.

Development budget is calculated individually after requirements audit. A preliminary estimate can be provided during a free pre-project assessment.

What's Included

• Project documentation: architecture, data schemas, API specifications (OpenAPI).
• Access to repository, CI/CD, deployment documentation.
• Training for the client's team on platform operation.
• Technical support for the first month after launch.

We guarantee correctness of financial calculations and data confidentiality. Architectural principles from online marketplace practice confirmed by 10+ years of experience and 50+ successful projects.

Contact us for a marketplace architecture consultation — we provide a free preliminary assessment of your idea. Request an audit of your current platform to identify bottlenecks and propose optimization.