1. Contents
  2. Reference
  3. Channels and tasks
  4. TriData / TriCon
  5. Orders Upload

Orders Upload

The task hands orders over to TriData. It is the only way out of TRADElube into this system: everything else comes in. What happens to the order afterwards is fetched back by Order Status Download.

What gets transferred

The order with its line items, the customer and the addresses, so everything TriData needs to make an order of its own from it. Each order is handed over exactly once. From then on it is tied to its counterpart in TriData through its channel mapping.

Which number TriData files it under is decided by the two entries in the channel's Configuration section, see TriData / TriCon: either your shop's order number, provided it can be read as a number, or the channel's counter.

The task's own configuration

One field, Age of Orders to Sync, in days and set to 14 out of the box. It limits how far back the task looks: orders older than that are not considered at all.

That is not a saving but the answer to the one question that can make this task expensive. Without a limit every execution would go through the entire stock of orders, and an online shop collects those by the ten thousand. Where you want to hand an older order over after the fact, you raise the value once and set it back afterwards.

How the transfer plan is built

One plan with eight sections, and the section bar is wider than the window.

Transfer plan of the orders upload task with the section bar and the opened Common section

Section What sits in it
Selection Which orders are handed over
Common The order itself: numbers, order date, payment method, whether it has been paid, shipping method, shipping cost and the comment
Customer The buyer with salutation, name, contact details and billing address
Address The delivery address where it differs from the billing address
Product Items The order's article rows
Discount Items The discount rows
Voucher Items The voucher rows
Surcharge Items The surcharge rows

The four line item sections are built the same way. TriData knows only one kind of order line, so all four carry the same rows, from Product Number through Gross Price and Tax Rate to Quantity. What you set in one of them you set the same way in the others, and what you do not want handed over you untick per section.

The Common section is the only one where individualization regularly pays off. The Comment row is a script assignment out of the box and composes what TriData has nowhere else to put: tracking number, voucher code and the customer's comment, each of them only where present. That is the place for everything your order processing is meant to see on the order.

Two rows of the same section hang off channel mappings rather than off a field: Payment and Delivery Term go through the tabs Payment Methods and Shipping Methods. Where nothing stands there, TRADElube hands the name from your client over unchanged.

Special features and limits

TriData accepts an order but hands none out. An order entered in TriData therefore never reaches TRADElube, and there is no downloading counterpart to this task.

An order handed over is not kept updated. Where something about the order changes on your side afterwards, it no longer arrives in TriData. Only the status flows back, and that is fetched by Order Status Download.

Further reading