Menu qrcode: what the square must survive on a real table

Forty cards go to the printer on Monday. By the second Saturday three carry a thumbprint of olive oil, one has been propped behind a candle nobody moves, and a table of four is holding a phone at arm's length waiting for the camera to catch. Nothing is broken in the code. The room around it is, and the room is the half nobody tests before paying for a print run.

What does "menu qrcode" mean?

Menu qrcode is the phrase operators in Italy type when they want guests reaching the menu by scanning instead of being handed a card, written as one word because that is how the term settled into daily use. The square itself is only an address, and the address is the least interesting half of the decision: what waits on the other side is what a guest judges.

A code stores a short string of characters and nothing else. Aim it at a PDF and you have handed the table a document to pinch and zoom. Aim it at a page that knows your prices, your opening hours and what the kitchen still has, and the same square becomes step one of an order.

Why does a code that scans on the office desk fail at table six?

Most scan failures are physical rather than digital. Printers work to a rough ratio of one to ten: a square read by a phone held 25 cm away wants to be about 2.5 cm across, and a code taped to a window and read from a metre away needs roughly 10 cm before anyone stops squinting at it.

Then the margin. Denso Wave, the company that invented the QR code, asks for a quiet zone of four blank modules on every side, so a designer who crops the square flush to the edge of a card has broken it without touching a single pixel inside. Gloss lamination throws the ceiling lights straight back at the lens; matte stock costs the same and does not. Dark ink on pale board scans in a dim room, while pale grey on cream looks refined in the artwork and dies under candlelight.

A code nobody can scan is worse than no code, because the guest never complains; they wait, then ask for a paper menu. So the designer refuses any colour pair under a 4:1 contrast ratio, and it re-checks that rule again on the way into the print pack, so even a colour typed in by hand is checked again before the print pack is made. I would rather argue with an owner about a shade of grey than let one table sit there tapping.

— Anzul Aqeel, founder of Get Menu

What the code points at decides everything after the scan

The page behind the square is what turns a scan into money. A menu built as a real page can be read with one thumb on a phone, the version of a site Google now indexes first. It can be dressed in any of 12 page layouts depending on how the menu reads, with a font picker and 57 colour themes so it looks like the restaurant instead of a template.

It also gets to be honest about the kitchen. Counts per item fall as orders arrive, so a dish that ran out at 21:10 stops being offered at 21:11 with nobody opening a laptop. Options carry their own prices, and required choices are enforced before a line joins the cart. Every line is re-priced from the live menu at checkout, so the number the guest sees is the number the kitchen reads. That holds even if somebody edited the price while the cart sat open on a table.

Who owns the square once the agency has gone?

A printed code is only as permanent as the address hidden inside it. Point that string at a generator's own domain and the cards belong to whoever keeps paying that generator, so a lapsed trial turns forty laminated cards into forty dead ends: perfect artwork, no destination.

Print codes that resolve to an address you control. Every restaurant here gets an address on getmenu.ae, included from day one, so the string on the card outlives whatever you decide about software two years from now. The customer list works on the same principle: names, numbers and order history export on any day, the last one included.

What changes in the dining room when the table can order for itself

Once the square carries the table number, the guest stops describing where they are sitting. A code is produced for every table, generated for you rather than pasted in one by one, and the print pack arrives by email in a shape a printer will accept without a phone call. The order arrives with the table attached, a ticket lands in the managers' group on WhatsApp, and the guest keeps a status page for that order without ever making a login.

The rest follows from the same scan. Group ordering lets six people at one table build a single bill from six phones. Scanning again on a later visit can earn a reward, tiers your regulars grow into can carry automatic discounts, and the card those regulars keep in Google Wallet comes with a designer for its colours and logo. Discounts never stack by accident; the best one wins and the rest stand down.

The numbers worth writing on the wall before the print run

Print costs are small and recur badly. Say forty cards cost €2 each, so €80, and a laminated card carrying prices costs that €80 again the day the pasta goes up. That is the real argument for putting the code on the card and the prices behind it.

The bigger number sits on the delivery marketplaces: 25–30% commission on the order value. At €100,000 of orders in a year, 28% is €28,000 gone before rent, and every one of those guests belongs to the app rather than to the dining room. Against that, an order taken through your own square costs the same monthly fee whether it is your 40th order or your 4,000th, because the fee is flat and the commission is 0%.

Two more worth knowing. The trial runs 15 days with no card details taken. Old order details (the pin, the note, the address) are cleared automatically after 120 days, while the sales dashboard keeps counting by day, item and channel and exports to a spreadsheet whenever the accountant asks.

Frequently asked questions

Do guests need to install anything to open a menu qrcode?

No. The phone camera opens a normal web page, the same way it opens any link. There is no app to install and nothing to sign into, which matters most for the guest who is at your table once, on holiday, on roaming data.

What is the difference between a qr menu that shows food and a qr code menu that takes the order?

A display-only qr menu ends at the picture: the guest reads, then waits for a waiter. An ordering page ends at a confirmed order with the table number attached, a kitchen ticket and a running total. The scan then replaces the second and third trips to the table, not just the paper card.

How do guests pay for what they order at the table?

Cash or your own card machine, at the table or at the door. No card details are held anywhere in the system, which removes a whole category of risk from the dining room and means the square on the table can never be a route to anyone's bank.

Can the same square work for delivery as well as the room?

Yes, with a different code. Table codes carry a table. A delivery code opens the same menu with a checkout that takes a GPS pin dropped at the address, a building and unit picked from a list, and a delivery fee set per building. One menu serves both services without maintaining two of anything.

Does a menu qrcode still work if the dining-room Wi-Fi is poor?

The page is built light: photos are compressed automatically and the layout is designed for a phone, so it loads on mobile data in most rooms. Give guests the Wi-Fi password anyway; a slow first load is the most common reason a table gives up and asks for the paper.