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.

BOPIS/ Click and Collect Emails and Alerts

  • Most projects typically have requirement for following:

    • Ready for Pickup/Collection E-Mail, Pickup/Collection Reminder E-Mail, Not Picked-Up/Collected E-Mail (upon being cancelled from ready for pickup status), Picked-Up/Collected E-Mail

      • Be good to have standard OOTB support for these e-mails

    • Pick-up End Date

      • Usually once order is ready for pick-up customer is given X period of time to pick up the order.

      • Product currently uses "ExpectedShipmentDate" for operational pick SLA indicators and also used for Customer pick-up SLA indicators.

      • Need ability to separate the SLA indicators between when should be considered the "pick-up start date" and "pick-up end date" from which "pick-up start date" could be amended once pick completed to ensure the end date is based on agreed time customer is given to pick up their items

      • Alert should be generated for store users upon exceeding "pick-up end date" to allow stores to cancel the order and return items to stock

  • Guest
  • Jun 1 2022
  • Needs more information
What is your industry? Retail
How will this idea be used?

Accelerate projects (particularly MVPs) for BOPIS projects

  • Guest commented
    20 Jul 04:46pm

    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:

    1. 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.

    2. 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.

  • Admin
    Aaron Cutter commented
    9 Jun 08:29pm

    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?

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.