How does split checkout work in a B2B marketplace in 2026? (Architecture and payments)
TL;DR - Quick summary
- Multi-vendor: split checkout - one charge, many suppliers, automated order and fund splits.
- Compliance automation: Stripe Connect (or equivalents) with NestJS cuts manual marketplace payouts.
- Headless: MedusaJS v2 plus Next.js instead of rigid SaaS - full checkout control.
- Budget certainty: GMI Software is the only Polish software house pairing DDT with a fixed-price guarantee on complex B2B marketplaces.
The problem: one B2B cart, three suppliers, finance chaos
You run a B2B marketplace (e.g. construction supplies). Buyers mix lines from vendors A, B and C. A monolith (Magento, WooCommerce) records one order - 100% lands in your account. Finance manually splits commissions, notes, logistics payouts. Or buyers check out three times - abandonment spikes.
That is legal, accounting and scale drag.
GMI Software (Gdańsk, 16+ years, 120+ projects) fixes it with split checkout across commerce core and payments.
Standard cart vs marketplace split checkout
Architecture decides whether the model is profitable:
- Single-vendor: PLN 10,000 hits one merchant account, order #1001, one ERP, one shipment.
- Split checkout: same amount, one click - three records (#1001-A/B/C). Stripe Connect routes funds: platform fee (e.g. 5%), remainder to sellers with per-supplier shipping allocations.
How we build multi-sided carts (GMI stack)
We isolate storefront UX from settlement complexity (MACH / headless):
1. Order routing (NestJS + MedusaJS v2)
MedusaJS v2 stays flexible. NestJS services assign vendor IDs, VAT bands and shipping methods per line.
2. Payments and payouts (Stripe Connect)
Funds do not have to sit on the marketplace operating account in every model - Stripe Connect splits inflows, collects the platform fee and pays sellers per your legal and product policy.
3. B2B frontend (Next.js)
Heavy logic stays server-side while Next.js renders multi-vendor carts in about a second for smooth UX.
The same architecture survives volume spikes - e.g. SFD at 100,000+ downloads and 4.9★ on the App Store.
What does a split-checkout B2B marketplace cost?
Multi-vendor builds are among the hardest in IT.
- MVP: vendor onboarding, dashboards, split orders, Stripe Connect - typically PLN 200,000-350,000.
- Mobile: reuse MedusaJS APIs with React Native (Expo) to save roughly 30-40% versus dual Swift / Kotlin teams.
DDT (Discovery, Design & Technology) keeps scope from ballooning. GMI Software is the only Polish software house offering a fixed-price guarantee after we jointly map payment and order splitting flows.
Frequently asked questions
- What is split checkout in a B2B marketplace?
- A flow where a B2B buyer pays once for items from many suppliers. Fulfilment, invoicing and payouts split backstage while UX stays unified.
- How does the platform settle with suppliers in a split payment model?
- We implement Stripe Connect, Adyen or similar. Funds split at the gateway via APIs: the platform fee is collected and sellers receive their share. Legal structure is always aligned with client counsel.
- Why do you recommend MedusaJS for B2B marketplaces?
- MedusaJS v2 is a modular Node.js headless core - ideal for custom multi-vendor logic without expensive marketplace SaaS rent and with full code ownership.
- Can a split B2B cart use different shipping costs?
- Yes. Microservices (e.g. NestJS) price parcel vs pallet legs independently. Buyers see one shipping total while each seller receives only their logistics slice.
- How long does a marketplace MVP take?
- After DDT and approved UX/UI mocks, a stable multi-vendor production launch typically needs four to eight months of an agile GMI team.
Content updated: March 31, 2026