> 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/quick-cross-selling-assignment.md).

# Quick cross-selling assignment

With the quick assignment you create and edit many Shopware cross-sellings at once in a table-like view.

The quick assignment is a tool in the Shopware admin that lets you create many cross-selling links between products in a short time, without opening each product. The view works like a spreadsheet: each row is a product, and next to it you enter the products that should be recommended for it. Use it when you maintain cross-sellings for whole categories or product groups or want to change existing sets at a glance.

{% hint style="info" %}
The quick assignment creates real Shopware cross-sellings, exactly the same as in the "Cross-Selling" tab of a product. The default theme shows them automatically as a slider on the product page, without adding anything to a Shopping Experience.
{% endhint %}

The quick assignment has no plan restriction. It can be used with every plan.

## What else the cross-sellings are used for

Cross Selling Pro can use the cross-sellings you maintain here as a product source:

* In a **bundle/set template** with the source "Cross-selling (from reference product)". This way you build sets for many products at once.
* In a **recommendation template** with the source "Cross-selling (from reference product)", for example for sliders in Shopping Experiences or on the cart page.

## Opening the quick assignment

In the Shopware admin, go to **Catalogues → Quick Cross-Selling**. Next to it you find the menu item **Catalogues → Cross-selling overview** (see below).

When you open the page for the first time, a notice at the top explains the steps. "Don't show again" hides it, "Show help" brings it back.

## Step 1: Choose source and name

In the card "Source & Name" you decide for which products you edit cross-sellings.

| Source                        | Which products are loaded                                                                                                                               |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "Category"                    | All products of a category including sub-categories, main products only.                                                                                |
| "Dynamic product group"       | All products of a dynamic product group, also main products only.                                                                                       |
| "Existing cross-selling name" | Only products that already have a cross-selling with this name, even if it is only attached to a variant so far. Well suited for editing existing sets. |

Then pick the category or product group under "Selection". With "Filter products" you narrow down the loaded products by name or product number.

**Cross-selling name:** Enter the name shown above the slider in the shop, for example "Recommended". It applies to the content language currently selected. If assignments with this name already exist, they are updated.

**Existing sets:** Instead of typing a name, you can select an existing cross-selling under "Existing sets". Its name is copied. "Load sets" refreshes this list. If you change the name afterwards, you change it for all products with this set. For a new set, clear the selection under "Existing sets".

Then click "Load products".

### Names in several languages

Below the name, expand "Name in other languages". There is one field per language of your shop.

* If you select an existing set, the other languages are already filled in.
* Empty fields are not saved, existing names are kept.
* If the name in the default language is missing, the plugin uses the name above. A set is therefore always created in the default language as well, even if you work in a different content language.

## Step 2: Assign target products

After loading, the card "Assignments" shows one row per source product.

1. In the column "Cross-selling products", use "Search product" to find the products that should be recommended for this source product and add them.
2. "Remove" takes a target product out again.
3. Same target products for many rows: grab the blue grip handle on the right of a cell, hold the mouse button and drag over the rows below. The value is copied downwards.
4. With many products, "Load more" loads further rows.

Each row also offers "Open in admin", "Open in shop" and "Delete cross-selling". With "Displayed source products" you limit the table to selected loaded products.

{% hint style="info" %}
A product cannot be assigned to itself as cross-selling.
{% endhint %}

### Variants

* Variants that inherit their cross-sellings from the main product stay unchanged. They automatically show the cross-sellings of the main product.
* Variants with their own cross-sellings (inheritance off) get the same set with the same products when saving, if they do not have the set yet or had the same products as the main product so far. The row shows this, for example "Also for 2 variants with their own cross-sellings".
* Variants with their own, different products stay unchanged. The message after saving lists them.
* If a set so far only exists on a variant, it is also created on the main product when saving.

## Step 3: Save

Click "Save". Before saving, the quick assignment asks for confirmation ("Save changes?") and shows:

* how many products with assignments will be saved,
* a warning if the cross-selling of products will be emptied (all target products removed),
* whether variants are saved as well or a set is created on the main product.

Confirm with "Save now". The plugin then reports how many cross-sellings were created, updated or removed. If saving fails, nothing is changed.

{% hint style="warning" %}
Only changed rows of the currently loaded page are saved. If you leave the page or load new products with unsaved changes, the quick assignment asks first. "Discard changes" drops your changes.
{% endhint %}

## Cross-selling overview

Under **Catalogues → Cross-selling overview**, the card "Existing cross-sellings" lists all existing cross-sellings. You also get here from the quick assignment with "Open overview", and back with "Back to quick assignment".

| Column                | Content                                                                              |
| --------------------- | ------------------------------------------------------------------------------------ |
| "Set"                 | Name of the cross-selling in the content language, otherwise in the default language |
| "Source product"      | The product the cross-selling belongs to                                             |
| "Target products"     | The recommended products                                                             |
| "Created" / "Updated" | Date                                                                                 |
| "Actions"             | "Edit" and "Delete"                                                                  |

Use "Search set, product, or product number" to find entries quickly. "Delete" removes the cross-selling only for this source product (including its variants with their own cross-sellings). Other products with the same set name are kept.

For variants with their own setting, an empty entry remains after deleting: "Empty, keeps the variant's own setting". This prevents the variant from suddenly inheriting from the main product again. If it should inherit again, switch inheritance back on in the product itself.

## Permissions

| Task                                | Required Shopware permission |
| ----------------------------------- | ---------------------------- |
| Open quick assignment, save, delete | Edit products                |
| View cross-selling overview         | View products                |

## Read more

{% 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 %}

{% 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/v0RzTVJFjsXNoeFkgj6R" %}
[Product page](https://docs.codegiganten.de/plugin-documentation/en/apps/cross-selling-pro-ai-cart-cross-selling-bundles-and-sets/product-page.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/quick-cross-selling-assignment.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.
