1. Contents
  2. Reference
  3. Channels and tasks
  4. CAO-Faktura
  5. Products To Category Update

Products To Category Update

The action sorts an article into a category. It is the third action needed for that: Products Update brings the article, Categories Update the category, and this one connects the two.

What gets transferred

The ERP system sends two identifiers, the article's and the category's. Both have to have a channel mapping in TRADElube already, otherwise the call fails with a named message and sits in traces as Failed. Neither an article nor a category is created here.

An article can sit in any number of categories. Each pair of article and category gets an assignment of its own, and a second call with the same pair changes the existing one instead of creating another.

The article counts as changed afterwards. That matters more than it sounds: the sorting is what a shop needs to show the article at all, and without that mark the next execution would pass it by.

How the transfer plan is built

The plan sits in the channel, in the Transfer Plans section under Products To Category and there in the Update tab. It has no sections, because there are only the two mandatory assignments Product and Category. They sit directly below the tab.

Both are mandatory when changing as well, and there is nothing to set on them. The plan is the connector's smallest, and that is no shortcoming: an assignment consists of nothing but its two ends.

Special features and limits

The order of the calls decides. Where the ERP system reports the sorting before the article or the category has arrived, the call fails and is not made up for. So it has to transfer articles and categories first and the assignments afterwards.

An article without a category is allowed. TRADElube requires no sorting. Whether a connected shop accepts such an article is the shop's decision.

Further reading