> 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/troubleshooting-and-faq.md).

# Troubleshooting and FAQ

Typical problems with Cross Selling Pro and how to check and solve them step by step.

Something does not appear, shows the wrong products or figures are missing? This page lists the most common cases with checks in a sensible order. Start at the top and work through the points one by one.

{% hint style="info" %}
Many questions can be answered faster with the preview in the template or the recommendation sandbox under **Products & data → Products**. There you see which filters applied and why a product was recommended.
{% endhint %}

## The block or slider does not appear at all

Important first: a block without results is **removed from the page**. This also applies if an error occurs. There is no message and no empty area. Only the Conversion Booster shows "No recommendations available." in this case.

Check in this order:

1. **Plan:** Is the type or layout included in your plan? Types and layouts not included are not shown in the shop, without any message. The shopping experience editor then shows "Not displayed". You see your plan under **System → Plans**.
2. **Placement:** For offcanvas and cart page, check "Enable" and "Recommendation template" per sales channel. Watch out for inheritance from all sales channels.
3. **No starting product:** "Automatic (PDP)" finds nothing on pages without a product (home page, category, landing page). In the customer account, templates that need a starting product fall back to personalised recommendations or bestsellers.
4. **Too little data:** "Frequently bought together" needs orders, personalised types such as "Recently viewed" or "Continue where you left off" need tracking, the wishlist type needs saved items. Set a fallback threshold (see below).
5. **Everything filtered out:** hard filters, "Only same brand" for products without a brand, rules. The template preview marks the rule that leaves nothing.
6. **Exclusions:** The current product, its variants and, in the cart, all cart products including variants are always excluded.
7. **Visibility:** With "Only show products the customer may see" (default on), products the customer may not see in the shop are left out.
8. **Quota:** Only in the Basic plan do recommendations stop until the end of the month when the quota is reached. You see the usage under **System → Plans**.
9. **Product data missing:** Under **Products & data → Sources**, check that the source is indexed. Under **System → Settings**, check that sales channel and language have a source assigned.
10. **Mobile:** On the cart page, "Hide on mobile devices" may be on, in the offcanvas "Enable on mobile" may be off.
11. **Browser:** Open the developer tools. Are requests to InsightSearch blocked by a Content Security Policy or an ad blocker? Are there script errors from a theme?

## The slider is sometimes empty, sometimes not

Set a fallback in the element:

| Setting                | Effect                                                                                                  |
| ---------------------- | ------------------------------------------------------------------------------------------------------- |
| Fallback threshold (≤) | The fallback applies if the number of recommendations is **less than or equal to** this value (0 to 50) |
| "Fallback type"        | "No fallback", "Other template", "Fixed products" or "Dynamic product stream"                           |

Example: limit 6, fallback threshold 3, fallback "Other template" with bestsellers. A fallback template with a type not included in your plan is not used.

## Unsuitable products appear

* Choose a narrower mode in the template, such as "Only same category". If it finds too little, it moves up to the parent category. The sandbox shows this as relaxed.
* Narrow down with the rule builder (from the Expert plan), exclude variants or use the product type "Same type" (beta, after activation).
* Choose a suitable weighting profile. The explanation in the sandbox shows which signal made the difference.
* Since version 2.2.1, InsightSearch calculates filters, boosters and purchase signals together with AI similarity. Recommendations may have changed as a result.
* Boilerplate sentences in product descriptions can reduce AI similarity. The area **Products & data → AI** has a setting for the description used for AI similarity.

## The product itself or cart products are recommended

Since version 2.2.1 or 1.4.1 this should no longer happen. The current product page is always excluded, and in the cart, the offcanvas and on the interstitial page all cart products including variants as well. On product pages, you can additionally switch on "Exclude cart products" in the template (default off). If it still happens, check your plugin version.

## Changes do not show up in the shop

* **Data field changed:** Then start "Reindex".
* **Product data changed:** The change takes effect after the next transfer. With the feed, Shopware must have regenerated the export.
* **Placement or bundle/set template changed, page cached:** Clear the shop cache.
* **Recommendation template changed:** takes effect immediately, affected pages are discarded on saving.

An overview is on the page [When changes take effect](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/when-changes-take-effect.md).

## The statistics are empty or incomplete

