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.
Add support for a callback to a custom login page in Store Engagement to support users that have timed out on their login session
In conjunction with https://watsonsupplychain.ideas.ibm.com/ideas/STORE-I-49, support the ability to have a callback URL in the case where a deeplink is called. It's possible that the deeplink is initiated AFTER a user's store engagement login se...
Allow page refresh on any page within Store Engagement
If you perform a page refresh via the browser or code, it loads the default Store Engagement page and you lose the view of where you were. It would be useful to allow a page refresh within any page of Store Engagement to reload the current cont...
Regional Store manager to have access to multiple store and ability to switch between stores without having to logout
Regional Store manager to have access to multiple store in his/her region.The ability to login to multiple stores by a single user is critical for Regional Store Manager who manages multiple stores within a region.This needs to be supported by bot...
Allow BOPIS orders where order is not picked from the store but shipped from warehouse
There are scenarios where items are special order items or not available in store or store does not participate in BOPIS. Also called as Site-to-Store. In these cases, the order is actually picked in warehouse, packed and shipped to the store (vi...
Reprint of Pick list on Store engagement (angular) UI
One a pick list is printed using Store engagement UI there is no option for reprinting the pick list. Some time pickers misplace/loss the pick list in that case they need to reprint the pick list.
Putback capability for click and collect order cancellations
For BOPIS orders as part of backroom pick the picked items are moved to a BOPIS staging location or some secure location which is not then available for picking or walk-in customers. In case of a customer cancellation at that point or a no-show, t...
Multi-UOM support in Store
Multi-UOM support with interconversion and a primary UOM. As an example, be able to receive as a case, putaway inventory by case and individual units that totals up to received qty, pick in different UOM e.g. dozen based on order or be able to bre...
Return Order Reciept in Store
Hi,One common return option with many retailers is Create Return Online(Self Service) or Create through Call Center and drop the item to store.For this scenario,once customer drops item to store - we need to receive the return order - record recei...
Boradcasting a common message to all store users
Can we have a feature in OMS through which we can broadcast common messages to all stores together on Store engagement application.e.g. "XYZ carrier system is down. Do not perform any packing operation". This will help in avoiding multiple tickets...
Expose Inventory audit/transaction history in store UI
Our store users and operations team are used to having the ability to see a history of when and how OH/ATS count changed including trickles from POS, user inventory movements, receipts, etc. These are currently exposed in console but not in any s...
Do not place IBM confidential, company confidential, or personal information into any field.