This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
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?