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

Modify how reserveItemInventory and reserveItemInventoryList internally determine Demand End Date to allow for infinite lead days.

Both of these APIs, reserveItemInventory and reserveItemInventoryList, assume infinite availability past the demand end date that is internally calculated. If the item doesn't exist that is "Current date + Processing time + lead days from ATP rule". Then for an item that does exist it is calculated as "Current date + Processing time + lead days from Item". The issue is this doesn't allow for infinite lead days as in there isn't a future date where in which we can definitely procure inventory.


The request is to have an item with a lead days of 0 calculate the demand end date as the high date (2500-01-01) or have it use the ATP rule configuration instead.


If the item exists and lead days is null or 0: DemandEndDate is fixed as Current date + Processing time + lead days from ATP rule

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 1 2019
  • Needs review
How will this idea be used?

This is the only reason reserveItemInventory and reserveItemInventoryList APIs can't be used to reserve inventory. The way they work today any reservation request made against an item with a 0 lead days completely ignores on-hand inventory and blindly makes the reservation. A reservation against an item that doesn't exist behaves differently, that is a clear defect.

What is your industry? Retail
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files