> 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/troubleshooting-and-support/presets-initial-setup-catalog-sync-and-sales-sync.md).

# Presets: Initial Setup, Catalog Sync, and Sales Sync

Presets prepare a cockpit selection in a logical order. They do not execute the selection themselves.

### Run Initial Setup

Marks payment/shipping methods, websites, store views, taxes, attributes, customer groups, and statuses. Then run **Run Selected** and subsequently complete the mappings.

### Run Catalog Sync

Marks Categories, Category Details, and Category Products. Then run **Run Selected**. Products are processed separately via the Products area.

### Run Sales Sync

Marks Orders and — if enabled — Credit Memos. Then run **Run Selected**.

{% hint style="danger" %}
Downloading credit memos does not mean a correct BC sales credit memo is created. The documented blanket order malfunction remains.
{% endhint %}

### Verify Selection

Check Enabled, Ready, Run Order, and Blocking Reason. After execution, verify the result count and business logs; a green cockpit row alone is not proof of success.


---

# 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/troubleshooting-and-support/presets-initial-setup-catalog-sync-and-sales-sync.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.
