Solution
Multi-vendor marketplace development
Vendor onboarding, commissions, payouts and catalog management on a scalable custom or Medusa-based marketplace.
- Risks removed
- 3
- Delivery phases
- 4
- Deliverables you keep
- 4
The situation
You're opening your platform to third-party sellers, or your current marketplace can't keep up. Vendor onboarding is manual, payouts are reconciled in spreadsheets and search slows as the catalogue grows.
Who it’s for
- 01Retailers adding third-party sellers
- 02Marketplace start-ups past their first version
- 03Groups consolidating several stores into one marketplace
Risks we remove
What usually goes wrong on this kind of project, and the fix we put in place for each.
Risk 01
Payout errors
How we remove it. Commission and payout logic covered by automated tests and reconciled against the payment provider.
Risk 02
Poor catalogue quality
How we remove it. Vendor product validation and moderation queues before items go live.
Risk 03
Slow search at scale
How we remove it. A dedicated search engine indexed from the catalogue, not database queries.
How we approach it
Each phase ends with something you can review before the next one starts.
01
Phase 1 of 4
Model
Define vendors, commissions, fulfilment and payout rules.
Build the core
Build vendor accounts, catalogue and order splitting on a Medusa or custom core.
Payments
Integrate split payments and payouts with full reconciliation.
Scale
Add search, caching and monitoring before seller volume grows.
What you get
Everything below is handed over in your name: code, accounts, documentation and credentials.
Handover manifest
4 of 4 handed over
- 01Vendor onboarding and dashboardsYours
- 02Commission rules and split payoutsYours
- 03Catalogue moderation and searchYours
- 04Admin tools for disputes and refundsYours
Repositories, accounts, licences and credentials are created in your organisation from day one.
Typical stack
Chosen at architecture, not by habit.
Typical stack: Medusa.js, Next.js, Stripe Connect, Search engine, PostgreSQL.
Questions we’re asked
Should we build or buy marketplace software?
If an off-the-shelf tool fits your commission and fulfilment model, buy it. We build when the model is your advantage, and we'll tell you which case you're in.
Who owns the code?
You do. Repositories live in your organisation from the first commit, and every licence, credential and deployment is in your name.
Do you sign an NDA before we share details?
Yes. We sign a mutual NDA before any discovery call where you share architecture, data or commercial details.
Book an architecture review
A 60-minute session with a senior architect. We review your current platform, integrations and growth plans, then send a written summary of risks and options.
- For companies with a real platform decision coming up
- NDA signed before we talk details
- The written summary is yours to keep