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.
Ability to trigger the Supply or Demand buckets inventory picture for an item on demand/need basis
Currently client systems are subscribed to supply change and demand change events from IV over webhooks to reflect inventory buckets for client front end needs. For any missing events due to any reason, there is no functionality in IV to retrigger...
Include an Identifier to differentiate between the Inventory dbavailabilitycache message triggered by a delta vs full sync(publish_all trigger)
In our integration with IV services, we encountered scenarios where a full sync is being consumed by MW system and in the interim delta change comes in, the delta change processing is delayed because of the lengthy processing of full sync messages...
Modify UpdateItemRelationship API to support to multiple items
API Update Item Relationship can use to update one item relationship at once .
Need API to fetch reservation details with the Item & Shipnode
Need API to fetch the reservation details for the given Item & ShipNode without passing any referenceId
OMS to IV item relationships
Currently no OOTB support to sync item relationships for items with variations between OMS and IV
Metrics in IV to understand the exposure rates
Ability to have insights into how much Inventory we are exposing for Demand and the reasons behind blocking by Dirty Node Vs Safety Stock vs Demand…etc., This information is critical for business and operations team. The below metrics are needed t...
Order Hub UI should be displaying all the product classes and corresponding inventory similar to Legacy Inventory Management UI
Please refer to the attached document.
IV Supply Sync Visibility
Need an acknowledgement process for Supply Sync in IV that will summarize saying they received “x” number of updates, processed “x” number, and the supply for “x” number of items did not change. IBM informed this requirement is on the product road...
Add Fields to Order Hub (reference, referenceType, lineReference, segment, segmentType)
We would like to have the option to view the following fields in Order Hub: reference, referenceType, lineReference, segment, segmentType.
GTIN based Inventory Availability and Scheduling in OMS CoC and Inventory Visibility
For our current client, inventory items are uniquely identified using UPCs(not to be confused with UPC in generic sense) and not SKUs, while the selling catalog identifies items using SKUs. These UPCs can change every year for the same item. For e...
Do not place IBM confidential, company confidential, or personal information into any field.