UberEats Clone Features: What Happens After the Order
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.
Clone vs Generic Script vs Building From Scratch
Where the proposed base sits against the original platform and a from-scratch build. The Omnistu column is proposed scope, confirmed in writing before any work starts; the scratch column is the work you take on yourself.
| What decides it | Proposed Omnistu base | Generic delivery script |
|---|---|---|
| Time to a working platform | Deployment timing agreed in writing before work starts | Ask for a written timeline |
| What a rate change does to old orders | Proposed: nothing - the rate is frozen onto the settlement row | Ask whether rate history is stored per order |
| Opening a second city | Proposed: draw a zone, set its charges, in the admin | Ask whether a second city is configuration |
| Walk-in and phone trade | Proposed: a built-in till, landing in the same books | Ask whether walk-in orders land in the same reports |
| Changing commission or delivery fees | Proposed: a settings change, no code change | Ask whether fee changes need a deployment |
| Paying restaurants and riders | Proposed: scheduled runs with overlap locks | Ask how partner payouts are run |
| Split payment | Proposed: recorded as separate payment legs | Ask how split payments are recorded |
| Source code | Complete source proposed, no per-order royalty | Ask whether full, unencrypted source is included |
Swipe sideways to see all columns.
Scope areas for this kind of build
The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.
Feature Set by Role
The Customer
- Search by dish, restaurant or cuisine with filters for rating, price and delivery time, seeing only the restaurants that actually deliver to them. Sizes, extras, allergens and nutrition on the dish page, then checkout for delivery, collection or a table, with scheduled times, tips, coupons and loyalty points behind it.
The Restaurant
- An order board to accept and prepare, a menu editor with photos, sizes, extras and bulk upload, items marked sold out in one tap, opening hours and holiday schedules, staff logins beneath the owner, and earnings and payout history in one view rather than in an email from you.
The Counter
- A built-in till inside the restaurant panel for walk-in and phone orders, so trade that never touched the app still lands in the same books. Dine-in and collection run through the same order pipeline with the rider steps simply skipped, which is why nothing happens outside your reporting.
The Delivery Partner
- Accept or decline assigned orders, turn-by-turn navigation to pickup and drop-off, the delivery code that confirms handover, and a running view of earnings, incentives and the cash they are carrying. Cash collected is tracked against a ceiling you set per partner and per store.
The Operations Desk
- Approve restaurants and delivery partners, draw delivery areas on a map and set their charges, step into any live order to reassign, progress, cancel with an authority record or edit it before preparation locks, and approve or reject refund requests with the trail that follows.
The Finance Desk
- Scheduled disbursement for stores and delivery partners with the cadence, minimum amount, waiting period and week start all configurable, overlap locks intended to stop a slow run paying twice, a full statement per restaurant, and sales, commission, payout and tax reports that export.
- Staff accounts carry granular module permissions, so support sees orders, finance sees payouts and nobody sees more than they should. A separate vendor-employee layer scopes store staff below the owner.
How It Works, End to End
Six stages, each mapped to a named surface in the proposed design rather than a diagram drawn afterwards.
They enter an address
- Coverage resolves from zone polygons rather than a scan, so the customer sees only restaurants that actually serve them. Which stores appear, which riders can be assigned and which staff can act on the order all follow from the zone it belongs to.
They build an order
- Items carry variation option stock, add-on groups, attributes, allergens, tags and daily stock counters. Sizes, crusts, toppings and extras sit on the dish, and a restaurant marks something sold out in one tap without calling you to do it.
The restaurant works it
- The order lands on the board, is accepted and prepared, and every status transition writes its own named timestamp. Alongside it the built-in till takes walk-in and phone orders into the same pipeline, so counter trade is not invisible to your reports.
A partner carries it
- Delivery partners are filtered by zone before assignment, follow turn-by-turn navigation, and close the job with a one-time delivery code the customer reads out. With verification enabled a delivered status carries evidence rather than being a tap somebody made in the street.
The money settles
- Commission percentage and discount split are recorded on the transaction row at the time, and item revenue reads the order line rather than the current menu price. Scheduled disbursement pays stores and riders on your cadence with overlap locks, leaving a transaction history behind every run.
The loop closes
- What a customer paid becomes what the restaurant is owed becomes what you pay out, all from the same record of the order. Sales, commission, payout and tax reports each show what was actually charged at the time, so changing a rate later leaves your old numbers as recorded.
- Loyalty points, wallet credit, cashback and referral rewards run alongside the whole loop, at rates you set rather than rates we chose.
Every Feature Earns Its Place
Each row is here because a delivery marketplace stops working without it, not because a competitor lists it. The list describes the proposed design; what ships in your build is confirmed in the written scope.
| Module | Why it is in the base build |
|---|---|
| Commission frozen at settlement | If the rate is read live, changing it rewrites history. Freezing it onto the transaction row is what makes last quarter's numbers still true next quarter. |
| Zones as the operating unit | Coverage, dispatch, staff access, marketing and notifications all hang off the delivery area. It is the closest thing to a tenant boundary in the data model, and it is why a second city is a setting. |
| Overlap locks on payout runs | Disbursement is the one job where a retry costs real money. A lock is the difference between a slow run and paying every restaurant twice. |
| The built-in till | Walk-in and phone trade is real revenue. Left outside the platform it is invisible to commission, to reporting and to the restaurant's own payout statement. |
| Split tender as payment legs | Part wallet and part card is one order and two movements of money. Recorded as a single total it cannot be reconciled against either rail. |
| Cash ceilings per partner | A rider carrying too much float is an operational risk you cannot see until it goes wrong. The ceiling stops assigning cash orders before it does. |
| The business-model guard | Commission and subscription are stored as a setting with a guard that refuses to disable both at once, so store economics can never become undefined by a stray click. |
| Surface-isolated credentials | Customer tokens cannot reach store routes, and store and delivery tokens resolve through their own middleware, so five surfaces never share a trust boundary. |
Swipe sideways to see all columns.
Three further modules are proposed alongside: an AI ordering assistant, a short-video food feed, and full tax handling with per-order computation and exports.
The Technology Behind the Features
Conventional and easy to hire for, chosen so the operating knowledge is common rather than exotic.
Boundaries we state in writing for your build
Search is database-backed
- Discovery could start on well-indexed database queries rather than an external search service. That is the right trade until your catalogue is very large, and a dedicated engine is one possible extension point rather than pretended away.
Riders are yours, or a courier integration
- The delivery partner app assumes you run your own riders. Connecting an outside courier company, if you do not, is an integration scoped separately. So is publishing to the Apple App Store on your behalf, which depends on your developer identity rather than ours.
Where the scope stops
- Also outside the build: a storefront design tailored to a specific vertical, and any regulatory certification for a controlled category. Those are honest limits, and we will tell you plainly where your market needs work beyond configuration.
Frequently Asked Questions
Answers describe the proposed platform design and our delivery approach. Project-specific pricing, timelines and support terms are agreed in writing.
What do the three mobile apps actually do?
They are three separate apps, not one app wearing three hats. Customers get ordering, saved addresses, live tracking, chat, wallet, loyalty, referrals and a membership programme. Restaurants get incoming orders, menu management with photos and stock, a built-in till for walk-in and phone orders, staff logins, expenses and their payout history. Delivery partners get assigned jobs, navigation to pickup and drop-off, the delivery code, their daily earnings and the cash they are carrying.
How many payment gateways are included?
The proposed design covers the major gateway families - Stripe, PayPal, Razorpay and other regional options - with the exact set confirmed in the written scope. Alongside them sit the customer wallet, cash on delivery, and operator-defined offline payment methods with a proof-and-approval workflow. The checkout never hardcodes the list: clients read the active methods from configuration, so which gateways appear is deployment state rather than a code change.
Does a delivery leave any proof?
Yes, and it is an operator toggle rather than fixed behavior. With delivery verification enabled, a one-time code sits between arrival and completion, so a delivered status carries evidence rather than being a tap the partner made in the street. Alongside it, cash collected is tracked against a configured ceiling per delivery partner and per store, so a partner carrying too much float stops being assigned cash orders until they settle.
How does the platform handle more than one city?
Through zones, and this is the design decision that most affects how fast you can expand. A zone carries its own coverage polygon, its own delivery pricing, its own cash-on-delivery ceiling and its own notification topics. Which restaurants a customer sees, which riders get assigned, and which staff can act on an order all follow from the area it belongs to. Opening a second city means drawing another area and setting its charges.
Is it only for restaurant food?
The core vertical is food and the catalog model was shaped around it, but nothing in the order pipeline is food-exclusive. Items carry variation option stock, add-on groups, attributes, allergens, tags and daily stock counters, and groceries, pharmacy and general retail use exactly that machinery. Vertical differences surface as configuration: unit handling through attributes, and prescription-style instructions through the order note and delivery instruction fields.
How are stores and delivery partners paid?
Through scheduled disbursement commands, with the cadence, minimum amount, waiting period and week start all configurable from the console rather than set in a crontab. The runs carry overlap locks so a slow execution never pays twice, and every run leaves a transaction history behind it. The detail that makes the numbers trustworthy is that every order records what was actually charged at the time, rather than working it out again later from current rates.
More pages on this build
Overview
The full proposal on one page.
Features
Every proposed capability grouped by who touches it.
You are hereBusiness model
How a platform in this category earns, and which lever to switch on first.
Cost
What actually moves the budget, and how a scope-first written quote is put together.
Company
Agency versus freelancer versus Omnistu, plus the checks to run before hiring anyone.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by UberEats.
UberEats Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to UberEats, and how clients search for it.
Discuss your scope by message
Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.
