How it works
Localization in TWICE has two layers:
System strings ship with default translations for all 24 supported languages. You override individual strings when you want to match your brand voice or clarify terminology for your customers. Content translations are always manually managed — you write the translated text for each field and language.
Language configuration
Default language
Every organization has a default language. This is the language your storefront renders when no other preference applies, and the baseline that content translations are compared against. It defaults to English but can be changed in Settings → Translations & Languages.Enabled languages
Enable additional languages to make your storefront available in those languages. TWICE supports 24 languages:
Disabling a language preserves all existing overrides and content translations. They reappear if you re-enable the language.
System string overrides
System strings are the built-in UI text on your storefront and checkout. Every string ships with a default translation maintained by TWICE Commerce. You can override any of these strings per language — including your default language — to match your brand voice.Scopes
Overrides are organized into three scopes:
Each scope is edited independently. Checkout overrides can also vary per checkout configuration if you run multiple checkout flows.
Override format
Each override targets a specific string using a namespaced key. The key combines the scope namespace and a dotted path that identifies the string:Editing overrides
Open Settings → Translations & Languages, select a language, and choose a scope from the sidebar (Online store, Commerce, or Checkout). The default language appears alongside your other enabled languages — you can override system strings in any language, not just non-default ones. The editor shows each string with:- Key — the string identifier
- Default — the built-in translation maintained by TWICE Commerce
- Override — your custom text (empty if not overridden)
Default-language overrides are useful for matching your brand voice without changing your primary language setting. For example, you can rename “Add to cart” to “Reserve now” in your default language.
Fallback behavior
When a customer views your storefront, the system resolves each string in this order:- Merchant override for the customer’s language — if you set one, it wins
- Default translation — the built-in translation maintained by TWICE Commerce
- Default language value — if no translation exists for the requested language, the default language value is used
Storefront language selector
When you enable more than one language, the storefront displays a language selector in the top bar — a thin strip above the announcement bar and header. Customers click it to switch languages without leaving the page. The selector shows each language by its native name (e.g. “Deutsch” for German, “Suomi” for Finnish). The active language is highlighted in the dropdown. Switching languages updates the page content, system strings, and any translated merchant content immediately. The language selector does not appear on checkout or order link pages. If only one language is enabled, the top bar is hidden entirely (unless the store selector is also present).Language resolution
Each storefront page renders in one language. The storefront takes the first of these that your store offers:?lang=parameter. The language selector sets this on every switch. Use it to link directly to a specific language version of a page.- The language the page already shows. Navigating within the storefront keeps the current language.
- The language the customer last picked. The storefront remembers the choice from the language selector for the customer’s next visit.
- The browser’s languages. The storefront tries them in the customer’s order of preference. Brazilian Portuguese (
pt-BR) matches Brazilian Portuguese, and Norwegian Bokmål (nb) and Nynorsk (nn) match Norwegian. - Default language. If your default language is not enabled, the first language in your enabled languages list applies.
?lang= value for a language you have not enabled is ignored.
The storefront loads the matching language bundle, applies any merchant overrides on top, and renders the page. Language bundles for non-default languages are loaded on demand to keep initial page loads fast.
A first-time visitor whose browser asks for an enabled language sees that language, not your default. Customers who pick a language in the selector keep it on their next visit.
Transactional emails
Transactional emails (order confirmations, shipping notifications) are sent in the recipient’s preferred language when that language is in your enabled languages list. If the recipient’s language is not enabled, emails fall back to your default language.FAQs
What is the difference between system strings and content translations?
What is the difference between system strings and content translations?
System strings are the built-in UI text that ships with your storefront — button labels, headings, form fields, error messages.Content translations are for your own content — listing names, descriptions, custom section content, collection titles, location names, policy document names, attribute names, descriptions, and option labels, variant names, storefront content, checkout step descriptions, and navigation item labels. Content translations are managed in Settings → Translations & Languages and in the online store and checkout editors.
Do I need to translate system strings myself?
Do I need to translate system strings myself?
No. System strings ship with default translations for all 24 supported languages. You only override individual strings when you want to customize the wording — in any language, including your default language.
Can different checkout configurations have different overrides?
Can different checkout configurations have different overrides?
Yes. Each checkout configuration can have its own set of system string overrides. This is useful if you run different checkout flows for different use cases (e.g. rental vs. purchase).
What happens if I disable a language?
What happens if I disable a language?
Disabling a language removes it from your storefront. All overrides and content translations for that language are preserved and reappear if you re-enable it.
Does the system auto-translate content?
Does the system auto-translate content?
No. Content translations and system string overrides are manually managed. You write or import the translated text for each field and language.
Can I export and import translations?
Can I export and import translations?
Yes. The translations editor supports bulk export and import for both content translations and system string overrides.
Related articles
Multi-Language Content
Translate listings, collections, locations, attributes, and variants
Online Store
Storefront architecture, themes, and multi-store support
Settings - Translations
Step-by-step guide to the translations settings UI