> 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/shopware/shopware6_en_us/configuration/status-management-and-order-status.md).

# Status Management & Order Status

Shopware manages order states through a **state machine** (status management) with defined **status transitions**. The connector uses these to automatically report the order status back to Shopware when specific events occur in BC.

**Setup**

1. Import the status management and transitions using [Load Initial Data](/shopware/shopware6_en_us/configuration/load-shopware-initial-data.md).
2. Define the following in the configuration:
   * **Order Status on Shipment** – which transition is triggered when a shipment is posted.
   * **Order Status on Invoice Creation** – which transition is triggered when an invoice is posted.
   * **Send Order Status Email** – whether Shopware sends an email to the customer when the status changes.

{% hint style="info" %}
The statuses are selected through a lookup on the loaded status transitions. If no values are available here, run **Load Initial Data** first.
{% endhint %}

**Feedback process**

```mermaid
flowchart LR
    A[Lieferung in BC buchen] --> B[Status Lieferung an Shopware]
    C[Rechnung in BC buchen] --> D[Status Rechnung an Shopware]
    B --> E{E-Mail senden?}
    D --> E
    E -->|ja| F[Shopware benachrichtigt Kunden]
```

For more information, see [Status Feedback to Shopware](/shopware/shopware6_en_us/order-processing/status-feedback-to-shopware.md).


---

# 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/shopware/shopware6_en_us/configuration/status-management-and-order-status.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.