Multi-Vendor Marketplace App Development That Survives Real Vendors
Buyer app, vendor dashboards, commission engine and payouts, built as one operation from the first milestone.
Most marketplace apps do not die because the code was bad. They die in week three of operations, when the tenth vendor gets stuck in onboarding, the commission maths turn out to be wrong, and nobody built a way to handle a disputed order. So when we scope a multi-vendor build, vendor onboarding, commission and settlement logic, and dispute flows go into the first milestone, not a later phase. We have built commerce platforms from Cairo since 2014 for clients in Saudi, the UAE and internationally: buyer app, vendor dashboard, admin panel, payouts. You get staging links early and weekly builds on your own phone, so you watch the operational side working long before launch day.
Built as an operation, not a demo
A marketplace is vendors, orders, money and arguments. We design the onboarding, settlement and dispute screens first, then wire the catalog and checkout around them.
Commission maths you can audit
Every order stores its commission breakdown at the moment of sale, so a rate change next month never rewrites last month's payouts. You can export and check the numbers yourself.
Arabic-first, English alongside
Bilingual builds with proper RTL are the default here, not an add-on. Vendor dashboards, buyer app and admin panel all switch cleanly, including numbers, dates and receipts.
Yours, on paper
Ownership is written down, not implied: source code, design files, store accounts and keys are yours once the final invoice clears. Vendor lists and financials sit behind an NDA from day one.
What a working marketplace actually needs
Vendor onboarding that vendors finish
Self-serve registration with document upload, admin review queue and an approval flow. A vendor who abandons signup is a vendor your competitor gets.
Commission and settlement engine
Per-category or per-vendor rates, fixed fees, promotions, refund reversals. Settlements run on a schedule you choose, with a statement each vendor can read and challenge.
Vendor payouts
Payout requests, admin approval, bank transfer records and a full ledger per vendor. Gateways like Tap, PayTabs or HyperPay handle collection; the split logic is ours to build correctly.
Dispute and return handling
A disputed order freezes its settlement until resolved, with a case screen for your support team. This is the piece most marketplace builds skip, and the one that decides whether buyers come back.
Vendor dashboard and buyer app
Vendors manage products, stock, orders and earnings from their phone. Buyers get search, cart, checkout with mada, Apple Pay, Tabby or Tamara where the gateway supports them, and live order status.
Admin control room
Approve vendors, set commissions, resolve disputes, run payouts, watch sales by vendor and city. Your operations team lives here, so we design it with them, not after them.
What a marketplace costs, honestly (USD)
| Scope | Price range | Typical timeline |
|---|---|---|
| App MVP (single-vendor or tightly limited pilot) | $3,000 - 4,500 | typically 8-12 weeks |
| Mid-scope build (multi-vendor with commissions, payouts, vendor dashboards) | $4,500 - 8,000 | typically 12-16 weeks |
| Advanced real-time platform (live tracking, multi-city, high order volume) | from $8,000 | 16+ weeks |
Straight talk: a real multi-vendor marketplace almost never fits the MVP row. Commission logic, settlements and dispute handling push most builds into the upper half of the middle band or past it, and we will say so on the first call rather than after a signed contract. Building from Cairo keeps the total roughly a third to a half below Gulf agency pricing.
How we build it
- Scoping call: we work through your commission model, vendor types and dispute policy on a call that fits your day (the time difference to the Gulf is a single hour), then send a written scope where every flow has its own acceptance test.
- NDA and contract: NDA signed before you share vendor lists or financial details; the contract ties each milestone payment to a named, testable deliverable.
- Milestone builds: you get a staging link early and a fresh build on your own phone every week, starting with vendor onboarding and the money flows, not the splash screen.
- Operations rehearsal: before launch we onboard test vendors, run a full settlement cycle and walk a fake dispute end to end against the written acceptance criteria.
- Launch and handover: store submission under your accounts, then everything from code to signing keys moves to your name at final payment.
Frequently asked questions
Can I launch a cheap MVP first and add commissions and payouts later?
You can, but we usually advise against it for a true multi-vendor model. Retrofitting settlement logic onto live orders is slower and riskier than building it in, because historical transactions have to be reconstructed. A cheaper honest option is a single-vendor pilot in the MVP band, then adding vendors once demand is proven.
How do vendor payouts actually work?
Buyers pay through a gateway such as Tap, PayTabs or HyperPay into your merchant account, and the platform keeps a per-vendor ledger of earnings, commissions and refunds. Payouts run as bank transfers on your schedule, with the app generating the statement and your finance person pressing the button. Fully automated splits are possible where your gateway supports them; we confirm that during scoping.
Do vendors get their own app?
They get a vendor dashboard, either as a separate app or a role inside the main one; for most marketplaces the separate vendor app wins because vendors live in it all day. Both sides ship Arabic and English with proper RTL, and both appear in the weekly builds on your phone.
Who owns the platform when it is done?
It all lands with you at the final invoice: source code, designs, both store accounts, signing keys, the lot, and the contract says so explicitly. We publish this on our Trust Center at /trust, and it applies to every project, not just large ones.
You are in Cairo and I am in Riyadh. How does that work day to day?
Remote delivery is our standard model, and Gulf timezones are one hour from ours, so calls happen in your working day. Between calls you have the staging server, a fresh build on your phone each week, and a written record of what each milestone must pass before you pay for it.
Bring us the commission model, we will bring the build plan
Send a paragraph about your marketplace idea and who the vendors are. You will get a scoped reply with a real number and timeline, not a sales script.
