> 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/download-orders.md).

# Download Orders

Orders can be downloaded individually, via the Download Cockpit, or through a verified background job.

### Prerequisites

* Shop active and connection successful
* Allows Order Download enabled
* Downloadable Order Status maintained for interactive runs
* Payment, shipping, and tax mappings complete
* Customer and number series setup present

### Status Filter

{% hint style="warning" %}
The **Selected** checkbox of the Magento status list is not evaluated for the interactive order filter in version 27.10.0.16. The authoritative setting is **Downloadable Order Status**. The separate standard job uses hard-coded status values.
{% endhint %}

### Single Order

Enter the Magento order ID, start the download, and check the dashboard entry and message.

### Batch Run

Download Cockpit → select Orders → refresh Preflight → start the run → verify count/status.

### Start From Order ID

Limits the starting point. Only change this with knowledge of the Magento ID sequence.


---

# 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/download-orders.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.