E menu: the four levels, and which one you need

An e menu is your menu shown on a screen instead of on paper. That definition covers four very different things, and the gap between them is the reason two restaurants can both say they have one and get completely different results.

This guide sets out the four levels, plainly, with what each costs you and what it gives back. It is written for independent restaurants and cafes, including those in Oman where a menu often has to work in two languages.

Level one: a picture of the printed menu

This is a photo or a PDF of the card you already print, put behind a link or a code. It is free and it takes an afternoon.

It is also where most restaurants stop, and it is barely better than paper. Nielsen Norman Group has studied this for two decades. Its advice is blunt: do not use PDFs to present content that could and should be a web page. PDFs load slowly, are hard to move around in, and are built for print rather than for a phone screen.

We have all felt this as a customer. You pinch, you zoom, the text goes sideways, you give up and ask the waiter anyway.

Speed matters here too. Google's own guidance for a page that feels quick is that the largest thing on screen should appear within 2.5 seconds for most visits. A photographed menu rarely gets close on a phone with average signal.

Level two: a proper web page

Now the menu is real text and images laid out for a phone. It can be read one-handed, it works in a browser with no app, and search engines can read it, which means it doubles as a simple restaurant website for a place that does not have one.

This is a genuine improvement and it is where a lot of good restaurants sit. What it still cannot do is know anything. It does not know the price you changed this morning unless somebody edited it, and it does not know that the last portion went at nine.

Level three: a menu that knows what is true right now

At this level the menu is connected to your kitchen's reality.

Prices are the ones you set today. Items that ran out are marked and cannot be ordered. Options and add-ons have their own prices, so a size or an extra is not a note somebody has to remember. If the menu is in a spreadsheet already, it uploads instead of being typed twice.

The value here is not glamour. It is the number of small corrections your staff stop making all evening.

Level four: a menu that takes the order

The last level is the one that changes the business. The e menu is also the ordering page. The customer chooses, confirms, and the order arrives in the kitchen as text, with the address or table number attached, without anyone repeating anything back down a phone line.

That is when a digital menu card stops being a document and starts being a member of staff.

"We started by putting menus on phones and thought that was the product. Restaurants kept asking the same follow-up question: fine, now how does the order get to my kitchen? The answer to that question turned out to be the whole business." — Anzul Aqeel, founder of Get Menu

What level four looks like in Get Menu

Here is what a restaurant gets, in the order a customer meets it.

Your menu lives at your own address on getmenu.ae, included in every plan, and opens as an ordinary web page. There are 12 page layouts, colour themes and a font picker, so a short drinks list and a long dinner card can each read properly, and Arabic item names and descriptions sit alongside English. For many small places this doubles as their restaurant website.

Items carry options and add-ons with their own prices, and a choice can be marked required so nothing is ordered half-specified. Photos are compressed automatically so pages stay quick to open. A whole menu can be uploaded from a spreadsheet rather than typed.

Stock counts fall as orders come in, options keep their own counts, and an item greys itself out at zero with nobody watching. Cancel an order and the stock comes back.

At checkout every line is priced again from your live menu, so the number on the screen and the number charged cannot drift apart, and a double tap cannot create two orders. You can set a minimum order value. Each order gets its own status page that the customer opens with no login.

About 2 seconds after the customer confirms, three messages go out. One is a confirmation to the customer. One is a ticket to your managers' group. One is a dispatch note to your riders' group, carrying the map pin dropped at checkout. Every message is logged with whether it arrived, and an SMS can go from your own SIM when WhatsApp cannot deliver.

For tables, a printed code per table means the order arrives with the table number attached, and a group can order from their own phones onto one bill. For delivery, the customer picks their building from a list you control and the fee can be different for each one.

For the customers who return, stamps can count per order or per amount spent, tiers your regulars grow into can carry a discount automatically, and rewards expire so they get used. The card sits in Google Wallet and updates itself, with the Apple version built and waiting on a certificate. Coupons carry caps, exclusions and expiry dates.

On the paperwork side, invoices carry your tax registration number as a PDF the customer downloads without logging in, sales export to a spreadsheet, and old order details are cleared automatically after 120 days. Your customer list is yours to export on any day.

Payment is cash or your own card machine at the door. There are no online payments, so no card details exist in the system at all. You have 15 days to try it, and nobody asks for a card.

Which level do you actually need

If you print a new menu more than twice a year, level two pays for itself in printing alone.

If your staff spend the evening telling customers what is unavailable, you need level three.

If a member of staff is typing orders that arrive as messages, you need level four. The same is true if your delivery customers order through somebody else's app. Levels one to three leave you with no record of who bought what.

There is a wider tour of everything around the menu in our guide to a restaurant management system. The table side is covered in the piece on how to scan qr to order. The free-code question is answered in our guide to a qr code menu free of charge.

Frequently asked questions

What is an e menu?

Your menu shown on a screen instead of on paper. It can be as basic as a photo of the printed card behind a link, or as complete as a page that shows live prices and takes the order.

Is a PDF menu good enough?

Rarely. It is slow on a phone, hard to read without pinching and zooming, and it cannot tell a customer that a dish has sold out. A normal web page beats it on every one of those points.

Do customers need an app to use an e menu?

No. It opens in the browser already on the phone, from a link or a printed code. In Get Menu the loyalty card also goes into the wallet the phone already has, so there is still nothing to install.

Can an e menu replace my restaurant website?

For many small restaurants it does. If the menu page carries your name, your hours, your location and a way to order, it answers almost everything a visitor came to find out.