1. **Background processing:** Cart, orders and clicks reach InsightSearch through the Shopware background processing. It must run permanently and process all queues the plugin uses. If events pile up for more than 24 hours, the plugin dashboard shows a notice with the right command. Details under [Technical operation](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/technical-operation.md).
2. **Consent:** If "Events from the browser" is set to "Only with consent", impressions and clicks from visitors without the comfort cookie are missing. With "Off", they are missing entirely.
3. **Order tracking:** Is "Enable order tracking" on, and does the sales channel with its language have a source assigned?
4. **Permissions:** Statistics and user tracking need the permission to view orders.
5. **Plan:** Full statistics are available from the Expert plan. Click rate and revenue tracking are available from Starter.
6. **Invoice payments:** If payments are never confirmed as paid, additionally select "Open" under "Transaction states considered "paid"". If older orders are missing, use "Sync" or "Recalculate payment status" under **Products & data → Sources**.
7. **Other currencies:** The tile on the admin dashboard only counts the default currency and points this out.
8. **Fewer impressions than before:** An impression only counts once at least half of the recommendation is visible, once per page view. Lower figures than in old versions are therefore normal.
9. **Break on the update day:** With the update to 2.2.1 or 1.4.1, session counting starts anew.

## The cogi Commander shows nothing or different figures

* Is the Commander installed and active? Is "Collect touchpoints reported by cogi Suite plugins" on?
* Impressions and clicks only appear if Cross Selling Pro is connected.
* Past periods can only be added for orders and revenue, via a command (see [Technical operation](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/technical-operation.md)).
* Differences to the statistics in the plugin dashboard are normal. These are two separate counts. In the Commander, cancellations are not deducted.

## Printess products end up in the cart without a design or always open the product page

* In the card "Printess", "Support Printess products" and "Open the editor in a modal" must be on. If the modal is off, the customer goes to the product page.
* If you have set up a custom configurator with "Open the configurator in a modal" switched off, all configurator products open on the product page, including Printess.
* Before version 2.1.9, every Printess recommendation led to the product page. In this case, update the plugin.
* From recommendations, a configurator product cannot be bought without a design. The shop then shows a notice in the cart.

## Milestone products do not appear

Check: progress bar from 2.5.0 (Shopware 6.7) or 1.4.0 (Shopware 6.6) installed, active and switched on. Milestone switched on under **Delivery → Placements → Milestones**. A template is active at the placement. Plan from Starter. The cart is not empty and the goal not yet reached. There are products in the matching price window. Variants with a "from" price do not count. More under [Milestone recommendations](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/milestone-recommendations.md).

## "Goes with …" or the replacement products are missing in the search

* Cross Selling Pro is active, connected and has a source for sales channel and language.
* The switches in the search plugin are on.
* Replacement products are only available from the Starter plan. In Basic, the quota may also be used up.
* With a relaxed or corrected search, no replacement products come from Cross Selling Pro.
* If you show your own shopping experience for zero results, "Replacement products in addition to the no-results CMS page" must be on.
* If Cross Selling Pro does not answer in time (about 1.5 seconds in the overlay, one second on the results page), the regular replacement products stay.

More under [Working with other plugins](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/working-with-other-plugins.md).

## The checkout interstitial page never appears

* Is "Enable intermediate recommendation page" on for this sales channel?
* Is a "Shopping experience for intermediate page" selected?
* Was the rule in "Only with this rule" deleted? A deleted rule never applies. Choose another rule or clear the field.
* Does the rule really apply to your test cart?

## The feed cannot be fetched

The plugin shows the cause and a suggested solution in the admin. Common cases:

| Cause                                                                                 | Typical solution                                                                         |
| ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Login required, access forbidden (password, IP restriction, firewall, bot protection) | Make the feed address accessible or choose push (DEV and stage only)                     |
| Not found                                                                             | Export deleted or deactivated, access key or domain changed                              |
| Timeout                                                                               | Generate the export via scheduled task instead of on request                             |
| Domain cannot be resolved                                                             | Internal domain: choose push                                                             |
| Invalid certificate                                                                   | Renew an expired or self-signed certificate                                              |
| No valid feed or empty                                                                | Check the export template, make products visible in the channel, check the product group |

First test: open the feed address in a private browser window. If no XML appears there, InsightSearch cannot read the feed either.

## The push is stuck

1. Is the Shopware background processing running permanently?
2. Are the scheduled tasks running? Stuck batches are requeued automatically. This can take up to 15 minutes.
3. Check the memory limit of the worker and whether your service restarts it after it ends.
4. Use "Restart" or "Abort" in the admin.
5. If the push reports that no products were found, check the product group and visibility in the sales channel.

## Notice "recommendation indices were deleted"

Your shop has not sent a sign of life for a longer period, usually because the scheduled tasks were not running. Get the scheduled tasks running again and start "Reindex".

## Read more

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

{% content-ref url="/pages/e00VEeT8TubzE8TB5J6M" %}
[When do changes take effect?](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/when-changes-take-effect.md)
{% endcontent-ref %}

{% content-ref url="/pages/4D3JvLVV6WwwtMOw6rFl" %}
[How-to guides](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/how-to-guides.md)
{% endcontent-ref %}

{% content-ref url="/pages/aG6vtzB13aErytbtzpSe" %}
[Preview and sandbox](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/preview-and-sandbox.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/troubleshooting-and-faq.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.
