Eight QR code mistakes restaurants still make

QR codes have been on restaurant tables long enough that most of the early problems should be solved. Yet walk into a dozen venues and you will still find the same mistakes: a code that leads nowhere, a code too small to scan, a PDF of last spring's menu, a code tucked where nobody looks. Each one sends guests waving for a server, asking for paper or simply giving up.

Most QR code mistakes are cheap to fix, and many take only an afternoon. The hard part is noticing them, because the people who work in a venue every day stop seeing the code on the table. This guide sets out the eight QR code mistakes restaurants still make, why each one matters and how to fix it, with a simple monthly check to catch them before guests do. Every figure in it is an example.

Many venues set up their QR codes in a hurry, often years ago, and have not looked at them closely since. The code was printed, stuck on the tables and forgotten. Meanwhile the menu changed, the website moved, the wifi was replaced and the tables were rearranged.

Others set them up with tools that were never meant to last: a free code generator, a link to a file in someone's personal cloud storage, a menu that only one person knows how to update. When that person leaves, or the free service changes its terms, the codes quietly stop working.

And because staff rarely scan their own codes, problems can go unnoticed for weeks. Guests notice first, and they tell servers, review sites or nobody at all.

The worst QR code mistake is a code that leads nowhere: a page that does not load, an error message or a site that has nothing to do with the venue. It happens when a code points to a link that has expired, a domain that has lapsed, a free service that has closed or a file that has been moved or deleted.

A dead link is worse than no code at all, because it wastes the guest's time and makes the venue look careless. Guests who meet one rarely try again on their next visit.

Fix it by making sure every code points to a link the venue controls and that will not expire: its own website, or a menu service it pays for and manages. Avoid free generators that send guests through their own short links, which can stop working without warning. Scan every code yourself regularly, from a guest's seat.

A code that is too small, too faint or too cluttered is hard for phone cameras to read. Guests hold their phones over it, move closer, move away, and eventually give up. It happens when codes are shrunk to fit a design, printed in pale colours, placed against a busy background or squeezed against a border.

Make codes large enough to scan easily from a seat, typically a few centimetres across for a code on the table. Print them dark on a light background, with clear space around them. Test them in the dining room's real light, at night, with several phones, including older ones.

A code that scans on the first try is a code guests use. A code that needs three attempts is a code guests learn to ignore.

The third mistake is still one of the most common: the code opens a PDF of the printed menu. Guests must zoom, scroll sideways and squint at two columns of small type. The file takes a while to download, and it cannot show what has sold out or what is on special tonight.

A PDF made sense as a quick fix years ago. Today, guests expect a menu built for their phone: a single column, readable text, sections they can jump to and photographs where they help. Our guide to QR menu design that is not a PDF on a phone covers what that looks like.

Replace the PDF with a live menu page. It will load faster, read better and stay up to date without anyone uploading a new file.

The fourth mistake matters most for venues where guests order or pay from the table. If every table has the same code, the menu cannot know where the guest is sitting, so orders and bill requests need extra steps, or reach the wrong place.

Give each table its own code, linked to that table, and show the table's number near the code. Then an order from table twelve arrives as table twelve's, and a guest asking for the bill from table twelve gets table twelve's bill.

Keep the codes and the table numbers in step. When tables are moved, renumbered or rearranged for an event, check that each code still matches its table. A stand for table twelve left on table fourteen sends the wrong orders to the wrong guests. Our guide to the table QR code: sticker, stand or menu card covers numbering and placement.

The fifth mistake is a code that still points at an old menu. The dishes have changed, the prices have gone up and the specials are from a different season, but the code still opens the menu someone uploaded months ago. Guests order dishes that no longer exist, or expect prices the venue no longer charges.

It happens when the code points to a file or page that must be replaced by hand every time the menu changes, and nobody does it. It is especially common where the printed menu is updated but the digital one is forgotten.

Fix it by pointing the code at a menu that updates itself: a live menu kept in the same place as the venue's other menus, so a change made once appears everywhere. Our guide to updating a QR menu in the middle of service covers keeping it current, even minute by minute.

The sixth mistake is QR code placement. A code on a poster by the door, a sticker flat in the middle of the table under the plates, a tiny code in the corner of a menu card: each is technically there and practically invisible. Guests sit down, look for a menu, do not see the code and ask a server.

Put the code where guests look when they sit down: facing the seats, at the edge of the table or on a stand, clear of plates, glasses and condiments. Add a few words saying what it does, such as "Scan for our menu and to order from your table".

Test it by sitting at every table. If you cannot see the code from every seat, guests cannot either.

The seventh mistake is forgetting the connection. A menu on a phone needs a signal, and many dining rooms have weak mobile coverage: basements, old buildings with thick walls, crowded rooms where everyone is using the same mast. Wifi and QR menus have to work together, and in many venues they do not.

If mobile coverage is weak, offer guest wifi, and make it easy to join: the network name and password printed near the code or on the table card, or a code that joins the network. Keep the guest network separate from the network the venue's own systems use.

Keep the menu light, too, so it loads on a weak connection. And always have an alternative: a paper menu for the corner table that never gets a signal, or a server who will take the order.

The eighth mistake is codes that are never checked after they go out. Stickers peel, cards get stained, stands go missing and codes fade. Occasionally, someone covers a genuine code with a fraudulent one that sends guests to a fake page, a form of phishing aimed at guests who trust the code on the table.

Make checking the codes part of the opening routine. Every code is in place, on the right table, clean, readable and genuine. Scan a few each day and all of them each week. Keep spares so a damaged code can be replaced in seconds.

