Multilingual Ordering
Reduce language friction without pretending translation is infallible
Common pain points
- Floor staff interpret table by table
- Translated names drift from kitchen items
Key capabilities
- Multilingual interface
- Shared menu identity
- Optional voice questions
- Prepare critical translations Review signature dishes, allergy, and modifier text first.
- Open the chosen locale Visible content depends on completed translation coverage.
- Send standardized items Kitchen works from the same item identity.
FAQs
Is every string translated automatically and correctly?
No. Review critical dish, dietary, and allergy language manually.
A good place to start when
- International guests materially affect ordering efficiency
- The restaurant can prioritize review of signature dishes, modifiers, and risk text
Confirm before rollout
- Which locales and surfaces are actually required
- Fallback behavior for untranslated fields
- How kitchen item identity maps from guest language
What the system does not do
- Translation does not replace human allergy confirmation
- A supported interface locale does not mean every menu string is complete
Observe first after launch
Track whether guests understand items and complete modifiers, then use the most frequent handoff terms to improve critical translation coverage.