Order Status Download
The task fetches back what TriData has done with an order handed over. It is the reverse direction of Orders Upload and has this one purpose only: your customer is to see in the shop that their order has shipped, without anybody entering the status by hand.
What gets transferred
Three statuses per order and nothing else: Order Status, Payment Status and Shipping Status. Line items, amounts and addresses stay untouched.
TriData keeps a single state per order for this, and all three come out of that one. That is why the channel has three separate mapping tabs, see TriData / TriCon: one and the same state of TriData means something different for the order status, for the payment status and for the shipping status, and you settle per tab what that is.
TriData's states carry keys of their own along the way, StorniertTriData and StorniertExtern for the two kinds of cancellation for instance. They stand there in German in the English interface as well, because they are data of the connected system and not a caption of TRADElube.
The task's own configuration
Two entries, and both limit what the task asks about at all.
| Field | Meaning | Note |
|---|---|---|
| Age of Orders to Sync | How far back the task looks, in days | 14 out of the box |
| Exclude Closed Orders from Sync | Whether orders whose status is already closed on your side are skipped | Ticked out of the box |
The two together see to it that in day-to-day operation the task only touches the orders something can still change about. The checkbox is the more effective of the two: a closed order does not change its status any more, and asking again only costs time. Take the tick out where you want to bring an order that is already closed up to date once more.
How the transfer plan is built
The channel's smallest plan: one section, no section bar, three rows. They stand there directly when you open the Transfer Plan area.
Each of the three rows takes its value from the same entry of TriData, led through the channel's respective mapping tab. So there is nothing to decide here. The deciding happens in the tabs. What you can do in the plan is untick one of the three rows where you want to keep one of the statuses yourself.
Out of the box the order status is mandatory, the other two are only written where the mapping delivers a value. An empty row in the tab therefore does not overwrite your status with nothing.
Special features and limits
The task only sees orders that have gone through Orders Upload. Without a channel mapping there is no counterpart in TriData to ask about.
What comes back is the status and not the order. Whatever else TriData changes about an order, a line item or an amount for instance, does not reach TRADElube.
Further reading
- TriData / TriCon: prerequisites, connection, mappings and the other four tasks
- Orders Upload (TriData): the way there, without which this task finds nothing
- Orders (reference): the detail view of an order and its sections
- Order data (reference): the status lists the three tabs point at
- Bestellstatus setzen: how a status is changed by hand
- Transfer plan (concepts): plan, section and assignment, plus the three ways to determine a value