Languages & locales
OneAce is translated into eight languages. Your team picks the one they want — at the organization level, with per-user overrides for anyone who prefers a different language.
Supported languages
Every user-facing string flows through the same translation pipeline, so no view will accidentally fall back to English for one team and Turkish for another.
| Code | Language | Region |
|---|---|---|
| en | English | Default |
| tr | Türkçe | Turkey |
| es | Español | Spain & LATAM |
| de | Deutsch | DACH |
| fr | Français | France & Benelux |
| pt | Português | Portugal & Brazil |
| it | Italiano | Italy |
| ar | العربية | MENA (RTL) |
How locale resolution works
OneAce picks a locale in this order — the first match wins:
- The user's explicit preference in their profile settings
- A locale cookie set during the last session
- The organization-level default locale (set by the owner)
- The browser's
Accept-Languageheader, matched against supported languages - English, as a final fallback
Right-to-left support
Arabic ships with full RTL support — directional icons, mirrored navigation, and right-anchored numeric inputs. The whole UI flips automatically when an RTL locale is active.
What's coming next
- Custom in-app glossaries for company-specific terminology
- Per-warehouse locale overrides for multi-region operations
- Translation memory export/import for self-hosted teams