Your menu in English — three ways and what each really costs

Most English menus in European restaurants were translated once, properly, by somebody competent. Then the kitchen changed a dish, the price moved twice, two items came off — and the English version stayed as it was.

Eight months later the server hands it over knowing it is wrong, and hopes the guest orders something that still exists.

The translation was never the problem. The problem is that it became a second document, and second documents do not get updated.

Why a translated menu drifts

The local menu is updated because guests see it and staff work from it. The English one is updated when somebody remembers — which means at the next reprint, if then.

The gap grows in three places, in this order:

1. Prices. A supplier raises, the local card is corrected, the English one is not. The guest sees one number and pays another.
2. Availability. A dish comes off. It stays on the English menu, and the server explains it at every table where a foreign guest sits.
3. New items. Seasonal dishes never make it across at all, so the international guest is offered a smaller menu than everyone else — usually the cheaper part of it.

Point three is the expensive one. It is invisible, because nobody complains about a dish they were never shown.

Three routes and what they cost

A translation agency

€70–280 per language for a menu of 40–60 items, plus layout and a print run if you print. Quality is good and the terminology is consistent.

The catch is not the price but the unit: you pay per commission, not per change. A €3 price correction becomes a €40 minimum order, so it waits — alongside three other corrections, until the season has changed.

Worth it when the menu genuinely does not move — a fixed card, one change a year.

Doing it yourself

Free in cash, 4–8 hours in time, and the quality depends entirely on who does it. A chef with good English will get the dishes right and the register wrong; a language teacher will do the reverse.

The realistic version: a bilingual member of staff writes the descriptions, and somebody who works the floor reads them aloud. Servers know which dishes get asked about — that list is not the same as the owner's.

Worth it when there is somebody suitable and the menu is short.

Automatic, inside the menu system

The menu is kept in one language and served in the others. Cost per additional language is zero, and — the part that actually matters — a change propagates by itself, because there is only one document.

The catch is that automatic translation is reliable for descriptions and unreliable for dish names, which is exactly where it produces the memorable failures. The working arrangement is automatic as the baseline, with manual overrides on the names and on anything regional. How to write those overrides is in translating local dish names.

Worth it when the menu moves, when there is more than one language, or when both.

Five mistakes visible on European English menus

1. The name translated instead of described. "Hunter's Stew" means nothing to anyone; the original name plus one line of description does the job.
2. Prices left in the local format. A guest reading 24,00 and expecting 24.00 is a small friction; a guest who cannot tell whether service is included is a bigger one.
3. Allergens only in the local language. This is not a courtesy issue. The duty is to convey the information to the consumer, so a list they cannot read does not discharge it — see allergens on the menu.
4. A separate English card handed over on request. It marks the guest as a special case, and it is the version most likely to be out of date.
5. Machine output published unread. The first ten items reveal the pattern of errors the system makes; the other fifty will contain the same pattern.

What must be translated, and what must not

Must: everything a guest needs to decide and to eat safely — descriptions, allergens, portion notes, whether something is spicy, what is included in the price, opening hours and ordering rules.

Must not: dish names, protected designations, and your own house names. Those are what the guest points at and searches for afterwards.

The order that works

1. Count who actually comes in before choosing languages — two weeks of tally marks at the till beats any assumption. Method in how many languages does your menu need.
2. Write the descriptions in your own language first. Translating a bad description produces a bad description in two languages.
3. Do the 20 best-selling items, not the whole card. They carry most of the turnover and most of the questions.
4. Have a server read them aloud. Repetition and awkward register surface immediately.
5. Decide where the English version lives. If the answer is "a second file", you have rebuilt the original problem.

Frequently asked questions

What does translating a restaurant menu into English cost?

An agency charges roughly €70–280 for a 40–60 item menu, plus layout and printing. Doing it in-house costs 4–8 hours. Inside a menu system the marginal cost of a language is zero.

Is automatic translation good enough for a restaurant?

For descriptions, as a baseline that you then read. For dish names, no — that is where the failures come from. Automatic with manual overrides on the names is the arrangement that holds.

Do I need to print a separate English menu?

Not if the digital version is available at the table. A separate printed card is the version that goes stale first, because it is reprinted least often.

Do allergens have to be in English too?

Yes, where the guest reads English. The obligation is to convey the information; a declaration the guest cannot read does not satisfy it.

From how many international guests is a multilingual menu worth it?

The question is usually the wrong way round. With an agency, each language has to earn its invoice. Inside a menu system the cost is zero, so the threshold is one guest a week — which almost every venue in a city clears.