Choosing a White Label Marketplace Software Provider: Four Options
Four kinds of seller answer to the same search term: a monthly rental, a boxed script, a custom agency and a ready-made platform you take ownership of. Their sales pages read alike. Their answers to a few blunt questions do not - who holds the source, what happens the day payments stop, and whether cash counted at a doorstep can ever be traced. Here is how to tell them apart, us included.
Talk to Our Team →See the ScenariosPlatform Rental, Script Vendor, Custom Agency or Miracuves
The differences that matter tend to show up after you sign, not on the pricing page. Columns for other routes describe common patterns and not any named company.
| Criteria | Rented platform | Script vendor | Custom agency | Miracuves |
|---|---|---|---|---|
| How you pay | A recurring fee | A one-time purchase, roughly $250 to $1,500 on the open market | Six figures and up | $2,799, one time |
| Where the source sits | With the provider | Yours, although certain vendors keep it back from all tiers | With you, once the contract is settled | In your repository from handover |
| Time to launch | Quick to start, on their terms | Unknown / DIY | 18 - 30 months for this scope | 6 working days to deploy |
| Rider fleet | Often left to outside couriers | Frequently absent | Effectively a second product | Rider accounts, job feed, live position, code handover |
| Cash on delivery | Depends on the provider | Commonly a plain payment type | The requirement most easily underestimated | Per-rider balance in its own table, settled to the operator |
| Money model | Held inside the provider's system | Frequently one balance column | Only as good as the team's domain experience | Four wallets with append-only history |
| Mobile apps | Depends on the plan | Lower tiers commonly come with web-view apps | Whatever is scoped | Three Flutter Android apps |
| After launch | Included while you keep paying | Depends on the vendor | Depends on the contract | Guidance for 60 days, priority fixes for 6 months and updates for 12 months |
Every route has a fair audience. A rental suits an operator who prefers to lease and never touch code. What we build for is the buyer who wants the marketplace to be an asset on their own books, with the source, the data and the deployment under their control.
Questions for Any Provider
Put the same eight to every bidder and compare how the answers are worded. Vague replies are answers too.
Who holds the source and the database?
Ask for the repository and the buyer, seller and order records by name. A license to operate software is not ownership, and the gap becomes obvious the first time you want to alter checkout.
What occurs once payments stop?
With a rental, the storefront and often the seller list stop with the invoice. With a platform you own, you keep a hosting bill and nothing else. Get the answer in writing.
Whose name shows anywhere?
Check the store listing, the splash screen, the emails and the admin console for the provider's name. Ours does not appear in the apps, the stores or the console, so nothing needs stripping out afterwards.
Show me a refund, all the way through
Not merely the buyer credit. Does your commission come back off the seller ledger, and do loyalty points unwind? A refund that moves money only one way leaves you a reconciliation job.
Where does doorstep cash go?
A rider takes notes at a door. Which table records it, whose balance is it until settlement, and how does it reach the operator wallet? "It is flagged as paid" is not an answer.
How many wallets exist?
Buyer, seller, rider and operator are four separate obligations. One shared balance means a spreadsheet stands between you and the question of who is owed what.
Can one seller reach another's data?
Sellers are tenants. Ask where the separation is enforced: in the repository layer, or in a filter each future query must remember to include.
What do the six days leave out?
Our scope leaves out gateway approval, messaging accounts, your catalog, seller recruitment, app store review and tax rates. A quote showing no exclusions has not been costed by anyone.
Several answers can be checked in the demo rather than taken on trust. Follow one order from the buyer's search to the operator's ledger and watch each balance move.
Our Six-Step Handover
The steps after you say yes, listed in sequence.
Confirm the supply and the accounts
We check your market, which gateways you will use, whether cash on delivery matters, and where the first sellers come from. Your side also starts the slow applications: merchant approval, messaging providers, a Firebase project and app store accounts. Those decide the calendar, so they begin before design does.
Carry your own identity across every surface
Name, icon, splash screen and colors go on the storefront, seller panel, operator console and all three Android apps, along with your emails and invoices. Commission bands, currencies, delivery zones, zip allowlists and tax classes are set for your market.
Install it on your infrastructure
The platform goes onto servers you choose, with the queue worker, scheduler and storage configured. Your gateway, SMS, email and Firebase credentials are entered and tested, plus an OpenAI key if you want the AI module.
Run a whole order, cash included
A real order travels through the split, the seller's acceptance, dispatch, the code check at the door and settlement. A cash order runs the same route, so you watch the money reconcile before any customer does.
Walk your team through the console
The people who will operate it see seller approval, listing moderation, commission bands, coupons, refund and withdrawal queues, and the wallet ledgers behind them.
Source transfer, then support
The Laravel backend and all three Flutter projects move into your repository with reversible migrations. Support runs as 60 days of launch guidance, 6 months of priority bug fixes and 12 months of updates.
Day zero deserves the most respect. A finished platform with no approved gateway account is a storefront that cannot take a real payment, and no provider can hurry a bank's own review.
Warning Signs to Leave the Deal
Most of these hide in fine print. Read the license, the deployment terms and the fee schedule before you look at the feature list.
What a Multi-Vendor Platform Has to Get Right
Six properties that never appear in a demo and are costly to find missing a year in.
A ledger that holds up
Histories that only grow, written in the same transaction as the balance they describe, so any figure can be rebuilt. Otherwise a disputed number has no answer.
Cash you can trace
Money taken at a door lands on the collecting rider's balance and settles to the operator in its own table. Otherwise pocket cash and bank cash never agree.
Sellers kept apart
Separation enforced at the repository, keyed to seller and rider identity. Otherwise one forgotten filter shows a seller's orders to a competitor.
Refunds that mirror the sale
A refund state machine that blocks double-spend and reverses commission and points. Otherwise each refund quietly overpays somebody.
Payments that verify themselves
Gateway-hosted card fields, so no card number touches your server, plus webhook signatures checked at the edge. Otherwise anyone who finds an endpoint can mark an order paid.
Delivery you can prove
Checkpoints along the route and a one-time code entered at the door. Otherwise "delivered" is only a claim.
Controls We Built, and Claims We Do Not Make
A marketplace has four separate security problems in one system: money moving between wallets, sellers who must stay invisible to each other, buyers handing over addresses, and riders whose cash and location are sensitive in their own right.
Ledgers nobody can quietly edit
Each entry is appended inside the same transaction as the balance change, so a movement and its record cannot drift apart. Any of the four wallets can be reconstructed from its history.
Seller data stays with the seller
Scoping lives in the repository layer and model policies, tied to seller and rider identity, so it does not rely on every later query remembering a filter.
Card numbers never arrive
Payment fields are hosted by the gateway and webhooks are signature-checked, which keeps the heaviest slice of payment compliance off your own servers.
Location and contacts walled off
A rider's movement trail and emergency contact details are visible to that rider and to the operator, and to nobody else.
Named, not gestured at
Argon2id hashing, CSRF tokens, parameterized queries, sanitized rich text, verified webhooks and audit trails that record the actor and the time of each change.
No certificate held, none claimed
The platform is ready for a penetration test and for the evidence ISO 27001 or SOC 2 asks for, but neither certificate is ours. Some items are deployment-layer duties we configure and you own after handover, and the hub names them separately instead of folding them into a compliance claim.
Illustrative Launch Setups
Two illustrative setups for buyers of white label platforms, each built only from capabilities that ship in the base build.
Read this before the scenarios below
- Neither is a client engagementWe have not yet deployed this multi-vendor commerce platform for a named client, so nothing here is offered as a customer reference.
- They describe setup, not resultsNo revenue, traffic or growth number appears, because none has been measured for this product.
- Real work is published elsewhereMiracuves client deployments, with their own reported figures, sit in the portfolio. They are built on the same foundations but are different products.
- Nothing depends on custom workEach capability listed is in the base build and can be opened in the live demo.
An Agency Delivering Marketplaces to Clients
How the platform is set up for a studio that sells finished marketplaces to its own customers, one branded product for each.
- Every client expects its own name, palette and domain, with no trace of the agency's supplier
- Clients differ on payment gateways, currencies and whether they need delivery at all
- Building each marketplace from zero makes every project a fresh risk
- A vendor's license terms can quietly limit what the agency may hand over
- One codebase its developers learn once and reuse
- Switch off the modules a client does not need, without touching code
- Commission, currencies and payment methods changed as settings
- Readable source it can extend for the client who wants more
- App name, icon, splash screen and palette applied to every surface
- Branded transactional emails and invoices
- Custom domain configuration
- AI, Blog and Tax modules that enable and disable independently
- Features disabled from the admin console, with no code change
- Complete source, so the agency can extend it
India · A Cash-Led Retailer Adding Sellers
How the platform is set up for a retailer that already has stores and stock, where cash still settles many orders, and that wants local sellers to widen the range.
- Cash closing orders at the door, after stock and commission are already committed
- Tax rates that vary by product category and by state
- Buyers who convert poorly against an English-only storefront
- Delivery that reaches some pin codes well and others not at all
- Take cash without building a spreadsheet to account for it
- Open a town only once a delivery route really exists
- Set commission per category instead of one rate for everything
- Keep the last mile, and the brand at the door, in house
- Cash on delivery confirmed by a server-checked code at handover
- A cash balance per rider, settled to the operator wallet
- An operator-set handling fee on cash orders
- Allowlists by zip that decide where checkout is available
- Tax classes bound to zones, with per-product rules
- Seller onboarding with KYC and a commission rate for each seller
Reader Questions
Does a platform provider differ from a custom agency?
What do I own after handover, and am I locked in?
Is the platform certified?
Is there a client I can see operating on this platform?
Who is this the wrong choice for?
Can an agency deploy it for several clients?
Put hard questions to each vendor bidding
Take the eight questions above to each call, ours included, and start with the one about who holds the source.
Try White Label Marketplace Software
Choose the seller who names what is missing
Six days to deploy, the whole source on infrastructure you control, and no certificate or client we cannot show you.
Talk to Us →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.




























