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

Products Download

The task fetches products from the WooCommerce shop into TRADElube. That is the direction for a shop maintaining its own catalogue, one you do not want to build a second time. As with the upload, parent articles and variants are kept apart, with one transfer plan per level.

What gets transferred

For each article in the shop a product is created in TRADElube. The plan Product applies to the simple articles and the parent articles, the plan Product Variation to the variants below them. A variant finds its parent article through that article's channel mapping, so the parent has to have been transferred first.

Categories, images and attributes do not come along. The channel transfers those into the shop only, not out of it, so there is no downloading counterpart to Categories Upload, Media Upload and Properties Upload. What this task fetches are the fields on the article itself, its texts and its prices.

How the transfer plan is built

Two plans, Product and Product Variation, with four sections each. That makes it considerably shorter than the plan of Products Upload, and the reason is the scope of the other direction: what the shop does not keep, it cannot deliver either.

Transfer plan of the products download task with the plans Product and Product Variation and the opened Selection section

Section What sits in it
Selection Which of the shop's articles are taken over at all, and how TRADElube recognizes a product already present
Common The fields on the product: Active, Product Number as a mandatory assignment, weight, dimensions and the Tax Rate through the mapping of the tax classes. In the plan Product Variation the Parent Product is added
Descriptions The texts, one tab per localization of your client
Prices The prices, one tab per price group and position

The Selection section decides what you pull into your client. The row Condition is unticked out of the box, so every article comes at first. The sources available for it are the shop's entries that allow a sensible split: SKU, Managed Stock, Virtual, Downloadable and Type. Through Type you tell simple articles from variable ones.

An article is recognized through its product number. The row Existing Item carries With SKU as Product Number: TRADElube looks for the product with this product number in the client before creating a new one. That way the task also runs against an existing catalogue without duplicating it.

You pick the language per tab, not per assignment. Unlike the upload, the Descriptions section carries one tab per localization: you set up which language version of your client is to be created from the shop's texts.

Prices come from a different field of the shop per tab. A tab for a sales price group takes the regular price, one for a special-offer price group takes the sale price. Whether the delivered amount is entered as a net or a gross price is decided by the shop through its setting on whether prices include tax.

Special features and limits

The parent article has to be there before its variants. A variant finds it through its channel mapping, and that is only created once the parent has been transferred. So the execution queues the parent articles before the variants.

Products Download and Products Upload maintain the same channel mapping. If both run on one channel, the order of the executions decides which side wins. Pick one direction per channel, and where you need both, use two channels.

Stock does not come along. Stock belongs to the side that holds the goods, and that is not the shop. So there is no stocks download task.

Further reading