Multilingual Menu for Swiss Restaurants

September 4, 2026 · 8 min read

Switzerland is one of the few countries in Europe where multilingualism is not a special case but everyday life. Four national languages, a high share of international guests and regions where the language border runs straight through the canton: if you run a restaurant here, you serve guests who cannot read your menu in their mother tongue almost every day.

Even so, many restaurants still put a single language menu on the table. You know the result from the floor: guests ask about every second dish, staff translate between orders, and when in doubt the guest orders what they recognise instead of what you would recommend. A multilingual menu does not solve this with more effort, it solves it with better preparation.

This article shows which languages your restaurant actually needs depending on its region, what should be translated and what should stay in the original, which mandatory information has to be correct in every language version, and which mistakes make multilingual menus useless in practice.

Guests who do not understand a menu rarely order boldly. They order safely. The familiar schnitzel, the pizza, the salad: dishes that have the same name in every language. Your specialities, the daily recommendation and the dishes with the better margin stay unordered, because nobody wants to risk receiving something they did not expect.

Then there is the operational cost. Every spoken translation takes service time that nobody has during the lunch rush. Misunderstandings lead to follow-up questions, to wrong orders and, in the worst case, to a plate coming back. And with allergies or intolerances, a language problem quickly becomes a serious one when a guest fails to recognise an ingredient.

A multilingual menu is therefore not a gesture of politeness but a tool: it sells your dishes, relieves your service team and reduces mistakes.

Which languages does your restaurant need?

More is not automatically better. A menu in eight languages, five of which are poorly maintained, looks less professional than a clean menu in three. The right selection depends on your location and your guest profile.

German-speaking Switzerland

German as the base, English for international guests, French for guests from the French-speaking part of the country. In cities with congress and business tourism such as Zurich, Basel or Bern, English is effectively mandatory, because a large share of visitors speaks neither German nor French.

French-speaking Switzerland

French as the base, English and German as additions. German-speaking guests from within the country are a constant presence in Geneva, Lausanne or Neuchâtel, especially at weekends and during the holiday season. Italian pays off in restaurants with many guests from Ticino or Italy.

Ticino and the Italian-speaking valleys

Italian as the base, German for the many holiday guests from the German-speaking cantons, English for international tourism. In Ticino the share of German-speaking guests is so high in peak season that a German version of the menu is often more important than the English one.

Bilingual cities and language borders

Biel and Bienne, Freiburg and Fribourg, Valais with its German and French halves, Graubünden with German, Italian and Romansh: at language borders, bilingualism is not an extra service but an expectation. A restaurant in Biel whose menu is only available in German excludes roughly half of its own city. In these regions both local languages should be maintained equally and completely, not one as the main language and the other as a short summary.

Holiday and tourism regions

In Zermatt, Interlaken, Lucerne, Geneva or the resorts of Graubünden, an international audience is added to the local language. English is the most important additional language there, followed by French, Italian and Spanish. Spanish is often underestimated, even though it is spoken both by holiday guests and by part of the hospitality workforce.

What to translate and what to leave alone

The most common misconception is that a multilingual menu is created by translating everything. The opposite is true: dish names in particular should often stay in the original.

Keep in the original regional specialities and protected names: Zürcher Geschnetzeltes, Rösti, Papet vaudois, Capuns, Pizzoccheri, Cordon bleu, Bündnerfleisch. These names are part of the identity of the dish, and a guest who reads them understands that they are ordering something typical of the country. A literal translation such as "sliced veal Zurich style" loses exactly that effect.

Do translate the descriptions, the category names, the side dish information, the notes on allergens and origin, and the daily menu. The name stays, the explanation underneath makes the dish understandable: "Zürcher Geschnetzeltes" with the description "veal in a creamy mushroom sauce, served with rösti" works for every guest, whatever their language.

Also pay attention to formats that differ between languages. In Switzerland prices are written with a dot, so CHF 24.50. Quantities such as dl, g or pieces should appear in every language version, otherwise guests have to guess how large a portion or a glass will be.

Mandatory information must be correct in every language

Swiss food service businesses are subject to declaration requirements that do not stop at the language border. These include in particular the origin of meat and fish and information about allergenic ingredients. If this information appears only in the German version of your menu, guests reading the French or English version are effectively not informed.

In practice this means that every language version contains the same mandatory information, in the same level of detail. If you provide allergen information verbally on request, the corresponding note has to appear on the menu in every language, otherwise part of your guests will not know that they may ask. The exact requirements and their interpretation are best clarified with the food safety authority of your canton, as enforcement is organised cantonally.

A digital system has a practical advantage here: origin and notes belong to the product, not to a printed menu version that somebody forgot to update.

Five mistakes that make multilingual menus useless

Raw machine translation without review. An automatically translated text is a good first draft but not a finished product. Culinary terms go wrong regularly, and a mistranslated dish looks unintentionally funny to guests. Have the translation checked by someone who knows both the language and your kitchen.
Flags instead of language names. A flag stands for a country, not for a language. Which flag should represent German in Switzerland, which one English, which one Spanish? Language names in the language itself, so Deutsch, Français, Italiano, English, Español, are unambiguous and respectful.
Half-translated menus. Categories in English, dishes in German, the daily menu not at all: this mixture is widespread and confuses more than it helps. Either a language is maintained completely, or it should not be offered at all.
A separate PDF per language. As soon as one price changes, every file has to be regenerated. In practice this does not happen, and after a few weeks the language versions show different prices. That is not only awkward, it leads to discussions at the till.
A hidden language switch. If guests have to scroll or hunt for a small icon, they will not find the switch. The language selection belongs visibly at the top of the menu.

With a digital menu, most of the effort that multilingual menus used to require simply disappears. At online-menu.ch you create each dish once and enter its name and description in up to five languages: German, French, Italian, English and Spanish. Your guests see the menu in the language they choose themselves, through the same QR code that sits on the table. You need no separate codes, no separate table stands and no separate files.

If a price changes, you change it once and every language version is immediately up to date. When a new dish is added, you enter the translations while you are working on the entry anyway. And because the dashboard shows which languages your guests actually open, after a few weeks you can see in black and white whether another language is worth adding or an existing one is barely used.

If you do not have a digital menu yet, our guide to creating a QR code menu walks through the setup step by step. For the wider operational picture, see our article on the benefits of a digital menu.

Languages chosen by location and guest profile, not by gut feeling
Every language offered is maintained completely, daily menu included
Dish names in the original, descriptions translated
Origin declarations and allergen notes present in all languages
Prices in Swiss format, quantities in every version
Translations proofread by someone who knows the language and the kitchen
Language selection visible at the top, language names instead of flags
Changes made in one central place, not in five files

Conclusion

In a country with four national languages and a high share of international guests, a multilingual menu is not an extra for upmarket restaurants but part of the craft. What matters is not the number of languages but that every language offered is complete, correct and current. Digitally, the maintenance takes care of itself, because all versions live in one place and are updated together.