> 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/catalog-processes-and-data-direction.md).

# Catalog Processes and Data Direction

The app supports download and upload processes with different data ownership.

### Magento → Business Central

Attributes/options, categories/assignments, products/details, images, related items, attribute sets, and MSI sources.

### Business Central → Magento

Simple, configurable, and bundle products, categories, images, related items, and inventory.

### Recommended Data Ownership

Define a leading system for each field. For SKU, commercial data, and inventory, BC is recommended; Magento can lead for web texts/SEO if BC does not upload them.

{% hint style="warning" %}
If the same fields are maintained in both systems, the next run can overwrite intended changes.
{% endhint %}

### Sequence

Reference data → categories → simple products → variants/parent → bundles → images → links → inventory.


---

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