Feature scope - proposed scope
Walmart Clone Features: Where Volume Retail Actually Breaks
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
Feature Set by Role
Customer
- Keyword search with autocomplete, filters and sorting
- Category tree of unlimited depth and a brand directory
- Guest basket tracked by session and merged on login
- Coupon, wallet credit and loyalty points applied together
Seller
- Registers with KYC, approved and suspendable by an operator
- Barcode and SKU management with bulk import and export
- Variant matrix with per-SKU price and stock
- Low-stock thresholds with alerts before the shelf empties
Delivery Agent
- First-class identity with KYC, approval and zone assignment
- Assignment feed with accept and reject
- Navigation to the seller for pickup, then to the buyer
- Live location broadcast while in transit
Operator
- Refund, withdrawal and moderation queues surfaced as daily actions
- Bulk approve and reject, because sellers import in thousands
- Cross-seller orders with a status timeline and edit history
- Manual status override with a recorded reason
How It Works, End to End
One basket, two sellers, a partial shipment and a return - traced through every state it passes and every balance it moves.
Two sellers, two queues, one order
- Each seller sees only their own lines, in a queue with accept and reject, from the web panel or the Android app. Stock moves per SKU, low-stock thresholds fire their alerts, and commission is visible on the seller wallet from the moment the line is accepted.
- This is the step most platforms get wrong. A delivery status per line means the fast seller's goods can be picked up, delivered and closed while the slower seller's line is still pending. The order itself remains open with a truthful state rather than being forced into one status that is wrong for half of it.
The agent verifies at the door
- An assignment appears in the agent feed with accept and reject. Navigation runs to the seller, then to the buyer. Checkpoints record picked up through to delivered, a one-time code is verified before handover, and on a cash order the collected amount lands on the agent's cash balance rather than mixing with earnings.
A return opens its own machine
- The buyer opens a return on one line with a reason and evidence. It walks a status machine of its own, which is what prevents a refund settling twice, and resolves as immediate wallet credit or back down the rail that took the payment. Loyalty points earned on that line reverse with it.
The books still agree at month end
- Commission on the returned line reverses automatically. Every balance movement across all four wallets paired with an append-only history row written in the same database transaction. Eight report types - sales, seller, product, customer, wallet, refund, withdrawal and tax - run over any date range and export to Excel, CSV or PDF.
- Nine statuses carry the order from pending payment to delivered, with cancelled, returned and failed ending it. Every transition is stamped with the actor, a note and a timestamp, and any operator edit leaves a field-level record - which is what makes a dispute three weeks later answerable.
Every Feature Earns Its Place
Feature lists are cheap. These are the ones that exist because a specific thing goes wrong in everyday retail without them.
None of these are exotic. They are the ten places where a marketplace that was demoed with fifty products stops working at fifty thousand.
The Technology Behind the Features
Deliberately ordinary choices, because the developers who maintain this after handover should already know all of it.
Why the index strategy matters more here than anywhere else
- Everything above transfers into your repository. There are no encrypted files and no licence callback of any kind.
Boundaries we state in writing for your build
Named as absent, or yours to own
- Store pickup Named on the hub as absent, not implied anywhere. If click-and-collect is part of your model, it is scoped work and it should be quoted before you buy rather than discovered after.
- Per-location stock Also named as absent. Stock is held per seller rather than per physical location, so a multi-outlet retailer wanting inventory split across branches is describing a custom module.
- SMS and email provider Integration-required - your accounts, your sender reputation, your deliverability. At volume this is a real recurring cost rather than a formality.
- Firebase project Push notifications across all three Android apps run through your own Firebase project.
More pages on this build
Five pages describing this proposed build. You are on Features.
Ready to run everyday retail at volume?
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Walmart .
Walmart Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Walmart, and how clients search for it.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com