Multi-language menus: when and how to add them

There is a moment most restaurants serving an international clientele eventually hit: a table of guests is squinting at the menu, the server is gesturing toward the lamb tagine, and everyone is smiling but nobody is ordering. The bilingual paper card is twice as crowded as a monolingual one. The server's English is good but not menu-good. And the kitchen has noticed that the international party orders the same dish every visit because it is the only one they can read.

Adding languages to your menu solves an obvious problem. It also introduces operational friction that catches restaurants off guard. This piece walks through the framework we recommend: which languages to add (and when), who should translate them, and how to keep them in sync so they do not silently rot.

Step 1: Diagnose whether you actually need this

The wrong reason to add a second language is "to look international." The right reason is "a non-trivial share of our guests do not order well in our local language."

Reasonable triggers:

• Tourist proximity. You are within a 20-minute walk of a station, port, hotel cluster, museum, or stadium that draws international visitors.
• Hotel restaurants. Your room-service and breakfast guests speak whatever languages the hotel attracts.
• University or business districts. International students and business travellers.
• Cuisine pull. Restaurants serving a specific national cuisine often draw diaspora and tourist customers from countries who recognise the cuisine but not necessarily the local language.

If none of those apply, your bilingual menu is mostly vanity. Skip it.

Step 2: Pick the right languages, in the right order

Start with one additional language. Adding three at once is a translation, layout, and maintenance disaster.

Rough European-restaurant defaults:

• Germany, Austria: German (default) → English first. French and Italian distant seconds outside specific tourist corridors.
• France: French (default) → English first. German strong in border regions, Italian on the Mediterranean.
• Italy: Italian (default) → English first. German strong in Alto Adige / Lake Garda; French along the Riviera; Russian and Chinese in specific high-tourism cities.
• Spain, Portugal: Local language (default) → English first. German strong in coastal resort towns.
• The Netherlands, Scandinavia: Local language (default) → English first. German common as a third in the south.
• UK, Ireland: English (default) → French, German, Spanish for tourist-heavy areas; Mandarin and Arabic in major cities.

If your customers are heavily from a single country (German-speaking groups in an Italian beach town, for instance), prioritise that language second over English.

Step 3: Decide who actually translates

Three options, each with real trade-offs.

Option A: Owner or staff translate themselves

Pros: Free. Voice and brand stay intact. Local idioms preserved.

Cons: Bilingual staff translate literally and miss menu conventions in the target language. "Caesar Salad with chicken" should be "Caesar Salad mit Hähnchen" in German, not "Cäsar-Salat mit Huhn." Hard to spot without a native ear.

Use this when: One of your team is native or genuinely fluent in the target language and has eaten in restaurants in that country recently.

Option B: Professional menu translator

Pros: Native speaker, menu-experienced, fast turnaround.

Cons: €0.10–€0.18 per word for menu translation is normal in Europe. A typical 80-item menu runs 600–1,200 words. Expect €100–€220 per language for a one-time professional pass.

Use this when: You serve a high-revenue clientele in the target language and the menu is reasonably stable.

Option C: Machine translation with a human review pass

Pros: Cheap, fast, scales to many languages.

Cons: Raw machine output is dangerous in menus. "Glasnudeln" auto-translates to "glass noodles" — fine — but "Schweinshaxe" auto-translates to "pork knuckle" which is technically correct and yet utterly fails to communicate to an English speaker what they are about to be served.

Use this when: You want a first draft to hand to a native-speaking server or friend for a review pass. The combination is the cheapest credible workflow.

Qarte's multilingual menus ship with AI-assisted translation built-in: every item has a translation field per supported language, and we generate a first draft you can edit. Your review time is far lower than translating from scratch.

Step 4: Translate the right things

A menu has more text than the dish names. In priority order:

1. Item names — most important. Use conventional translations where they exist (a "Schnitzel" stays "Schnitzel" in English).
2. Item descriptions — second priority. This is where customers commit to the order.
3. Category names — translate, but keep short. "Starters", not "Hors d'Œuvres / Appetisers / Small Plates."
4. Allergen and dietary labels — critical for compliance (see our allergen guide). Translate accurately or use universal icons with a localised legend.
5. Drinks — proper nouns (cocktail names, wine names) stay in their original. Descriptions translate.
6. Operational notes — "Please ask your server", "Subject to availability", etc. Often skipped; should not be.

Step 5: Build a workflow that does not rot

The single failure mode that kills multilingual menus: the German version is updated and the English version is not. After three months they say different things. Customers in the wrong language get surprised.

Two patterns that survive contact with reality:

Pattern 1: One-language source of truth, others derived

Pick your primary language as the source. Every change happens there first. Translation happens immediately after, ideally in the same update workflow. The menu publishes only when all supported languages are in sync.

The trade-off: small slowdowns to ship menu changes. The win: no drift.

Pattern 2: Parallel maintenance with publish gating

Each language is maintained independently, but the menu cannot publish a new version unless all supported languages have entries for every dish.

This is harder, but works in fast-moving kitchens where the chef edits in the local language and a server reviews English translations in batch each morning.

Both patterns assume your menu tool tracks per-item translations as first-class entities. If you are doing this in InDesign or Word, drift is guaranteed; you cannot mechanically check whether all languages cover all items.

Step 6: Handle the long tail honestly

The 80-item core menu is the easy part. The hard part is the long tail:

• Daily specials. Add a "Specials" entry in each language with a generic placeholder, and refresh both languages whenever the chef adds a special. Or accept that specials only appear in your primary language and have staff explain.
• Allergen-modified versions. "Gluten-free pasta" should not become a new top-level menu in another language — surface it as an item attribute instead.
• Seasonal pivots. A menu that swaps half its items quarterly multiplies translation costs. Plan for this.

What about regional variants?

A common question: do we offer "English" or do we offer "American English" and "British English"?

For 95% of restaurants the answer is one English. The distinctions ("eggplant" vs "aubergine", "shrimp" vs "prawn", "cilantro" vs "coriander") are not worth the complexity. Pick the variant most common to your guest profile.

For German: standard High German is fine across Germany, Austria, and German-speaking Switzerland for menu purposes. Restaurants in Vienna sometimes use Austrian variants ("Paradeiser" instead of "Tomate") as a brand statement; that is a marketing choice, not an i18n one.

How Qarte handles this

In Qarte, every menu item has a default-language version and N translation entries. When a customer scans the QR code, the menu detects their browser language and serves the matching version (with a language picker for override). The dashboard shows you, per item, which languages have a translation and which are missing. A new menu cannot publish if your "required languages" list is not fully covered.

Combined with AI-powered translation, the first draft for any added language ships in minutes — and review/edit is the only manual step.

The compliance angle

In several EU countries, allergen information must be available in the language of the country. Adding "additional" languages does not exempt you from publishing the local-language version. If you operate a restaurant in Germany serving primarily international guests, you still need a German allergen disclosure — even if 80% of your customers read it in English.

This is worth raising with your inspector if you operate near a language border or in a heavily international district.

TL;DR

• Add a second language when a meaningful slice of guests cannot order well in your default language.
• Start with English first in most of Europe; pick the second language based on your actual guest mix, not aspiration.
• Use machine translation as a draft, native speakers as review. Pure machine output in menus is dangerous; pure human translation is expensive.
• Maintain languages with a publishing process that prevents drift. Drift is the silent killer.
• Allergen information must be in the local language of the country, regardless of other languages offered.

---

Want to add a second language without spinning up a translation project? Start a free Qarte trial, import your menu, and let the AI draft translations you can review in a single sitting.