Foundation's translations feature lets you communicate with buyers in their preferred language — automatically. From the moment a buyer activates their account, the platform detects their locale and serves translated content across the web portal, mobile app, and emails.
This article covers:
Which languages are supported
How locale detection and language selection work
What parts of the product are translated
Current limitations
Speak your buyers' language
Translations is a platform-level feature that serves content in a buyer's preferred language across the web portal, mobile app, and outbound emails. It works automatically — no action required from your team to enable it for your buyers.
The translations feature is enabled at the builder’s organizational level via a feature flag. Enabling it for your organization requires some simple coordination with the Foundation team.
Supported Languages
Foundation supports native translations for the following locales at launch:
Locale | Language |
en-US | English (U.S.) |
en-AU | English (Australia) |
en-CA | English (Canada) |
en-GB | English (UK) |
fr-FR | French (France) |
de-DE | German (Germany) |
it-IT | Italian (Italy) |
pt-BR | Portuguese (Brazil) |
pt-PT | Portuguese (Portugal) |
es-MX | Spanish (Mexico) |
es-ES | Spanish (Spain) |
How It Works
When a buyer loads the platform, their on-device or browser locale is evaluated on every page load. If a non-US locale is detected and the buyer hasn't yet confirmed a language preference, a modal appears prompting them to confirm or change it. Once confirmed, the preference is saved to their account and applied going forward.
During activation
Language selection is built into the buyer onboarding flow. Buyers with a non-English locale are prompted to confirm their language before proceeding — so the experience is localized from the very first interaction.
After setup
Buyers can update their language preference at any time from their account settings.
What's Translated
Translations apply to the core product experience, including system-generated text such as labels, buttons, and navigation elements.
Supported Interfaces
Once a locale is set, translations are applied across the following interfaces:
Buyer mobile app (iOS and Android)
Buyer web portal
Operator web interface
Outbound email communications
Notifications (in-app and email)
Supported Features
Within those interfaces, translations are applied to:
Navigation and general interface text
Activation and onboarding flows
Milestones and progress tracking
Utilities, team, home details, and warranty sections
Good to know: Mobile translation support is delivered via OTA (over-the-air) update — no app store update is required.
Current Limitations
Asian languages: Japanese, Mandarin, and Cantonese are not yet supported and will be added in a future release. Right-to-left (fka “RTL”) languages like Arabic, Farsi, and Hebrew are more difficult for computers to translate; we do not currently have an ETA for these translations.
User-generated content: Translations currently do not apply to user-generated content, such as messages, updates, or manually-created Action Items. This content will continue to appear in the language it was originally written. ETA for automatically translating user-generated content (UGC) is H2, 2026.
Configurable WarrantyOS Content: Content that is configurable – such as labels and custom form fields within the warranty sections — is not translated.