A restaurant menu translation starts with one kitchen-approved source for every item, restriction, variation, price, and availability note. Translate what guests need, retain an original name when a literal translation loses meaning, add an approved explanation, and test each version on a phone before service. Guests and staff see the same current choices.
Build one approved source before translating
Do not separate translation from operational review: the shift lead should approve the same language version that will be published. First, record the guest-facing facts that are already approved for each item. The translation is a second expression of those facts, not a new interpretation of the kitchen’s intent.
| Menu field | Keep as the approved source | Translate for the guest | Check before service |
|---|---|---|---|
| Dish name | The item the kitchen can identify | A plain explanation when the original name is not enough | It still points to the same dish |
| Restriction or ingredient note | Confirmed wording and its scope | Clear language beside the affected item | It does not add an unconfirmed safety claim |
| Variation | What changes and what is included | The choice, limit, and any approved surcharge | The guest can distinguish it from the base item |
| Availability | Location, daypart, or stated period | The condition that applies to the guest | The public page matches the current service |
For menu controls that require guest input, the W3C guidance on labels and instructions is a useful design reference: clear labels and instructions help a person understand selectable options. It does not determine food claims, which still need an approved restaurant source.
Keep names, restrictions, and choices separate
A dish name is not automatically an ingredient list, and a translated restriction is not automatically a safety guarantee. Keep each fact in its own field so a change to one does not quietly alter another. For example, retain a cultural dish name when it is the clearest identifier, then place a short approved explanation beside it rather than inventing a literal substitute.
Use the same caution with dietary and allergen questions. The FDA food-allergy resource provides U.S. packaged-food labeling context; it does not prescribe a restaurant menu workflow. Treat it as a reminder to obtain the kitchen’s confirmation for each item. If a detail is not confirmed, say less and route the question to the responsible person; do not translate uncertainty into a promise.
Translate the decision, not just the words
Each language should let a guest answer the same practical questions: What is this item? What can I choose? What changes with this option? Is a stated limit relevant at this location or service? The final wording can differ by market while the approved choice stays the same.
The digital-menu modifier guide separates the base item from add-ons, exclusions, and variations. Pair it with the digital-menu price update checklist whenever the translated page displays an approved price beside a variation. Do not use translation to hide a condition that the original menu shows.
Test the public version before the shift
Follow the digital-menu QR code placement guide after opening a language version, so the printed code, its label, and the fallback all lead guests to the same current menu.
Open every language version on a phone, follow the same path a guest uses, and compare it with the approved source. Check the menu link and QR route, the visible item name, the restriction wording, each variation, and any availability note. If an item is temporarily unavailable, use the separate sold-out item process instead of leaving a translated page to imply it can still be served.
Translation belongs in the broader release check. The seasonal menu update checklist covers planned replacement and retirement, while the restaurant mini-site content checklist helps align menu, hours, location, and guest entry information. Brief the next shift from the tested public page, not from a private draft or chat message.
Restaurant menu translation checklist
- Is there one kitchen-approved source for each item and its guest-facing facts?
- Does every retained original name have a clear explanation when a guest needs one?
- Are restrictions and ingredient notes translated only from confirmed wording?
- Can a guest distinguish the base item, each variation, and its stated limit?
- Do visible prices, locations, service periods, and availability match the approved source?
- Has someone opened every language version from a phone or QR route?
- Does the next shift know which public page is the current source?
Use this checklist whenever a restaurant adds a language, revises a dish description, or changes a guest-facing menu term. The purpose is not perfect literal equivalence; it is a clear, confirmed choice in every language the restaurant publishes.