IBM Sterling
This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
As a follow-up to my previous comment.
The store dashboards use the ExpectedShipmentDate and SLA configuration when displaying some of the widgets. The dashboards are therefore incorrect for retailers that communicate when an order is ready for pickup to the customer upon completing the pick in store. In this scenario the customer has start pickup date upon order being picked in store and an end pickup date of start pickup date + X duration depending on how long the customer is given to pickup the order.
For this use case we would ideally have two separate SLAs for store management.
Backroom Pick SLA - Some retailers will give stores an SLA to pick orders and therefore would be ideal to add this visibility into the dashboards.
Customer Pickup SLA - Similar to existing SLA displayed however this should ideally be considered only from "Ready for Customer Pickup" status for this use case since we only communicate the pickup end date once order has been picked.
Thank you for the feedback Nam. We do intend the BOPIS accelerator as a starting point for implementation, rather than a turn-key solution, so it will not be able to handle every scenario. We will take point #1 into consideration for future improvements. Point #2 would be beyond the scope of what we can achieve as an accelerator.
Hi Aaron,
The BOPIS accelerator description meets some of the use cases around providing events to send customer communication e-mails.
Some enhancements that are needed are the following:
The product creates a tight coupling of when store user is required to pick the order and when customer is required to pickup the order using the common ExpectedShipmentDate attribute. Due to potential inventory shortages Customer is usually informed to wait for communication that their order is ready to pickup and they'll have X days to then pickup the order. Therefore the SLA and attribute for when store user should pick and for customer pickup should ideally be separated. Upon the configurable X days after shipment is ready for pickup an event should be triggered to allow options such as alerting the store to cancel the shipment and return items back to store stock.
Some clients would like to only send customer communications during certain hours of the day only and therefore a means to control when customer e-mails are sent should be possible if stores are picking orders outside of normal working hours.
Hi Nigel, thank you for submitting your idea. There certainly are many common components and features needed for any BOPIS implementation. This is why we created the BOPIS deployment accelerator, which supports common BOPIS scenarios including customer notification and overdue customer pickup events and monitoring.
If you haven't reviewed this accelerator, you can find the documentation here: https://www.ibm.com/docs/en/order-management-sw/10.0?topic=software-building-deploying-bopis-deployment-accelerator
Could you please take a look at this accelerator and see if it meets the use cases you have suggested?