> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/shopware/shopware6_en_us/master-data-management/multilingual-item-data.md).

# Multilingual Item Data

The connector supports **multilingual product data**. The name and description can be transferred to Shopware per language.

**Basis**

* The **language mapping** (*Language* module) connects BC languages with Shopware languages.
* The **item translations** in BC and the language-dependent **marketing text** serve as the translation source.

**What is transferred per language?**

| BC source                      | Shopware field  |
| ------------------------------ | --------------- |
| Item translation (description) | `name`          |
| Marketing text (entity text)   | `description`   |
| Item No.                       | `productNumber` |

The transfer takes place as a language-specific update (PATCH) with the matching language header.

{% hint style="info" %}
**Web Name** and **Description** are managed separately. Multilingual product names and HTML descriptions are available in separate areas on the Item Card.
{% endhint %}

**Procedure**

1. Import the languages with [Load Shopware Initial Data](/shopware/shopware6_en_us/configuration/load-shopware-initial-data.md) and map them in the *Language* module.
2. Maintain the item translations in BC.
3. Enter the language-dependent marketing text (see [Marketing Text & Rich Content](/shopware/shopware6_en_us/master-data-management/marketing-text-and-rich-content.md)).
4. Upload the item – the language variants are transferred along with it.

### Frequently Asked Questions

#### What is required for the multilingual transfer?

The BC languages must be mapped to the Shopware languages in the “Language” module. To do this, first load the initial data and then maintain the mapping. Without a language mapping, no translations are transferred.

#### Where do the name and description for each language come from?

The language-dependent product name comes from the item translations in Business Central, and the long description comes from the language-dependent marketing text. During the upload, both are passed to Shopware as a language variant (PATCH with a language header).


---

# 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.solutioo.de/shopware/shopware6_en_us/master-data-management/multilingual-item-data.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.