> 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/erste-schritte/mehrere-webshops-websites-und-store-views.md).

# Mehrere Webshops, Websites und Store Views

Business Central, Magento und der Connector verwenden unterschiedliche Ebenen:

* **Webshop-Konfiguration in BC**: Verbindung und Verhalten
* **Magento Website**: kommerzieller Verkaufskanal
* **Magento Store View**: sprach- oder darstellungsspezifische Ansicht

### Mehrere Connector-Shops

Jede Konfiguration besitzt einen eindeutigen Web Store Code. Mappings und Downloadstatus werden diesem Shop zugeordnet.

{% hint style="warning" %}
Prüfen Sie Shopfilter besonders im Mapping Hub, Download Cockpit, Dashboard und bei Migrationsprüfungen.
{% endhint %}

### Websites auswählen

Markieren Sie in **Magento Website Selection** mit **Selected**, welche Websites Produktuploads erhalten. Der Admin-Kontext ist kein normaler Verkaufskanal.

### Store Views und Sprachen

1. Store Views laden.
2. **Auto-Map Languages** ausführen.
3. Sprachcodes prüfen.
4. ungenutzte Views deaktivieren.
5. **Validate Store Views** ausführen.
6. lokalisierte Texte pflegen.

### Default und Overrides

Zuerst wird der Standardwert hochgeladen, danach folgen Store-View-spezifische Namen, Beschreibungen, SEO-, Status- und Sichtbarkeitswerte.


---

# 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/erste-schritte/mehrere-webshops-websites-und-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.