Instock Ordertasks API
Fulfillment of orders by associates and ASRS is split into chunks called `ordertasks`. An `ordertask` can represent a picking of several lines of customer order, for example. Each ordertask corresponds to exactly one order and one order can have multiple ordertasks. On the other side, each action of robots of ASRS can be attributed back to exactly one ordertask. Incloud promises, once order gets into one of the terminal statuses (`done` or `canceled`) the set of corresponding ordertasks is immutable, i.e. no new ordertasks to be added, and each ordertask record is immutable. Ordertasks corresponding to customer order are created after order fulfillment is planned, i.e. after order status changes from `registered` to `reserved`. Once customer order is `done` or `canceled`, a client of API can reconstruct full picture of fulfillment of order by retrieving ordertasks data. Ordertasks may be presented by Incloud for all type of orders (`customer`, `reception`, `adjustment`, `extraction`). | Ordertask status | Description | |----------------|---------------| | `reserved` | ordertask is in progress. | | `done` | ordertask has been completed. | | `canceled` | ordertask has been canceled. |