Menu translation mistakes that confuse guests and kitchens.
Why translating menus word-for-word creates operational problems — and how to keep dish names, allergens, dietary claims, and service language clear across languages.
- Crumb guide
- Translations
- Updated
A translated menu is not a vocabulary exercise. It is an operational document. If the guest misunderstands a dish, front of house has to fix it. If an allergen note is softened, the kitchen inherits the risk.
The best translated menus preserve intent: what the dish is, what the guest should expect, and what safety information must remain exact.
Do not translate dish names too literally.
Some names should stay as names. ‘Cacio e pepe’ does not become ‘cheese and pepper pasta’ unless the restaurant would write that in the original language. Translate enough to help the guest order, but do not flatten the identity of the dish.
Separate description from compliance.
Dish prose can be adapted. Allergen language should not be improvised. ‘May contain nuts’ is a safety statement, not copywriting. Keep allergen terms consistent across every language and avoid euphemisms.
Be careful with dietary claims.
Vegetarian, vegan, gluten-free, low calorie, and dairy-free do not map perfectly across guest expectations in every market. If the kitchen can make something without an ingredient, say that. If the dish is prepared in a shared fryer, say that too.
Keep the kitchen language visible.
The translated guest menu should not create a second reality for the kitchen. If a server repeats a guest’s translated wording back to the pass, the team still needs to know exactly which dish and modification is being discussed.
Review the high-risk words first.
Before polishing adjectives, check the words that carry risk: nuts, peanuts, sesame, milk, egg, fish, shellfish, gluten, celery, mustard, sulphites, vegan, fried, raw, cured, and alcohol. These are the words guests use to decide whether they can eat.
Use a translation register.
Keep a short approved list for the terms that should never drift: allergens, preparation methods, dietary claims, menu sections, and the restaurant’s recurring dish components. If ‘smoked celeriac’ appears in six dishes, it should not be translated six different ways.
Ask a native speaker the service question.
The review question is not ‘is this literal?’ It is: would a guest order the right thing from this line, and would the waiter understand the modification if the guest repeated it back? If the answer is no, the translation is not finished.
Frequently asked.
- Can machine translation be trusted for menus?
- For first drafts, yes. For service-ready copy, no. Allergen terms, dietary claims, and any line that carries safety meaning need native-speaker review against the kitchen’s actual workflow.
- Should dish names stay in the original language?
- Often yes. ‘Cacio e pepe’ doesn’t become ‘cheese and pepper pasta’ unless the original menu would write that. Translate the description, not the dish’s identity.
- How do we keep translations consistent across menu updates?
- Maintain a translation register for the terms that recur — allergens, preparation methods, dietary claims, section names. New menu items inherit the register instead of being re-translated each time.