Connecting Shopware
This guide connects your Shopware shop with TRADElube: from the integration in the shop's administration through the key pair in the channel to the mappings and the first transfer. TRADElube signs in through an integration, not as a user. Why that is so is under Shopware (channels). The path through TRADElube, which is the same for every system, is covered in full by Setting up a channel.
Prerequisites
- Access to your Shopware shop's administration, with the right to create integrations.
- The Shopware channel in TRADElube is created. We take care of that, see Setting up a channel.
Step by step
Caution: Shopware shows the secret access key in the creation dialog only. After saving there is no way back to this value. Copy the key pair in step 3 before you close the dialog.
Open the integrations. In your shop's administration, open Settings, then the entry Integrations.

Create the integration. Via Add integration you open the dialog. Give it a name you will recognize the connection by later, for instance TRADElube, and switch Administrator on. The reason: without administrator rights the sign-in still succeeds, but individual tasks fail later when writing into the shop.

Take over the key pair. The dialog shows the two values Access key ID and Secret access key even before saving. They only become active once you save. Copy both, each via the copy button next to the value, and then save via Save integration.
Enter it in TRADElube and connect. Under the navigation entry Channels, open your Shopware channel via the button Edit. In the Login Details section, the shop's address goes into the field Url, the access key ID into Client Id and the secret access key into Client Secret. Test the connection right away via the button Connect. It shows within seconds whether address and sign-in are right, and the working connection is the precondition for everything that follows.

Fill the mappings. In the Mappings section, Reload fetches your shop's entries into the column External per tab, with a suggestion based on matching names. For maintained catalogues such as payment or shipping methods, Import creates the missing internal entries along the way. Order, payment and shipping status you map by hand instead. Why is under Setting up a channel. The Properties tab only has an external side once the property groups exist in the shop: create one group of the same name there per selection property before you map.
Pick the external root category. In the field External Root Category you pick the node in the shop under which TRADElube creates your category tree, on a fresh installation Home. Without it the categories end up outside the shop's navigation. The field Root Category above it may stay empty, see Shopware (channels).
Enter the variant axes in the transfer plan. The tasks' transfer plans come almost completely preset. Two sections come empty and still decide the outcome: Properties and Variant Properties in the transfer plan of the task Products Upload. Before the first transfer, enter there which of your properties go into the shop and which of them are the axes of your variants. Otherwise all products arrive without an error, yet no version can be picked in the shop. What belongs in which section is under Products Upload (Shopware).
Start the initial fill. Start the tasks once by hand, in this order: first categories, manufacturers, properties and media, then the products. The reason: whatever a record needs as a reference has to be there first, and a product refers to all four. Afterwards you set the cadence per task. Both in detail: Planning and starting tasks.
Checking the result
Once the connection is up, the first Reload fills the external side of the mappings. This is what the Payment Methods tab looks like afterwards:

If the column External stays empty or the application reports an error, check the three values from step 4. After the initial fill, the task's Traces section shows Created per record, and your catalogue is in the shop. Check a sample, ideally a product with variants.
Frequent pitfalls
- The secret access key cannot be found any more. It is shown at creation only, in step 3, and searching is pointless: create a new integration and enter its key pair in TRADElube again.
- The integration has no administrator rights. The connection succeeds, yet individual tasks fail later when writing into the shop. On such errors, check the Administrator switch from step 2 first.
- No version can be picked in the shop. Then the Variant Properties section from step 7 stayed empty. The variants are in the shop, but without their axes, see Products Upload (Shopware).
- The shop runs with an English system language. Two fixed values of the task Customers Upload are pre-filled with German names. Until you have adjusted them before the initial fill from step 8, every customer fails. What to do is under Customers Upload.
Further reading
- Setting up a channel: the path through TRADElube, which is the same for every system
- Shopware (channels): login details, the twelve mappings and the thirteen tasks
- Products Upload (Shopware): the two plans and what belongs in properties and variant properties
- Customers Upload (Shopware): the two fixed values to adjust with an English system language
- Planning and starting tasks: initial fill, cadences and the manual start