< Back

Export product properties


In this part we will synchronize Contentserv attributes as Shopware properties – to be exact as property values. Shopware strictly differs between the Shopware properties and it’s property values. The properties must be maintained in Shopware first for the connector to be able to fill them with their according values.

Don’t forget to import them into your station values once you created all on the Shopware side.


There are two recommended ways of configuring the product properties. The Shopware connector must be told which elements of Contentserv represent which property on the Shopware side. This can be implemented by either using attribute references or a valuerange mapping. We recommend the first way because it is represents the data flow much more transparently.

Note: As of now, the Shopware 6 API does not support creating properties externally. Therefore all wished Shopware properties must be created by hand on the Shopware side first. These must then be synchronized back to Contentserv by importing the station values.

Using attribute references (Recommended)

Using a CS valuerange mapping

Using attribute references (Recommended)

Contentserv Maintenance

If the properties of your products are the same with the variant building attributes, you can re-use the maintained attribute reference for them as well. Otherwise a new attribute reference should be created which will represent the attributes a product will have on the Shopware side.

Create the attribute reference product attribute.

Activate the selection of multiple attributes.

Leave the language-dependency unchecked.

For a far easier maintenance, we would recommend using the inheritance by parent elements. For example: If all T-shirts have textile it can be mapped at their common parent node.

When mapping the station values using this method, we map a Contentserv attribute directly to the Shopware 6 property. Therefore for the station value type, select “Pdmarticle attribute”.

Map each attribute to each property.

Exporting the product properties to Shopware

Go to the datamap and enable properties, and map the property selector attribute as the source for that row.

Open the configuration for properties.

Find the attribute which contains your width value and map it. (same as with variants)

Map this attribute to width within the properties configuration.

Click the cogwheel and open the sub configuration.


Click the red cogwheel to enter the sub sub configuration.

Change object type to property

Run your job.

Your property should now be available.

Re-validation: Am I finished with my configuration?

So, you feel like you followed every step but still the connector does not spit it out. In this case here’s a quick check where the problem lies 90% of the time.

1. Is the attribute maintained in the Shopware properties attribute reference in the PIM product?
2. Is the attribute set in the station values?
3. Is the attribute configured in the datamap? The variants need their own property datamap row. You have to copy your newest changes to them as well.

If it’s not one of those, you might have discovered a bug. In that case you can create a ticket in our Redmine system.

Old step: Using a CS valuerange mapping

Contentserv Maintenance

If you already exported variants successfully, this will be a piece of cake. Since Shopware variants utilize properties, the process is almost the same.

You will need a CONTENTSERV attribute which tells the SAWSConnector which properties to use for a specific product. Best is a selection CSType where you choose for each product what its properties are.

For example an attribute like this, similar to the variant selector.


We are gonna use width in this example. Open the configuration for your imported Shopware VIx values, and navigate to Property groups.

Click the wrench and set the select option to Valuerange entry and choose the same valuerange list you used for your attribute just before.

Now map your property groups.

Exporting the product properties to Shopware

Exporting the product properties is completely analogue to exporting them via attribute references.

Click here to get to that part of the configuration

Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Previous Export variant products
Next Export custom fields
Table of Contents