1. Contents
  2. Reference
  3. Channels and tasks
  4. Shopware
  5. Orders Download

Orders Download

The task fetches the orders from the Shopware shop into TRADElube, with their line items, the two addresses and the customer who placed them. It is the only task of the channel that creates customers, which is why there is no task Customers Download either: a customer is created with their first order.

What gets transferred

For each order in the shop an order is created in TRADElube with its order number, time, currency and the four states an order carries: Order Status, Payment Status, Shipping Status plus Payment Method and Shipping Method. All five come across through the channel's tabs, not as text, see Shopware.

Added to that are the billing and shipping address, the customer and the line items.

Line items come in five kinds, and that is this task's most visible act of translation: Shopware keeps products, discounts, vouchers, surcharges and shipping costs in one line item list, told apart only by what is in the row. TRADElube separates them into Product Items, Discount Items, Voucher Items, Surcharge Items and Shipping Items. A discount is thereby a discount and not a product with a negative price, and each kind gets its own section in the transfer plan.

The task's own configuration

The task's Configuration section carries a single field, Age of Orders to Sync in days, preset to 14.

It limits how far back a complete execution goes. The reason is size: the shop keeps no list of what has changed since yesterday, so without that limit TRADElube would have to walk the entire body of orders on every execution. Raise the value if orders stay open with you for longer than two weeks. In day-to-day operation it is rarely the bottleneck, because orders not yet released are read along every time anyway, see below.

How the transfer plan is built

The task has exactly one plan, so there is no tab bar above the sections. That plan carries ten of them instead, more than any other task of the channel: the bar is wider than the screen, and the arrows at its ends scroll it along.

Product Items section in the transfer plan of the orders download task, with its five mandatory assignments

Section What sits in it
Selection Condition, meaning which of the shop's orders go along at all, and Existing Customer, meaning how a customer is recognized
Common The head of the order: number, time, currency and the five values from the mappings
Customer The person who ordered, together with the salutation from the Salutation tab
Billing Address The address that is invoiced
Shipping Address The address that is delivered to
Product Items Product number and name, quantity, gross price and tax rate, all as mandatory assignments
Discount Items The deductions the shop applied to the order
Voucher Items The same for redeemed vouchers, plus their code
Surcharge Items Surcharges such as a small-quantity or cash-on-delivery fee
Shipping Items The shipping costs

Condition is prepared but switched off. The script behind it compares the order's sales channel against the shop's first sales channel. This is the place for a shop that runs several sales channels and whose orders are not all meant to end up in the same TRADElube channel: switch it on, enter the sales channel you want, and the rest stay out.

Existing Customer decides whether a returning customer is recognized as one. The assignment only takes effect where the shop's customer has no channel mapping yet. It is preset to search first by the shop's customer number and then by the e-mail address. With Origin Customer Number and With EMail stand beside it as individual sources. Without that assignment, the first order of an already existing customer creates them a second time.

The shipping address is only created where it differs. Where billing and shipping address are the same in the shop, the order in TRADElube refers to the same address twice instead of duplicating it. Where the billing address is missing, the shipping address takes its place.

The four line item sections are built alike, and their assignments are mandatory: quantity, price and tax rate have to deliver a value on every transfer, otherwise the order's total would be wrong rather than incomplete.

Special features and limits

An execution does not always look at the same period. Started by hand and on the very first execution, the task goes over the full Age of Orders to Sync, and over every order in it. After that it does so at most once an hour. If it runs more often, the runs in between look only at the last three hours, and within those only at the orders still open in the shop. That is why a tight cadence is cheap on this task: the short execution really is short.

Whatever is not released yet in TRADElube is always read along. Regardless of the period, the task collects every order still open on your side and fetches its state from the shop. An order whose payment is still outstanding thereby gets its new payment status, even where the short execution would otherwise have passed it by.

A change to the mappings re-reads the orders. Salutation, countries, order status, payment methods, payment status, shipping methods and shipping status belong to this task's configuration. If you change one of those tables, the orders in the window count as due for checking and are transferred again. That is intended: a mapping that was missing before should reach the orders that were already there.

The way back is a task of its own. What you change on the status in TRADElube is reported back to the shop by Orders Status Upload, and what you change on the customer by Customers Upload.

Further reading