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

Zomato Clone Development Company: What to Check Before You Hire

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 / Typical scoping questions

Typical scoping questions

What does a crawler get?

  • Ask them to view source on a category page while you watch. Rendered content means an organic channel; an empty shell means every visitor you ever have is one you paid for.

Where does the cuisine list live?

  • Rows in a table, or constants in code. Your market's vocabulary will be wrong on day one and you will want to fix it on day two, so the cost of that correction matters more than the initial list.

Who is allowed to leave a rating?

  • Anyone, or somebody whose order actually happened. Ratings feed the filter customers sort by, so an untrustworthy rating is not cosmetic, it is a broken ranking you cannot repair later.

Who decides what appears first?

  • Ask them to move a restaurant to the top of the feed in front of you. If nobody can, you have no inventory to sell and no answer for the restaurant asking why it is not there.

What did a featured position earn?

  • Ask for the report rather than the feature. Placement that is not scheduled and measured is not a revenue line, it is a favour you did for a restaurant and forgot to price.

Does search sort the whole catalogue?

  • Ranking over a set already scoped to the ordering zone stays cheap as listings grow. Sorting everything to show somebody eight results is a cost you pay on every browse forever.

Where do the photographs live?

  • A discovery catalogue is mostly images. If storage is not selectable at runtime with a fallback, growth in media eventually becomes a migration rather than a setting.

Can a restaurant edit its own listing?

  • If updates route through your support desk, your catalogue goes stale at exactly the rate you grow. A real store panel is what keeps hours, menus and photos current without anybody chasing.

What is on your list of what is missing?

  • Any provider whose list is empty either has not looked or is not telling you. Ours names database-backed search, no reservation engine, test mode and permissive cross-origin rules, further down this page.
03 / A proposed launch process

A proposed launch process, without time promises

Define the first service area

  • Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.

Apply your branding

  • Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.

Set the commercial rules

  • Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.

Connect your own accounts

  • Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.
04 / Red Flags That Mean

Red Flags That Mean Walk Away

Five answers that should end the conversation

  • "Search engines can render JavaScript now." Sometimes, unevenly, and slower. On a catalogue whose entire economic argument is organic reach, that is not a risk worth taking to save the work of rendering on the server.
  • "We'll seed your catalogue for you." Ask where the data comes from and who owns it. A catalogue assembled from somebody else's listings is a licensing problem you inherit, and no vendor can hand you a catalogue that is legitimately yours.
  • "Anyone can leave a review, it drives engagement." It drives a ranking nobody trusts. Once ratings are known to be gameable the filter customers sort by is worthless, and a rating system cannot be made credible retroactively.
  • "The algorithm decides what ranks." Then you cannot sell a position, cannot explain a listing's placement to the restaurant paying you, and cannot correct it when it is obviously wrong. Owning the ranking is the business.
05 / What a Discovery Platform

What a Discovery Platform Has to Get Right

The machinery that separates a catalogue people find from an ordering app with a search box.

06 / What We Have

What We Have Not Done Yet

Six items, stated before a purchase rather than after one.

What does not arrive is the catalogue

  • No codebase supplies listings, menus, hours or photographs, and a vendor offering to seed them is offering you data somebody else owns. Gathering the catalogue is field and content work, it is the real cost of a discovery platform, and it is entirely yours.

Search runs against the database

  • Index-hinted scopes with eager-loading discipline over a zone-scoped set, which is right for most catalogues and stays fast well past city scale. Typo tolerance, synonyms, relevance tuning and faceted search need a dedicated engine, and that is one possible extension point.

No table reservation engine

  • 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. On a platform built to be publicly readable, closing those before the first crawler arrives is worth scheduling early.

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. Clone names the functional target rather than the provenance of the code: this is an original implementation on Laravel, Next.js and Flutter, with no affiliation to Zomato or Eternal.
07 / A Delivered Engagement

A Delivered Engagement, and What It Was Not

A custom-built delivery platform: three applications, six isolated third-party integrations and three environments, with the source transferred to the client at handover.

08 / Hire on the answers

Hire on the answers, not the deck

Most of what separates a discovery platform from an ordering app can be checked in ten minutes: view source, rename a cuisine, sell a position, then read what it earned.

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

10 / 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