> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/cross-selling-for-cart-and-checkout/pre-requisites.md).

# Pre-Requisites

## Supported environments

The plugin runs on **self-hosted Shopware installations** and in **PaaS environments (Cloud)** as long as at least **Shopware 6.7.0.0** is installed.

{% hint style="warning" %}
SaaS environments are not supported.
{% endhint %}

## System requirements

| Component     | Requirement                                      |
| ------------- | ------------------------------------------------ |
| Shopware      | 6.7.0.0 or newer                                 |
| PHP           | 8.2 or newer                                     |
| MySQL/MariaDB | as required by Shopware 6.7                      |
| Theme         | Shopware Default Theme or themes derived from it |

## Sales channels

The plugin is activated **per sales channel**. In shops with multiple sales channels you can selectively enable cross-selling only where it is needed — for example switched on in your B2C shop and off in your B2B shop.

## Recommended preparation

To create meaningful rules right away during the quickstart, the following should ideally already exist in your shop:

* **At least one well-maintained product catalog** with active products.
* **Optional: dynamic product groups** (Catalogues → Dynamic product groups) — these make it considerably faster to assign whole product ranges to a rule.
* **Optional: Shopware cross-sellings** on products — if you already maintain them, the plugin can reuse them without double work.

None of this is mandatory — but each of these makes creating your first rule noticeably quicker.


---

# 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.premsoft.de/en/plugins/cross-selling-for-cart-and-checkout/pre-requisites.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.