> 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/master-data-management/items-and-catalog-overview.md).

# Items & Catalog Overview

Business Central serves as the source for item master data and inventory in the standard scenario. The connector can additionally load Magento products, categories, images, and assignments into BC.

### Supported Areas

* Simple products
* Configurable products with freely definable variant axes
* Bundle products
* Product attributes and custom options
* Categories and product-category assignments
* Main and additional images
* Related items
* Store-view-specific texts and SEO data

### Basic Rule for Uploads

A product upload processes the current BC state. Synchronization fields show Web ID, status, timestamp, and messages.

{% hint style="info" %}
Actions are partly labeled "product import", "inventory import", or "image import". In fact, they send data **from Business Central to Magento**.
{% endhint %}

### Recommended Approach

1. Set up websites, store views, attribute sets, and variant axes.
2. Review item master data and Magento fields.
3. Assign categories, attributes, texts, and images.
4. Upload a single product.
5. Verify the result in Magento and the logs.
6. Only then use bulk upload.


---

# 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/master-data-management/items-and-catalog-overview.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.
