Watson Commerce Ideas

Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, Call Center and CPQ are now a part of Watson Supply Chain. Please bookmark the Watson Supply Chain Idea Portal.

Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, Dynamic Pricing, Price Optimization, Promotion Optimization, Markdown and Deal Management. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with your peers and IBM experts on the Watson Marketing and Commerce Community and the Order Management Interest Group, now a part of Watson Supply Chain.

Submit ideas for other Watson Customer Engagement Products:

  • Watson Marketing
  • Watson Supply Chain

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

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 17 2018
  • Needs review
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.

What is your industry? Retail
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 17, 2018 15:48

    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

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 17, 2018 16:37

    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.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 17, 2018 19:02

    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.