Order flow process: ATP-inventory with the Payments subsystem

The order process, from a merchant's perspective, is composed of various steps.

The Site Administrator scheduled the following jobs:

• ATP-inventory jobs

• Payments jobs

The following steps outline the lifecycle of an order from placing an order to shipping it to the customer.

1. Place an order. A customer or an administrator who has the authority to act on behalf of the customer places an order with the store. The order moves to one of the following states:

   B

   Backordered

   I

   Submitted

   M

   Either a part or the total amount is approved.

   The Prime Payment event is triggered and corresponding payment actions are run.

   Approve the order.

   Approve payment for the order, if required. Payment methods such as COD (Cash on Delivery) and Bill Me do not need approval.

   If the order contains products that are to be backordered, then it moves to state B (backordered). Orders can be backordered with the command ProcessBackorders, or by a scheduler. For reauthorization, the order goes back to state M or a state such as A, I, B, or C. After a backorder is approved, allocate it. Do not reorder, or the order might go back for approval again.

   Release the order to fulfillment. The ReleaseToFulfillment scheduler job releases the orders to fulfillment. When all order items for the order are released, the order moves to state R (Released).

   Create a pick batch for all orders released to the specified fulfillment center.

   View and print pick tickets.

   View and print packaging slips.

   Pick and pack products specified in the pick ticket and packing slip.

   Create package.

   Ship goods. Ship the order to the customer.

   Confirm shipment has been sent. When all order items are shipped, the order moves to S (Shipped) status.

   Finalize the order. The OrderClose scheduled job runs to initiate closure of the order.