> 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/gls-connector/gls-connector_en_us/daily-work/international-shipping-and-customs.md).

# International Shipping and Customs

International shipments with GLS: set the incoterm correctly, enter international data and understand what is transmitted.

This page explains how to prepare international shipments and which details are actually sent to GLS. Which countries you may ship to is governed by your GLS contract.

## How the app detects a customs route

The app compares the shipper and recipient countries, based on the **EU Country/Region Code** values on the **Countries/Regions** page. If there is a customs border between them:

* The upload is blocked if the package has no incoterm.
* Before the upload, a dialog asks you to confirm that the goods values and accompanying documents are correct.

Maintain the EU country/region codes completely. The app does not perform a full legal customs check.

## Procedure for an international shipment

1. Create the packages on the sales order as usual.
2. Open the package card and set the **incoterm directly on the package card** (Service Details).
3. Optional: Open **International Data** and enter the details for your own records.
4. Create the accompanying documents, such as the commercial invoice, outside the app.
5. Choose **Upload Packages to GLS** and confirm the notice about goods values and accompanying documents.

{% hint style="warning" %}
The incoterm sent to GLS is the one **on the package card**. An incoterm that you enter only on the **GLS International Data** page is not copied to the package. Always set it on the package card. With multiple packages, the incoterm of the first package applies.
{% endhint %}

## International data

The **International Data** action opens **GLS International Data**.

| Field                             | Content                                 |
| --------------------------------- | --------------------------------------- |
| **Incoterm**                      | Delivery terms (local only, see note)   |
| **Commercial Invoice No.**        | Number of your commercial invoice       |
| **Invoice Date**                  | Date of the commercial invoice          |
| **Currency Code**                 | Currency of the goods values            |
| **Export Reason**                 | e.g. sale, sample, repair               |
| **Receiver EORI No.**             | EORI number of the receiver             |
| **Receiver VAT Registration No.** | VAT registration number of the receiver |

### Invoice lines

**Generate Invoice Lines** adds any items of the package that are missing from the local invoice lines. For each line, you see the item, description, quantity, unit price, line amount, unit weight, tariff number and country of origin. Maintain the tariff number and country of origin on the item so that the lines are complete.

## What is transmitted to GLS

| Detail                                | Transmitted to GLS |
| ------------------------------------- | ------------------ |
| Destination address and country codes | yes                |
| Incoterm on the package card          | yes                |
| Fields in GLS International Data      | no                 |
| Invoice lines                         | no                 |

The international data and invoice lines are for your own preparation in Business Central.

## What the app does not handle

* no electronic customs declaration
* no CN23
* no generation, printing or upload of a commercial invoice
* no paperless transmission of customs documents

Create the required accompanying documents with your usual tools and enclose them with the shipment according to GLS requirements.

## Troubleshooting

| Message or situation                         | Cause                                           | Solution                             |
| -------------------------------------------- | ----------------------------------------------- | ------------------------------------ |
| Upload blocked, incoterm missing             | Customs route detected, package has no incoterm | Set the incoterm on the package card |
| No customs notice despite non-EU destination | EU country/region code maintained incorrectly   | Check Countries/Regions              |
| Customs notice for an EU destination         | EU country/region code missing for the country  | Check Countries/Regions              |
| GLS rejects the country or product           | Not enabled in your contract                    | Clarify with GLS                     |


---

# 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/gls-connector/gls-connector_en_us/daily-work/international-shipping-and-customs.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.