> 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/configuration/item-field-mapping-attributes-and-variant-axes.md).

# Item Field Mapping, Attributes, and Variant Axes

The connector separates field mapping, Magento attributes, and variant axes.

### Item Field Mapping

Business Central fields can be mapped to Magento attribute codes. Mapping lines carry the web store reference.

### Magento Attributes

The initial data download loads attributes, options, type, scope, and search/filter properties. Review Attribute Sets before product uploads.

### Variant Axes

The **Variant Axes** page defines any number of axes per web store, for example Color, Size, Material, or Length.

1. Create a line per axis.
2. Enter the Magento Attribute Code.
3. Assign the BC source.
4. Set the sequence.
5. Activate the axis.
6. Upload a test family.

{% hint style="info" %}
Central variant axes replace the older Color/Size special fields.
{% endhint %}

### Limitations

For certain simple variants, price, weight, and customer-specific axis attributes are not fully written in all routines. Test your variant type.


---

# 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/configuration/item-field-mapping-attributes-and-variant-axes.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.