> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/configuration-assistant.md).

# Configuration assistant

The setup assistant creates your first recommendation templates in a few steps and assigns them to the cart.

In the Administration, the configuration assistant is called "Setup wizard". It guides you through creating your first recommendation templates with simplified settings. It is most useful right after the initial setup, when no template exists yet. You can change all values later in the full template editor.

## Start the assistant

There are two ways:

* In the plugin dashboard (**Content → InsightSearch**), click **"Setup wizard"** at the top right.
* As long as there is no template, the overview shows the notice "No recommendation templates yet" with the button **"Start setup wizard"**.

The assistant replaces the page content, and the sidebar is hidden while it runs. Your progress is remembered in the browser. If you close the page by accident, you can continue at the same point later.

## Controls

| Button   | Effect                                    |
| -------- | ----------------------------------------- |
| "Next"   | Go to the next step.                      |
| "Back"   | Go to the previous step.                  |
| "Skip"   | The template of this step is not created. |
| "Cancel" | Leave the assistant.                      |

Nothing is created until the very end, then all templates are created at once.

## The steps

Which steps you see depends on your plan. The assistant only shows recommendation types and features included in your plan.

{% stepper %}
{% step %}

### "Welcome"

A short explanation of the assistant. Click **"Let's go"**.
{% endstep %}

{% step %}

### One step per recommendation type

Each recommendation type in your plan has its own step:

| Step                          | Shows                                                                               | From plan |
| ----------------------------- | ----------------------------------------------------------------------------------- | --------- |
| "Similar Products"            | Products that complement the product being viewed, for example on the product page. | Basic     |
| "Recently Viewed"             | Products the customer has viewed in this session.                                   | Basic     |
| "Top Sellers"                 | Your best-selling products. Works well on category pages or the home page.          | Starter   |
| "Buy again"                   | Products from the customer's own order history. Intended for the account area.      | Starter   |
| "Product Bundles"             | Products that are often bought together. Good on the product page.                  | Expert    |
| "Trends"                      | Currently popular products, based on click and purchase data.                       | Expert    |
| "Personal Recommendations"    | Products tailored to the individual customer's behaviour.                           | Expert    |
| "Continue where you left off" | Products the customer added to the cart but never ordered.                          | Expert    |
| "Inspired by your wishlist"   | Products based on the wishlist of logged-in customers.                              | Expert    |

Each of these steps has three fields:

| Field                     | Meaning                                                                        | Default                                           |
| ------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------- |
| "Template name"           | Internal name to recognise the template.                                       | Name of the step, for example "Ähnliche Produkte" |
| "Max. number of products" | The maximum number of products shown (1 to 50).                                | 6                                                 |
| "Button type"             | Button on the product card: "Add to cart", "Show details" or "Details + cart". | "Add to cart"                                     |

{% hint style="info" %}
The default template names are in German, also in the English Administration (for example "Ähnliche Produkte" or "Topseller"). Rename them if you like. For "Inspired by your wishlist", the Shopware wishlist must be enabled in the relevant sales channel.
{% endhint %}
{% endstep %}

{% step %}

### "Bundle / Set"

{% hint style="info" %}
Available from plan Expert.
{% endhint %}

This step creates a bundle/set template: a product selection shown next to a main product as a complement, for example "Frequently bought together".

| Field                     | Meaning                                                                  | Default                   |
| ------------------------- | ------------------------------------------------------------------------ | ------------------------- |
| "Template name"           | Internal name.                                                           | "Häufig zusammen gekauft" |
| "Max. number of products" | Maximum number of products in the configurator.                          | 6                         |
| "Product source"          | "Manual product selection", "Dynamic product stream" or "Cross-selling". |                           |

Depending on the source, another field appears. For "Dynamic product stream" you choose the group. For "Cross-selling" you enter the "Cross-selling name" exactly as it is set on the products. Below it, the assistant lists "Existing cross-sellings in your shop (click to apply):". One click applies the name.
{% endstep %}

{% step %}

### "Cart Assignment"

{% hint style="info" %}
Available from plan Starter.
{% endhint %}

Here you assign templates to the cart. These recommendations then appear without being placed in a Shopping Experience.

| Field                                    | Effect                                        |
| ---------------------------------------- | --------------------------------------------- |
| "Cart page recommendation template"      | Recommendations on the cart page.             |
| "Offcanvas cart recommendation template" | Recommendations in the side cart (offcanvas). |

You can only choose templates you create in this run. The assignment applies to all sales channels.
{% endstep %}

{% step %}

### "Finish"

The assistant shows a summary: "All set! {count} template(s) will be created." with all templates and assignments. Check the details and click **"Create templates & finish"**.
{% endstep %}
{% endstepper %}

## After the assistant

{% hint style="warning" %}
Templates only become visible in the shop once you embed them. Recommendation templates go into a Shopping Experience as an element, for example in the product page layout. Only the cart assignments appear without a Shopping Experience.
{% endhint %}

1. You find your new templates in the sidebar under **Delivery → Recommendation templates**, the bundle template under **Delivery → Bundle/set templates**.
2. Open **Delivery → Placements** and check in the sections "Offcanvas" and "Cart" whether "Enable" is switched on and the right template is selected.
3. Embed the other templates via **Content → Shopping Experiences**. The page [Getting started](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/getting-started.md) shows how.

You can start the assistant again at any time. Existing templates are left untouched; the assistant only creates new ones. Give them different names so you can tell the templates apart in the list.

## Read more

{% content-ref url="/pages/2dkUkWwHSp2l8a2do7ni" %}
[Getting started](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/getting-started.md)
{% endcontent-ref %}

{% content-ref url="/pages/hSRY2MxmbdY5dCCa9KY4" %}
[Creating recommendation templates](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/recommendation-templates.md)
{% endcontent-ref %}

{% content-ref url="/pages/T18Rtfo4NyPNuI34n60w" %}
[Placements](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/placements.md)
{% endcontent-ref %}

{% content-ref url="/pages/6AdOnxV0EK6VLHvPjoRj" %}
[Bundle and set templates](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/bundle-and-set-templates.md)
{% endcontent-ref %}


---

# 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.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/configuration-assistant.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.
