Order Management
Last updated
Last updated
In the fulfillmenttools platform, an order is a request from an end customer via an external store system that must be fulfilled in one of the facilities. An order contains information on the customer, the delivery preferences, the items which are ordered and optionally, additional information such as services.
In this graphic you can see an example how an order flows through the different modules of the platform. The different parts you see in the graphic will be explained below.
The order is the key component of the connection between shop systems and our fulfillment platform. It is the starting point and basis for all subsequent order routing processes of the DOMS and contains ordered items and services as well as any potential delivery preferences of the customer.
The order entity can also be used to provide further information that may be relevant in the subsequent routing or fulfillment process.
The fulfillmenttools systems differentiate between ship-from-store order and click-and-collect orders. Ship-from-store (SfS) orders are shipped from a facility by a shipping provider to the customer's address. Whether this facility is actually a store or a warehouse does not matter. Click-and-collect (C&C) orders are picked up by the customer in the store.
Additionally, custom services can be added to order lines or independent of order lines to an order. Custom Services add services to orders or order lines which are executed after picking. This could be shortening of pants, an engraving of a watch or an appointment for an eye test at an optician.
There are use-cases where not every order should be fulfilled as soon as possible. In some cases it might me necessary to do some manual checks on an order, e.g. customer verification or fraud detection. This is where a "locked" order comes in plance. Locked orders are routed to a facility but do not result in a pickjob until they are unlocked. The unlocking can be done manually via the backoffice or via API.
Since a locked order does not create a pick job such an order is not effected by a time triggered reroute.
The expiry feature allows automatic canceling of orders if they are not fulfilled within a specified timeframe. When an order is placed, a specified fulfillment time is set. If the order is not fulfilled within this timeframe, the expiry feature automatically cancels the order and releases the reserved items.
Configure the expiry feature by defining a buffer time which is added to the provisioning time to determine the expiry time. Additionally, the "provisioningTime" value must be defined in the order. Alternatively, an expiry entity can be created via the API.
There can only be one expiry entity for each process
If updated, the expiry time is recalculated based on the new information.
Please see here for the API documentation.
Please go to the for more information on managing orders via API. The API documentation can be found here.
Please go to the for more information on how to create locked orders.