Look out for codes that look different from the others, stickers placed over existing codes, or links that open somewhere unexpected. If guests report anything odd, check at once.

Behind all eight mistakes sits a quieter one: offering only the QR code. Some guests do not want to use their phones, some have flat batteries, some find small screens hard to read, and some simply prefer a printed menu and a conversation.

A venue that offers only a QR menu makes those guests feel unwelcome. A venue that offers the code alongside a printed menu, or a server happy to help, serves everyone.

Keep a few printed menus ready, train servers to offer them without hesitation, and make sure guests who order in person get the same care as those who order by phone.

Fixing the code itself is only half the job. Once guests scan, the menu behind the code has to load quickly, read well on a phone and help them find what they want. A perfect code that opens a slow, confusing menu still loses guests.

Good QR menu design means a single column that fits the screen, readable type, section tabs, search and filters, photographs where they help and prices that are easy to find. Our guide to a digital menu that loads before the drinks do covers speed, and our guide to the QR code menu, five years on covers what has worked for venues over time.

Test the code and the menu together, as a guest would, at a table, on mobile data.

Some codes work perfectly and still lose guests, because of what happens next. The code opens a page that asks guests to download an app, create an account or hand over an email address before they can see a single dish. Others open behind a wall of cookie banners and pop-ups that fill a small screen.

Each barrier costs guests. Someone who wanted to see the drinks list in ten seconds does not want to sign up for anything, and many will put the phone down and wait for a server.

Let guests see the menu the moment they scan. If you want their details, ask later, give them a reason, such as a receipt by email or news of the next tasting evening, and make it optional.

A QR menu should work for everyone at the table, including guests who find small screens hard. Some menus use tiny type that cannot be enlarged, pale grey text on white, or pictures of a printed page that screen readers cannot read aloud.

Check that the menu behind the code lets guests enlarge the text, uses strong contrast and works with the accessibility settings guests already use on their phones. Descriptions and prices should be real text, not images.

These are small details for the venue and large ones for the guest who needs them. A guest who cannot read the menu has to ask for help, and some will not ask at all.

If guests can order from the table using the code, the mistakes above matter even more. A dead link means no order at all. A missing table number means orders reaching the wrong table. An out-of-date menu means orders for dishes that no longer exist.

The ordering flow brings its own mistakes too: asking guests to sign in before they can see the menu, options that can be skipped, no confirmation that an order has been sent. Our guide to scan to order: the flow that actually works covers how to set the flow up so guests finish their orders.

Whatever the code does, make sure the team knows how it works, so they can help guests who get stuck.

A short monthly check catches most QR code mistakes before guests do:

It takes less than an hour in most venues, and it prevents weeks of quiet frustration.

Guests are the best source of information about QR code mistakes, but only if the venue listens. Servers hear the complaints first: "the code doesn't work", "I can't read this", "this isn't the menu you have". Make it easy for servers to pass those comments on, and act on them quickly.

Read reviews for mentions of the QR code, the menu or the wifi. A single mention may be bad luck; several suggest a real problem.

Watch the numbers too, where your menu system shows them: how many guests open the menu, how far they get and what they search for. A fall in the number of guests opening the menu can be the first sign that a code has stopped working.

An invented café installed QR codes during a busy year and has not looked at them since. A new member of staff scans one and finds it opens a PDF of a menu from two seasons ago, through a free link service that now shows an advert first. Several stickers are faded, and two tables have no code at all.

The café spends an afternoon on a QR check. It replaces the PDF with a live menu, puts a new code on every table linked to its own menu page and each table's number, prints the wifi details on each table card and adds the codes to its opening checklist. It keeps a stack of printed menus at the counter.

Within a few weeks, guests stop asking whether the menu is current, servers stop explaining how to read the PDF, and more guests order from their phones without help.

In servearound, each table has its own QR code, linked to that table, which can be downloaded as SVG or PNG for printing, and print designs can carry a code styled with the venue's own look. The code opens the venue's live digital menu for that table, not a PDF, so the dishes, prices and specials guests see are always today's, and a dish 86'd on the point of sale shows as sold out at once.

The menu itself is laid out for a phone, with category tabs, search, filters and photographs where the venue adds them, and its look is published by the venue with each version kept. The menu report shows how far each visit gets and what guests search for, which can show when something stops working. See the menus module, or get in touch to see it on your tables.

Dead links, codes too small or faint, PDFs, no table number, out-of-date menus, poor placement, weak wifi and codes nobody checks.

Usually because they point to a link that has expired, a free service that has changed or a file that has been moved or deleted.

Large enough to scan easily from a seat, often a few centimetres across, dark on a light background with clear space around it.

Yes. It is slow, hard to read on a phone and cannot stay current. A live menu page is better in every way.

If guests order or pay from the table, yes, so orders and bills reach the right table.

If mobile signal is weak, offer easy guest wifi with the details near the code, keep the menu light and keep paper menus for the worst spots.

A fraudulent sticker can be placed over a genuine code. Check codes daily, look for anything unusual and act on guests' reports.

Glance at them every day as part of opening, and do a full check of every code and the menu behind it every month.

No. Keep printed menus and servers ready for guests who prefer them.

QR code mistakes are cheap to fix and easy to miss. The eight that still cost venues orders are dead links, codes too small or faint, PDFs behind the code, no table number, menus that point at last spring, codes placed where guests do not look, wifi and QR menus that do not work together, and codes nobody checks for damage or tampering.

Point every code at a live menu the venue controls, give each table its own clearly placed and numbered code, make the menu behind it fast and built for a phone, support weak signals with easy guest wifi, keep printed menus for guests who prefer them, and run a short monthly check so guests never find the problem first.