IBM Sterling Ideas
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.
Today, Sterling provides for calculation of store node sell-through velocity based on the order fulfillment that OMS has visibility to by virtue of orchestrating orders.
However, in practice, a given store node derives a large portion of its sell-thru from in-person, in-store "take" sales (non-order based transactions). We need a means of logging (importing) a given node's non-order based sell-thru for use in velocity and order sourcing and scheduling rules. Ideally, the mode of import for non-order based sell-through would be flexible to allow for either real-time unit-level deltas as provided in real-time by POS APIs, or periodic bulk loads representative of a given time frame from our POS Sales Audit system(s).
|What is your industry?||Retail|
How will this idea be used?
A given store may see high foot traffic and in-store sales, but not necessarily be a heavy fulfillment location. In general, we want to fill order units from stores with slow-moving inventory, so as to not cannibalize in-person "take" sales. Today, a given store's velocity does not reflect the speed with which its inventory is sold-through inclusive of walk-in POS sales.
Do not place IBM confidential, company confidential, or personal information into any field.