In this article
Your menu has been sitting there for years. The question was never whether it's good — it's who can actually read it.
Somewhere tonight, someone is sitting at one of your tables who doesn't read your menu comfortably. Maybe a tourist, maybe a new colleague from another country who lives three streets away. That person doesn't order the dish with the best margin or the best story — they order whatever looks the least risky, usually the cheapest and most recognisable thing on the page, and pay the bill without ever knowing what they missed.
This site has already written about menu psychology, about descriptions that sell, about allergen management, and about strategies for attracting tourists. None of those pieces are about the translation itself: what it actually costs to make a menu properly available in another language, what the law says about it, and what it costs you to simply never do it.
This isn't a "tourist problem" that only concerns Bruges or Amsterdam. It's a readability problem, and it shows up anywhere a guest sits down who doesn't have your language as their first one — including a village restaurant with one token English menu by the door.
Seven numbers, in this order: how big the problem actually is, what the law requires, what translation costs, what letting it go stale costs, why a guest orders the familiar dish over the best one, what the two sides look like in euros — with a calculator for your own numbers — and what one badly translated sentence costs you long after the menu itself has changed.
Why "we added an English menu" isn't enough
One extra language is a start, not a solution. It does nothing for the guest who reads German, Polish or Spanish but not English; it does nothing for the allergen line, which has to be specific and correct in the consumer's own language, not roughly right in the most common one; and it doesn't survive the first time your menu changes — which happens at least once a season in most kitchens.
A free translation tool solves that faster than an agency would, but trades one problem for another: it translates word by word instead of dish by dish, and it rarely recognises a fixed culinary term like "vol-au-vent" or "confit" as anything other than loose words. The result reads as machine-made to a native speaker within a sentence — which is exactly the signal that undermines trust in the rest of the menu too.
What actually holds up isn't a translated PDF, it's a small process: one source document in your own language, a translation per language that you maintain rather than deliver once, and a clear answer to the one question that outranks all the others — the allergen list. The rest of this article builds that process, number by number.
Free guide Everything about menu & drinks From pricing to the wine list — the complete guide to a menu that sells. Read the guide7 numbers your menu has never had to answer for
Each of these numbers stands on its own. Together they explain why a menu in one language costs more than it feels like it does.
1. How much of the room actually can't read your menu comfortably
Don't count "tourists". Count the guests reading your menu in a language that isn't their first — and that's a bigger group than most owners assume, even outside the high season. In a touristic city, that's whoever arrives by train or from the campsite. In every other city, it's the residents who live there without reading the local language fluently: the expat, the student, the new colleague from abroad.
European tourism research puts food and drink at roughly a quarter of a traveller's trip budget on average — up to 35% in pricier destinations, against around 15% in cheaper ones. That's not a nice-to-have on top of your revenue; in a touristic area it's a substantial share of it, and it's exactly the share your menu has never had to convince in a language it understands.
Do the maths yourself: if a third of your covers struggle with the menu as it stands today, that's not an edge case. That's a third of your room ordering with hesitation instead of appetite.
2. The rule that says "understandable" is not a guess
Regulation (EU) No 1169/2011 requires allergen information — the 14 EU allergens, including on a non-prepacked dish such as a restaurant menu item — to be available in writing, in a language the consumer can "easily understand". Member States may specify, within their own territory, which official language or languages that has to be.
That's not a slogan, it's the legal bar. An allergen line run through a free translation tool that turns "contains nuts" into something nobody recognises doesn't clear that bar — even if the rest of the menu reads perfectly well. It's the one line on your menu where "understandable enough" isn't a setting, it's an obligation.
And it's exactly the line that breaks first under a literal, unchecked translation: an allergen is a word with exactly one correct translation and no room for interpretation — precisely the kind of sentence a machine translation gets wrong most often.
3. What one menu, translated properly, actually costs per language
Professional translation from a menu's source language into most European languages runs roughly €0.11 to €0.20 per word for common language pairs today, with a minimum project fee of €45 to €85 — agencies charge that minimum to cover setup and proofreading, regardless of how short the text is.
An average menu runs about 400 to 600 words. At 480 words and €0.16 a word, that's roughly €77 per language, plus the minimum fee if you fall under that word count. Adding four languages to a menu is a few hundred euros, once. That's the price of fixing the problem, not of maintaining it.
Hold that number against what's still on the table in number six below — that's why this one feels small rather than heavy.
"Vol-au-vent" is already a French phrase — and shows exactly what a literal translation of it produces.
This particular wordplay is French — but every menu has at least one term that's just as fixed, and just as literally untranslatable.
4. What that same menu costs once you never touch it again
A menu that never changes doesn't exist — a seasonal shift, a few daily specials, a dish that gets swapped out: most kitchens adjust their menu at least once a season. Translate it once and leave that translation untouched afterwards, and within a few months the translated version no longer matches what's actually coming out of the kitchen.
That's not a cosmetic problem. It's the menu handed to a foreign guest that no longer matches what the server just described — the exact moment trust in the rest of the menu goes with it.
The fix isn't a full re-translation every season. It's a master file in your own language, where every change only sends the difference for translation — usually about a third of the menu, not the whole thing again.
5. Why a guest orders the familiar dish over the best one
There's an old, well-established finding in behavioural economics: people avoid an uncertain gamble more strongly than a known risk, even when the odds are identical — known as ambiguity aversion, since the Ellsberg paradox of 1961. A dish a guest can't read is exactly that kind of uncertain gamble: not "maybe expensive" or "maybe spicy", but entirely unknown.
On a menu a guest can't read comfortably, the dish that wins isn't the one with the best margin or the best story. It's the dish the guest already recognises — usually the cheapest, the most generic, the one that can't disappoint because there's nothing left to discover.
That's the dish in this article's title: not a bad dish, but the dish that would sell if the description convinced instead of confused.
Using this article's own assumptions: four languages, a 480-word menu, a quarter of the room hesitating.
Work it out further with the calculator in number six below — these are this article's starting numbers, not yours.
6. The maths most restaurants never actually do
Put the two amounts side by side and the pattern is clear: translating costs a few hundred euros, once, plus a fraction of that to maintain. What a menu that doesn't convince leaves on the table adds up over a whole year — faster than most owners expect at a busy venue.
Work it out below with your own numbers. Change the assumptions freely — the point isn't the exact figure, it's that the two columns are rarely anywhere near the same size.
7. The one sentence that outlives the menu it came from
A literally translated menu has produced the same kind of stories for decades: "chicken soap" instead of chicken soup, "fried witch" for a fish dish, a Spanish speciality that suddenly claims something entirely different in English. Funny for whoever reads it, less funny for the venue it happened at — because that one photo of that one sentence gets shared, exactly the way a fake review or a badly handled complaint does.
The effect doesn't stop at the laugh. Venues that reply to reviews consistently and well see, on average, a higher rating and more new reviews coming in; the same principle applies to a menu — correctness is the baseline a guest judges the rest of the experience against, and one visible mistake weighs more than ten correct lines.
That's the real risk of "we'll run it through a free tool quickly": not that it costs nothing, but that it only has to go wrong once to stay online for years.
Work it out for your own restaurant
Enter your own numbers. The assumptions underneath — word count, rate per word, seasonal changes — are fixed at a realistic middle value; change the five fields above and the result updates.
This isn't accounting, it's a thinking tool: the point isn't the exact euro figure, it's which column comes out bigger.
Translation cost against revenue left on the table
Enter your own figures — the rest does the maths.
—
Fixed assumptions: a menu of ~480 words, €0.16 per word plus a €70 minimum fee per language, four seasonal updates a year each changing about a third of the menu.
This is a thinking exercise with your own numbers, not an accounting guarantee — feel free to replace any assumption with your own experience.
What the calculator doesn't do is tell you which languages. Look at your own bookings and Google profile: the language guests already use to find you is almost always the language they'll want to read your menu in next.
And what it never replaces: the allergen list stays the one line that has to be correct, whatever the maths on the rest of the menu says.
How to actually do this tomorrow, without rebuilding the whole menu
Three steps, in this order — not because the rest doesn't matter, but because these three fix the most, fastest.
1. Translate what's mandatory and risky first
- The allergen list for every dish — the rule from number two above, not optional.
- Your ten best-selling or highest-margin dishes — the dish a guest currently skips because they don't understand it.
- Have a human proofread this, even if the rest is done by machine.
2. Work from one master file, not from copies
- One source document in your own language, with a version number and a date.
- Every language is a translation of that file, never of a previous translation — otherwise small errors stack up.
- Note per dish when it was last translated.
3. Only translate the difference at every change
- Mark what's new or changed in the master file at each seasonal update.
- Only send that part for translation — the number from step four above, not the whole menu again.
- Repeat this at every seasonal change, not just the big annual update.
The short answer
A menu in one language was never a choice you consciously made — it just never was a problem until someone sat across from you who couldn't read it. That moment happens more often than you'd think, and it costs you a bit of revenue, a bit of trust, or both, every single time.
The fix is small compared to what it solves: a few hundred euros, a master file, and the habit of translating the difference at every seasonal change instead of the whole menu.
Start with the allergen list — that one isn't a choice — and with your best dishes. The rest of the menu can follow once you see it working.