> 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/sales-document-items-and-options.md).

# Sales Document, Items, and Options

The created BC sales document takes over Magento header and line data.

### Header

Magento numbers, customer, addresses, payment/shipping method, location, currency, prices-including-tax, and external reference.

### Item Lines

SKU is mapped to a BC item. Quantity, price, discount, tax, and variant information (if applicable) are transferred.

### Shipping Costs

Depending on setup, shipping costs are created as a G/L account line. Verify the account, posting groups, tax, and Replace Magento Shipping Cost.

### Product Options

With **Download Order Item Options** enabled, ordered options are added as information lines.

{% hint style="warning" %}
Information lines are not inventory-affecting item lines. Verify they do not unintentionally affect posting or print layout.
{% endhint %}

### Number Series

The configured Sales Order No. Series can change the global Order Nos. After testing, verify the global setup.


---

# 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/sales-document-items-and-options.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.