Feature scope - proposed scope
White Label Food Delivery App Features: The Platform Underneath
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
Six kinds of user, one backend that holds every business rule, and no role that has to squint at another role's screen.
The Customer
- Browse and search by dish, cuisine or restaurant, narrow by rating, price and delivery time, and see only kitchens that reach the address. Sizes, extras, allergens and nutrition sit on each dish. Checkout covers delivery, collection or a table, with a scheduled time, a tip, a coupon, loyalty points and wallet credit.
The Restaurant
- An order board for accepting and preparing, a menu editor with photos, sizes, extras and bulk upload, one-tap sold-out switches, opening hours and closures, staff logins under the owner, and a single view of earnings and payout history instead of a monthly email from you.
The Counter
- A till built into the restaurant panel rings up walk-in and phone orders, so trade that never touched the app still lands in your books. Table ordering and collection use the same order pipeline with the rider steps skipped, which leaves nothing happening outside your reports.
The Rider
- Accept or decline the jobs assigned, follow navigation to pickup and to the door, close the drop with the delivery code, and watch earnings, incentives and the cash in hand add up. Cash collected is measured against a ceiling you set for each rider and each restaurant.
The Operations Desk
- Approve restaurants and riders, draw delivery zones on a map with their charges, and step into any live order to reassign it, move it on, cancel it with a recorded authority or edit it before preparation locks. Refund requests are approved or rejected here, and the trail is kept.
The Finance Desk
- Payout runs for restaurants and riders, with cadence, minimum amount, waiting period and week start all set by you. Overlap locks stop a slow run from repeating. Each restaurant gets a full statement, and sales, commission, payout and tax reports export on demand.
- Staff roles carry module-level permissions, so support can see orders while finance sees payouts and nobody sees more than the job needs. A separate employee layer keeps restaurant staff scoped beneath the owner.
From First Address to Settled Payout
Seven stages, and every one maps to a named part of the code you receive.
An address goes in
- Coverage is resolved from zone polygons instead of scanning every restaurant, so the customer meets only kitchens that serve the spot. The zone also decides which riders can be assigned and which staff may touch the order afterwards.
A basket takes shape
- Dishes carry option stock, add-on groups, attributes, allergens, tags and a daily stock counter. Sizes, crusts and toppings live on the item, and a restaurant can mark something sold out itself, without opening a ticket with you.
Payment is taken
- Thirteen gateways sit beside wallet credit, cash on delivery under a limit you set and offline methods you define, each with proof and approval. A basket can be part wallet and part card, and each part is stored as its own payment leg instead of one blended figure.
The kitchen cooks
- The order reaches the board, gets accepted and prepared, and each status change is stamped with its own time. The till pushes counter and phone orders into the same pipeline, so they show up in reports rather than in a notebook.
A rider brings it
- Riders are filtered by zone before assignment, follow the map, and finish the job with a one-time code the customer reads out. With verification switched on, a delivered status carries evidence and is not just a tap made on a doorstep.
The money is settled
- Your commission percentage and the discount split are frozen onto the transaction row, and item revenue is read from the order line, not from today's menu price. Payout runs then pay restaurants and riders on your cadence, leaving a transaction history behind each run.
The books close
- What the customer paid becomes what the restaurant is owed, which becomes what you pay out, all read from one order record. Reports show the figures as they were charged, so raising a rate next quarter leaves this quarter's numbers alone.
- Loyalty points, wallet credit, cashback and referral rewards run alongside the whole loop, at rates you choose.
Every Feature Earns Its Place
Each row is here because a delivery marketplace breaks without it, not because a rival lists it.
Three further modules attach without threading through the core: an AI ordering assistant, a short-video food feed, and tax handling with per-order computation and exports.
The Technology Behind the Features
Deliberately ordinary, so the person you hire to extend it does not have to be us.
One Laravel application owns every rule and the five surfaces are presentation layers over a single versioned API. That is why the clients agree with one another about every order.
Boundaries we state in writing for your build
No restaurants, no riders, no fleet
- No restaurants, menus, riders or delivery vehicles come with the platform. Signing and verifying restaurants, food safety and allergen accuracy, rider classification and insurance, and the tax and consumer rules of every market you serve are your responsibility.
Search, fleets and iOS are extras
- Discovery is database-backed by design, with an external engine one possible extension point. Connecting an outside logistics provider is a scoped integration. The Flutter source builds for iOS, but signing, store listings and release management are delivery work.
Place one real order, then follow the money
Order on the website, accept it as the restaurant, watch it travel through delivery, then open the same order in the console and see your commission and the restaurant's payout line calculated against it.
Four apps. One set of books. Your source.
Customer, restaurant and rider apps plus your console, over a single backend and schema. The code is handed over outright and none of what the platform earns comes back to us.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Uber Eats , Talabat , Zomato , Grubhub , ChowNow , Goldbelly , or any other food delivery or restaurant ordering service.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com