> For the complete documentation index, see [llms.txt](https://docs.bogos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bogos.io/detailed-guide/translation.md).

# Translation

The BOGOS app now supports a Translation feature, enabling users to change the app’s element display language based on store language settings.

{% embed url="<https://www.youtube.com/watch?v=U-J0kL-rLaE>" %}

<img src="https://1174860429-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBQEzvXIQmpPrTmxjT8T6%2Fuploads%2FNtjUmudhEx97946efWkH%2Funknown.png?alt=media&amp;token=97458c47-35dc-44ef-b459-9ef66785b554" alt="" height="320" width="624">

1. ### Translation by BOGOS

* Users can manually create translations for the app elements or use the automatic translation option provided by AI.
* When the store language setting is changed, the elements of the app will automatically update to match the selected language.

{% hint style="warning" %}
IMPORTANT\
**Product names** within the Gift Slider and Classic Bundle sections are not translatable and will remain in original languages.

**Discount values (percentage or amount off)** within the Classic Bundle section also cannot be translated.
{% endhint %}

### 2. Translation by 3rd-Party Integration

* When a 3rd-party translation service is integrated (currently supported: Transcy, with Weglot integration coming soon), BOGOS will automatically adopt the translations provided by the external service.
* In this mode, BOGOS’s own translation system will be disabled, and the app will rely entirely on the 3rd-party service for language translation.

**How to integrate BOGOS with 3rd-party translation apps?** Read our guide on the [Integration x Translation apps](https://docs.bogos.io/integration/translation-apps.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.bogos.io/detailed-guide/translation.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.
