In OMS - Order Management System, Node Cutoff Time is the latest time in a day by which an order must be received and allocated to a ship node for it to be processed and shipped on the same business day. Currently SIP does not support configuring node cut offs for different delivery options (standard home delivery/nominated home delivery/click & collect). Operationally fulfilment node (warehouse/store) could have different cut-off for different delivery option.
For example,
for standard home delivery -> carrier pickup late in night -> so cut-off could be late in the evening,
but for nominated home delivery -> carrier pickup in early as they need to deliver the next day -> so cut-off could be early in the evening.
Some examples below:
for Warehouse_1 ,
Standard home delivery, Cut off 22:00 PM , Processing time : 24 Hrs.
Nominated home delivery, Cut off 19:00 PM , Processing time : 2 Hrs.
for Fulfillment_store_1 ,
Standard home delivery, Cut off : 11:15 PM & 13:15 PM (multiple cut-offs for same delivery option to support multiple pick waves), Processing time : 2 Hrs.
Considering this cut-off nuances is important as the earliest delivery date shown to customer will differ before and after cut-off. Sterling OMS does support this level of configuration.
--------------------------------------------------------------------------------------
Example 1: Warehouse_1 - Standard Home Delivery
Configuration
Scenario A - Order before cutoff
Order placed: Monday 21:30
Before 22:00 cutoff
Order enters processing immediately
Processing completes Tuesday 21:30
Picked up Tuesday 23:00
Customer Promise
Scenario B - Order after cutoff
Order placed: Monday 22:15
Misses cutoff by 15 mins
Processing starts Tuesday
Processing completes Wednesday 22:15
Picked up Wednesday 23:00
Customer Promise
Impact
A 45-minute difference in order placement results in the customer seeing a delivery date one day later.
--------------------------------------------------------------------------------------
Example 2: Warehouse_1 - Nominated Next Day Delivery
Configuration
Scenario A - Order before cutoff
Customer Promise
Scenario B - Order after cutoff
Order placed: Monday 19:15
Cutoff missed
Processing deferred to Tuesday
Picked up Tuesday evening
Customer Promise
Impact
Without delivery-option-specific cutoffs, SIP could incorrectly offer Tuesday delivery, resulting in failed customer promises and operational exceptions.
--------------------------------------------------------------------------------------
Example 3: Same Warehouse, Different Delivery Options
Order placed Monday at 20:00
Although inventory is available in the same warehouse, the customer sees different delivery promises because different delivery options have different operational cutoffs.
This is exactly the capability OMS supports today.
--------------------------------------------------------------------------------------
Example 4: Fulfillment_Store_1 with Multiple Pick Waves
Configuration
Scenario A - Order at 09:00
EDD
Scenario B - Order at 11:30
EDD
Scenario C - Order at 14:00
EDD
Impact
OMS supports multiple cutoffs/pick waves per delivery option. SIP currently cannot model these nuances, leading to less accurate promise calculations and potentially overstated customer promises.
--------------------------------------------------------------------------------------
Business Impact Statement
OMS supports delivery-option-specific and multi-wave node cutoff configurations, enabling promise calculations to reflect the true operational capability of each fulfillment node. Without this capability, SIP may calculate the same EDD for orders that are operationally processed under different carrier pickup schedules and fulfillment cutoffs, resulting in inaccurate delivery promises, reduced customer experience, and increased operational intervention.
Hi Team,
We were expecting feature similar to OMS node notification schedule which acts as the cut off time by which node has to be notified for processing to start for the same day and then processing time is added to notification schedule to arrive at ETS (Expected Shipment Time)
As I understand the feature that is delivered is slightly different, the feature is about shipping cut off which indicates that node has to complete processing by that time if it has to be shipped and picked by the next carrier pick up schedule. So, if we have to sync OMS with SIP, then we should add OMS node notification schedule to node processing time and set it as SIP shipping cut off time, correct?
example:
OMS Node Cut off: 17:00
Node Processing time: 2 hours
Carrier pick up schedule :19:30
Should be configured as
SIP Shipping cut off : 19:00 (17:00 + 2 Hours)
Node Processing time: 2 Hours
Carrier pick up schedule: 19:30 hours.
So that, any orders placed before 17:00, will have ETS stamped as currentDate at 19:30 hours. Else it will be stamped as nextDate at 19:30 hours
So, please let us know if SIP is planning to move away from notification schedule concept to shipping completion time as cut off ?
Feature has been released on Sept 2025. Marking Delivered
For more information refer to
https://www.ibm.com/docs/en/sip?topic=service-shipping-cutoff-times
Cutoff can be defined at both level Node, and ShippingGroup-Node Level
UI interaction
https://www.ibm.com/docs/en/sip?topic=promising-configuring-shipping-cutoff-times
Hello team, could you please let us know if this feature is released and provide the respective api specs?