> 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/prerequisites-and-compatibility.md).

# Prerequisites and Compatibility

What you need before installation: Business Central version, GLS credentials, master data and compatibility notes.

Check these points before installation. This prevents the setup from failing because of missing credentials or incomplete master data.

## Business Central

| Requirement                 | Value                                   |
| --------------------------- | --------------------------------------- |
| Product                     | Microsoft Dynamics 365 Business Central |
| Minimum application version | 25.0                                    |
| App version described       | 26.13.40.0                              |
| Dependencies on other apps  | none                                    |

The app requires at least Business Central 25.0. Business Central shows you during installation whether a specific version can be installed in your environment.

For the rollout, we recommend a **Business Central sandbox**. There you can complete the setup and a test shipment without changing your production company.

## GLS

You need the following from GLS:

* a business customer contract that is enabled for your GLS shipping API,
* access to the GLS shipping API with a **Client ID**, **Client Secret** and **Contact ID**,
* **separate credentials for sandbox and production**,
* the products and services approved in your contract, for example for international shipping, hazardous goods, ShopReturn or Pick\&Return.

{% hint style="warning" %}
A successful connection test only confirms that the sign-in works. It does not confirm that a specific product, country or service is enabled in your GLS contract.
{% endhint %}

## Master data in Business Central

* **Company Information** or an alternative shipper address with a complete address.
* **Countries/Regions** with a maintained EU Country/Region Code. The connector uses it to determine whether a shipment crosses a customs border.
* **Items** with weights and, ideally, dimensions on the item units of measure.
* At least one **GLS box** or a reasonable default maximum weight in the configuration.
* Customers with complete ship-to addresses.

For details, see [Prepare Boxes and Items](/gls-connector/gls-connector_en_us/setup/boxes-and-items.md).

## Printing

The app provides labels as PDF, PNG or Zebra. Use PNG for integrated batch printing from Business Central. Zebra data requires a suitable label printer and a way to send the file to it. For more information, see [Labels, Printing and Tracking](/gls-connector/gls-connector_en_us/daily-work/labels-printing-and-tracking.md).

## People and permissions

* A person with administrator rights installs the app and assigns permission sets.
* Anyone who maintains the setup needs **GLS Super User**.
* Anyone who ships needs at least **GLS Integration User**.

See [Installation and Permissions](/gls-connector/gls-connector_en_us/installation-and-permissions.md).


---

# 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/prerequisites-and-compatibility.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.