< Back
Print

How to address different Shopware 6 Sale-Channels from one Contentserv System

Introduction

Shopware 6 offers the management of multiple sales channels.


You can find more information here: https://docs.shopware.com/en/shopware-6-en/settings/saleschannel

Challenges with multiple sales channels

  • Multiple same and/or different languages and sales channels
  • Multiple category trees
  • Multiple and different category assignments
  • Different visibility of the article in the different sales channels
  • Deleting an item when it is no longer used in all sales channels

Multiple same and/or different languages and sales channels

This is quite simple. Firstly, you have to link the respective Shopware Sales Channel with the SC::Channel entries. You can do this at the respective station under the Station values in the Sales Channel section.

And you must map all languages and sales channels in the data map. Even if you select the same language several times, the data for the translations will only be sent once. However, it is important for the visibility and the category assignments that everything has been configured.

Multiple category trees

In order to be able to manage multiple category trees, you must introduce a top level in CS. Since each SC::Station can only have one root node, all categories of the Shopware Station must be below this main category.

Set the root node in the station settings under “Property Synchronisation”.

 

In the data map configuration you must now specify which upper categories you want to use. Shopware recognises this by the fact that no ParentID is sent. We have developed a special plugin for this (SC::Shopware 6 – Create unique IDs for categories and discard selected root ParentIDs), which makes it easy for you to configure this.

 

Multiple and different category assignments

The allocation of the products is done as generally in the Shopware 6 Connector via the SC::Channel tables. Here, too, the category assignment (Linked CS Channel) of the respective sales channel is carried out:

Note: The attribute “Linked CS::Channel” is a multiple selection, i.e. if the product is contained in several categories, then select all categories. Do not create any further lines for one and the same sales channel!!!

Wichtig ist auch hier im Mapping, das im Schleifenplugin “alle Channel” geladen werden.

 

Different visibility of the article in the different sales channels

You control the visibility via the status of the SC::Channel tables (e.g. active or planned). The respective status is indicated in Shopware as 10, 20 or 30.

10 = Only visible via link
20 = Only visible via search
30 = Visible via search, link and catalog

The easiest thing to do is to create a transformation list that maps the SC::Channel status with the Shopware status.

In the data map, you must now read out and send all configured sales channels. This is configured via a loop plugin. It is important to use the correct settings when loading so that you can evaluate all sales channels.

Be sure to load all channel entries and not just the one for the current language!

The visibility is converted here via the transformation list mentioned above

 

In Shopware, the respective visibilities are then updated, depending on the mapping table for the sales channels:

 

Deleting items when it is no longer used in all Sales Channels

In order to decide whether a product is to be created / updated or whether it is to be deleted, the correct conditions must be set in the respective “Node Maps”.

If an article is set to e.g. blocked in all SC::Channel, then it can be deleted or if it is still active in at least one sales channel, then it may not be deleted, but must be run via the node map “Create/update product”.

In order to simplify the configuration, we have developed a new condition plugin with version 1.15, which simplifies the configuration.

You can use and configure this condition plugin for the installation / update of the products (R1).

For products that can be deleted (R5), you can configure it as it is shown here.

 

If you have further questions, feel free to contact us!

Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents