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
Add following functionality for 'On Hold' bulk items up to XX mins. As per following scenario ... We have created a remorse hold, to hold order's for 30 mins. To resolve the hold, we have created hold processing agent which is abstract transaction of process order hold Type. And part of the YFSProcessOrderHoldTypeUE code of the custom agent, we have added custom code to check whether to resolve the hold or not, if the condition is not being satisfied hold will not be resolved. In that case if the hold is not resolved, available_ts in yfs_task_q is getting incremented by 15 mins. After 15 mins passed, we could observe the custom agent picking particular record based on available_ts in yfs_task_q and once again checking whether to resolve the hold or not, if the condition is satisified hold will be resolved, else once again available_ts in yfs_task_q will be further incremented by 15 mins. This behavoir is happening for single order.
But when we trying to validate the behavoir for bulk orders, what we could see is agent is not immediately picking the order after the available_ts is passed in yfs_task_q. Due to which time to resolve the hold is increasing upto 1 hr.
Ex: available_ts in yfs_task_q is at 12:30, for bulk orders we could see agent is picking the record at 12:37. And if the load is being increasing further the agent
is picking the record at 12:47, which 17 mins more than the available_ts.
How will this idea be used?
To provide bulk order hold functionality and improve the customer experience.
|What is your industry?||Retail|
|What is the idea priority?||Medium|
|Link to original RFE|