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

Zomato Clone Features: Most Visitors Browse, and the Build Knows It

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, with the public ones built to be read rather than logged into.

The Browser

  • Somebody who is not ordering tonight. They arrive from a search engine on a server-rendered page, read a restaurant profile with photos, hours and the full menu, sort a category by rating or delivery time, and leave. This is the majority of your traffic, and it is the session most delivery platforms treat as a failed conversion.

The Diner

  • The same person on the night they order. Search by dish, restaurant, cuisine or category, filters for rating, price and delivery time, then delivery to the door, collection in person, or ordering at the table as a dine-in guest. Scheduled and repeat orders, wallet, loyalty points and a membership carrying member pricing sit underneath.

The Listed Restaurant

  • Its own profile and photos, its own menu with variations and add-ons, its own hours, holidays and delivery radius, all edited by the restaurant rather than by your support desk. It sees its orders, its ratings, its earnings and its payout history, which is what keeps a listing current without anybody chasing it.

The Editor

  • Whoever decides what people see first. Categories and cuisine taxonomy, the home feed and its offers, featured positions with their schedules, and the campaigns arranged around them. On a discovery platform this role is a commercial one rather than a design one, because placement is inventory.

The Delivery Partner

  • Assigned orders within their 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. Discovery does not change the delivery loop, and the delivery loop is where the operational cost of a browsing platform actually lands.

The Finance Desk

  • Sales, commission, placement, payout and tax reports that each show what was charged at the time. Placement revenue is reported alongside commission rather than tracked in a spreadsheet, which is the difference between selling positions and guessing what they were worth.
  • Console roles are scoped so editorial, support and finance each reach their own surface, and nobody reaches everything by default.
03 / How It Works

How It Works, End to End

Seven stages, beginning several weeks before anybody places an order.

Somebody finds a page

  • In the proposed design, the storefront renders on the server across a full route set with policies, registration funnels and tracking, so a crawler and a first-time visitor both receive content rather than a loading state. This is what makes organic search a channel that keeps working after a campaign budget stops.

They browse without ordering

  • Category and cuisine pages, restaurant profiles, photos, hours and full menus, all readable without an account. The read path is the one that is optimized, because on a discovery platform the common case is a visit that ends in nothing and still has to be cheap to serve.

They search the way people actually talk

  • By dish, by restaurant, by cuisine or by category, with filters for rating, price and delivery time. Categories and cuisines are rows rather than constants, so the vocabulary your market uses to describe its own food is an operator decision rather than something we chose for you.

You decide what is at the top

  • The home feed, its offers, its campaigns and its featured positions are arranged, scheduled and priced from the console. Placement becomes inventory you can sell and report on rather than a ranking you cannot inspect, and that is the revenue line discovery unlocks.

Eventually somebody orders

  • Delivery, collection or a table, with sizes, extras and allergen notes on the dish, multiple payment gateways plus wallet, cash and offline methods in the proposed scope, live tracking, proof of delivery and in-order chat between customer, store and rider on one record.

The rating goes back into the catalogue

  • A rating belongs to an order that actually happened, which is the structural defence against a listing being talked up or down by people who never ate there. It feeds the filter that decides what the next browser sees, which is how a discovery catalogue compounds.
04 / Why these

Every Feature Earns Its Place

Each row is here because a discovery platform stops working without it, not because a competitor lists it.

05 / Technology

The Technology Behind the Features

Chosen so the read path is cheap and the write path is guarded, which is the shape a browsing platform needs.

06 / Boundaries we state

Boundaries we state in writing for your build

Search runs against the database

  • Index-hinted scopes with eager-loading discipline, which is the right trade for most catalogues. Typo tolerance, synonyms, relevance tuning and faceted search at very large scale need a dedicated search engine, and that is one possible extension point rather than pretended away.

The catalogue starts empty

  • Importing listings from an external source, or wiring a paid maps and places provider for richer location data, are integrations scoped separately. Nothing in the platform seeds your catalogue, and any vendor implying they can hand you one is describing somebody else's data.
  • Proposed go-live checks: test-mode passcodes verifiably off in production, cross-origin rules narrowed to your domains, and transport and frame headers added at the server or middleware layer. Closing them is a pre-launch hardening pass quoted separately. Operator two-factor is scoped where your deployment needs it.

Answers from the proposed control map

  • When an acquirer or a partner sends a security questionnaire, we would answer from the documented control map agreed in the scope rather than improvising an answer for the occasion.
07 / The catalogue

The catalogue is the asset. You should own it.

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

Zomato Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Zomato, and how clients search for it.

08 / More pages

More pages on this build

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Zomato.
Zomato Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Zomato, and how clients search for it.

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