Engagement scope - proposed scope
Choosing a White Label Marketplace Software Provider: Four Routes
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
Typical scoping questions
Who holds the source and the database?
- Ask for the repository and the buyer, seller and order records by name. A licence to operate software is not ownership, and the gap becomes obvious the first time you want to alter checkout.
What happens the day 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.
The Six-Step Delivery Process
What follows a yes, in the order it happens.
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.
Put your identity on 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.
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
- 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.
Red Flags That Mean Walk Away
Most of these hide in fine print. Read the licence, the deployment terms and the fee schedule before you look at the feature list.
What a Multi-Vendor Platform Has to Get Right
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.
- 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.
Modelled Reference Deployments
Read this before the scenarios below
- Neither is a client engagement We 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 results No revenue, traffic or growth number appears, because none has been measured for this product.
- Real work is published elsewhere Omnistu client deployments, with their own reported figures, sit in the portfolio. They are built on the same foundations but are different products.
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
Choose the seller who names what is missing
Omnistu is an independent software development project. 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.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com