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.
The feature to support Carry is available in IV. The following were provided
Availability API has additional flag "considerFulfillmentOptions" and considerSafetyStock" which can be turned off to retrieve the in-store walkin availability (https://developer.ibm.com/apis/catalog/inventoryvis--ibm-sterling-intelligent-promising-apis/api/API--inventoryvis--inventory-apis#post-1656250489)
Similar is available on the available supplies API (https://developer.ibm.com/apis/catalog/inventoryvis--ibm-sterling-intelligent-promising-apis/api/API--inventoryvis--inventory-apis#post868743680)
In the events the walk-in availability can be calculated using the supply quantity attribute
The real use case that we have been asked to handle is to Delivery From Store which is different from Pickup or Ship to Home.
Each store can be either enabled for BOPIS or DFS or SHIPPING or in combinations of these delivery methods.
The clients wanted to manage below separate for each of these delivery methods
Safety stock (Item-node-deliveryMethod)
Fulfillment Overrides for the Node
Fulfillment Option Update (Item-Node-Delivery Method)
node and network level availability APIs must honor the respective deliverymethod's
The real challenge is, there is no way to manage the above parameters independently and its really a missing piece and we can not manage with just two DeliveryMethod (SHP, PICK).
It will really be useful if we could share the ETA by when in future it will delivered. For of the retailers do have these different delivery methods in the current/legacy system itself and it becomes challenge to meet like-to-like to start with.
The use case what we have at our Company is we publish Find in Store Inventory to the frond end caching solution. We originally intended to use Product Availability event but we discovered that if an item has fulfilment options has flagged false product availability will not be published any more for any supply change events. So we are blind to changes to FIS. So adding this new Delivery method will help immensely.
In order to identify carry-only item's ATP (eg. for an item that's eligible for CARRY only such as a new product trial release), we suggest a workaround of setting that SKU's SHIP and PICK safety stock to 100%. Our latest feature release allows users to look up ATP with/without safety stock.
CARRY/DEL method is not planned to be supported in the short term 2021 roadmap, but it will be considered for future iterations.
It would be helpful if you can expand on the reason for this use case.