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.

Configure Global Safety Stock by Node Type

Environment Details
CoC - 18.2

Business Requirement:
Consider the following scenario to better explain the exact requirement - 

Item ID - 123
Onhand Inventory in DC - 100
Onhand Inventory in Stores (all stores combined) - 100
Safety Factor (DC) - 0
Safety Factor (All Stores combined) - 4

Expectation:
Availability to Promise (WEB) - 100 + 100 - 4 = 196

Our Analysis:
There is no configurable feature in the product to achieve this requirement. However, we can configure 4 per Store (Node) but not at the Node Type level.
Let us know if there is anything configurable in the present product.

We want the feature to be at the Node Type level.

FYI, this is a very common requirement for apparel retailers. I expect this feature to be available OOB and not through any customization.
The inventory picture per store is shallow in Eileen Fisher. Hence, having a safety stock of 4 per store will never lead to a sale in the SFS program.

At the same time, having a safety stock of zero may lead to potential cancellation of web orders as the store inventory is very dynamic. Hence, its a very logical requirement of business to have a safety stock on the store inventory when consuming the web order demand as part of the SFS program.

We strongly recommend this feature as OOB.

Let me know if you have any Qs.

 

Thanks

Abhi

  • Guest
  • Sep 17 2018
  • Future consideration
What is your industry? Retail
How will this idea be used?

This is a very common requirement for apparel retailers. I expect this feature to be available OOB and not through any customization.
The inventory picture per store is shallow in Eileen Fisher. Hence, having a safety stock of x per store will never lead to a sale in the SFS program.

At the same time, having a safety stock of zero may lead to potential cancellation of web orders as the store inventory is very dynamic. Hence, its a very logical requirement of business to have a safety stock on the store inventory when consuming the web order demand as part of the SFS program.

We strongly recommend this feature as OOB.

Let me know if you have any Qs.

  • Guest commented
    17 Sep, 2018 07:02pm

    Having shallow store inventory is very realistic with today's retail business moving into more boutique stores.

    Currently we're unable to configure Global Safety Stock value to guarantee that at least X number of units are available to cash and carry customers across entire chain. Configuring store safety stock to 0 (zero) will essentially expose entire chain inventory to the web with the risk for 'cash and carry' customers never be able to get this item in a store. Configuring it to 1 will result in some of the SKU's being completely ignored by RTAM - practically means that some of the SFS eligible items will never be exposed to the WEB.

    I see it as a major Sterling OMS shortcoming that seriously handicaps business in today's very competitive retail environment.

    IBM should lead the way - not follow. Please consider implementing this sourcing rule ASAP.

    Thanks,

    Alex Pinskiy | Sr. Manager OMNI Channel Order Management/Customer Service Technologies

    EILEEN FISHER Inc.

  • Guest commented
    17 Sep, 2018 04:37pm

    I agree - the Safety Factor at Network level makes sense for Ship-from-Store. It is typical that store inventory for many SKUs is 1 - typically stores will stock multiple units of common colors & sizes. But they may only stock 1 unit for less common sizes / colors. I have seen a similar profile at retailers that sell high-value product like jewelry.

    In all these scenarios, Safety Stock applied at each store level would essentially mean that these SKUs cannot be shipped from store. A better approach in these cases is to set the Safety stock at the aggregate Store network level. I have seen multiple clients configure this using other competitive OMS solutions.

  • Guest commented
    17 Sep, 2018 03:48pm

    This is a good feature to have. A lot of time retailers struggle with safety stock numbers for the network. The traditional model of location based safety stock serves best for distribution centers.

    Also the leading competitor order management system already has this feature for a long long time.

    Regards,

    Nikhil

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.