What EMenuScan is, who it is for, and what it deliberately does not do

The one thing we set out to fix

A restaurant does not lose money on the food. It loses it in the gap between a guest deciding something and the system finding out — the wait to be noticed, the order carried in somebody's head, the bill assembled from three slips at the counter, and the month that ends with nobody quite knowing what sold.

Everything in the product exists to close one of those four gaps. When we are deciding whether to build something, that is the test it has to pass.

How it is built, and why that matters to you

It is a web application. There is nothing to install on a terminal, no licence per till, and no app for your guests to download — any phone, tablet or laptop with a browser will do, and an existing thermal printer will print the bills.

It is also a single system rather than a set of tools that talk to each other. Ordering, the floor, billing, delivery cash, offers, ratings, staff and reporting are the same product and the same login, which is why a price is changed once and a report does not need reconciling against a second system.

• Runs in a browser on hardware you already own
• One login for every branch, with data scoped per branch
• Indian Standard Time and rupees, wherever the server lives
• Every report exportable to CSV, whenever you want it

What we will not do with your data

Your menu, your customers, their numbers and order history, your invoices and your sales figures belong to your restaurant account. One restaurant's data is never visible to another. We do not sell, rent or share it, there is no advertising in the product, and your guests are not being tracked by anybody else while they order.

The two legal documents say this in the language a contract needs, and they are worth reading before you pay rather than after.

• Branch users only ever see their own branch
• Every state-changing action in the portal is written to an audit log
• The back office can be restricted to your own network by IP address
• Delivery payment photographs are destroyed after ten days

What it deliberately does not do

This list is here because the fastest way to lose a customer is to let them assume something and find out in month two. None of the following is a roadmap item being coyly described — they are things the product does not do.

• No payment gateway: your takings never pass through us
• No offline mode: ordering and billing need a connection
• No inventory, purchasing or recipe costing, so no margin reporting
• No GST return filing, and no statutory payroll contributions or income tax
• No marketplace: nobody browses a list of restaurants and finds you here

Everything claimed anywhere on this site is built and running today. Where a capability costs more than the base plan, the page saying so also says the price.

How to check any of this

Ask. A demo is twenty minutes with your own menu on the screen, and the fastest way to find out whether a product fits your floor is to make somebody show you the part you are sceptical about. Bring the awkward question — the one about the bill, the tax, the rider's cash or what happens when the internet drops.