Skip to content

Languages & currency

Language and locale settings make the platform feel native wherever you operate: enable the languages your customers speak, translate your menu and key messages, and the apps follow each customer’s preferred language with graceful fallback to your default. Everything is managed from your admin dashboard.

Dashboard → Settings → Language (/settings/languages/language) is where you manage the languages your business supports and the translations behind them:

  • Enable the languages you want to offer alongside your default.
  • Edit per-app translations — the customer app and the partner app each have their own set of translatable text, so you can localize what customers see without touching what staff see (or vice versa).

Your default language is the fallback: anywhere a translation is missing, customers see the default-language text instead of a blank — so you can roll out a new language gradually.

Menus support per-language fields: item names, descriptions, and category names can each carry a translation per enabled language. You add these as part of menu editing — see the multi-language section of Building your menu.

A practical workflow:

  1. Build and finalize the menu in your default language first.
  2. Enable the additional language under Dashboard → Settings → Language.
  3. Go back through the menu adding the translated fields, starting with your best-selling categories.
  4. Open the customer app in the new language and read the menu end to end — machine-translated dish names are the most common embarrassment a test catches.

Your currency is configured for your business during onboarding and then flows consistently through checkout, receipts, the partner app, and reports — there’s nothing to maintain day to day. If you ever need to change currency, contact your SupaOrder account manager rather than changing settings yourself: prices, wallets, and historical reports are all affected.

For reporting, there’s a dedicated currency-wise breakdown at Dashboard → Reports (/reports/currency-wise) — see Reports & analytics.

Timezone and locale formats are also set during onboarding, alongside currency (see step 1 of the launch checklist). They drive when “today” starts in your reports, how scheduled orders display their time slots, and how dates and numbers are formatted on receipts.

From the customer’s side, language is simple:

  • The app follows the customer’s preferred language when it’s one you’ve enabled.
  • Anything you haven’t translated yet shows in your default language — never a blank or an error.
  • Menu content (names, descriptions, categories) shows its per-language version where one exists.

That means partial translation is safe to ship: enable the language, translate the high-traffic content, and fill in the rest over time.

SymptomTry this
Customer sees a mix of two languagesNormal during rollout — anything untranslated falls back to your default; finish the missing translations
A dish shows the default-language name in the new languageAdd the per-language name for that item in the menu — see Building your menu
Staff see translated text they don’t wantCustomer app and partner app translations are separate under Dashboard → Settings → Language — adjust only the partner app set
Prices or dates look wrong for the regionCurrency, timezone, and formats are onboarding-level settings — contact your account manager
  • Enable the language under Dashboard → Settings → Language (/settings/languages/language).
  • Review the customer app translations for that language.
  • Translate menu categories, item names, and descriptions (Building your menu).
  • Place a test order in the new language end to end — menu, checkout, notifications, receipt.

Related: Building your menu · Launch checklist · Reports & analytics · Dashboard navigation map