All articles

When a QR menu is the wrong idea

We build QR menus, and there are restaurants that should not have one. Here is how to tell which you are, and how to do it so guests do not resent it.

Search “is a QR menu worth it” and every result on the first page is written by a company that sells QR menus. They all conclude yes. One of them leads with a statistic that 78% of customers prefer scanning to paper.

Then look at what comes up alongside them: Reddit threads titled “QR Code Menus Are Ruining Dining Out!”, and restaurant owners telling each other that if you put a PDF behind a code, guests will hate it.

Both of those things are on the same page of results, and only one of them is written by someone with nothing to sell.

We build QR menus. Here is the version I would give you across a table.

The cases where it is genuinely the wrong call

Your dining room is dim and your guests are older. This is the complaint underneath most of the complaints. A paper menu works in candlelight. A phone at minimum brightness with small type does not, and the guest who cannot read it will not tell you. They will order the thing they recognise and leave slightly annoyed.

Your restaurant is the expensive one. People paying a lot for dinner are partly paying to be looked after. Handing them a task is the opposite. There is a reason the QR menu spread through cafes and casual places and never really landed in fine dining.

Your menu barely changes. The strongest argument for a digital menu is that you can change it. If you have printed the same card for six years because the food does not change, the main benefit does not apply to you and you are taking on the drawbacks for nothing.

Your signal is bad. Basements, thick stone walls, tavernas up a hill. If the page takes eight seconds to load on the venue’s own patchy signal, you have replaced a menu with a loading spinner. Test this in the actual room before deciding, not at home.

The mistake that causes most of the hatred

Almost every “I hate QR menus” complaint is not really about QR codes. It is about a PDF behind a QR code.

A PDF on a phone is a genuinely bad experience. You get a full page shrunk to postcard size, and then you pinch and drag around it looking for the starters like you are reading a map in a car. It is worse than paper in every way, which is why people are annoyed.

A menu built as a proper page — sections you can tap, prices that are readable without zooming, photos of the food — is a different object that happens to be reached the same way. Guests do not complain about those, and when they do, it is usually one of the four reasons above rather than the format.

If you take one thing from this: never put a PDF behind the code. If that is the only option available to you, keep the paper.

When it is clearly right

  • Your prices move. Fish, daily specials, anything seasonal. Reprinting is the cost you are actually removing, and it is a real one.
  • You have good photos of the food. This is the one advantage paper cannot match at any price, and it demonstrably shifts what people order.
  • You are busy and understaffed. Guests reading while they wait is genuine relief on a full Saturday.
  • You serve visitors. A menu that can be read in another language without anyone being asked to translate at the table is worth a great deal in a tourist town, in both directions.

The arrangement that annoys nobody

Do both. Keep a stack of paper menus, put the code on the table as well, and let people choose. The cost of printing twenty menus instead of two hundred is nothing, and it removes the entire objection at a stroke.

The owners who get complaints are the ones who took the paper away to save money and presented it to guests as an upgrade. Guests can tell. Keep some paper, and the digital menu stops being something imposed on people and becomes something available to them.

Why we would tell you not to buy this

Because a restaurant that installs a QR menu into the wrong room ends up with annoyed guests, blames the QR menu, and rips it out in three months. That is worse for us than never building it.

Every article on page one of that search is written by a company whose revenue depends on the answer being yes. Ours does too. It is still not always yes.