Review an AI menu translation against the restaurant’s approved source menu. Check the meaning of dishes, ingredients and options, verify prices and allergen information, then preview the languages you intend to publish. A fluent translation can still describe the wrong dish.

Make the source menu reliable first

Use the current dish list, prices, portions, required choices and optional extras. An AI import from a supported photo or PDF is a draft that needs comparison with the original.

Resolve unclear source descriptions before translating. Keep distinctive dish names where appropriate and explain them with a description; replacing a name with a more familiar but different dish can mislead guests.

Check the details that change an order

Review more than the dish name. Size, preparation choices, included sides, optional extras and price supplements affect what guests expect and what the kitchen receives.

Use someone who understands the target language and the restaurant’s food where possible. MenuSnap’s language availability does not itself verify the accuracy of every translation maintained by a restaurant.

  1. Compare the dish name and description with the source.
  2. Check portion sizes, required options and added charges.
  3. Check menu headings, categories and set-menu choices.
  4. Preview long labels and any right-to-left language you enable.

Verify allergen information with the restaurant

Check ingredients and allergen wording against the restaurant’s own recipes and supplier information. Translation should preserve verified information, not infer whether a dish is safe.

If a recipe or ingredient is uncertain, resolve it with the restaurant team before publishing a claim. Keep a clear route for guests to ask staff about dietary needs. An AI draft does not replace that conversation.

Review the published guest journey

Open the restaurant menu on a phone and switch between the enabled languages. Check dish details, choices, prices and readability rather than relying only on an import preview.

Missing content may fall back to the restaurant’s default language. That can keep a field visible, but it does not mean the translation is complete. Check the actual guest view after changes. The public demo illustrates ordering; it does not validate your menu.

Maintain translations when the menu changes

Recheck affected translations when you change a dish, recipe, portion or option. A previously reviewed translation can become outdated even when it still reads naturally.

Translation and related text tasks share a plan allowance. Check the usage shown in your account before processing a large menu; do not assume the allowance is a fixed count of unique dishes or that every repeated request is free.

  1. Keep a record of the source information used for review.
  2. Publish the reviewed languages and inspect the guest menu.
  3. Recheck affected content after a source-menu change.
  4. Review remaining AI allowance before the next large task.

MenuSnap frequently asked questions

Does support for 31 languages mean every dish is already translated?

No. Available languages and completed restaurant content are different things. Check which languages your restaurant enables and which fields have a reviewed translation.

Can AI identify allergens without recipe information?

Do not rely on it to do so. The restaurant must verify ingredients and allergen information from its own reliable sources before publishing.

Should I translate the same dish name literally in every language?

Not always. A recognisable local name with an accurate explanation may be clearer than a literal translation. The description must still represent the actual dish and its choices.