---
title: "Localisation - User Interface"
canonical: "https://red-ant-documentation.refined.site/space/RET/538837052/Localisation%20-%20User%20Interface"
format: markdown
---
## Overview

The platform's localisation functionality is designed to enhance the user experience by allowing sales associates to choose their preferred language for the user interface. By default, the platform displays in English, but this feature provides the flexibility to switch to other available languages. 

## Key Features

- **Language Selection at Login:**
  - Users can select their preferred language from a list of available options directly from the login screen.
- **Multiple Language Support:**
  - The platform offers a range of languages to cater to a diverse user base, ensuring a seamless experience for global users.
- **Dynamic User Interface Translation:**
  - Upon selecting a different language, the user interface will be dynamically translated, making it easier for sales associates to navigate and interact with the platform.
- **Default Language (English):**
  - The platform defaults to English unless the user specifically configures their preferred language. This ensures consistency for new users. After logging out, the language that was selected is retained.

## Considerations

**Data Feed Exceptions:**

While the platform translates most user interface elements, it does not automatically translate data fetched on demand from external systems, such as the product catalogue. 

If the retailer is able to provide translated versions of these data feeds, they can be used.

**Default Local Country Code:**

The local country code can be set as the default within the telephone number list, streamlining the entry process for users by automatically prioritising the most relevant country code.

**Region-Specific Address Look-Up:**

The address look-up feature can be configured to return results tailored to the specific region where the store is located, enhancing accuracy and efficiency in address entry and verification.

## Known Limitations

**User interface design:**

By default, the user interface design of the platform follows a Western layout, adhering to the left-to-right (LTR) reading orientation. 

**Retail Analytics:**

There is currently a known limitation whereby the metrics displayed within Retail Analytics cannot be translated based on the language selection made by the user - this is because this information is stored in an external system. 

**Virtual Consultations:**

The customer-facing elements of the virtual consultation are currently only available in English.

## FAQ

<details>
<summary>Can the customer registration form (assisted & self-registering) be translated into multiple languages?</summary>

Both the in-app (assisted) and self-register (QR) forms have been designed to support translations. However, whilst the in-app assisted registration can dynamically translate based on the language selected pre-login (see above), there are several options that can decide what controls the language the self-registration form displays in:

1. Based on the region set on the customers device (will default to English if we don't have translations associated with the region of the customers device)
2. Default to English and have an option on the form to choose an alternative language
3. A combination of options 1 and 2
</details>

<details>
<summary>Can both automated and 1-2-1 messaging comms be translated?</summary>

RetailOS can support translated communications based on the customer's preferred language - this applies to transactional (i.e. automated emails) and personally curated (1-2-1) communications. 

By default, all communications are in English, however, if translated versions are provided these can be set up accordingly. 

In cases where a customer's preferred language lacks a translated version, the platform automatically reverts to using the English template. For 1-2-1 communications, the translated messaging templates are grouped by language in the template dropdown within the message composer.
</details>

<details>
<summary>Does the messaging composer support right-to-left (RTL) languages such as Arabic?</summary>

Yes. The messaging composer fully supports RTL (right-to-left) languages. When a template in an RTL language—such as Arabic—is selected, the composer will automatically:

- Render the predefined subject line (Email only) and message body in a right-to-left format.
- Adjust the text input to conform to RTL writing direction.
- Display the message preview in RTL, ensuring the sales associate can see exactly how the message will appear to the customer before sending.

This ensures a consistent and culturally appropriate messaging experience for RTL language recipients.
</details>