> 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/getting-started/system-requirements-and-compatibility.md).

# System Requirements & Compatibility

So that the Shopware 6 API Connector works reliably, the following requirements should be met.

**Business Central**

* **Microsoft Dynamics 365 Business Central** – cloud (SaaS) **or** on-premises.
* A currently supported platform/application version (the app is continuously adapted to new BC releases).
* Permissions to install extensions and to assign the permission set that is supplied with the app.

**Shopware 6**

* **Shopware 6**, **version 6.4 or higher** recommended.
* A reachable **Admin API** at `https://<ihr-shop>/api`.
* API access – either an **administration user** (password grant) or an **integration access** (Access Key ID / Secret Access Key).

{% hint style="info" %}
The two access variants and their advantages and disadvantages are described in [Authentication Methods in Detail](/shopware/shopware6_en_us/configuration/authentication-methods-in-detail.md).
{% endhint %}

**Network & availability**

| Requirement               | Description                                                                                   |
| ------------------------- | --------------------------------------------------------------------------------------------- |
| Outbound HTTPS connection | Business Central must be able to reach the Shopware Admin API via HTTPS.                      |
| Valid certificate         | The Shopware instance should have a valid TLS certificate.                                    |
| Stable base URL           | The website URL should not change constantly (otherwise the credentials have to be adjusted). |

**Premium modules**

Some functions (for example the **PDF document upload**, **group items**, and **SharePoint documents**) require additional Shopware plugins from solutioo. You can read which function has which prerequisite in [Editions & Modules (Basic vs. Premium)](/shopware/shopware6_en_us/getting-started/editions-and-modules-basic-vs.-premium.md).

{% hint style="warning" %}
For **on-premises** installations of Business Central, outbound web services (outbound HTTP) must be enabled for the extension.
{% endhint %}

**Frequently asked questions**

<details>

<summary>Does the connector work with Shopware 6 Cloud (SaaS)?</summary>

Yes, provided that the Admin API is reachable and you can create an integration access or an administration user.

</details>

<details>

<summary>Do I absolutely need Shopware 6.4+?</summary>

6.4 or higher is recommended. Older versions can have different API fields; if in doubt, talk to our team.

</details>


---

# 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/getting-started/system-requirements-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.