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.
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...
Porduct scan is not allowed by product id for the orders having products with same item id and multiple UOMs. It is applicable on all scans in store application.
We have a Retail customer whose catalog allows multiple items created with same item id but different UOMs (EACH, CASE). When order products are scanned by using item id, it returns two items and error pops out saying multiple items found for ent...
Consolidate Call Center and Store Engagement into a single Customer Engagement Solution
The idea there are separate solutions needed for customer engagement is antiquated and driven more by either poor organizational structures and silos, and/or the current market environment of solutions. IBM has the ability to take the lead in this...
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...
Support for deprecated Inventory Visibility APIs for OMS on-prem to OMoC 2 migration implementation
Cetrain OMS Deprecated APIs that are currently being exposed as OMS web services do not have alternative Store/IV APIs
Bill of lading (BOL) functionality should be part of Store offering/product
Bill of lading (BOL) is one of the most important documents in the shipping process.
To ship any goods, a bill of lading is required and acts as a receipt and a contract.
A completed BOL legally shows that the carrier has received the freight ...
Ability to create 'Physical Counts' in Store to synchronize the physical and system inventory mandated as a part of the corporate policy or client requirements
Ability to create 'Physical Counts' to synchronize the physical and system inventory mandated as a part of the corporate policy or client requirements.
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.