Parameter for Post-Release Warehouse or store Processing (Pick, Pack, Ship) Time in OMS

We need to account for the time taken by a warehouse to process an order after it has been released (i.e., the internal processing time before shipment). This is critical for accurately calculating and communicating the Expected Shipping Date (ESD) and Expected Delivery Date (EDD) to customers, especially in the following scenarios:

Future-dated deliveries: When a customer specifies a ReqDeliveryDate in the future. Ship date , release notification dates are calculated based on delivery date provided

Unplanned or future stock: Where inventory is expected to be available at a later date.

As per our understanding and review of the documentation:

There is no out-of-the-box (OOTB) parameter in the findInventory or scheduleOrder APIs to configure or influence the warehouse processing time post-release.

While the system considers factors like shipping calendar, receiving calendar, and receipt processing time for procurement scenarios, it does not provide a similar configuration for outbound processing time at the warehouse.

The minNotificationTime parameter is available but is used to specify the time after an order is scheduled to a node.

Advance notification days and Maximum notification hours as per our understanding is used for release notification calculation and this is the maximum time needed.This is not directly the processing time for the warehouse after notification.

We raised a PMR as well for the same (TS019875580) and was concluded with the below response from support to raise a RFE, see below

Currently there is no configuration to consider processing time at node post notification time.

Possible Solution with RFE:

Solution 1: If the config/time is going to be standard across nodes / node Type. we can provide a property to set it and will enhance code to consider the same.

Solution 2: If the value can be different for different nodes and is independent of node type. Then node notification can be enhanced to have processing time at node. This way config are available to customer to set using API and product will consider it in findInventory and scheduleOrder.

In both the cases: You need to raise RFE.

Solution 1: Less impact as we dont need to make DB changes to support use case.

Solution 2: Need DB change and business logic update to consider the same.