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

Orders Status Upload

The task reports an order's state back to the Shopware shop: the order status, and on request the payment and shipping status and the tracking code. It is the opposite direction to Orders Download and the reason a customer sees in the shop that their order is on its way.

What gets transferred

The task sends not the order but only its states. The task does not touch line items, addresses or amounts. They were created in the shop and stay there as they are.

Only what is released goes along. An order only travels back into the shop once it carries the flag Released in TRADElube. That is where you decide whether an order has been dealt with. Until then nothing changes in the shop, however often the task runs.

Two further conditions apply: the order has to have changed since the last transfer or to have failed last time, and it has to fall inside the period given by Age of Orders to Sync.

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 released orders are searched for.

The value belongs to this task and not to the channel: Orders Download has a field of its own by the same name. It makes sense to set both alike, because an order that is no longer fetched no longer needs reporting back either.

How the transfer plan is built

The task has exactly one plan, and it is the leanest of the channel: four sections and one single assignment per section. There is no Selection section here, because which orders go along is decided by the release and not by a condition.

Section What sits in it Out of the box
Order Status The order's target state in the shop switched on
Payment Status The payment's target state Disabled
Shipping Status The delivery's target state Disabled
Shipping Items The Tracking Code for the delivery Disabled

The three status sections carry the same preset script, and it decides when TRADElube touches the shop at all:

If the status the shop holds is mapped to one of your status kinds and is not a closed one, your status wins. Otherwise the shop keeps its own.

That is the safeguard against reopening. An order that is canceled or completed in the shop is not touched by TRADElube any more, even if something happens on your side afterwards. If you want it differently, the assignment is laid out as a script and the shop's state is available inside it as a source.

The way to the target state is Shopware's own. TRADElube only names where the order is meant to end up and leaves the intermediate steps of its own status sequence to Shopware. That is why a jump Shopware needs two steps for does not fail.

Tracking Code takes several numbers. The preset script splits the field's content at the commas and hands Shopware a list. So a delivery with two parcels is entered as 12345,67890 and not on two lines.

Special features and limits

An order that no longer exists in the shop is skipped, not reported as an error. In the traces it carries the note that the order was not found. That is the right treatment: a record deleted in the shop is no reason to color the execution.

Once the order is completed, the stock is pulled along. When the order status reaches a closed state, TRADElube marks that order's products as changed. The next execution of Stocks Upload thereby carries into the shop the stock that changed through the delivery, without you triggering anything.

A change to the mappings reports everything again. Order status, payment status and shipping status belong to this task's configuration. If you change one of those three tables, the released orders in the period count as due for checking and are reported again.

Further reading