Make QR code menu cards that actually get scanned

Making the image takes a minute in any free tool. Making the card is where restaurants lose the guest, and they lose them silently: a scan that fails looks exactly like a customer who was not hungry. This is a practical guide to the physical thing on the table, written for a cafe or restaurant that is about to send a file to a print shop.

By hand, or by the box

If you need one code for the front window, make it by hand and be done.

If you need one per table, do not. Thirty tables means thirty different codes, because the whole point of a code per table is that the table becomes the address and the ticket tells the kitchen which one. Get Menu generates a code for every table for you, has a designer so the card carries your own colours and logo, and emails a print pack ready for the printer. That turns an afternoon of copying and pasting into a file you forward.

Give the code white space

The commonest print mistake is crowding. Denso Wave, which invented the format, is specific about this in its printing guidance: a QR code "requires a four-module wide margin at all sides of a symbol". A module is one of the small squares the pattern is built from, so the clear border must be four of those squares wide.

Designers hate that empty band and often trim it, or run a logo into it. The code then scans on the screen mock-up and struggles on the table.

Print it big enough for a seated guest

Size is not decoration. Denso Wave's note on module size recommends for stable reading that each module is made up of four or more printer dots, and warns that every scanner has its own smallest readable module size. In plain terms: the smaller you print, the more the ink and the camera have to be perfect.

The honest test is the room, not the ruler. Print the card, put it on a real table, sit down normally and scan from where a guest's hand would be. If you lean in, print it larger.

Keep it dark on pale, and matte

Colour is where brand pride does the most damage. Pale grey on cream looks lovely and reads badly. The web accessibility standard asks for a contrast ratio of at least 4.5:1 for normal text, and a printed code deserves at least that much separation between the pattern and its background, for the same reason: the camera, like the eye, needs the two to be clearly different.

Two more habits worth keeping. Dark pattern on a light background, not the other way round. Matte lamination rather than gloss, because a glossy card under a Doha ceiling light throws a highlight straight across the pattern.

Tell the guest what it is

A bare square is a question. Two lines under it are an answer: what it opens, and what to do. Something like "Scan for our menu, order from your table" is enough. Add the table number in readable print as well, because staff use it and a guest sometimes reads it out.

The day the menu changes

This is the part that decides whether the print run was money well spent. If the code points at a file, a new price means a new file or a new print run. If it points at your own ordering page, the card never changes.

Behind ours, the menu lives on an address on getmenu.ae, included from day one, with items carrying options and add-ons with their own prices. Stock counts fall as orders arrive and an item goes sold out at zero on its own. Every line is priced again at checkout from the live menu, so a card printed in January cannot promise January's prices in June.

When a guest orders, 3 messages go out over WhatsApp: a confirmation to the customer, a ticket into the managers' group with the table on it, and a rider dispatch with the GPS pin dropped at checkout for anything going out of the door. Regulars grow into tiers, stamps turn into rewards, and the card sits in Google Wallet, updating itself with no app to install. After 120 days the system wipes the details of an old order by itself.

"We make a code per table and send the whole pack ready to print, rather than handing over one picture. One code repeated on every table turns every ticket into table one, and nobody notices until the food reaches the wrong people." — Tanzeel ur Rehman, co-founder of Get Menu

A short checklist before you send the file

Four-module clear border. Dark on pale, matte finish. Big enough to scan sitting down. Two lines of instruction and the table number. A destination you control, so the run lasts a season rather than a month.

You can try the whole set-up for 15 days without giving a card, and after that it is a flat monthly price with 0% commission on your sales. For more depth, our QR code menu guide covers the wider setup, menu boards covers the screens above the counter, and the restaurant app question covers why a web page beats asking guests to install something.

Frequently asked questions

Can I make a QR code menu card myself?

Yes, for one or two. Once you need a different code per table, generating and laying them out by hand is where mistakes creep in, and a duplicated code sends every order to the same table number.

How big should the code be on a table card?

Big enough to read from a seated position without leaning in. Print a test card and try it in your own light rather than trusting the size on screen.

Can I put my logo in the middle of the code?

A small one, usually. Keep it well inside the pattern, never in the four-module border, and always test the printed card afterwards rather than the design file.

Does the card need reprinting when prices change?

Not if the code opens your own ordering page. You change the price on the menu and every printed card follows. Cards only need reprinting when the code points at a fixed file.