> 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/konfiguration/katalog-und-bestand-einrichten.md).

# Katalog und Bestand einrichten

Diese Einstellungen legen Standardverhalten für Produkte und Bestände fest.

### Katalogfelder

* Allow Item Upload
* Upload Item Image
* Upload Simple Variants
* Use Model as Configurable
* Upload Bundle Items
* Upload Product Category
* Update Product URL
* Set Item Category According to Magento
* Default Category / Attribute Set / Visibility

### Variante versus Modell

**Use Model as Configurable** bestimmt, ob ein Modell als Magento-Elternprodukt verwendet wird. Variantenachsen werden zentral gepflegt; ältere Color-/Size-Felder sind veraltet.

### Kategorien

**Upload Product Category** sendet Produkt-Kategorie-Zuordnungen. Die Standardkategorie ist Fallback.

### MSI-Bestand

* Inventory Sync Mode = Magento MSI
* Upload Inventory
* Upload Variant Inventory
* Allow Update Magento Inventory
* MSI Source → BC Location

{% hint style="warning" %}
Legacy Stock Item ist in dieser Version nicht zuverlässig. Verwenden Sie MSI nach erfolgreichem Mappingtest.
{% endhint %}

### Negative Mengen

Der Schalter **Upload Negative Quantity** beeinflusst den aktuellen MSI-Upload nicht. Regeln Sie negative Mengen organisatorisch.


---

# 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/konfiguration/katalog-und-bestand-einrichten.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.