The quiet cost of an unreadable menu
A couple from Munich sits down in a trattoria in Verona. The menu is in Italian. They recognise four words: pizza, pasta, tiramisù, bruschetta. They order two of them.
The kitchen's best dish — the braised veal shank the chef is actually known for — was on the same page. They did not order it because they could not tell what it was, and asking felt like work.
This happens every service in every tourist town, and it never shows up as a complaint. The guests leave satisfied. They just spent less than they would have.
What actually goes wrong
Three separate things, and only one of them is about money.
Guests default to the familiar. Faced with a list they cannot parse, people pick the safe option. Recognisable dishes are almost always the cheap ones — the margherita, the carbonara, the schnitzel. Your higher-margin dishes require a description the guest can read.
Nobody orders what they cannot pronounce. There is a real reluctance to point at an unfamiliar word and mispronounce it in front of a waiter and a partner. Guests avoid the awkwardness by ordering something they can say out loud.
Allergies and diets become guesswork. A vegetarian who cannot read the ingredients orders the dish that is obviously vegetarian. Someone avoiding gluten or nuts may skip the meal entirely. In tourist areas, a large share of dietary problems are language problems.
Why paper translation rarely works
Most restaurants in tourist areas know this and have tried to fix it. The usual attempts run into the same walls.
A second printed menu in English. Doubles your printing bill, and English does not help the French, Czech or Japanese guest. It also doubles the reprinting work every time a price changes, which is why the English version is so often out of date.
A translated PDF on the wall or a link. Better, but a PDF on a phone means pinching and zooming through a document designed for A4. Guests give up.
A stack of laminated menus in four languages. Now you are storing and cleaning four sets of menus, and the moment a dish changes, all four are wrong at once.
The common failure is the same: paper forces you to choose a fixed number of languages in advance, and to pay again every time anything changes.
What changes with a digital menu
A digital menu removes the constraint that made translation expensive. The dish exists once; each language is a field on that dish rather than a separate physical object.
The guest picks their own language. They scan the code and switch to their language in one tap. You do not have to guess who is coming through the door in August.
Adding a language costs nothing to print. Deciding to serve Czech guests next season is a translation task, not a printing job. There is no minimum order and no leftover stock when you change a price.
Prices and dishes stay in sync across all languages. You change the price once and it is correct in every language simultaneously. The classic tourist-town problem — the English menu still showing last year's prices — simply cannot happen.
Descriptions can do their job. This is the part most owners underestimate. In a printed menu, space forces you to write "Ossobuco — 24€". On a screen you can write what it actually is: slow-braised veal shank, saffron risotto, gremolata. That sentence is the difference between a guest skipping the dish and ordering it.
Which languages are worth having
More is not automatically better. Every language you enable is a field to fill for every dish, and an empty field looks worse than no translation at all.
A practical way to decide:
Start with where your guests actually come from. Not where you imagine they come from — check. Your card terminal shows issuing countries. Your booking system shows nationalities. Hotel receptions nearby will tell you who they are sending. Most restaurants find two or three dominant nationalities and a long tail.
Always include English. It is the fallback for everyone whose language you do not cover — the Dutch, Scandinavian and Polish guests will read English comfortably.
Add the languages of your neighbours. Northern Italy gets Germans and Austrians. The French Riviera gets Italians and British. Prague gets Germans and Poles. Geography predicts your guest list better than global tourism statistics.
Stop before you can no longer maintain them. Four well-written languages beat nine half-filled ones. You can always add another next season.
What to translate, and how
Translate the description, not just the name. "Ossobuco" translated to "Ossobuco" helps nobody. The description is where the sale happens.
Keep dish names in the original where they carry meaning. A German guest wants to know they are eating ossobuco — that is part of the experience. Give the original name and explain it underneath. This is a menu, not a dictionary.
Do not translate literally. Culinary terms rarely map word for word. Guanciale is not bacon, and calling it that will disappoint someone. Describe it: cured pork cheek.
Have a native speaker read it once. Machine translation has become good enough for a first draft, but it still produces phrases that read as slightly wrong to a native, and a menu that reads slightly wrong makes the restaurant feel slightly cheap. One reading by a native speaker fixes this for good.
The commercial case, briefly
The dishes you most want to sell are the ones that need explaining. A guest who cannot read the explanation orders the cheapest recognisable thing on the page and leaves. That is not a lost customer — it is a smaller bill from a satisfied one, which is why it never appears in any complaint or review.
Removing the language barrier does not require convincing anyone of anything. It just lets the guest see what you already offer.
QR-View shows your menu in up to 19 languages — the guest picks theirs when they scan. See a real menu or start a free 15-day trial.