> 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/magento-2-api-connector/magento2_en_us/getting-started/multiple-webshops-websites-and-store-views.md).

# Multiple Webshops, Websites, and Store Views

Business Central, Magento, and the connector use different levels:

* **Webshop configuration in BC**: Connection and behavior
* **Magento Website**: Commercial sales channel
* **Magento Store View**: Language- or presentation-specific view

### Multiple Connector Shops

Each configuration has a unique Web Store Code. Mappings and download statuses are assigned to this shop.

{% hint style="warning" %}
Pay special attention to shop filters in the Mapping Hub, Download Cockpit, Dashboard, and during migration checks.
{% endhint %}

### Selecting Websites

In **Magento Website Selection**, mark with **Selected** which websites should receive product uploads. The admin context is not a normal sales channel.

### Store Views and Languages

1. Download Store Views.
2. Run **Auto-Map Languages**.
3. Verify language codes.
4. Deactivate unused views.
5. Run **Validate Store Views**.
6. Maintain localized texts.

### Default and Overrides

The default value is uploaded first, followed by Store View-specific names, descriptions, SEO, status, and visibility values.


---

# 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/magento-2-api-connector/magento2_en_us/getting-started/multiple-webshops-websites-and-store-views.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.
