Executing Inventory API calls with postman

Case 1: Add to Cart inventory check

When you click Add to Cart button, the backend executes the ts-app commands to check the inventory availability for the selected SKU. If the on-hand inventory is available, it updates the ESTAVAILTIME column in the ORDERITEMS table with the current timestamp. If the on-hand inventory is unavailable, it checks whether the item can be backordered. If so, it retrieves the earliest date from the expected inventory and updates the ESTAVAILTIME column accordingly.

Case 2: Allocate and DeAllocateInventory on clicking Checkout button

When you click Checkout button, the backend executes the AllocateInventoryCmdImpl class in the ts-app. This class performs key operations, including allocate, AllocateFromBackorder, deallocate, and deallocate backorder. It also updates order items to Future Orders if the requestedShipDate is not empty in the ORDERITEMS table.

Case 3: Hard reserve inventory by ReleaseFulfillmentCenter scheduler job when placed order is processed

When a placed order is processed, the ReleaseFulfillmentCenter scheduler job is executed to perform a hard reserve of inventory. This job ensures that the inventory for the ordered items is secured, preventing it from being allocated to other orders and confirming that it is set aside expressly for the customer.

API Call

• URL: {{host{}}}:{{port{}}}/inventory/api/v1/available-inventories/reserve?store=Ruby&processAllOrNone= { Unknown macro: \{value}}
• Method: POST

Command affected

com.ibm.commerce.inventory.commands.DoInventoryActionCmdImpl

Method Update

The method should be updated to include the Inventory API call shipItems().

Case 4: Process Backorder inventory by ProcessBackorder scheduler job when placed order

As we have reviewed the Commerce Order Inventory code, we do not need to call any explicit ProcessBackorder API in Commerce to process the backorder inventory. Below is an overview of how Commerce processes backorders:

1. The Commerce Order System runs the ProcessBackordersCmdImpl scheduler job at specific intervals to handle backorders. It first fetches order items with an inventory status of BO (backorder) based on the time placed.
2. After selecting the order items, it calls the AllocateInventoryCmd command, which performs the following three actions:
   1. This command calls DeallocateExpectedInventoryCmdImpl to reverse the backorder inventory for the backordered items. (You can refer to this as a reverse backorder.)
   2. Then, it calls the AllocateExistingInventoryCmdImpl command, passing singleFulfillmentCenter = Y to the stored procedure to allocate the entire required quantity from a single Inventory Location (IL) for those backordered items.
   3. If the required on-hand inventory is unavailable from point 2.b, the ordered item is marked as eligible for allocation from backordered items. It then calls the AllocateExpectedInventoryCmdImpl command to allocate the quantity from backorders, reverting the order item status to BO.
      Note: In Step 2.b, if you request a quantity of 10 and only five are available on hand, no allocation from on-hand inventory will be performed, as ssingleFulfillmentCenter = Y is specified. In Step 2.C, when you allocate inventory from backorders, five will be assigned from expected inventory, while five from on-hand inventory will be recorded in the QTYALLOCBACKORDER column.