Skip to Main Content
IBM Sterling


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).


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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

ADD A NEW IDEA

Inventory Visibility

Showing 29

Enhance the supplyChange.v2 event schema to allow propagation of custom attributes included in the original IV request.

Problem Statement:We are using the supplyChange.v2 event to publish IV resonance data to a configured webhook endpoint. As part of our implementation, we are including several custom attributes (e.g., SourceSystemID, AdjustmentReasonCodeID, etc.) ...
about 1 month ago in Inventory Visibility 1 Future consideration

Enhance IV bundles to support the idea of key skus

If I have a bundle 789 consisting of components: SKU 123 (key sku) SKU 234 (key sku)a SKU 345 (non key sku) SKU 456 (non key sku) While inquiring availability for bundle 789, I would like IV to only check the bundle components where getNodeAvailab...
about 1 year ago in Inventory Visibility 1 Future consideration

Inventory Audit for Historic Availability

Would be helpful to have inventory Audit for the currentAvailability of an item in Order Hub and IV UI. Similar to the Inventory Audit screens for Supply and Demand of an item, having the ability to see what the availability of an item was at a ce...
2 months ago in Inventory Visibility 1 Future consideration

Database for IV

Need a read only database to connect to that shows all supply and demand records, quantities, ship nodes, sourceTs, segment info, etc. from IV. This will help with data cleanup and visibility. We have no way of knowing about stale data unless we q...
10 months ago in Inventory Visibility 2 Future consideration

Ability/ Option to clean up data loaded into IV via a self-serve option/ API

Currently, IV APIs do not give the option to clean up the data loaded into it via the integration with OMoC. There are APIs to perform adjustments or to zero-out the supplies/ demands and hence availability in IV (and thereby the process to clean ...
over 6 years ago in Inventory Visibility 3 Future consideration

Provide "null" as value when there is no record of the item

Currently, when we call IV asking for the availability of a SKU that does not exist (eg "Hobbit_250", IV returns "0" units available. But considering that IV has no record of this product, we want IV to return "Null" If there is a record of the pr...
6 months ago in Inventory Visibility 0 Future consideration

Allow multiple tags to be passed in getTagListForOrdering API

Better perfromance could be achieved if getTagListForOrdering API allowed multiple tags to be passed in the input. That will allow us to not call the API for each tag.
7 months ago in Inventory Visibility 0 Future consideration

Node Availability API to support Node Transfer

Adding support for node transfer in IV will allow a retailer who does not have SIP whom is currently supporting click and collect just from store stock to easily transition to supporting DC to Store transfer as well as Store to Store transfer when...
over 1 year ago in Inventory Visibility 1 Future consideration

Ability to consider unassigned demands (no assigned node) in availability calculation

The Get Network Availability API exposed in Inventory Visibility mandate Distribution Group to be passed in the input. The API does not consider OPEN_ORDER/ BACKORDER demand types while computing the availability in IV. This leads to inconsistenci...
over 6 years ago in Inventory Visibility 8 Future consideration

Additional attributes in the reservation data.

During reservation create/update we want to pass additional attributes associated to reservation, persist it and publish them in the event message along with reservation details. These additional attributes are supporting information for the downs...
over 1 year ago in Inventory Visibility 0 Future consideration