PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Feature scope - proposed scope

Talabat Clone Features: A Market Is a Zone, Not a Deployment

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.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

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.

02 / Feature Set by Role

Feature Set by Role

Five surfaces over one Laravel backend, each of them aware of which market it is currently in.

The Customer

  • They set an address and get only the restaurants that deliver there, with the charge that applies in that area rather than a national figure. Search by dish, restaurant or cuisine with filters for rating, price and delivery time, then order for delivery, collection or a table, paying by card, wallet or cash depending on what their market offers.

The Restaurant

  • Menus, variations and add-ons edited by the restaurant itself, its own opening hours and holiday schedules, items marked sold out in one tap, staff logins beneath the owner, and its own earnings and payout history. A restaurant in one market never sees or affects a restaurant in another.

The Cash Rail

  • Cash on delivery treated as a first-class payment method rather than a fallback, because in much of this region it is what makes a first order possible at all. Ceilings are set per zone and per delivery partner, and what was collected is reconciled against what was expected instead of assumed.

The Delivery Partner

  • Assigned orders within their own zone, navigation to pickup and drop-off, proof of delivery at the door, and a running view of earnings and the cash they are carrying against their limit. Partners are filtered by zone before assignment, so dispatch cost stays bound to the area rather than to the size of your fleet.

The Country Manager

  • Console roles scoped so a manager reaches their own market and nothing beyond it. They draw coverage, set the charges, choose which gateways their customers see, edit the notification wording in their own language, and watch dispatch and cycle time for the area they are accountable for.

The Group Finance Desk

  • Scheduled disbursement across every market, computed from what was actually charged at the time, with overlap locks designed to stop a slow run paying twice. Sales, commission, payout and tax reports export per market or across the estate, and, in the proposed design, a rate changed in one country leaves every other country's history as recorded.
  • Staff accounts carry granular module permissions on top of market scope, so support sees orders, finance sees payouts, and nobody reaches everything by default.
03 / How It Works

How It Works, End to End

Seven stages, each one aware of which market the order belongs to.

The address decides the market

  • Coverage resolves from zone polygons rather than from a city field on a form. Which restaurants appear, what delivery costs, which payment methods show at checkout and which riders can be assigned all follow from the geometry the customer is standing inside.

They read it in their own language

  • The storefront runs on Next.js with MUI and Redux Toolkit carrying internationalization and right-to-left support in the build. Push, mail and SMS wording lives in editable templates keyed by message and user type, so an Arabic-first market is a language pack and a content pass rather than a second front end.

They build an order

  • Sizes, crusts, toppings, extras and allergen notes are modelled as variations rather than separate products, with daily stock counters and one-tap sold-out. The same catalogue machinery carries groceries, pharmacy lines and parcels when a market wants more than restaurants.

Cash is counted, not assumed

  • Where the order is cash, a ceiling applies per zone and per delivery partner, and a partner over their limit stops being assigned cash orders until they settle. Collected cash is reconciled against what was expected, so exposure is a number on a screen while it is still small.

The restaurant and the rider work it

  • The order lands on the store board, is accepted and prepared, and each transition writes its own named timestamp. Delivery partners are filtered by zone before assignment, follow navigation to both ends and close the job with proof of delivery at the door.

The market settles on its own terms

  • In the proposed design, commission percentage and discount split are recorded on the transaction row, and item revenue reads the order line rather than the current menu price. Disbursement runs on your cadence with overlap locks, and, in the proposed design, a rate you change in one country next month leaves every completed order in every country as recorded.
  • Offers, loyalty points, wallet credit and campaigns run alongside the whole loop, and a campaign can be scoped to a single market rather than fired across the estate.
04 / Why these

Every Feature Earns Its Place

Each row is here because a multi-market operator stops working without it, not because a competitor lists it.

Three additional Laravel modules sit beside the core and matter differently across an estate: tax computed per order and exported per market, an ordering assistant, and a short-video feed whose content can be scoped to the country it was made for.

05 / Technology

The Technology Behind the Features

Conventional and easy to hire for in every market you are likely to operate in.

Every business rule lives in the one Laravel application, with the five surfaces sitting over a single versioned API. That means one deploy, one schema and one set of rules across every country, which is exactly what a fork per market gives away.

06 / Boundaries we state

Boundaries we state in writing for your build

A zone is not a legal entity

  • The platform models markets, not companies. If your Egyptian operation must invoice as an Egyptian entity with its own tax registration and its own numbering, that is a corporate structure question the software does not answer, and it is scoped work rather than a settings tab.

Balances in several currencies

  • Pricing and collection per market are handled. Holding operator or vendor balances in more than one currency at once, and reconciling movements between them, is a genuine extension rather than a configuration choice, and it is the first thing to raise if your group settles centrally.

Somebody else's riders

  • The delivery partner app assumes you run your own fleet. In a country where you would rather not, connecting a third-party courier means mapping their states onto ours and handling their callbacks, which is integration work shaped by whatever API that company publishes.

Answers from the proposed control map

  • Also outside the build: single sign-on and a second factor for console staff, feeding order and payout rows into your own data warehouse, and standing behind an external assessment. Each is named here rather than discovered later, and each is quoted before it starts.
07 / One codebase

One codebase. As many markets as you can staff.

Customer, restaurant and delivery apps plus your console over one Laravel backend, with every market's charges, cash rules, gateways and language held as configuration you control.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Talabat.

09 / Next step

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.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead