> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/product-configurator/admin-dashboard/multilingual.md).

# Multilingual

The configurator is fully **multilingual**. If you run your shop in several languages, you can maintain all customer-facing texts per language.

## What is translatable

Storable per language are, among others:

* a field's **label**
* the **placeholder**
* the **option names** of select lists
* the **default value**
* the **info text** of the help popover
* the **label of the add button** for repeatable sections
* contents of **rich text** and **explanation** elements

## How to translate

1. Open your configurator in the **Elements** tab.
2. Switch the **language** at the top to the desired translation.
3. Enter the texts in the respective language and save.

This works exactly like Shopware's built-in tools (e.g. categories or products).

## Default language and fallback

* **English** is the default language and needs no special marking.
* Mandatory texts (e.g. the field label) only have to be filled in the **default language**.
* If you leave a translation empty, the shop automatically falls back to the default language. So the customer never sees an empty field, but in case of doubt the default text.

## Activation per sales channel

Independent of language, the configurator can be activated or deactivated **per sales channel** (see [Plugin configuration](/en/plugins/product-configurator/configuration.md)). This lets you, for example, run an international channel differently from your main shop.

{% hint style="info" %}
First maintain the default language completely, then add the translations. Thanks to the fallback to the default language, your shop remains fully functional throughout.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.premsoft.de/en/plugins/product-configurator/admin-dashboard/multilingual.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.