> 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/stammdatenverwaltung/sammelupload-uber-upload-data.md).

# Sammelupload über „Upload Data“

Die Seite **Upload Data** fasst Kategorien, Produkte und Bestand zusammen.

### Tatsächliche Richtung

Die markierten Daten werden **von Business Central nach Magento hochgeladen**.

{% hint style="warning" %}
Beschriftungen wie „Import Products“ sind irreführend; es handelt sich um Uploads.
{% endhint %}

### Wirksame Auswahlfelder

Upload Category, Upload Products und Upload Inventory. Beim Produktlauf werden auch konfigurierbare Produkte, Bundles, Bilder und Links angestoßen.

### Felder ohne Wirkung

In Version 27.10.0.16 wertet die Aktion **Upload Customer Price**, **Upload Customer** und **Upload All Inventory** nicht aus.

### Sicherer Ablauf

Shop/Mappings prüfen → Kategorien → Testprodukte → Bilder/Links → Bestand → Activity Log.

{% hint style="danger" %}
**Upload All** erst nach erfolgreichen Einzeltests verwenden.
{% 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 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/stammdatenverwaltung/sammelupload-uber-upload-data.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.