Login  Sign up

July 2022

Planned Product release to production is August 9th, 2022

Edit Promise Time

To continue to enable retailers to support a good customer experience, the ability to edit an order's promise time to a sooner time has been added to the command center. In the first iteration of editing promise time users were only able to move an order's promise time further out into the future, now users can edit the order's promise time to be a closer date and time. To allow for some operational stability and control, a new app attribute, MinTimeIntervalInMinutesForPromiseTimeUpdate, has been created which will prevent promise times from being edited to close to the present time. By default, this attribute is set to 120 minutes and will not allow an order's promise time to be between the present time and two hours from the present. This is to ensure that orders are not moved forward without leaving enough time for the operations teams to respond to the update.

Also to ensure that all parties are aware of changes to promise times, a Delivery Exception will now be displayed in the Command Center if an order's promise time has been updated by the delivery provider. Hovering over this icon will display the order's original promise time (and date) and will also display the order's new promise time (and date).

Disabling Carryout Follow Up Auto-Responder

In the carryout workflow a customer indicating their arrival using a "Here" text message, or a location-based service indicating their proximate arrival, would create a requirement for a carryout associate to claim the order. Previously, if this was not done in a given period of time a carryout auto-responder would be generated and sent to the customer. In some scenarios this is not a desirable addition to the customer experience, so we have added the ability to disable this auto-generated text message.

Before, this behavior was controlled using two separate app attributes (OrderNotificationCarryoutFollowUpMessage and OrderNotificationCarryoutFollowUpInSeconds) we've now consolidated these and added the enabling/disabling ability. Clients wishing to adjust this will need to edit the values for the new app attribute OrderNotificationCarryoutFollowUp. This will contain three properties that can be adjusted:

  • OrderNotificationCarryoutFollowUpEnabled
    • This will allow TRUE or FALSE
      • When True, the follow up message will be generated and sent to carryout customers if the carryout notification has not been taken in the given timeframe
      • When False, the follow up message will not be sent to the customer.
  • OrderNotificationCarryoutFollowUpInSeconds
    • This property will accept a number value.
      • The number indicated here will indicate how long to wait for an employee to claim the carryout before the follow up message is sent to the customer (if that has been enabled).
  • OrderNotificationCarryoutFollowUpMessage
    • This property will be the text message string that is sent to the customer

For clients who've had these properties prior to this update, those will be carried into this new, consolidated app attribute. By default the values are set to the following:

"OrderNotificationCarryoutFollowUpEnabled": "True",
"OrderNotificationCarryoutFollowUpInSeconds": "90",
"OrderNotificationCarryoutFollowUpMessage": "Test Message Response"

With these defaults, if a customer indicates their arrival and the order is not claimed in 90 seconds, a text message will be sent to the customer saying "Test Message Response"

Out for Delivery Option Added to Rules Management

The order status of "Out for Delivery" has been added to the Rules Management create/edit rules page. Using this status to send a text message to customers when their delivery order is on the way is a great way to ensure that customers are ready to receive their orders.

Adding Bag Charge

In many areas there are now requirements to add additional charges when plastic and/or paper bags are being used. This is now available through the ShopperKit mobile app. After the order has been picked, when enabled, associates will be prompted to indicate how many bags have been used in this order. This will create line items that are include with the POS integration and will appropriately add bag charges to the order. There is an app attribute that controls this behavior, BagFee. This attribute will accept a JSON value with the following attributes:

  • BagFeeEnabled
    • This is a TRUE/FALSE value that will enable this feature
  • BagFeeUPC
    • The value entered here will be the UPC that is sent to the POS for the bag fee
  • BagFeePriceInCents
    • The value entered here will be the cost per bag. Example if "250" is entered, each bag indicated will cost $2.50


  • Fixed the issue occurring when ecommerce solutions were updating item quantities
  • Fixed the issue where ID checks where not being triggered when alcohol items where subbed or added in an order import process
  • Fixed issues occurring when a 3rd party is updating promise times and a delivery exemption is not being triggered
  • Fixed issue when trying to produce multiple order summaries but getting a NULL screen instead
  • Resolved use case around pick sessions closing due to over-night picking
  • Fixed an issue that was causing an unending loading screen within the mobile app
  • Fixed the issue that was resetting printer settings after an update
  • Resolved field validation that was preventing saving the app attribute AllowSendTestMessageTimeFrame