White Label Marketplace Software for Multi-Vendor Commerce
White label marketplace software that launches under your own brand, with the part most platforms leave out: the delivery fleet. Catalog, cart, checkout, orders and refunds sit on one Laravel backend, vendors run their own shops and get paid from a wallet ledger, and your own delivery agents close the loop with OTP-verified handover and cash reconciliation.
Six surfaces, one REST API. A customer storefront and Android app, a vendor panel and vendor app, a deliveryman app, and an operator console spanning catalog, orders, finance, marketing and configuration.
Go Live in 6 Days with Multi-Vendor CatalogVendor PayoutsDelivery FleetCOD ReconciliationAI Catalog CopyWhite-Label
⚡ Platform at a Glance
Multi-Vendor From Day One
Vendor registration with KYC, admin approval, per-vendor shops, product moderation and commission held per vendor or per category.
Your Own Delivery Fleet
Deliverymen are a first-class identity, not a flag on a user. Assignment feed, live location, OTP proof of delivery and a cash-collected ledger.
Four Separate Wallets
Customer, vendor, deliveryman and operator balances are kept apart, each with an append-only history so a balance can always be re-derived.
Thirteen Ways to Pay
Eleven gateways plus operator-defined offline methods and cash on delivery, each webhook signature-verified before an order moves.
AI on the Catalog
Descriptions, SEO titles and image alt text generated per product, with per-feature token quotas and a per-call cost log.
Owned, Not Rented
Full source, your branding, your commission rate, your gateways, deployed on your infrastructure in six working days.
🚀 Ready to launch your own multi-vendor marketplace under your brand?
Live in Action
Marketplace Software Demo: Six Live Surfaces, One Database
Six live surfaces on the same database: the customer storefront on web and Android, the seller panel on web and Android, the delivery app, and the operator dashboard. Sign in to each with the credentials below and follow a single order all the way through: a customer places it, a seller accepts and packs it, an agent collects and verifies it at the door, and the operator sees every state change and the money that moved.
USER WEB
Browse, Cart and Checkout in the Browser
The buyer experience on the web: category tree, brand directory, search with filters and autocomplete, a product page with the variant matrix and reviews, a multi-vendor cart, and checkout with coupon, wallet and loyalty applied together.
-
Open the storefront in your browser
-
Login with the customer credentials below
-
Explore: Search, Product, Cart, Checkout, Orders
-
Try: user@demo.com | User_321
USER APP
The Same Storefront on Android
The Flutter customer build against the same REST API: home rails and category browse, search, product detail with variants, cart and checkout, order tracking with live status, wallet and loyalty, plus push notifications and in-app support chat.
-
Download the Android customer build
-
Sign in with the customer credentials below
-
Explore: Home, Search, Cart, Orders, Wallet
-
Try: user@demo.com | User_321
SELLER WEB
Shop, Products, Orders and Payouts
The seller panel on the web: shop profile and KYC, product CRUD with the variant matrix and stock, bulk import and export, AI-assisted descriptions, an order queue with accept and reject, refund responses, sales analytics, and a wallet showing commission with a withdrawal request flow.
-
Open the seller panel and sign in
-
Login with the vendor credentials below
-
Explore: Products, Orders, Refunds, Wallet, Analytics
-
Try: vendor4@demo.com | Vendor_$321
SELLER APP
Run the Shop from a Phone
The Flutter vendor build for sellers who work away from a desk: the live order queue with accept and reject, product and stock edits, refund responses, customer chat, wallet balance with commission visible, and withdrawal requests.
-
Download the Android seller build
-
Sign in with the vendor credentials below
-
Explore: Orders, Products, Stock, Chat, Wallet
-
Try: vendor4@demo.com | Vendor_$321
DELIVERY APP
Assignments, Proof of Delivery and Cash
The last mile: an assignment feed with accept and reject, navigation to the vendor for pickup and then to the customer, status checkpoints from picked up to delivered, one-time-code verification at the door, and a wallet separating earnings from cash collected on COD orders.
-
Download the Android delivery build
-
Sign in with the delivery credentials below
-
Explore: Assignments, Pickup, OTP Handover, Earnings
-
Try: delivery@demo.com or +91 9876543212 | Delivery_$321
ADMIN DASHBOARD
Catalog, People, Finance and Configuration
The operator cockpit: product moderation, cross-vendor orders with a full status timeline, refund and withdrawal queues, vendor and deliveryman approval, commission and tax setup, marketing, reports, and every business rule held as configuration rather than code.
-
Open the admin dashboard in your browser
-
Login with the admin credentials below
-
Explore: Moderation, Orders, Payouts, Settings, Reports
-
Try: admin@demo.com | Admin_$321
Video Walkthrough
Video Demo: Storefront, Vendor Flow and Operator Console
A walkthrough of the platform as an operator sees it, rather than a feature reel. It follows a single order from a customer search through the vendor queue and the delivery handover, then shows the same order in the admin console with its status history, its tax lines and the wallet entries it produced on both sides. The catalog and moderation screens follow, then vendor subscriptions and commission, then the configuration surface where gateways, currencies, languages and delivery zones are set. If a specific flow matters more than the tour, ask and we will open it live with data in it.
App Flows
App Screens: Customer, Vendor, Delivery and Operator
The interface across the surfaces that matter: home and category browse, search with filters, the product page with its variant matrix and reviews, the multi-vendor cart and checkout, the vendor order queue and wallet, the deliveryman assignment feed with OTP handover, and the operator console.
Want a guided walkthrough of a specific flow? Book a call and we will open the surface you care about with live data in it.
Client Reviews
Marketplace Builds We Have Shipped
We have not yet deployed this multi-vendor commerce platform for a named client, so nothing below is presented as a client reference. These are approved quotes from operators who launched other Miracuves marketplaces built on the same foundations: vendor onboarding and approval, a merchant console, dispatch to a delivery fleet, and commission and payouts on one ledger.
Proof in Production
Marketplace Reference Deployments: India and Thailand
Two modelled reference deployments showing how this platform is configured for two very different commerce markets. Both are illustrative scenarios rather than client engagements, built only from capabilities that ship in the base build. Real client deployments, with their own reported figures, are published on the Miracuves portfolio.
India
COD-Led Multi-Vendor Marketplace
How the platform is configured for a marketplace where cash still closes a large share of orders and growth runs outward from the metros into tier-2 and tier-3 towns.
- Cash closing the order at the door, days after it was placed, with stock and commission already committed
- Tax rates that differ by product category and by state, needing a line on every invoice
- Buyers who do not shop in English and convert badly against an English storefront
- Delivery that reaches some pin codes reliably and others not at all
- Take cash without inventing the accounting for it in a spreadsheet
- Open a new town only once a delivery route genuinely exists
- Set commission per category rather than one flat rate across electronics and apparel
- Run the storefront in the language the market actually reads
- Cash on delivery with a server-verified code at handover
- A cash-collected balance carried per agent, settled to the operator wallet
- Operator-set handling fee on cash orders
- Zip allowlists deciding where checkout is offered at all
- Tax classes bound per zone with per-product rules
- Languages and currencies configured across web and three Android apps
- Seller onboarding with KYC and per-seller commission
This is a modelled reference deployment, not a client engagement. Every capability listed above ships in the base build and is demonstrable in the live demo. The figures are properties of the platform, not results reported by a customer.
Thailand
Provincial and Cross-Border Marketplace
How the same platform is configured where one catalog has to serve Bangkok, the provinces and neighbouring markets, each with different delivery economics and a different currency.
- Delivery economics that differ sharply between a dense Bangkok route and a provincial or island one
- Buyers who expect to pay on arrival rather than in advance
- Selling into neighbouring markets that quote in a different currency
- A second market usually meaning a second deployment to keep in step
- Serve provinces and capital from one catalog without one subsidising the other
- Quote every buyer in the currency they recognise
- Add a neighbouring market as configuration rather than a second platform
- Keep the last mile, and the cash, under the operator brand
- Zones with per-category shipping cost overrides
- A currency catalog whose default drives checkout display
- Cash on delivery with per-agent reconciliation
- Delivery fleet with pickup and delivery checkpoints
- Multi-language storefront across every surface
- Nine order statuses with a full status history per order
- One REST API serving storefront, seller panel and all three apps
This is a modelled reference deployment, not a client engagement. Every capability listed above ships in the base build and is demonstrable in the live demo. The figures are properties of the platform, not results reported by a customer.
The Basics
What Is White Label Marketplace Software?
You are buying a marketplace that already runs. Buyers browse and check out, sellers you approve list their own stock and draw earnings from a wallet, riders you employ close the last mile, and a commission you set is taken on every completed order. Underneath it all sits one Laravel 12 backend across 131 normalised MySQL tables, serving a single REST API that feeds the web storefront, the seller panel, the operator console and three Flutter Android builds. Nothing here is stitched together from separate products.
Marketplace
Unlimited category nesting, variant matrices, brands, downloadable goods, low-stock alerts and a dedicated clearance rail, with every seller listing passing an approval queue before a buyer ever sees it.
Logistics
Riders hold their own verified account, pull from a live job feed, broadcast position while moving and close each drop with a one-time code. Cash they collect settles through a dedicated ledger rather than a spreadsheet.
Money
Separate balances for buyer, seller, rider and operator, each with a history that can only be appended to. Commission resolves when an order completes, unwinds when it is refunded, and every payout request queues against a gateway settlement record.
Built for Web, Android, Vendor & Delivery
What Does White Label Ownership Mean?
White label means the platform ships under your name, not ours. You receive the full source code for the storefront, the three Flutter Android apps and the operator console, deployed on infrastructure you control. Payment gateways, SMS, push and AI keys stay on your own accounts, because they are your accounts. There is no Miracuves branding to strip out afterwards, and no licence sitting between you and your customers. The handover is the whole system, not permission to operate somebody else’s.
What carries your brand. The app name and icon as they appear on the store listing, the splash screen and in-app logo, the colour palette across all six surfaces, the customer storefront, the vendor panel, the operator console, and the transactional emails and invoices your customers receive. Android publishing support is included so the apps go live under your own developer account; iOS compilation, signing and App Store submission are a separate scope.
What you own outright. The complete Laravel 12 backend and Flutter source, with no encrypted or obfuscated files. The MySQL database and every record in it. The payment gateway, SMS, push and OpenAI accounts, because they were opened in your name and the keys never leave it.
What white label does not mean. It is not a hosted tenancy on somebody else’s platform, and not a reskin rented by the month. If a provider keeps the source code, controls the deployment, or bills you per transaction, that is a SaaS licence with your logo on it. This is a handover.
-
Customer storefront plus a Flutter Android app
-
Vendor panel plus a Flutter Android app
-
Deliveryman Flutter Android app
-
Operator console with role-scoped staff access
-
REST API v1, v2 and v3 with OAuth2 for partners
Treat everything described here as shipping in the base build unless it carries a configuration-required or integration-required label. Where credentials are involved, whether gateways, SMS, push or AI, you supply them, because those contracts are yours to hold rather than ours.
Features
Marketplace Features: Catalog, Checkout, Fulfilment and Payouts
Every item listed here ships in the base build and can be seen working in the live demo. Anything you have no use for is disabled from the admin console, without a line of code changing.
Catalog and Categories
Product records carrying multi-image galleries, a category tree that nests to any depth, a brand directory, a reusable attribute library and tag-driven search tokens.
- Multi-image galleries with video on any product
- Category tree nesting to any depth
- Brand directory plus attribute and colour libraries
- SKU and barcode handling with bulk import
Variant Matrix
Colour, size and custom attributes resolve down to individual SKU rows, each holding its own price and quantity, so stock and pricing move at variant level rather than product level.
- Variants across colour, size and custom attributes
- Each SKU row holding its own price and quantity
- Stock thresholds raising low-stock alerts
- Digital variants released by single-use code
Search and Discovery
Autocompleting keyword search, filtering across price, brand, rating, seller and attributes, several sort orders, per-buyer search history and operator-defined search keys.
- Autocompleting keyword search
- Filter by price, brand, rating, seller or attribute
- Sort on relevance, price, recency or popularity
- Per-buyer search history and operator search keys
Merchandising Rails
Rails for featured, most-wanted, best-selling and top-rated stock, a daily deal, time-limited flash offers with per-product discounts, and a clearance storefront of its own.
- Featured, most-wanted and best-selling rails
- Daily deal plus time-limited flash offers
- Separate clearance storefront for short-dated stock
- Restock alerts notifying buyers when stock returns
Multi-Vendor Cart
A single cart holding stock from several sellers, divided at checkout into one order per seller, with guest carts held against the session and merged into the account at login.
- Single cart spanning multiple sellers
- Guest cart held by session, merged at login
- Save for later and move to wishlist
- Shipping estimated per seller ahead of checkout
Checkout and Coupons
Coupons, wallet balance and loyalty points all applied to the same order, shipping chosen per seller, and order placement protected by an idempotency check.
- Coupon, wallet and loyalty stacked on one order
- Flat or percentage, scoped to product, category or cart
- Free-shipping coupons with per-buyer usage caps
- Order placement protected by idempotency
Order State Machine
Nine states running from awaiting payment through to delivered, with cancelled, returned and failed as terminal branches, and every transition recorded to a status history.
- Nine states from awaiting payment to delivered
- Per-line status supporting partial fulfilment
- Status history recording actor, note and timestamp
- Field-level edit history on operator changes
Refunds and Returns
Each refund request carries its reason and runs through a status machine of its own, settling either as immediate wallet credit or back down the original gateway.
- Refund request carrying reason and evidence
- Its own status machine, preventing double-spend
- Settled as wallet credit or back through the gateway
- Loyalty points unwound on cancellation
Four Wallets
Buyer, seller, rider and operator balances kept apart, with every debit and credit paired to a history row inside the same database transaction.
- Separate buyer, seller, rider and operator wallets
- A history row written for every balance movement
- Top-up through any gateway you have configured
- Operator-defined bonus tiers on added funds
Loyalty and Referral
Points accrued against order value or by category, spent at checkout, convertible into wallet balance, alongside referral codes that pay both parties.
- Points accrued on order value or by category
- Spent at checkout against the total
- Convertible to wallet balance on request
- Referral codes paying both parties
Delivery and COD
A job feed with accept and reject, pickup and drop checkpoints, position broadcast in transit, one-time-code confirmation at the door, and a cash-collected balance held per rider.
- Job feed with accept and reject
- Position broadcast while in transit
- One-time code confirmed at the door
- Cash collected held and reconciled per rider
Reviews and Chat
Ratings and written reviews with image upload, seller responses, buyer-to-seller messaging with attachments, and a support queue running threaded conversations.
- Ratings and reviews with image upload
- Seller responses on any review
- Buyer-to-seller messaging with attachments
- Support queue with threaded conversations
For buyers: everything above is white-label and switchable per deployment from the admin console. Turning any of it off is a setting, not a code change.
Monetization
Revenue Models: Commission, Subscriptions, Delivery and Placement
Six revenue lines run on one ledger, and they combine. An operator can take commission on a sale, charge the vendor a monthly plan, mark up the delivery fee, sell a featured slot and hold the float between payout runs, all against the same order.
Commission on Sales
A percentage set globally, per category, per vendor or per product, deducted from the vendor wallet when the order completes and reversed automatically on refund.
Vendor Subscriptions
Tiered packages with product-count limits, reduced commission, featured placement and priority support, billed on a cycle with a trial and a grace period on failure.
Delivery Margin
A configurable mark-up on the shipping charge, a handling fee on cash-on-delivery orders, and a settlement fee applied when an agent withdraws.
Featured Placement
Paid banner slots, sponsored positions on search and category pages, and a participation fee for vendors joining a time-boxed flash deal.
Wallet Float
Customer top-ups and vendor balances sit on the platform between payout runs, and add-fund bonus tiers give operators a lever to encourage larger top-ups.
White-Label Deployment
The platform itself can be resold. Agencies and networks run a branded marketplace per client or per territory from the same codebase.
Want a revenue model that fits your market? commission bands, subscription tiers and delivery margin are all operator-set. Book a call and we will map the levers against the volumes you actually expect.
Control Center
Admin Dashboard: Catalog, Orders, Payouts and Configuration
The operator console is where the marketplace is actually run, and every module answers to its own permission. The role system is fine-grained enough that a finance clerk can clear payouts without ever reaching the catalogue, and a moderator can approve listings without seeing a single setting.
Operator Control
KPI Dashboard
Gross merchandise value, order volume, seller and buyer counts, a sales chart, leading categories and sellers, and queues showing exactly what is waiting on an operator decision.
Catalog Moderation
A queue of seller-submitted listings with approve, reject and bulk handling, full editing rights over any listing, and control of the category, brand and attribute libraries.
Cross-Vendor Orders
Every order across every seller, carrying a status timeline, field-level edit history, revised delivery dates, manual status override with a stated reason, and invoice generation.
Refund Queue
Requests arriving with reason and evidence, approved or rejected with a note, and settled either into the buyer wallet or back through whichever gateway took the payment.
Withdrawal Queue
Seller and rider payout requests with approve, deny and mark-processed, running against withdrawal methods the operator defines and each seller’s saved payout details.
People and Approval
A buyer directory, seller approval and suspension with subscription handling, and rider approval, suspension and zone assignment.
Marketing Surface
Banners, flash offers, featured deals, the daily deal, platform-wide and per-seller coupons, and composers for push, email and SMS campaigns.
Tax Configuration
Tax classes and rates bound by zone, per-listing tax rules through a polymorphic binding, inclusive or exclusive display, and a tax line breakdown on every order.
Business Settings
Commission, loyalty ratio, one-time-code lifetime, currencies, languages, delivery countries and zip allowlists, shipping methods and per-category cost overrides, all held as configuration.
- Gross merchandise value, orders and growth at a glance
- Pending seller and listing requests raised as actions
- Refund and withdrawal queues with live counts
- Leading categories, sellers and products by period
Reports and Exports
Sales, seller, product, buyer, wallet, refund, withdrawal and tax reporting across any date range, exported as Excel, CSV or PDF.
- SEO metadata and robots directives per route
- Sitemap regenerated on a daily schedule
- Analytics injection for GA, GTM or Pixel
- Structured data on product and blog pages
Need governance beyond this? Age-gated categories, country-specific catalogue rules, per-seller document expiry or four-eyes approval on payouts are all addable as custom modules. Ask and we will scope it.
Pricing
How Much Does White Label Marketplace Software Cost in 2026?
The white-label platform is $2,499 as a one-time purchase, deployed in six working days. That covers the source code, the customer storefront, the vendor panel, the operator console and all three Android applications, installed on your infrastructure under your branding. Building the same surface from scratch is an eighteen to thirty month programme with a senior team, and stitching it from separate commerce, logistics and payout products means three subscriptions, three security reviews and integration work that never quite finishes. What the fixed price does not include is anything that is yours to own: gateway credentials, an SMS and email provider, a Firebase project, an OpenAI key, catalog data and the tax rates for your jurisdictions. Custom modules and deeper changes are quoted separately after scoping, typically two to eight weeks.
Not sure which option
is right for you?
Talk to us - we'll understand your goals, timeline, and budget, and point you to exactly what you need. No upselling, just honest advice.
Deliverables
What's Included: Full Source Code, Apps and Deployment
The handover is the whole system, not a licence to run somebody else’s platform.
Customer App
A branded Android build talking to the same REST API as the storefront: browse, cart, checkout, order tracking, wallet and support in one place.
- Branded Android build for your buyers
- Browse, search, cart, checkout and order tracking
- Wallet, loyalty and referral included
- Push notifications and in-app support chat
Vendor App
The seller side on a phone: catalogue, stock, the order queue, refund decisions, buyer chat, wallet and withdrawal requests.
- Branded Android build for your sellers
- Catalogue, stock and order queue on mobile
- Refund decisions and buyer chat
- Wallet balance with withdrawal requests
Delivery App
The rider surface: jobs, navigation, status checkpoints, one-time-code handover, cash collected, and earnings with a payout flow.
- Branded Android build for your riders
- Job feed with accept and reject
- Position broadcast and one-time-code handover
- Earnings, cash collected and payout requests
Customer Storefront
The public marketplace: category browsing, search with filters, product pages carrying variants and reviews, and a cart spanning sellers.
- Buyer web storefront with full search
- Seller web panel for shop and catalogue
- Product and category pages built for search engines
- Responsive across desktop, tablet and phone
Vendor Web Panel
Shop profile and KYC, catalogue management with bulk import, analytics, and everything a seller handles from a desk rather than a phone.
- Operator console with role-scoped staff accounts
- Permissions granular to the module
- Seller approval and listing moderation
- Commission, coupons and payout processing
Operator Console
Moderation, orders across sellers, refunds, payouts, people, marketing, tax and configuration, with role-scoped staff access from the first day.
- Complete Laravel 12 source, nothing encrypted
- REST API v1, v2 and v3 serving every client
- 131-table schema with reversible migrations
- Modular packaging for AI, Blog and Tax
Full Source Code
Laravel 12 backend and all three Flutter projects handed into your repository, unobfuscated, with nothing calling home for a licence.
- App name, logo, splash screen and colour theme
- Transactional email templates in your branding
- Custom domain configuration
- White-label applied across every surface
Deployment and Handover
Installed on your infrastructure with queue, scheduler and storage configured, followed by an admin walkthrough and the configuration checklist.
- Server setup on the provider you choose
- Queue worker, scheduler and storage configured
- 60 days of launch guidance
- 6 months priority bug fixes, 12 months of updates
Want to see precisely what transfers? Book a walkthrough and we will open the storefront, the seller panel, the rider app and the operator console against live data, then show you the repository you would be taking ownership of.
Built For
Who Is This Marketplace Software Built For?
White label marketplace software earns its place when the commercial half already exists, whether that is stock, sellers, buyers or a territory, and only the software is missing. It is equally the right shape for an agency or systems integrator delivering a marketplace to a client, where the finished product has to carry the client’s name and none of ours.
Regional Retail Groups
Vertical Marketplace Founders
COD-Heavy Markets
Distributors Going Direct
Franchise and Multi-Location Networks
Agencies and White-Label Resellers
If catalogue, sellers, fulfilment or repeat purchase sit at the centre of your model, this is the layer underneath it. Talk to us and we will say plainly whether it fits, or whether a different platform in the range is the better starting point.
Where It Fits
Use Cases: Retail, Grocery, Fashion & Cross-Border
The platform underneath is identical in every case below. What differs is which modules are switched on, and which part of the operating model leads.
General Retail Marketplace
A broad marketplace carrying many sellers across many categories, with a category tree of unlimited depth, brand pages and a moderation queue holding the quality line. Commission and seller subscriptions carry the revenue, while your own riders keep the last mile under your brand instead of an aggregator’s.
Grocery and Daily Essentials
Grocery leans on precisely what other commerce platforms treat as edge cases: stock that turns over quickly, restock alerts telling buyers the moment an item returns, a clearance storefront for short-dated goods, and riders collecting cash at the door.
Fashion and Lifestyle
Fashion is fundamentally a variant problem. Colour and size resolve into SKU-level rows holding independent price and stock, galleries carry the range, and reviews with image upload do the work description copy never manages.
Electronics and High-Value Goods
High-value electronics need the audit surface. Every order carries a status history and a field-level edit log, one-time-code confirmation proves the handover took place, and the refund pipeline leaves a defensible record when a dispute lands.
Digital Goods and Media
Digital goods never meet a courier. Downloadable products carry their own variants and a one-time code enforcing single-use access, with authors and publishing houses modelled for book and media catalogues.
Cross-Border Commerce
Cross-border rollouts draw on the multi-currency table, the translation store, delivery country codes with zip allowlists, and per-zone tax profiles, so a single deployment serves several markets from one operator console.
Unsure which of these describes you? Most operators are a blend of two. Book a call and we will map your catalogue, your seller mix and your fulfilment model against what the platform already does.
Why Now
Why Launch a Multi-Vendor Marketplace in 2026?
Almost nobody needs persuading that marketplaces work. The argument that actually lands is narrower: an operator is already carrying the difficult part, whether supply, buyers or territory, and renting the straightforward part from someone taking a cut of every order. Owning the software is how that stops.
You Keep the Commission
The rate on every order becomes yours to set rather than an incumbent’s to take. Once volume is real, that single line usually settles the business case on its own.
You Own the Customer
Addresses, order histories, balances and buying patterns live in a database you administer. That is the precondition for any direct marketing or loyalty programme worth running.
Supply You Already Control
A retailer with inventory, a distributor with suppliers, a network with outlets: each begins with the expensive half already done. What is missing is software, not a business.
Last Mile Under Your Brand
Delegate delivery and you delegate the one moment the buyer actually remembers. Running your own riders keeps the handover, the packaging and the cash inside your operation.
Markets Served Badly
A payment rail used only locally, a language nobody localised for, a cash-first buying habit, a rule the global platforms treat as an exception: each is an opening that tends to stay open.
One Substrate, Not Five
Commerce, delivery, content, AI and payouts share one codebase. That means a single supplier relationship, a single data model and a single security review instead of five of each.
Why Launch
The figures below describe the build, not the sector. They are drawn from the schema and the shipped feature set rather than from market forecasts, which vary by whoever published them.
Tech Stack
Tech Stack: Laravel 12, Flutter, MySQL and Redis
A conventional, hireable stack. Nothing here is exotic, which is deliberate: the developers who maintain this after handover should already know it.
Backend and Business Logic
PHP 8.2 · Laravel 12 · nWidart Modules
- Controller to service to repository to model, with transactions at the service boundary
- 114 Eloquent models over 131 normalized MySQL tables
- Modules for AI, Blog and Tax that enable and disable without touching core
- Observers, events and listeners driving notifications and ledger writes
Mobile Applications
Flutter · Dio · Provider with GetIt
- Customer, vendor and deliveryman builds from one shared architecture
- Sanctum bearer tokens with role claims for seller and delivery agents
- Firebase Cloud Messaging per app, with topic subscriptions
- Google Maps in the deliveryman build for pickup and drop-off routing
Data and Caching
MySQL 8.x · Redis 7.x · InnoDB
- utf8mb4 throughout, soft deletes on customer, vendor, agent and product rows
- Composite indexes on the hot paths, including vendor with status and created date
- Redis for cache, queue and session, with a database queue as fallback
- Append-only wallet histories so any balance can be re-derived
Payments and Settlement
Eleven gateways · Offline · COD
- Stripe, PayPal, Razorpay, Mercado Pago, Iyzico, PhonePe, Paytm, PayUZ, SSLCommerz, Flutterwave and PayTabs
- Signature verification at the webhook boundary, idempotent by gateway transaction id
- Operator-defined offline methods with manual verification
- Cash on delivery reconciled through a dedicated agent transaction table
Communications and AI
FCM · Twilio · Vonage · OpenAI
- Push through Firebase Cloud Messaging to all three apps
- SMS through Twilio or Vonage, email through SMTP or Amazon SES
- OpenAI for product descriptions, SEO copy and image alt text
- Per-feature token quotas with tokens and cost logged per call
Storage and Delivery
S3-compatible · Intervention · CDN
- AWS S3, DigitalOcean Spaces, Wasabi or MinIO through Flysystem
- Image optimization and responsive variants generated on a queue
- WebP conversion where the client supports it
- CDN recommended at the edge for static and media assets
Note for tech buyers: the platform is structured so your own team can take it over. Standard Laravel conventions, a documented schema, reversible migrations and a modular boundary for anything custom.
How It Works
How It Works: Browse, Buy, Fulfil and Settle
One order, followed end to end, across all four surfaces and both ledgers.
How It Works
Discover and Add to Cart
A customer arrives and finds a product through whichever route suits them.
- Category tree, brand directory or keyword search with autocomplete
- Filters on price, brand, rating, vendor and attributes, with sort options
- Product page with gallery, variant picker, stock indicator and reviews
- Added to a cart that can hold items from several vendors at once
Checkout and Pay
The cart splits by vendor and the totals resolve before any money moves.
- Shipping address selected, with a method chosen per vendor
- Coupon, wallet balance and loyalty points applied together
- Payment through one of eleven gateways, an offline method or cash on delivery
- Placement guarded by an idempotency check so a double submit cannot duplicate
Vendor Accepts and Packs
Each vendor sees only their own portion of the order.
- Order lands in the vendor queue with buyer and item detail
- Accepted or rejected with a reason, then marked packed and ready
- Stock decremented automatically at the SKU level
- Packing slip and invoice generated as PDF
Assign and Collect
The operator or the auto-assignment job puts the order in front of an agent.
- Assignment appears in the deliveryman feed, accepted or rejected
- Navigation to the vendor for pickup, then to the customer
- Live location broadcast while the order is in transit
- Status checkpoints written with a timestamp and a geo position
Verify and Hand Over
The handover is proved rather than asserted.
- One-time code verified at the door against a time-boxed record
- Cash collected on COD orders and written to the agent balance
- Order moves to delivered and the customer is notified on push, email and SMS
- Delivery trail retained for the SLA and dispute record
Settle and Reconcile
The money resolves across four wallets in one transaction.
- Commission split between operator, vendor and delivery agent
- Vendor balance credited and the platform commission debited
- Cash collected reconciled from the agent balance to the operator wallet
- Every movement paired with an append-only history row and a reference id
Visual Flow Diagram
Browse → Cart → Checkout → Vendor Accepts → Assign Agent → Pickup → OTP Handover → Settle
Architecture
Platform Architecture and Backend Flow
Layered Backend
Controller for the HTTP boundary, service for orchestration and transactions, repository for data access, Eloquent for the entity. Business rules live in one layer, not scattered across controllers.
Modular Packaging
AI, Blog and Tax ship as nWidart modules with their own routes, migrations and providers, so an operator can disable one without touching the core application.
Event-Driven Side Effects
Order placed, status changed, vendor approved, payout requested and refund processed each emit an event. Listeners fan out to notifications, ledger writes and analytics.
Queues and Scheduler
Redis-backed workers under Supervisor handle images, PDFs, email, push and AI calls. A cron scheduler runs commission recalculation, subscription renewals, abandoned-cart reminders and backups.
Append-Only Ledgers
Wallet histories, order status histories, order edit histories and refund statuses are written, never updated, so the financial and operational record can be replayed and audited.
Horizontal Scale
A stateless application tier behind a load balancer, MySQL with read replicas for reporting, Redis for cache and queue, and S3 with a CDN for media.
Build to Scale
Built to Scale: Catalog Depth, Order Volume and Fleet Load
Scale on a marketplace fails in predictable places. The catalogue outruns its index. The order tables turn hot the moment a campaign lands. The fleet writes position data without pause for as long as it is on the road. Each of those has a decision already taken in this build rather than left for later.
Catalogue and Read Load
Category trees, banners, configuration and the popular-product rails live in Redis instead of being assembled on every request, which accounts for the bulk of storefront reads. Listings paginate at the server rather than handing back unbounded sets, and relations are eager loaded, so browse and search never fall onto the N+1 path a growing catalogue exposes first.
Order Tables at Peak
The tables that run hot are orders, order details, notifications, chat and delivery history. Composite indexes follow the queries actually issued against them: seller paired with status and creation date, rider paired with status. Completed orders past twelve months can move to an archive table sharing the same schema, shrinking the working set without breaking a single join or report.
Work That Runs Off the Request
Image processing, invoice and report generation, email, push fan-out and AI enrichment are queued jobs supervised by Supervisor, with failures captured and retried on a backoff. A surge of orders cannot stall a page render, and a mail provider going down degrades notifications rather than taking checkout with it.
Fleet Write Volume
Riders generate writes continuously for as long as they are working. Position updates are pushed onto their own queue instead of running inside the request cycle, and both delivery history and notifications are obvious candidates for time-based partitioning at the storage layer once fleet size makes it worth doing.
Cached Reads
Category trees, banners, configuration and popular-product rails come from Redis rather than being rebuilt per request, covering most of the storefront read path.
Hot Tables Indexed
Orders, order details, notifications, chat and delivery history carry composite indexes matched to the queries actually run, seller with status and date among them.
Async by Default
Image processing, invoice generation, email, push fan-out, AI enrichment and reporting all sit on queues, so none of them occupies a buyer request.
Fleet Write Load
Delivery history and notifications are candidates for time-based partitioning; position updates are written on a dedicated queue instead of synchronously.
Search Headroom
MySQL full-text holds the default. Elasticsearch or Meilisearch drops in behind the same service interface once the catalogue outgrows it.
Archive Path
Completed orders past twelve months move to an archive table on an identical schema, keeping the working set small without disturbing joins or reporting.
Search Past MySQL
MySQL full-text with indexed columns carries the default, which is sufficient for most catalogues. Elasticsearch or Meilisearch slots in behind the same search service interface with index synchronisation on a queue, making the upgrade a matter of configuration and infrastructure rather than a rewrite.
For founders and technical leads: a single modest instance is a legitimate starting point, and none of this needs replacing to grow from there. What changes as you scale is the infrastructure behind it, not the code.
Security
Security: OWASP-Mapped, GDPR-Ready and VAPT-Ready
Security on a marketplace is not a single control; it is four distinct problems sitting in one system. Money moves between four wallets and must never be quietly editable. Sellers are tenants who cannot be allowed to see one another. Buyers hand over addresses and payment intent. Riders carry cash and leave a live location trail that is itself sensitive. Each gets a specific mechanism rather than a general assurance: ledgers that only append, written inside the same transaction as the balance they record; tenant scoping enforced at the repository layer against seller and rider identity; payment fields hosted by the gateway so no card number reaches the server at all; and emergency-contact and location data walled off to the rider and the operator alone.
Security headers are yours after handover
Rate limits ship at sane defaults, not tuned ones
Captcha is available and off by default
A WAF is recommended and not included
Two-factor is configurable, not mandatory
Dependency audits are a standing task
Built to the Controls
Argon2id password hashing, encrypted session cookies carrying HttpOnly and SameSite, CSRF tokens on every state-changing web route, and mass-assignment protection across the models.
GDPR-Ready
Soft deletes on buyer, seller and rider records, a per-user JSON export, account deletion with a grace period before personal data is purged, and marketing gated behind explicit opt-in.
Tenant Isolation
Seller and rider scoping enforced in the repository layer, model policies governing read and write, and API token abilities mapped to permission slugs rather than a blanket scope.
Payment Integrity
Card numbers are never stored. Webhook signatures are verified at the boundary, transactions made idempotent against the gateway id, and refunds held behind a status machine that prevents double-spend.
Injection and XSS
Eloquent parameterisation throughout, form-request validation on every write endpoint, Blade output escaping, and Mews Purifier applied over rich-text fields such as descriptions and support replies.
Audit Trail
Order status and field-level edit histories, refund transitions, per-actor wallet histories, AI usage logged with cost per call, and an application error log surfaced inside the console.
Where certification is concerned the position is plain: the controls listed here are built, and the platform is ready both for a penetration test and for the evidence gathering that ISO 27001 or SOC 2 demand. Neither certificate is held and neither is claimed. Several items are deployment-layer responsibilities that we configure and you own after handover; those are named as such below rather than folded into a compliance claim.
Advance Add-Ons
Add-Ons: Search, Analytics, Integrations and Automation
The base build covers the marketplace. These are the extensions operators ask for once volume arrives, quoted after scoping rather than bundled.
External Search
Elasticsearch or Meilisearch behind the existing search service, with index sync on a queue, for catalogs where MySQL full-text has stopped being enough.
Advanced Analytics
Cohort analysis, vendor performance scoring, basket analysis and forecasting on a read replica, beyond the standard sales, refund and tax reports.
ERP and Accounting Bridges
Two-way sync with an existing ERP, accounting package or POS, so stock and settlement do not have to be reconciled by hand.
Loyalty and Membership Tiers
A paid membership with free delivery and member pricing, layered over the existing loyalty points and wallet, in the style buyers now expect.
B2B and Wholesale
Tiered pricing per customer group, minimum order quantities, quote requests and credit terms, for operators serving trade buyers alongside retail.
Sponsored Placement Engine
A self-serve advertising surface where vendors bid for position on search and category pages, with budget control and delivery reporting.
Observability Stack
Prometheus and Grafana or a vendor equivalent, log aggregation and OpenTelemetry tracing, for operators who need more than the built-in error log.
iOS Builds
The three Flutter projects compiled, signed and submitted for the App Store, with the review cycle and the store assets handled alongside.
Building in eCommerce? We Have the Whole Market Covered.
The same foundations under this platform carry several adjacent products. If your model is closer to one of these, start there instead.
Amazon Clone
Full-scale multi-vendor marketplace with catalogue depth, fulfilment workflows and buyer trust mechanics.
Alibaba Clone
B2B wholesale marketplace with bulk pricing, supplier verification and trade enquiry workflows.
Noon Clone
Regional eCommerce marketplace built for Middle East logistics, payments and Arabic-first shopping.
Flipkart Clone
Large-scale value marketplace with flash-sale events, seller onboarding and mobile-first buying.
Marketability
Marketability, Revenue Potential and Business Prospects
What this platform is worth to any given operator turns almost entirely on whether the supply or the demand already exists. The scenarios below are arithmetic on inputs the operator sets, offered to make the levers legible. They are neither a forecast nor a promise.
Commission Compounds
Your rate applies to every order that completes. For an operator already pushing volume through somebody else’s platform, the difference in rate alone tends to cover the build several times over.
Vendors Are Recurring Revenue
Subscription tiers convert a one-off onboarding into a monthly line item, and the tier structure itself becomes the natural upsell as a seller grows.
Delivery Is Margin, Not Cost
Operating your own riders turns the shipping charge from a pass-through into margin you control, with the cash-handling fee layered on top wherever cash still dominates.
The Asset Is the Network
A seller roster and a buyer database outlast the software by some distance. The platform is simply what makes both yours to own instead of yours to rent.
- A commission on every order, set globally, by category or by seller
- Seller subscription tiers carrying product limits and reduced rates
- Margin on the shipping charge, plus a handling fee on cash orders
- Featured slots and sponsored positions sold to sellers
- A settlement fee taken when a seller or rider withdraws
- Wallet float held between payout runs, with bonus tiers on added funds
- A sales channel you own rather than a listing you rent
- A buyer database with order history attached, marketable directly
- A seller network holding value independently of the software
- A commission rate you set instead of one set for you
- Last-mile delivery carrying your brand rather than an aggregator’s
- Source code you can extend, licence onward or resell
The app name and icon on the store listing, the splash screen and in-app logo, the colour palette across the storefront, vendor panel, operator console and all three Android apps, and the transactional emails and invoices your customers receive. Android publishing support is included so the apps ship under your own developer account. iOS compilation, signing and App Store submission are available as an additional scope.
It is the same platform. The Amazon Clone page describes it for operators who want a marketplace modelled on Amazon specifically; this page describes the same build for operators launching under their own brand without reference to an existing marketplace. The source code, the price and the six-day deployment are identical.
Example Revenue Scenarios
About these figures: every scenario is arithmetic on inputs an operator chooses, published to make the levers concrete. None of them is a projection, and Miracuves guarantees no commercial outcome. Six days describes our deployment window for the base platform, not your route to market.
Regional retailer going multi-vendor
Vendors onboarded in year one
An operator with existing stores adds thirty local sellers and takes a commission on each order alongside their own sales.
The commission rate, the order volume and the delivery margin are all operator-set. The platform cost is one-time; what recurs is hosting, gateway fees and the team running it.
Vertical marketplace launch
Working days to deployment
A founder with a supplier network launches a focused catalog rather than a general store, competing on relevance instead of breadth.
Deployment time is our build time on the base. Catalog loading, vendor recruitment and market entry are the operator work and set the real timeline.
Agency running white-label deployments
Codebase, many branded marketplaces
A studio deploys the same platform per client or per territory, each fully branded, from one codebase it already knows.
Per-deployment licensing is a commercial conversation rather than a page price. What the platform provides is the branding depth and module toggles that make repeat deployment practical.
Why Miracuves
Miracuves vs Other Marketplace Software Providers
There are many ways to get a marketplace: generic commerce scripts, freelancers, agencies, or white label marketplace software you own outright.
Why Founders Choose Miracuves
Fixed Price, Not a Range
$2,499, written as a number rather than a starting point. Scope is agreed in writing before build, and anything added to it is quoted openly instead of absorbed.
Commerce and Logistics Together
Most scripts end at the payment confirmation and pass delivery to an aggregator. Here the fleet, the one-time-code handover and the cash reconciliation are part of the same codebase.
Source Code on Handover
Backend and all three Flutter projects move into your repository. Nothing obfuscated, no licence server phoning home, no reason to keep paying us to stay online.
Six Working Days
Installed on your own infrastructure with queues, scheduler and storage configured. The platform already exists, so the work is deployment and branding rather than development.
A Hireable Stack
Laravel, MySQL, Redis, Flutter. Whoever takes this over after us can be hired through ordinary channels rather than sourced through us.
Honest Readiness Labels
Anything needing configuration or a third-party integration is labelled as such on this page. What depends on your credentials is stated outright rather than quietly counted as included.
Compare & Discover Why Operators Choose Us for Multi-Vendor Commerce
| Criteria | Miracuves Marketplace Software | Generic Clone Script | Custom Dev Agency |
|---|---|---|---|
| Time to Launch | 6 days (Production) | Unknown / DIY | 6-9+ months |
| Source-Code Ownership | ✔ Full | Often limited / encrypted | Usually yes |
| Feature Depth (Marketplace-grade) | High (catalog, payouts, fleet) | Basic (single-vendor storefront) | Depends on budget |
| Security & Compliance | Strong (built to the controls, GDPR-ready) | Minimal | Varies widely |
| Scalability & Performance | Cloud & CDN-optimized | Rarely considered | Depends on architecture |
| Monetization Options | Multiple (commission, plans, delivery) | Usually commission only | Custom (more time & cost) |
| Admin & Analytics | Full-fledged dashboard | Very basic or missing | Custom build (extra cost) |
| Cost vs Speed vs Quality | Balanced | Cheap but risky | High cost, slow |
| Ongoing Support & Updates | Available with clear plans | Usually none | Depends on contract |
Most of what separates these options is depth. A single-seller storefront script and a marketplace carrying a delivery fleet and four wallet ledgers are different products, and the gap becomes obvious around month six rather than in week one.
Industries
Industries We Serve
This platform suits any operator selling physical or digital goods through more than one seller. General retailers use the full category tree and brand directory. Grocery operators lean on fast stock movement, restock alerts and clearance. Fashion brands use the SKU-level variant matrix. Electronics sellers need the audit trail and OTP handover on high-value orders. Pharmacies use moderation and controlled catalog access. Book and media sellers use the digital product tables with authors and publishing houses. Distributors going direct use vendor onboarding and commission. Franchise networks run per-location inventory under one console.
- 🛒 General Retail
- 🥬 Grocery & Essentials
- 👗 Fashion & Apparel
- 📱 Electronics
- 💊 Pharmacy & Wellness
- 📚 Books & Media
- 🏭 Distribution & Wholesale
- 🏪 Franchise Networks
- 🎨 Handmade & Artisan
- 🌍 Cross-Border Retail
Miracuves marketplace software is built as a marketplace-first commerce platform adaptable to any catalog sold through multiple vendors, priced by your own rules, delivered by your own fleet and white-labelled entirely under your brand.
Version History
Release Log
| Version | Date | <span style="color: rgb(6, 6, 8); font-family: Montserrat, sans-serif; font-size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 700; text-align: left; white-space-collapse: collapse; background-color: rgb(255, 255, 255);">What's New</span> |
|---|---|---|
| v4.0 | Aug 2026 | Laravel 12 upgrade. AI module for catalog copy and SEO. Clearance storefront and restock subscriptions added. |
| v3.6 | 2025 | Deliveryman app with OTP proof of delivery, live location and a cash-collected ledger. |
| v3.4 | 2025 | Vendor subscription packages with trials, grace periods and per-tier commission rates. |
| v3.0 | 2024 | Tax module with per-zone rates, wallet ledgers per actor and the refund status machine. |
Blog & Resources
Marketplace Software: Latest Insights and Guides
Guides on marketplace economics, vendor onboarding, delivery operations and the decisions that matter before you launch.
Last Updated on September 4, 2026 by samruddhi kadam Key Takeaways Online Retail Marketplace Security…
Last Updated on September 4, 2026 by sakshi Key Takeaways An online retail marketplace connects…
Online Retail Marketplace vs B2B Marketplace: Which Business Model Fits Startups Better?
Last Updated on September 4, 2026 by sakshi Key Takeaways Flipkart follows a consumer-focused hybrid…
Last Updated on September 4, 2026 by samruddhi kadam Key Takeaways Multi-Vendor Ecommerce Marketplace Revenue…
Last Updated on September 4, 2026 by samruddhi kadam Key Takeaways Multi-Vendor Ecommerce Marketplace Planning…
FAQ
FAQ: Pricing, Features, Payments and Deployment
Everything you need to know about Miracuves marketplace software.
A marketplace that already works, shipped under your brand. Buyers browse and purchase, sellers you approve list their own stock and draw payouts, riders you employ finish the last mile, and a commission you set is taken on every completed order. It arrives as a web storefront, a seller panel, an operator console of role-scoped modules and three Flutter Android builds for buyers, sellers and riders, all speaking to one versioned REST API.
$2,499, paid once, live on your infrastructure under your branding inside six working days. Anything beyond the base build is scoped and quoted on its own, and usually runs two to eight weeks depending on what is being added.
Yes. The Laravel backend and all three Flutter projects move into your repository at handover. Nothing is obfuscated, there is no licence callback, and keeping the platform running never depends on us.
Eleven ship integrated: Stripe, PayPal, Razorpay, Mercado Pago, Iyzico, PhonePe, Paytm, PayUZ, SSLCommerz, Flutterwave and PayTabs. Operator-defined offline methods and cash on delivery are built in alongside them. Every gateway runs on your own merchant credentials, which is why each carries an integration-required label.
Yes, and it is a large part of why this platform suits cash-heavy markets better than a general commerce script. Cash a rider collects posts to that rider’s own balance, reconciles against the operator wallet at settlement, and lives in a dedicated transaction table rather than being filed as an ordinary payment.
Riders are a first-class identity carrying KYC and admin approval, not a flag set on a buyer account. Each gets a job feed with accept and reject, navigation to seller and buyer, position broadcast while moving, status checkpoints, one-time-code confirmation at the door, and a wallet with its own withdrawal flow.
Yes. Sellers register with KYC, wait on operator approval, then run their own shop end to end: product creation with variants and stock, bulk import and export, AI-assisted descriptions, an order queue, refund responses, sales analytics and withdrawal requests, from the web panel or the Android app.
As a percentage, set globally or narrowed to a category, a seller or an individual product. It comes out of the seller wallet when the order completes and reverses itself automatically if that order is refunded. Subscription tiers can carry a reduced rate as a paid benefit.
Yes. Currencies carry exchange rates the operator sets, a polymorphic translation store holds both interface and content strings, and delivery country codes with zip allowlists govern where you will ship. Rates are set rather than fetched automatically, which is a deliberate choice.
It drafts product descriptions, SEO titles and descriptions, tag suggestions and image alt text through OpenAI, with token quotas per feature and a log capturing tokens and cost on every call. It runs on your own OpenAI key, making it integration-required rather than included.
No. The three Android builds sit inside the base price. The Flutter projects do compile for iOS, and we quote App Store builds, signing and submission separately, because the developer account and the review cycle are work of their own.
The controls are in place: Argon2id hashing, CSRF protection, parameterised queries, HTML sanitisation, tenant scoping, webhook signature verification and append-only audit ledgers. That makes it ready for a penetration test and for ISO 27001 or SOC 2 evidence gathering. Neither certificate is held, and we claim neither.
Everything that belongs to you: merchant approval from a gateway, an SMS and email provider, a Firebase project, an OpenAI key, your catalogue data, your seller recruitment, tax rates for your jurisdictions, and app store review. Six days is our deployment window for the base platform, not your route to market.
Let's turn your idea into
a live platform.
Get a free consultation, a clear timeline, and honest answers. We'd rather earn your trust than rush a sale.
Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Amazon, Flipkart, Walmart, Etsy, Myntra, Noon or Fancy, or any other marketplace operator.
“White label marketplace software” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party marketplace website or application.
All third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
