If your dining room sees tourists, then your menu is, in practice, multilingual whether you planned for it or not. The only question is whether the language work is done deliberately and well, or whether it falls on the server to translate dishes verbally, twenty times an evening, in three languages they half-speak.
This guide is written for restaurants whose guests come from beyond the local market: city centres, hotels, tourist routes, coastal areas, and any room that sits near a transit hub. It covers which languages are worth offering, why pure machine translation tends to backfire, how to handle allergens across languages safely, and the formats that actually work in service. It is practical, not aspirational.
Which languages should you offer?
The instinct is to add as many as possible. The right answer is the opposite: start with the languages that match your actual guests, in the order of frequency, and stop where the return drops.
The four-language baseline
For most tourist-facing restaurants in Europe, four languages cover 85 to 95% of incoming guests:
- The local language. Always the primary, always the source of truth for the kitchen and the staff.
- English. The default fallback for any guest who does not read the local language. North American, Northern European, Asian, and most international guests will use it.
- The dominant neighbour language. For France, this is often Spanish or Italian. For Portugal, Spanish. For Greece, Italian or German. Pick based on your actual guest mix, not assumption.
- One more, tied to your specific market. German in Mediterranean tourism. Portuguese in Brazilian-tourist destinations. Mandarin in luxury hotels. This last slot earns the most when chosen carefully.
When to add a fifth
A fifth language is worth adding only if you can name a clear guest segment that uses it consistently. "We sometimes see Russian guests" is not enough. "Our hotel partner books fifty Russian guests per month, twenty go to dinner" is.
What not to do
Do not auto-translate into thirty languages and call it a feature. A menu that opens in poor Korean to a Korean guest is worse than a menu that opens in English. Quality matters more than count.
Why machine translation alone backfires
Modern machine translation is good. It is not good enough to handle a restaurant menu without a human pass. This is the part most platforms gloss over, and it is the part that produces the famous menu-translation horror stories you have seen on social media.
Dish names lose their meaning
A French "tarte tatin" translated literally into English becomes "tatin tart" and into Mandarin becomes a string that means nothing to the guest. The traditional name should usually be preserved, with a short descriptive line under it ("upside-down caramelised apple tart"). Machine translation alone does not make this judgement; it just translates.
Cultural false friends
"Entrée" in French means starter. "Entrée" in American English means main course. A machine translation that keeps the word identical confuses American guests who then expect their starter to be the main meal. Human review catches this. Machines do not.
Ingredient nuance
"Veau" in French is veal. Machines occasionally translate it as "calf," which is technically correct and gastronomically wrong. The dish that reads "calf with cream sauce" in English is a dish no one orders. Small mistakes like this cost real revenue.
The hybrid approach
The format that works is machine translation as a draft, then human review by someone who speaks the target language and knows food. This is not expensive: a hundred-dish menu can be reviewed in two to three hours per language. It is the difference between a menu that sells and a menu that confuses.
Allergens across languages: the safety floor
This section is not optional. Allergen handling in a multilingual context is a safety topic, not a marketing topic, and a single translation mistake here can end a career.
Stick to the standard 14
EU allergen regulations define fourteen allergens (gluten, crustaceans, eggs, fish, peanuts, soy, milk, nuts, celery, mustard, sesame, sulphites, lupin, molluscs). Use this list as the canonical reference, exactly the same in every language, ideally with icons so the user can match them without reading.
Icons over words
An allergen icon set is the safest way to communicate across languages. A peanut icon is a peanut icon in any language. Words are where the risk hides: machine translation of "noisette" (hazelnut) into a generic "nut" loses the precision a guest with a specific allergy needs.
Always offer a verification path
Even with icons and translations, a guest with a serious allergy should be able to ask a staff member who knows the ingredient list. Print a small line on the menu, in every language: "Please ask your server about allergens or intolerances." This is both safer and more hospitable than relying entirely on the printed information.
Train the staff in one shared protocol
Multilingual menus do not replace staff training. They support it. Every server should know, in the local language, the exact ingredient profile of the five most-ordered dishes and the protocol for any uncertainty (ask the kitchen, never guess). This is the safety floor.
The format that works in service
Language matters, but format matters almost as much. A perfectly translated menu that is hard to switch into another language is a menu that guests do not switch.
One QR, one menu, many languages
The cleanest setup is a single QR code per table that opens the menu in the device's language by default, with a visible language switcher in the corner. The guest does not have to choose anything; the language they read in is already the language of their phone. The switcher is there as backup.
Photos as a universal layer
A good photo is a translation. A guest who does not read the language confidently can still point at the photo and order. For tourist-facing rooms, photos for the top 30 to 40% of dishes are worth the effort.
Pricing stays in the local currency
Do not convert prices into the guest's currency. This sounds helpful and is actually confusing: the conversion is approximate, the symbol creates noise, and the guest pays in local currency anyway. One currency, the local one, consistently.
Keep dish names in the original language
"Bouillabaisse" stays bouillabaisse in every translation. A short description below the name carries the explanation. This preserves the identity of the dish, signals authenticity to international guests, and avoids the awkward English-ified versions of traditional names.
What changes in service
A well-designed multilingual menu changes the dynamics of the floor. It is worth describing because it is the real return on the work.
Servers stop translating
The most exhausting thing for a server in a tourist room is explaining every dish in halting English, French, or Italian, twenty times a shift. With a proper multilingual menu, this work disappears almost entirely. Servers shift from translators to hosts. They have more time for actual hospitality.
Guests order with confidence
A guest who reads the menu in their own language orders things they would otherwise skip. They try the regional speciality. They choose the wine pairing. They add the dessert they understood. Average tickets in tourist-facing rooms rise 10 to 20% after a clean multilingual layer is added.
Allergen incidents drop
This is the quiet, important one. When guests can read allergen information in their language, ambiguity drops, and the rate of allergen-related incidents (orders sent back, kitchen interruptions, anxious guests) drops with it. Service runs calmer.
Reviews improve
International guests overwhelmingly mention the menu format in reviews when it works well. "We could read everything in English," "the allergen icons were great," "they had a Spanish menu." These small details show up in Google and TripAdvisor ratings, which then drive the next wave of bookings.
What to do this week
If you want to move from "we sort of have a translated menu" to a working multilingual layer, here is the realistic plan.
- List your top three guest languages, based on actual reservation data and observation, not assumption.
- Get a clean machine-translated draft of the full menu into those languages.
- Have each language reviewed by a native speaker who knows food. A few hours each.
- Add the standard 14 allergen icons to every relevant dish, identically in every language.
- Print one QR per table, with a language switcher in the digital menu. No need to print multiple paper versions.
- Brief the team for one shift: the menu now handles the language work, your job is hospitality and the verification path for allergens.
Done well, this is one focused week of effort, and it changes the way the room runs from the next service onward.