> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/settings/localization.md).
# Localization
### **Overview**
**Localization** is used to modify the names and text displayed in the POS application without making changes at the code level. It allows users to search for a specific text or label and update its displayed value according to the customer's requirements.
### **Screen Elements**
| **Screen Element** | **Description** |
| ------------------ | ----------------------------------------------------------------------------- |
| UI Language | Selects the language for the localization settings. |
| Search | Allows users to search for a specific name or text that needs to be modified. |
| Override | Allows the selected localization value to be customized. |
| Name | Displays the internal name or identifier of the text. |
| Value | Displays the current localized value that can be modified. |
| English Value | Displays the original English value for reference. |
| "Save" | Saves the localization changes. |
| "Close" | Closes the Localization screen. |
| "Import" | Imports localization data. |
| "Export" | Exports localization data. |
### **Working**
#### **Change a Display Name**
1. Open "Localization" from the required settings section.
2. Select the required language from "UI Language".
3. Enter the name or text that needs to be changed in "Search".
4. Click "SEARCH" to find the required localization entry.
5. Locate the required name in the list.
6. Select the "Override" option for the required entry.
7. Modify the value in the "Value" field with the required name.
8. Click "Save" to save the changes.
9. Select "Import" to import the required localization data.
10. Select "Export" to export the localization data.
11. Verify that the updated name is displayed in the relevant screen or report.
### **Use Case**
1. Rename a specific label displayed in the POS application.
2. Change report names according to the customer's preferred terminology.
3. Customize system labels without modifying the application code.
4. Update displayed text to match the terminology used by a specific business.
5. Modify a particular name across the UI using the localization entry.
6. Search for a required text quickly using the "Search" option.
7. Configure localized values for the selected "UI Language".
8. Maintain customer-specific terminology while keeping the underlying application configuration unchanged.
### **Notes**
* Localization allows text or names to be modified without making changes at the code level.
* Use the "English Value" column as a reference when identifying the required text.
* Enable "Override**"** before modifying a localization value.
* Search for the exact name or text when multiple localization entries are available.
* After saving, verify the change in the relevant screen or report.
* Changes should be made carefully to avoid modifying the wrong localization entry.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rbsgo.com/dineplan/backoffice/settings/localization.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
