1. Contents
  2. Guides
  3. Orders
  4. Processing orders

Processing orders

This guide sets up the order flow: orders arrive from the shop by themselves, are checked at a glance, and are ready for your ERP system. TRADElube is the hub in between: the shop delivers the order, TRADElube translates it through the channel's mappings into your own statuses and methods, and the ERP system picks it up. What every field of an order means is under orders (reference) and is not repeated here.

Prerequisites

  • A channel to your shop or marketplace that has been set up, with its mappings for order status, payment methods and shipping methods filled. The steps are under setting up a channel.
  • For the handover to the ERP system: its connection as a connector, or the custom channel's order export as a file.

Step by step

  1. Leave the collecting to the task. Your channel's Orders Download task fetches new orders at the interval of the Performance field. The Age of Orders to Sync field limits how far back it reaches. Each order becomes a record with positions, addresses and the customer details as a copy taken at the time of the order.

  2. The mappings do the translating. Order status, payment method and shipping method of an incoming order come from the channel's mappings: on the outside the shop's value, on the inside your entry from the order and shipping lists. That is maintained once during setup, and afterwards only when either side gains a new value.

  3. Check. The list shows the newest order at the top, and a gray order status means not released. In the detail view the three status fields sit in the Common section, the positions with their totals below. Through Select in the Customer section you link the order to the customer master, if the task has not already done so.

  4. Control the release. Only what carries the Released tick is passed on. By default every order arrives released. Whether and when is decided by the Release assignment in the transfer plan of Orders Download, where the release can be tied to conditions through a script, to the payment having arrived on prepayment for instance. For the individual case you take the tick off the order by hand.

  5. Hand over to the ERP system. A connector such as the CAO-Faktura connector fetches the released orders by itself, at the pace of the connected program. Without a connector, the custom channel's Orders Export task produces a file you download by hand or pass to a data source through an endpoint. Which actions your system has is listed under channels and tasks.

Checking the result

  • Every order from the shop appears in the list, with the order status in the color of its level.
  • The order's Channels section shows one row per system involved: the origin and, after the handover, the target.
  • In the traces one transfer is listed per order. Narrow down to the task's name through the Filter field.

Frequent pitfalls

  • An order that is not released stays put, without an error. That is intended and visible in the list by the gray order status. If you miss an order in the ERP system, check the Released tick from step 4 first.
  • The time window limits the reach back. Orders older than Age of Orders to Sync are no longer fetched by the task from step 1. If you connect a shop after the fact and need the history, widen the field temporarily.
  • An order is a record. Price and name changes on the product change no existing order. Corrections happen on the position itself, while checking in step 3. Why it is built that way is under orders (reference).

Further reading