> 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/the-magento-configuration-card.md).

# The Magento Configuration Card

The **Magento Configuration** page contains exactly one record per web store. The **Web Store Code** is the central key for configuration, mapping, downloads, and logs.

### Setup Areas

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>⚙️ General</strong></td><td>Store code, name, active status, and last connection status.</td></tr><tr><td><strong>🔌 Connection</strong></td><td>Base URL, API path, authentication, test status, and initial download.</td></tr><tr><td><strong>🧾 Orders &#x26; Documents</strong></td><td>Download, document type, number series, status filter, and fulfillment.</td></tr><tr><td><strong>🧮 Taxes &#x26; Posting</strong></td><td>Posting groups, tax mapping, and prices including tax behavior.</td></tr><tr><td><strong>👤 Customers</strong></td><td>Customer creation, default customers, and templates.</td></tr><tr><td><strong>🛍️ Catalog &#x26; Products</strong></td><td>Categories, items, images, variants, bundles, and default values.</td></tr><tr><td><strong>📦 Inventory Sync</strong></td><td>Magento MSI, sources, variant inventory, and negative quantities.</td></tr><tr><td><strong>🧩 Variant Axes</strong></td><td>Central link to the attributes that form variants.</td></tr></tbody></table>

{% hint style="info" %}
The Magento base URL is maintained without a trailing `/`; the default path is `/rest/all/V1`.
{% endhint %}

### From Connection to Active Store

{% stepper %}
{% step %}
**Create a record**

Assign a unique Web Store Code and a descriptive name.
{% endstep %}

{% step %}
**Test the connection**

Verify credentials and URL; review Last Connection Status and Last Error.
{% endstep %}

{% step %}
**Download initial data**

Retrieve reference data from Magento and then complete the mappings.
{% endstep %}

{% step %}
**Review Health and suggestions**

Use Setup Health and Apply Setup Suggestions as verification tools.
{% endstep %}

{% step %}
**Set Active only after individual tests**

Run item, inventory, and order tests with test data end to end.
{% endstep %}
{% endstepper %}

### Key Actions

{% columns %}
{% column width="50%" %}
**Setup**

* Test Connection
* Download Initial Data
* Guided Setup
* Mapping Hub
* Setup Health
  {% endcolumn %}

{% column width="50%" %}
**Operate & verify**

* Apply Setup Suggestions
* Migration Verification
* Download Cockpit
* Developer Log Setup
* Reset Magento Data
  {% endcolumn %}
  {% endcolumns %}

{% hint style="danger" %}
**Reset Magento Data** is not a web-store-specific configuration reset. The implementation resets Magento and sync fields on items and variants tenant-wide, deletes all parent items, and resets image sync data. Configuration, mappings, Store Views, MSI mappings, dashboard, and logs are preserved.
{% 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 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/the-magento-configuration-card.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.