The real reason people aren't scanning your QR menu

A café owner we work with called us last spring, frustrated. She'd switched to a QR menu, printed neat little cards for every table, and then watched half her customers still flag down a server to ask what the specials were. "The tech doesn't work," she said. "People won't use it."

So we drove over and sat at one of her tables for twenty minutes, just watching.

The tech worked fine. The card was the problem. It was the size of a business card, laid flat next to the salt, with the code printed maybe two centimeters across. To scan it you basically had to pick it up and hold your phone a hand's width away, squinting. Nobody wants to do that while they're chatting with the person across the table. So they didn't.

We swapped it that afternoon for a standing tent card, code about the size of a coaster, one line above it: "Menu here — just point your camera." The next weekend the servers stopped getting asked for paper menus. Same restaurant, same customers, same software. The only thing that changed was whether scanning felt like effort.

I bring this up because almost every "QR menus don't work" complaint I hear turns out to be a version of this. The link is fine. The menu is fine. What's broken is the ten seconds between a hungry person sitting down and them deciding it's easier to just ask.

Make the first step stupidly easy

Here's the uncomfortable truth: people are lazy at restaurants, and they should be. They came to relax, not to complete a task. If scanning your code takes any noticeable effort, a chunk of them will opt out, and the ones who opt out are usually the ones who'd have ordered the most.

So the code needs to be big, upright, and roughly at eye level when someone's seated. Flat on the table is the single most common mistake I see. A phone camera hates shooting straight down at a glossy surface under warm restaurant lighting; the glare kills it. Stand the code up and the whole problem disappears.

And put a real sentence next to it. Not "Scan QR" in tiny grey text. Something a person would actually say out loud. The café that fixed this used "Menu here — just point your camera," and it worked because it told people two things they didn't know they needed: where the menu is, and that they don't need a special app to get it.

That app fear is real, by the way. A surprising number of guests hesitate because they assume scanning means downloading something. If your menu opens straight in the browser (it should), say so.

The menu behind the code matters more than the code

Getting the scan is half of it. The other half is what loads.

If your menu takes six seconds to appear on a phone that's on shaky café wifi, you've lost them. They'll close the tab and ask a server anyway, and now you've got the worst of both worlds. Whatever you use to host the menu, load it yourself on an actual phone on cellular data, not your office desktop, and count the seconds. If it's slow, that's your project for the week.

Same goes for reading it. Tiny text you have to pinch to zoom, categories buried three taps deep, prices that don't line up. A menu that's annoying to read on a phone is worse than a laminated card, because at least the card doesn't make anyone feel dumb.

What I'd actually do this week

If you've got a QR menu and it's underperforming, don't rip it out. Do the boring stuff first. Stand the codes up. Make them bigger. Write a human sentence next to them. Then sit at your own table, order nothing, and try to use your menu like a stranger would. You'll spot the problem in about a minute, and it almost certainly won't be the technology.

The café owner texted me a few weeks after we made the changes. Turnover was up slightly, and the servers were less slammed during the rush because they weren't running menus back and forth. She never did believe it was the card. That's fine. It worked anyway.

If you're setting one up from scratch and want the menu side handled properly — fast on mobile, easy to read, easy to update — that's the part we built hayde.menu to do. But honestly, half of getting QR menus right has nothing to do with software. It's a stand-up card and one good sentence.