> 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/onboarding-and-best-practices/operate-multiple-sales-channels.md).

# Operate Multiple Sales Channels

You can serve multiple Shopware **sales channels** through a single connection – for example, different storefronts or brands.

**Procedure**

{% stepper %}
{% step %}
**Map the channels**

Mark the default channels in the mapping.
{% endstep %}

{% step %}
**Control the assortment per channel**

Assign items to specific channels – see [Sales Channels on the Item](/shopware/shopware6_en_us/master-data-management/sales-channels-on-the-item.md).
{% endstep %}

{% step %}
**Check visibility**

After the upload, the connector sets the visibility per channel automatically. Check how the items appear in each storefront.
{% endstep %}
{% endstepper %}

**Recommendations**

* Clearly define which items belong in which channel.
* Use tags to structure assortments across channels.

{% hint style="info" %}
An item that is not assigned to a channel is **not visible** in that channel – if products are missing, check the channel assignment first.
{% 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.solutioo.de/shopware/shopware6_en_us/onboarding-and-best-practices/operate-multiple-sales-channels.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.