Watch a table of four visitors open a menu they cannot read. A long silence, then one of them appoints themselves translator and gets half of it wrong. Nobody orders a starter. Nobody asks what the house special is. Four plates arrive, all from the safest corner of the page, and the bill lands well under what it could have been. If you have a season, a station around the corner or a hotel across the road, the decision to translate your restaurant menu is not a gesture of hospitality. It is a revenue decision, and one of the cheapest on the table.
What an unreadable menu quietly costs you
Nobody complains about this. There is no bad review saying the menu defeated us. The table simply orders less and leaves, and the loss shows up as a slightly thin average check on a night that felt busy. That is what makes it expensive: from behind the pass it is invisible.
- Guests order what they understand. A description is a sales pitch — untranslated it is a wall of letters they skim past.
- Nobody asks a waiter mid-service to translate twelve dishes. They point at the one word they know, usually the cheapest safe option on the page.
- Starters, sides and desserts die first. Those are the impulse lines, and impulse needs comprehension.
- Anyone with an allergy or a dietary rule skips what they cannot verify. A translated allergen line turns a polite no into an order.
- It shows up in reviews, both directions. "Menu in English" is the phrase the next table reads before choosing you.
Pick your languages from your actual guests
The reflex is either to add English and stop, or to switch on six languages because they cost nothing extra. Neither is right. Every language you publish is a surface that has to stay true — a dish you change in one place and forget in five others. Two languages maintained properly beat six that drift.
- Ask the floor. Within a week your servers know which language they end up miming in most.
- Look at what is around you: a station, a marina, a conference hotel, a campsite. Each delivers a different crowd, and it arrives on a timetable.
- Check where bookings come from — the hotels nearby, the tour operators, the coach that stops on Thursdays.
- Use numbers if you have them. Scan analytics on yourmenu.app show how many people opened the menu, roughly where and when — a decent proxy for who is in the room in August versus November. Analytics sit on the Premium plan.
- Season beats the annual average. If your August is Dutch and Danish, a menu translated for the year misses the month that pays for your winter.
How to translate a restaurant menu: AI versus human
Machine translation crossed a threshold a few years ago, and most of a restaurant menu now sits comfortably above it. Prices, drinks, portion sizes, ordinary descriptive sentences — AI handles those fluently and instantly. Paying a human by the word for Coca-Cola 0.3l and mixed leaf salad means more money and more time to arrive in the same place.
Where it slips is precisely where your menu is most itself. Machines translate meaning, and a dish name is often not meaning at all — it is a proper noun, a regional word, a joke, a grandmother. Translated literally you get customs-declaration prose: ropa vieja becomes "old clothes", arme Ritter become "poor knights". The dish stops being a dish and turns into a description of one.
So the split is not AI or human. It is AI for the ninety percent, your own hands for the ten that carry your identity. That is the order of operations yourmenu.app is built around: auto-translate a language, then tune any individual line by hand. AI translations sit on the Premium plan at $19 a month; the menu itself is free.
The lines worth fixing by hand
You do not need a translator for the whole menu. Go through it once with a marker and pull out these.
- Dish names, always. Especially anything named after a place, a person or the house itself.
- Culture-bound ingredients with no clean equivalent: Spätzle, Quark, morcilla, sobrasada. A literal rendering is either wrong or unappetising, often both.
- Cuts and cooking methods. Butchery vocabulary is regional and machine translation flattens it — a specific cut becomes some piece of meat.
- Anything with wordplay in it. Humour does not survive the trip; rewrite it in the target language or leave it out.
- Portion and format words: Halbe, Schoppen, ración, media ración, tapa, sharing board. Get these wrong and you get an argument at the table about what arrived.
- Allergen and dietary wording. The badges are standardised — all 14 EU allergens, included on every plan — but any free text beside them deserves a careful read in each language.
- Heat and spice descriptions. Mild is not a fixed quantity across cultures, and this mistranslation comes straight back to the kitchen.
Dish names: keep yours, explain underneath
The strategy that works is the one museums use: keep the original, put the explanation beside it. Königsberger Klopse stays Königsberger Klopse, and underneath, in the guest's language, veal meatballs in a caper cream sauce with potatoes. Pulpo a feira stays pulpo a feira, and the line below explains the octopus, the paprika, the olive oil.
Two things happen. The guest can order out loud without embarrassment, which matters more than it sounds — people quietly avoid dishes whose names they cannot say to a waiter. And the name keeps doing its job as a piece of your place instead of being sanded into a generic description. It also spares your floor team translating a name backwards on the way to the pass.
Short rule: names stay, descriptions travel.
Currency belongs next to language
A guest reading a translated menu is usually running a second translation in their head — the price into their own money, with a rate they half remember. That hesitation lands on the lines you most want ordered: the second bottle, the sharing board, the top of the price range. A second currency saves them that mental sum. yourmenu.app supports multiple currencies, auto-converted or set by hand per currency, which matters when you would rather show a clean 25 than 24.37.
Keeping a multilingual menu current
This is where printed translations die. You translate once, in a quiet week in March. Then the menu moves: a supplier changes, a description gets reworded, prices go up in autumn. The original changes and the translation does not, so your English menu sells a dish you no longer serve at a price you no longer charge. On laminated card nothing catches that. The second menu yellows in the drawer under the till.
A live menu shrinks that problem down to a single edit, because there is only one menu. You change the dish once, from your phone — no second file, no second print run, no new QR code — and you re-run the translation on that one line instead of reprinting a second menu. Whoever scans next gets the current version. And because the code on your tables encodes a permanent short link rather than the menu address, you can rename the menu, move to a custom domain (Premium) or redesign it entirely, and the printed codes keep working.
Start with one language: the one your floor team keeps miming in. Building the menu costs nothing — one complete menu, a permanent QR code, allergen badges and instant updates are free forever, no credit card — and you add AI translations when the second language arrives. The tourist table is already sitting down. The only question is whether they can read what you are proud of.