> 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/order-processing/orders-and-documents-overview.md).

# Orders & Documents Overview

The sales process begins with downloading a Magento order. It appears in the Order Dashboard and, depending on setup, can be created immediately or manually as a BC sales document.

### Standard Flow

1. Download order.
2. Check dashboard entry and message.
3. Apply customer, payment, shipping, and tax mappings.
4. Create or open the BC sales document.
5. Verify item and option lines.
6. Post shipment and invoice in BC.
7. Report shipment, tracking, and invoice to Magento.

### References

The Magento order number and internal ID are carried on the BC document. The dashboard shows sales, shipment, and invoice numbers.

{% hint style="warning" %}
Before the first production order, verify tax posting, shipping costs, payment method, location, and number series.
{% endhint %}

The connector protects against duplicate orders and can restore missing dashboard links. Nevertheless, only retry a run after investigation.


---

# 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/order-processing/orders-and-documents-overview.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.