> 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/configuration/websites-store-views-customer-groups-and-msi.md).

# Websites, Store Views, Customer Groups, and MSI

Four mapping areas are important for multi-store, language, customer, and warehouse processes.

### Websites

Use **Selected** to define which Magento websites receive product uploads.

### Store Views

Map a BC language code, mark active views, and run validation.

### Customer Groups

Map a Magento Customer Group to a BC Customer Price Group. Test the pricing effect separately.

### MSI Sources

Map a Magento Source Code to a BC Location Code. Only active mappings are considered.

{% hint style="warning" %}
A missing or incorrect location mapping leads to wrong quantities or skipped sources.
{% endhint %}

### Recommended Test

1. Select a website and Store View.
2. Validate the language.
3. Map an MSI source.
4. Upload a test item.
5. Verify texts, visibility, and quantity in Magento.


---

# 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/magento-2-api-connector/magento2_en_us/configuration/websites-store-views-customer-groups-and-msi.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.