> 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/order-processing/order-intake-from-shopware-into-bc.md).
# Order Intake from Shopware into BC
Learn how orders are imported from Shopware into Business Central.
The Shopware 6 API Connector enables the automatic import of orders from your online shop into Business Central.
### 1. Order Import
{% columns %}
{% column width="41.66666666666667%" %}
#### Manual Import
1. Click *"Shopware"* :right: *"Download Orders"*.
2. The new orders are imported.
{% endcolumn %}
{% column width="58.33333333333333%" %}
#### Automatic Import
For the automatic import:
1. Create a **Job Queue Entry.**
2. Select the corresponding codeunit.
3. Define the interval (for example, every 15 minutes)
{% endcolumn %}
{% endcolumns %}
### 2. Imported Data
{% columns %}
{% column width="50%" %}
#### Order Header
| Shopware Field | BC Field |
|---|
| Order number | External Document No. |
| Order date | Document Date |
| Customer | Sell-to Customer No. |
| Billing address | Sell-to Address |
| Shipping address | Ship-to Address |
{% endcolumn %}
{% column width="50%" %}
#### Order Lines
| Shopware Field | BC Field |
|---|
| Item number | No. |
| Item name | Description |
| Quantity | Quantity |
| Unit price | Unit Price |
| VAT | VAT % |
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column width="83.33333333333334%" %}
#### Additional Data
* **Shipping costs:** are created as a separate line.
* **Discounts:** are processed as line discounts or vouchers.
* **Payment information:** the payment method is mapped.
{% endcolumn %}
{% column width="16.666666666666657%" %}
{% endcolumn %}
{% endcolumns %}
### 3. Order Status Filter
You can filter which orders are imported:
| Status | Description | Import recommended |
|---|
| open | New order | ✅ Yes |
| in_progress | In progress | ✅ Yes |
| completed | Completed | ⚠️ Optional |
| cancelled | Canceled | ❌ No |
### Frequently Asked Questions
#### As which document type is a Shopware order created in Business Central?
This is controlled by the “Download Order As” configuration option: Quote, Order or Invoice. The document is only created automatically if “Generate Sales Order” is also enabled. The number series used comes from “Sales Ord No.Series”, and the location from “Ord Download Location”.
#### How do I recognize in Business Central which Shopware order a document came from?
The connector stores the fields “SOUSHW Web Order ID”, “Web Order No” and “Web Order Auto Increment” on the sales document. In addition, the external document number is set in the format `SW:{order number}`, so that every BC order can be assigned unambiguously to the Shopware order.
#### How is the customer of an order determined?
The connector loads the Shopware customer via `customer/{id}` and looks for the matching customer using the “SOUSHW Web ID” or – depending on “Cust. Mapping Type” – by email, phone or mobile number. Guest orders are posted to the “Default Guest Cust.”; if “Create Unknown Cust.” is enabled, a new customer is created from the “Cust. Template” when no match is found.
---
# 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/order-processing/order-intake-from-shopware-into-bc.md?ask=&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.
