In short: menuQR started with a QR code that led to a stamp-sized PDF. The fix: the PDF stays as it is, the code stays the same — only the content behind it is swapped. Hosting is in Germany, no subscription renews itself, and the seven trial days carry no obligation.
It began like so many good ideas: with a bad mood and an empty stomach.
A restaurant, a table, a QR code. I scan it — and nothing happens. Then a PDF loads, the size of a postage stamp. I zoom, swipe and zoom again. Somewhere between the starter and despair a thought arrives that will not leave: this cannot be that hard.
Spoiler: it was harder. Just not the way I expected.
The real problem sits behind the counter
I talked to restaurateurs. A lot. And the problem was not the guests. It was the office behind the kitchen. The menu had long been finished as a PDF — lovingly designed, with last month's prices. Every change meant: reprint, re-laminate, get annoyed again. And the digital options? They wanted you to retype the entire menu. Dish by dish. As if a restaurateur had nothing else to do.
So I turned the recipe around: the PDF stays. The QR code stays. Only the content behind it changes.
Under the hood: simple only works when it is built well
Simple for the user almost always means elaborate underneath. That is why the printed code holds a dynamic link instead of a rigid pointer to a file. Upload a new PDF and you swap the content. The code on the table stays the same, whether day one or season ten.
menuQR has been a SaaS application from the start: one platform for many restaurants. Every account is cleanly separated, updates reach everyone automatically, nobody has to install or wait for anything. The guest menu is a lean web app rather than a native one. It opens in the browser and works on any smartphone, even on the weak wifi in the corner by the window.
Then come the parts you do not see but notice: encrypted storage, servers in Germany and subscription management where cancelling is as easy as starting. The analytics show views, time spent and peak times by hour and weekday. They are built to help restaurateurs and not to spy on guests.
Design is not decoration, it is hospitality
A guest at the table has three seconds of patience and one free hand. That is what the menu page is built for: designed for the phone first, readable without zoom acrobatics and without pop-ups between guest and dish.
The dashboard for restaurateurs follows one clear rule: what you need daily is one click away. Everything else stays out of the way. Upload, look, done.
A QR code with personality
The most common question after the first test: “Can the code look like us, too?” It can. There are six templates or free styling: shape of the dots and markers, colours, frames, corner radius and, in the Enterprise plan, your own logo in the centre. A code standing on a table is part of the brand, not just technology.
The same goes for menuQR itself. Name, logo and language should work just like the product: short, clear and with a wink. That is why our blog is called à la carte and not “Resource Center”.
What was never negotiable
Data stays in Germany. There is no subscription that quietly renews itself. And there are no tricks in the fine print. Test for seven days, then decide. Full stop.
menuQR today is exactly what I wished for at that table back then: one scan and the menu is there.
The rest is a matter of taste.
Robin Steppat, founder and developer of menuQR
Who builds the product, what he did before and how you can check it is on the developer page.