> 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/set-up-shipping-costs.md).

# Set Up Shipping Costs

During the order import, the connector transfers the **shipping costs** calculated in Shopware as a separate document line. You define whether this line is an **item** or a **G/L account**.

**Settings**

| Field                          | Meaning                                                       |
| ------------------------------ | ------------------------------------------------------------- |
| **Shipping Costs Type**        | *Item* or *G/L Account*                                       |
| **Shipping Costs Item**        | Item No. for the shipping cost line (for type Item)           |
| **Shipping Costs G/L Account** | G/L account for the shipping cost line (for type G/L Account) |

**Process**

{% stepper %}
{% step %}
**Choose the type**

Decide whether shipping costs are to be posted as an item (for example "SHIPPING") or as a G/L account.
{% endstep %}

{% step %}
**Enter the reference**

Enter the matching item number or G/L account in the configuration.
{% endstep %}

{% step %}
**Automatic transfer**

During the order import, the shipping amount from Shopware is added automatically as a line (provided it is greater than 0).
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Recommendation:** A dedicated shipping cost item makes reporting and VAT handling easier than posting to a G/L account only.
{% endhint %}


---

# 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/set-up-shipping-costs.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.