> 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/getting-started/guided-setup-wizard.md).

# Guided Setup Wizard

The wizard guides you through setup in eight steps and blocks when required fields are missing.

### Step 1 – Welcome

Enter shop code, name, URL, and API path.

### Step 2 – Authentication

Choose method and credentials, run **Test Connection**.

### Step 3 – Initial Data Download

Download initial data; verify last download and Cockpit readiness.

### Step 4 – Required Mappings

Auto-suggest payment, shipping, and tax mappings; complete manually.

### Step 5 – Orders & Fulfillment

Define download, document type, automatic creation, number series, start ID, location, and tax behavior.

### Step 6 – Customer Defaults

Choose customer creation or default customers and customer template.

### Step 7 – Catalog & Inventory

Review uploads, variants, MSI mode, category, Attribute Set, visibility, and source/language mappings.

### Step 8 – Summary

Verify connection, initial data, mappings, number series, and overall status. **Finish** activates the shop.

{% hint style="info" %}
For an incomplete existing setup, the wizard opens at the first still-open step.
{% 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/magento2_en_us/getting-started/guided-setup-wizard.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.
