> 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/artikel-feldmapping-attribute-und-variantenachsen.md).

# Artikel-Feldmapping, Attribute und Variantenachsen

Der Connector trennt Feldmapping, Magento-Attribute und Variantenachsen.

### Artikel-Feldmapping

Business-Central-Felder können Magento-Attributcodes zugeordnet werden. Mappingzeilen tragen den Webshopbezug.

### Magento-Attribute

Initialdaten laden Attribute, Optionen, Typ, Scope und Such-/Filtereigenschaften. Prüfen Sie Attribute Sets vor Produktuploads.

### Variantenachsen

Die Seite **Variant Axes** definiert beliebig viele Achsen pro Webshop, z. B. Farbe, Größe, Material oder Länge.

1. Zeile pro Achse anlegen.
2. Magento Attribute Code hinterlegen.
3. BC-Quelle zuordnen.
4. Reihenfolge festlegen.
5. Achse aktivieren.
6. Testfamilie hochladen.

{% hint style="info" %}
Zentrale Variantenachsen ersetzen die älteren Color-/Size-Sonderfelder.
{% endhint %}

### Grenzen

Bei bestimmten einfachen Varianten werden Preis, Gewicht und kundenspezifische Achsenattribute nicht in allen Routinen vollständig geschrieben. Testen Sie Ihren Variantentyp.


---

# 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/konfiguration/artikel-feldmapping-attribute-und-variantenachsen.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.