Products Export

The action hands your articles out to the ERP system. It is needed where the range originates not in CAO-Faktura but in TRADElube or in a connected shop, and the ERP system needs it for quotes, invoices and orders.

What gets transferred

What is handed out is every product of the client, sorted by product number. The ERP system collects them in blocks and says which article to start from and how many it wants. Without that, everything comes.

On the first call the whole range goes out, after that only what is new, has changed or did not get through last time. A product deleted in TRADElube is reported as a deletion. When something counts as changed is under tasks.

The manufacturer goes along as an identifier, not as a name. For the ERP system to make anything of it, it has to have collected the manufacturer through Manufacturers Export already. The same holds for sorting into categories through Categories Export.

How the transfer plan is built

The plan sits in the channel, in the Transfer Plans section under Products and there in the Export tab. It has three sections.

Section	What sits in it
Common	The master data: identifiers, Product Number, Active, Matchcode, Stock, the three image names, EAN, Weight, Tax Rate and the two timestamps
Descriptions	The texts per language: Name as a mandatory assignment, two pairs of short and long text and the three meta fields
Prices	Seven price fields of the ERP system, to each of which you assign one price group of your client

Matchcode is unticked out of the box. It is the field by which a clerk finds the article again in the ERP system, and Name and Product Number stand ready as sources.

Three places in it are a decision rather than merely an assignment.

Which stock goes out

The Stock assignment offers one source per store of your client. Where you keep several stores, you decide here which one the ERP system sees. If it is meant to see the total, you enter that as a script assignment. There is no ready-made total, because the right answer depends on which store sells at all.

Which prices go out

The ERP system keeps one purchase price, one default sales price and five further sales prices. TRADElube keeps named price groups instead, and the two lists are not the same length. Out of the box only the first two fields are filled. The remaining five you assign where you want to give the ERP system more price groups, and leave empty otherwise.

Which price group a price field belongs to is not visible to the ERP system. So settle the order as soon as you fill more than two, otherwise a price without meaning sits in the ERP system.

Which text goes where

For the texts the ERP system has four fields, two for the shop and two for the document, and TRADElube has two. Out of the box the short description and the description go into the two shop fields. Where your ERP system needs the text on the quote and the invoice instead, tick Short Description and Long Description. Filling both pairs at once is possible as well and sends the same text twice.

Special features and limits

Several rows of the plan cannot be filled, because TRADElube does not keep the value: Product Group, Sort Order, Delivery Status, FSK18, Pack Unit, Tax Class Id, Date Available and Was Ordered in the first section, plus the two Product Variant Name rows in the second, one for the parent product and one for the variant. They are there because the ERP system knows these fields.

Properties do not go along. The plan has no section for them, and whatever properties you keep on an article in TRADElube stay here. The other direction can do it, see Products Update.

A variant tree arrives flat, with one exception: the Parent Product Id assignment in the Descriptions section names the parent article's identifier to the ERP system. What it makes of that is its own decision.