How to Translate Portion Sizes and Add-ons Clearly: Check Each Option Against a Meaning Card

A translated menu should help guests choose the same food the kitchen will prepare. Once the dish names are right, check portion sizes, included items, additions, substitutions, and extra charges. Even fluent wording can make “swap the side” sound like “add another one.” Confirm the source-language facts first, then check what each choice actually changes.

Create a meaning card for each option that could be misunderstood

This is not just a record of the menu’s language versions. It breaks each choice into facts that can be checked. First record the source wording and what the kitchen actually does, then ask someone who knows the target language and the dishes to review the translation. Don’t ask AI to fill in fields without supporting information.

• Dish and size: ____; serving size, volume, or number of pieces confirmed by the restaurant: ____; included sides: ____.
• Option in the original: ____; option in the target language: ____; what this choice actually changes: ____.
• Does the original item remain: ____; is an additional serving added: ____; are any choices mutually exclusive: ____.
• Included or charged separately: ____; price and extra charge: ____; where guests can see this before choosing: ____.
• Kitchen reference and person confirming it: ____; language reviewer: ____; meaning that still needs clarification: ____.

Use these questions to spot differences in meaning

• Addition or substitution: Does the original side remain? The translation must match the actual change in quantity; don’t use a single word meaning “add” to cover both.
• Not included or can be left out: The first describes what is sold; the second describes an available adjustment. Don’t translate one as the other and change the original promise.
• Portion size or suggested number of diners: State the actual number of pieces, volume, and size as confirmed by the restaurant. A suggestion for sharing is not a guarantee that the food will serve a certain number of people.
• Included in a set meal or offered as alternatives: When drinks, desserts, or coffee appear together, make clear whether they are all included, guests choose one of two options, or they must be ordered separately. Don’t rely on layout alone to explain the relationship.
• Same name or same dish: A distinctive name can be retained, but its explanation must match the restaurant’s ingredients and preparation. Don’t replace it with a familiar term that refers to a different dish.

Get the facts right before polishing the language

If the original only says “signature chicken,” the translator won’t know how it is prepared, whether it is bone-in, or what it comes with. Ask the kitchen to clarify facts that could affect a guest’s choice; there is no need to disclose the full recipe or process. Vegetarian, ingredient, and allergen information must also be based on the restaurant’s recipe and supplier information. Don’t infer safety from a dish name, photo, or AI output. Removing an ingredient does not eliminate the risk of cross-contact.

If there is any uncertainty about the recipe or conditions in the kitchen, ask the person responsible at the restaurant to confirm before replying to a guest. Language reviewers are responsible for natural, accurate meaning; the kitchen is responsible for the facts about the food. Neither role replaces the other, and unverified dietary claims must not be guaranteed to guests.

Review the entire selection on a phone

Check the categories, dish names, descriptions, sizes, and surcharges in each language version that is about to go live. Make sure they are consistent, long sentences don’t crowd out important distinctions, and numbers and units are clear. Missing translations may fall back to the default language; a page that isn’t blank does not mean the translation is complete.

Ask front-of-house staff to use the page to answer: “What does this price include? What does it cost to change the side? How much extra do you actually get?” If they can’t answer clearly, revise the corresponding meaning card rather than relying on staff to explain a different interpretation on the spot. MenuSnap provides multilingual menus and AI-assisted translation. Tasks and usage depend on plan and account conditions; this does not mean that content is accurate and complete in every selected language.

When the source changes, recheck only the affected options

When a recipe, portion size, side, or option changes, mark the affected fields on the meaning card and send them for review in the relevant language. You can keep using your existing process for managing source versions and review records; you don’t need to redo the entire menu each time. Don’t expand into a language for which no suitable reviewer is available. Guests can continue to use confirmed content and get help from staff.

At closing, sort recurring questions into categories: unclear dish name, mistaken portion size, unclear inclusions, or missing translation. If the issue is the relationship between options, prioritize revising that option. Don’t count every question as a translation error, and don’t add languages if that would create content you cannot maintain over time.