> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/translations.md).

# Translations

## Translations

**Menu path:** `Administration -> Dictionaries -> Products`

The `Translations` tab is used to maintain product name translations for languages used in the organization.

It is useful in environments where the same product is handled in many countries, languages or locations.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FuDwEM5zeHLG1dEtiUbSX%2F066.png?alt=media&amp;token=b66560b2-ea19-465c-9148-93d4f1b08e9c" alt=""><figcaption></figcaption></figure>

### What is on the screen

| Element        | Meaning                                                          |
| -------------- | ---------------------------------------------------------------- |
| `Default name` | Default product name coming from basic product data.             |
| `Language`     | Name of the language for which the translation has been defined. |
| `Locale`       | Language or location code, for example `pl`.                     |
| `Translation`  | Translated product name used for the given language or location. |

### When to check

Check the `Translations` tab when:

* the product should be presented in a language other than the default name,
* users from different countries see the same product record,
* the product name visible in the system, on POS, in documents or reports requires language verification,
* the report concerns an incorrect or missing product name in a given language.

### What to watch out for

* Available languages and locales depend on implementation configuration.
* Missing translation does not always mean an error. In that case, the system can use the default name.
* Changing a translation can affect how the product is presented in places that use localized names.
* If the translation should be visible on POS, data synchronization may be required.

### Related pages

* [Source data](/aquila-store-user-manual/products-and-product-records/source-data.md)
* [Configuration on cash register](/aquila-store-user-manual/products-and-product-records/configuration-on-cash-register.md)
* [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.md)


---

# 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://docs.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/translations.md?ask=<question>&goal=<user_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.