Configure and review guest menu translations
Console: Settings → Business settings → Translations. For the menu lead and
authorised setup owner. Guest content languages differ from the language of the
staff interface. Changing your Console or app language does not establish that
every menu has translated content.
Review the language configuration
Check Base language → Menu language against the language in which the source
menu is actually written. Not set needs a deliberate setup decision before
relying on assisted translation.
Under Guest languages → Available translations, choose only languages the
restaurant intends to review and maintain. The base language is excluded from
target choices; changing the base can remove it from the guest-language
selection. Save intended configuration changes and reopen to verify them.
The current page can show language selectors as read-only for restaurant
operators. Arrange changes through the authorised TablePort setup/support path
when those fields are disabled. Do not change account access merely to make the
controls editable.
Read coverage in context
Translation coverage tracks items, collections and categories for the first
location and the related shared catalogue. It is not a verification of every
location menu or every guest-facing field.
Check the language card's translated/total count and each entity group. No
guest languages selected, No location to translate, and a coverage load
error are different situations. Use the relevant configuration, location setup
or retry path; do not interpret an error as zero translations.
A 100% indicator measures recorded translation entries. It does not prove their
wording is correct, current, complete in every field, or reviewed by a fluent
speaker. Verify each selling location and channel separately.
Translate missing entries deliberately
Use Translate … missing for the intended language only when authorised and
ready to review its effect. Read the translating progress and wait for the
result. This action saves generated content; it is not just an unsaved proposal
for a later Publish button. Saved shared items/categories can affect other menus
using them.
After completion:
- Recheck coverage and inspect representative translated items, collections and
categories, including size/option labels and descriptions.
- Have a fluent reviewer verify the actual menu meaning, ingredients,
allergens, and any guest-facing restrictions against the kitchen's source
information. Do not approve a changed food claim merely because it reads
naturally.
- Open the intended menu on the guest ordering surface and kiosk where used.
Select the guest language and inspect real names, descriptions, choices,
prices, wrapping and the complete ordering flow.
- Use the existing entity's translation editor for supported corrections and
save that entity's changes separately. See Menu items.
A stored translation does not necessarily regenerate when its source wording
changes. Review previously translated entries after menu edits rather than
assuming the missing-entry action updates all old wording.
Recover a partial or uncertain result
If translation cannot complete, earlier entries can already be saved. Reopen
coverage and inspect the same language and entities before another bulk action.
Missing-entry generation does not by itself prove every existing description was
corrected. Preserve accurate human edits and avoid deleting translations or
creating duplicate items as a retry shortcut.
If a guest still sees unexpected wording, check the actual selected content
language, saved entity, location menu and device sync. Use
Menu recovery when visibility or choices
also differ.
Escalate with business/location, source/target language, entity, intended
meaning, coverage/progress state and exact error. Use synthetic examples or the
minimum menu text needed; keep guest contacts, credentials and private notes out
of translation prompts and public captures.