Shopware

Shopware is an online shop. TRADElube signs in to its admin interface and writes the catalogue into it: categories, manufacturers, images, products, prices and stock. Orders come back the other way. In the channel type selection the channel sits in the group Onlineshops.

The transfer plans of its tasks are largely pre-filled, because TRADElube knows what a Shopware product looks like. The work sits in the mappings instead, meaning the question of which order status in the shop corresponds to which status in TRADElube. Once connection and mappings stand, the task Products Upload transfers your catalogue without you assigning a single field by hand.

Prerequisites

What	Where it comes from
A reachable Shopware shop	You enter its address in the field Url
An integration with administrator rights	You create it in the Shopware administration. Connecting Shopware shows the way. It yields the pair Client Id and Client Secret
A category in the shop for the category tree to be created under	On a new Shopware installation that is Home
The property groups and units you want to transfer	You create them in the shop, see special features and limits

TRADElube signs in through the integration, not as a user. That is the sign-in Shopware provides for connected programs, and it exists independently of any staff account: if somebody leaves the company, the connection does not break.

Setting up the connection

The order is not arbitrary, because every step lives off the previous one:

Enter the login details and sign in via the button Connect. Only with an established connection do the mapping tables have an external side at all. Without it every Reload stays without effect.
In the field External Root Category, pick the node in the shop under which TRADElube creates the category tree. Without it the categories end up outside the shop's navigation. The drop-down fetches its entries from the shop only when opened: it stays empty for a moment, and it stays empty for good as long as there is no connection.
Fill the mappings, see below.
Start the tasks.

Configuration section of the Shopware channel with an empty root category field and the external root Home

The field Root Category above it refers to the TRADElube side and may stay empty. Empty means "all categories on the top level", which is the correct setting for a catalogue with several roots, not a forgotten one. Only if you deliberately want to transfer one subtree do you enter its root there.

Mappings

The channel holds twelve tabs, one per list that exists on both sides. The column External shows the entry in the shop, the column Internal the one in TRADElube.

Payment methods tab with the columns External and Internal and the buttons Reload and Import

Tab	What gets mapped
Salutation	The shop's salutations onto those of the client
Countries	The shop's country list. Without the mapping, an imported order's address has no country
Languages	The shop's languages onto the client's localizations
Order Status	The shop's order status onto the status in TRADElube
Payment Methods	Invoice, prepayment and whatever else the shop offers
Payment Status	Open, paid, refunded and the further stages
Shipping Methods	Standard shipping, express shipping and others
Shipping Status	Open, shipped, returned
Delivery Times	The shop's delivery times. The internal side here is not a list but a number of days, which TRADElube calculates from the shop's entry
Base Units	Piece, litre, kilogram
Properties	Your selection properties onto the shop's property groups
Sales Channels	Only needed if you want to control the sales channels per product

Only entries that are active in the shop and assigned to a sales channel appear. A disabled payment method therefore never shows up, and you map nothing a customer will never see.

Above the table sit six buttons. Four apply to the individual row: New, Delete, Move Up and Move Down. Two talk to the shop:

Reload fetches the list from the shop and creates one row per external entry. Where the names match, TRADElube proposes the internal side straight away.
Import creates the missing internal objects in the client, for instance the countries you do not keep yet. This is the intended way to take over a catalogue the shop already maintains, not a shortcut: it saves you the manual work, and the mapping is created along with it.

It does not work the other way round: TRADElube does not create master lists in a Shopware shop. What the shop keeps, you maintain in the shop.

For Order Status, Payment Status and Shipping Status we advise against importing. These three carry meaning: they decide which state counts as completed and which triggers a follow-up step. What the shop keeps there is its own view, and an import puts it as a second row next to the status kinds you actually need. You maintain these three in the settings and map them by hand.

Available tasks

Thirteen tasks, eight into the shop and five out of it. Download means from the shop into TRADElube, upload the other way round.

Task	Direction	Transfers	Notes
Categories Download	Import	Categories	Takes over a tree maintained in the shop
Categories Upload	Export	Categories	Creates them under the external root category
Manufacturers Download	Import	Manufacturers
Manufacturers Upload	Export	Manufacturers
Media Download	Import	Media
Media Upload	Export	Media	Runs before the products, otherwise a product has no image to refer to
Properties Upload	Export	The options of the mapped selection properties	Transfers the options, not the groups, see below
Products Download	Import	Products
Products Upload	Export	Products including variants, prices, descriptions and image references	The channel's largest task, with one plan per level
Stocks Upload	Export	Stock only	Separate from the products, so a change in stock does not drag the whole product record along
Orders Download	Import	Orders including line items, addresses and customers	The field Age of Orders to Sync limits how far back the search goes
Orders Status Upload	Export	Order, payment and shipping status	The way back to the shop after you have processed an order
Customers Upload	Export	Customers with billing and delivery address

Which of these tasks exist in your client is decided by your needs: what gets created is what you actually use, and the list under the navigation item Tasks is correspondingly shorter than the table above. How a task runs and what its schedule means is under tasks.

There is no task Customers Download, and none is missing: customers are created in TRADElube together with the order that triggered them. Nor is there a Stocks Download, because stock is kept by the side that holds the goods, and that is not the shop.

Special features and limits

The task Properties Upload transfers the options of a selection property, for instance the color shades, but not the group they belong to: TRADElube creates neither property groups nor units in the shop. So the sequence is: create the group in the shop, map it in the tab Properties, save, then run the task. The same holds for base units such as Stück.

Common questions

No variant can be selected in the shop. Then the section Variant Properties is empty. The products are fully created, but without an axis the configurator has nothing to offer, see Products Upload.

Two shops on one client. That is provided for, as two channels of the same type with their own login details, their own mappings and their own tasks, see channels.