IBM Sterling Ideas

Shape the future of IBM!

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Expected Delivery Date Calculation based on item and shipping node combination

We have a requirement to calculate Expected delivery date for following
scenarios:

1. Website displays item's availability and Expected delivery date.
Item availability information is fetched from the cache, sent by OMS in
RTAM feed. OMS can fetch EDD using findInventory API call based on
sourcing rules. But there is no OOTB support to send this EDD along
with RTAM availability message to web.
2. OMS provides support on minNotificationTime for an item and also for
a shipping node (whichever is higher). Our requirement is to define
processing time based on item and shipping node combination. e.g. a
couch can be shipped by a DC in 2 days but vendor takes 5 days to ship
this couch. The same vendor takes 3 days to ship a shirt while DC takes
1 day. There is no available option to support this feature though this
is a very standard use case. Consider example of Amazon which clearly
differentiates EDD of an item if shipped by seller vs shipped from
Amazon fulfilled wareshouses. These values do change based on the item
being ordered.

Moreover there is no user exit to customize this based on node/item
processing time.

We had extensive discussion with IBM team including Peter Stubbs and
Steve Igreyas. The decision was to raise a product enhancement request
to support this feature OOTB.

  • Guest
  • Mar 7 2018
  • Not under consideration
What is your industry? Retail
How will this idea be used?

Customer gets to know accurate expected delivery date and makes a decision on order capture. 

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.