Languages & currency

You can run in as many languages as your customers need. There are two halves to it — the app’s own wording, and your content — and they are managed separately.

Choosing languages

Pick from the full standard language list and set one as your primary. That is the fallback: anything untranslated appears in the primary language rather than blank.

Right-to-left languages are supported and the apps lay out accordingly. If you add one, look at the result on a real device — RTL affects far more than text direction.

Translating the app’s wording

Every app has its own translation editor: the customer app, the partner app, the POS register, the kiosk and the in-store tablet. Each is organised by area and screen, and each supports CSV export and import — which is how you actually do this. Export, send the file to a translator, import it back.

Do not translate everything at once. Start with the customer app, then the app your staff use, then the counter devices. A partly-translated kiosk is worse than an English one, so finish each before starting the next.

Translating your own content

Your content is translated where it is created rather than in a central list. Nearly everything carries a language section: outlets, categories, dishes, add-ons, variants, coupons, banners, walkthrough slides, custom pages, cancellation reasons — and every notification template.

Two consequences worth planning around:

Adding a language is not one job. It is the app strings plus every piece of content you have created since launch.
New content needs translating as you go, or it will silently appear in the primary language for everyone else.

Currency

Your primary currency is set in Brand settings and is what everything is priced and reported in.

Additional currencies with exchange rates you maintain let customers see prices in their own, where your plan includes multi-currency. Rates are yours to keep current — nothing updates them for you — and the currency-wise report (/reports/currency-wise) breaks sales down by currency.

Timezone and country

Timezone is set on your brand. It decides what “today” means in every report, when scheduled work runs, and how operating hours are interpreted. Getting it wrong shifts every report by hours.

Country drives phone number defaults and formatting. Sign-up can also be restricted to particular countries, with minimum and maximum phone lengths — the simplest defence against sign-up spam from outside your market.

What customers experience

The app picks up the customer’s device language where you support it, and falls back to your primary otherwise. Customers can switch manually. Messages go out in their language, provided that template has been translated.

Adding a language: a checklist

Enable it, and confirm your primary is still right.
Export the customer app strings, translate, import.
Translate the menu — dishes, categories, add-ons.
Translate the notification templates, including order status.
Translate banners, walkthrough and any custom pages.
Open the app in that language on a real device and order something.
Only then repeat for the staff-facing apps.

Troubleshooting

Symptom	Cause
Some text is still in the primary language	It is untranslated — that is the fallback working
An dish name is not translated	Content translates where it is created, on the dish itself
A message arrived in the wrong language	That template has not been translated
Prices look wrong in a second currency	Exchange rates are yours to maintain; nothing updates them
Reports are a few hours out	Check the brand timezone
Customers cannot sign up from a country	Sign-up country restrictions are in the admin configuration

Was this page helpful?

This site uses a chat widget that sets a cookie so it can keep your conversation. See the privacy policy.