1. Contents
  2. Reference
  3. Channels and tasks
  4. WooCommerce
  5. Products Upload

Products Upload

The task writes your products into the WooCommerce shop, with descriptions, prices, references to the images already uploaded, category assignments and attribute values. It is the channel's largest, and the one whose transfer plan you will touch in any case: the Attributes section is empty out of the box, and without it no variant can be picked in the shop.

What gets transferred

For each product in TRADElube a product is created in the shop, and a parent article and its variants are treated separately: each has a transfer plan of its own.

The tasks whose results this one builds on run first: Categories Upload, Media Upload and Properties Upload. The reason is always the same: into the shop the product carries only the reference, not the image and not the category. What is not there yet cannot be named.

Stock does not go along. That is what Stocks Upload is for, because stock changes far more often than a product does.

The manufacturer does not go along either, because the channel knows no manufacturer. In full under WooCommerce.

How the transfer plan is built

The task has two plans, Product and Product Variation, and above them sits the tab bar that switches between them. Below it lies the second tab bar with the sections, and it is longer than the screen is wide: the arrows at its ends scroll it along.

Transfer plan of the products upload task with the Product Variation plan selected and the Attributes section open, holding the two axes Color shade and Version

Section What sits in it In the plan Product Variation
Selection Which products go into the shop at all, how TRADElube recognizes one already present there, and what happens to a product that drops out same
Common The fields on the product itself: Status, SKU as a mandatory assignment, Tax Class, weight and dimensions same
Description Name, description and short description without name and short description, which the variant takes from the parent article
Images The references to the images called Image and carries the cover only
Prices The one price the product carries in the shop same
Categories The categories it is meant to sit in inside the shop absent, a variant sits in its parent article's categories
Attributes The attribute values on the product, one tab per property same, but filled differently, see below
Metadata Additional entries WooCommerce has no field of its own for same

One section is empty out of the box, namely Attributes, and it decides the variant structure in the shop. An execution without it creates all products without error, and still the shop's configurator has nothing to offer. It is not pre-filled because TRADElube cannot know which of your properties is meant to be an axis in the shop and which stays a feature on the product. That decision is yours, and it comes out differently per shop. What goes where:

Plan Which properties belong in it
Product all selection properties, the axes included
Product Variation only the axes

The reason for the apparent duplication: WooCommerce keeps the attribute on the parent article and the chosen value on the variant. Leave the axes out of the plan Product and you get variants whose attribute is missing on the parent article. Enter more than the axes in the plan Product Variation and you send every variant values that do not distinguish it from its siblings.

There is no inheritance to the variant: what sits on the parent article sits on the parent article. So the second plan is not the optional extra but the place where the individual variant's values are set at all.

Each property gets its own tab inside the section. You create a new one through the button Insert above and remove it again through the bin symbol on the tab.

Only mapped properties are on offer. Whatever has no attribute of the shop facing it in the channel's Properties tab does not appear here in the first place. So where one is missing, it is missing from the mapping, not from the plan.

The field Variations is set by the shop itself as soon as a variant uses the attribute, which is why it is fixed here and cannot be changed. So you only enter the axes, and the shop works out by itself which attribute its configurator offers.

Besides Condition and New Item, Selection also holds Removed Item. It answers what happens to a product in the shop that has dropped out of the condition or been deleted in TRADElube. The choices are Delete and Skip.

A product is recognized through its product number. The row Existing Item carries With Product Number as SKU for that: TRADElube looks for the article with this SKU in the shop before creating a new one.

You pick the language per assignment, not per tab. The Description section has no tab bar for language versions. Instead the sources carry the language in their name, for instance Name [Deutsch]. So what goes into the shop is the one language version you set there.

Prices takes exactly one price. Which of your price groups that is, you set. Whether TRADElube sends the net or the gross price is decided by the shop instead, through its setting on whether prices include tax. Bulk and customer group prices are not transferred by this task.

TRADElube converts length, width and height, because the two sides keep different units of measure. You enter the dimensions on the product as usual, and in the shop they appear in the shop's unit.

Special features and limits

The parent article goes into the shop before its variants. A variant attaches itself to its parent article there, and finds it through the parent's channel mapping. So the execution queues the parent articles before the variants.

Products Upload and Products Download maintain the same channel mapping. If both run on one channel, the order of the executions decides which side dictates the price. So settle per channel where the catalogue is maintained.

Further reading