Scan menu barcode: what the square really is

Somebody walks into a print shop and asks for a barcode for their menu. The printer knows exactly what they mean and prints a square matrix, everyone is happy, and the word never gets corrected. It matters only once: at the moment an owner starts comparing suppliers and cannot tell which of two products is being described.

Is a menu barcode the same thing as a QR code?

In everyday speech, yes: when people say scan menu barcode they mean the square black-and-white matrix printed on a table card or a window, which a phone camera reads to open a menu. Technically they are different formats with different capacities, and the difference explains why one can carry a menu and the other cannot.

The striped barcode on a packet of instant noodles is a one-dimensional symbol holding 13 digits and nothing else. Those digits are not information about the product; GS1, the body that issues them, defines them as a lookup key into a product database. Point a phone at one and, at best, you get a number.

The square is two-dimensional and stores actual characters: enough to hold a web address comfortably, along with error correction that lets the code still read when part of it is scratched, wet or covered by a thumb. At the strongest of the correction levels Denso Wave built into the format, roughly 30% of the symbol can be damaged and the address still resolves. That property is why these survive on restaurant tables and the striped kind never would.

Why the distinction changes what you buy

A striped barcode needs a scanner and a database behind it, which is why supermarkets have both. A square needs neither: the address travels inside the code itself, and every phone sold for close to a decade has read it from the normal camera app with no extra software.

For a restaurant, that means the whole purchase is the destination. The printing is trivial and identical everywhere. What differs between one supplier and the next is what waits at the end of the address, and whether that address still belongs to you in two years.

What belongs behind the square

A live page rather than a document. Pointing the code at a PDF hands the guest a photograph of paper to pinch and zoom, which is worse than the paper was, because paper does not need two hands.

A working qr code menu knows things a document cannot. Counts run per option as well as per item (you can run out of one sauce without losing the whole dish) and an item at zero is simply not offered. A status page exists per order with no login needed, so a guest who closes the tab can still see where their food is. Where delivery is involved, the building and unit number are picked from a list rather than typed into a notes field somebody has to phone about, and a dispatch reaches the riders' group with the pin attached.

Print is permanent and software is not, which is the wrong way round for most restaurants. If the address inside the square belongs to whoever generated it, your printed cards stop working the day you stop paying them. That is the only part of this decision that cannot be undone cheaply.

— Anzul Aqeel, founder of Get Menu

Where to put it, and how many

One code per table if you have tables. A shared code loses the one piece of information that makes dine-in ordering work: where the guest is sitting. With a code per table the table is the address, and nothing about location has to be typed or asked.

A print pack is emailed ready for the printer, which sounds like a small convenience and removes a real blockage: the artwork job that sits on somebody's list for six months. Beyond the tables, the useful placements are the window for passers-by, the counter, and the sticker on a delivery bag. The bag sticker is the cheapest way to turn a marketplace order into a direct one next time.

What changes once orders arrive structured

The kitchen stops transcribing. An order that comes in as a chat message has to be read, interpreted and rewritten by somebody, and every one of those steps is a place to lose a modifier. An order that arrives from a qr menu is already structured, already priced and already attached to a name and number.

The messages then leave on their own: 3 messages per order in about 2 seconds (the guest's confirmation, the kitchen's ticket, the rider's dispatch) with nobody typing them. Because the order is a record rather than a conversation, the paperwork works too. The customer can download a PDF invoice without logging in, and stamps count automatically, with nobody having to mark an order delivered for one to register.

The commercial half follows the same logic. An aggregator's fee is a percentage of every ticket, usually somewhere in a 25% to 30% band, and it falls on a regular exactly as heavily as on a stranger. A code on the bag costs the price of a sticker.

The two things a square cannot fix

It cannot make a bad menu decidable, and it cannot make a full kitchen faster. Both get blamed on the technology within a month of installing it.

A menu that was confusing on paper is more confusing on a screen, because a phone shows eight lines at a time instead of forty. If the categories are wrong, fix them before printing anything; changing the sort order in the admin takes minutes, and reprinting does not. Capacity is the harder one. Taking orders faster than the pass can plate them simply moves the queue from the counter to the kitchen. The honest answer there is an auto-confirm timer for when the kitchen is flat out, plus a realistic time in the confirmation rather than an optimistic one.

What the square does add cheaply is a place to put an offer. Ten kinds of upsell sit behind it (pairings, ladders and thresholds) along with a secret menu hidden behind an unlock code for regulars who know to ask, which is a genuinely fun use of a printed sticker.

Frequently asked questions

Can a phone scan a normal striped barcode from a menu?

Some apps can read one, but there is nothing useful to read: a retail barcode is a 13-digit lookup key, not an address, so nothing opens. If a supplier offers a menu barcode and shows you stripes rather than a square, ask precisely what happens when a guest points a camera at it.

Do guests need an app to scan menu barcode squares?

No. The camera app on any recent phone recognises the square and offers the link as a banner. Requiring an install is the fastest way to lose a table, and any supplier who needs one should be asked why.

Can customers pay online?

No. Payment is cash or the restaurant's own card machine at the door or the counter. That is a deliberate boundary: nothing is charged inside the page, so no card details exist anywhere in the system to be stolen.

What happens to my printed cards if I change software later?

That depends entirely on whose address is inside the square, which is why it is worth deciding on day one. Codes here resolve to your own address on getmenu.ae, and the menu itself can be uploaded from a spreadsheet in one go rather than typed. The trial runs 15 days with no card required, and detailed order contents are cleared after 120 days.