Login  Sign up

September 2020 | Mobile 1.2.10070 - Classic 5.8.4

Delivery Integration Exception Management

With this release, ShopperKit is beefing up it's delivery partner integration capabilities by introducing functionality that will allow your store associates to see and respond to delivery integrations exceptions and errors from within the client applications as well as Command Center Order Inspector. Delivery Integration exceptions can happen for a number of reasons. Perhaps the delivery address isn't recognized or the zipcode is outside of the defined delivery radius. Maybe you are attempting to cancel the delivery too close to the already claimed delivery window. Each delivery partner has their own set of rules that may trigger exceptions within the integration workflow. Regardless, with the new exception management functionality you will be able to quickly identify orders where the Delivery Partner has reported an error and depending on the exception, you may in fact be able to force ShopperKit to retry sending the order through the integration. 

Anytime an order has a delivery exception, the red delivery exception icon will be visible on the order in both client applications or command center as seen below.

The details of the exception can be seen from within the Delivery History screens either from the order details of the order in the client applications or from the Delivery History menu option in the Command Center order inspector. Here you will be able to see exactly what exception the integration is passing back to ShopperKit. As many integration issues can be corrected by adjusting setup parameters for the specific provider, ShopperKit allows you to try re-submitting the order to the provider by tapping the retry option.

SMS Messaging improvements

Twilio message delivery feedback

In an effort to provide store associates with better visibility Into their text messages communications with customer, ShopperKit will now provide Twilio message delivery status back to the chat client. Due to the fact that messages are sent by Twilio asynchronously, there may be delays between when the message is sent and the delivery status for the order is updated in the chat client. 

Messaging Hours of Operation

As many of our retail partners run their fulfillment operations during off hours where it would be inappropriate to send text messages to their customers, we are introducing a new feature that allows you to explicitly define the hours of the day that text messages can be sent to customers. If users attempt to send a message to the customer outside of the defined Messaging Time Frame, those messages will be enqueued and will appear in the chat client with an hourglass icon to indicate they are being held. All enqueued messages automatically get sent once the window opens up.

To configure the Messaging window, we have introduced a new AllowSendTextMessageTimeFrame application attribute that may be configured at both Client and Store levels. The attribute is a JSON object with controls to indicate if the attribute is enabled along with the start and end time of the window. The StartTime and EndTime controls are defined using UTC/GMT. The example below would allow a store on EDT to limit the hours of texting to 8AM - 9PM.

"StartTime": "12PM",
"EndTime": "1AM"

Unmonitored Order Auto Responder

As some of our retail partners find it difficult to monitor text message communications on orders after they have moved past a certain point in the order workflow, we have introduced a new attribute driven auto response feature. By setting the SMSChatAutoResponder application attribute at either the Client or Store level, ShopperKit will automatically respond to any inbound SMS messages received for orders that fall within or have moved beyond the defined status value. The attribute is a JSON object that contains controls for Order Status, Minutes Past and Message. Once an order has been in or moved past the defined status for a period of time that is equal to or greater than the Minutes Past control, the Message value will be sent as a response to the customers inbound text message.

OrderStatusId: 4,
MinutesPast: 15,
Message: "We are no longer actively monitoring text communications on this order. If you need to speak to someone, please call us direct at 404-867-5309."

As the Order Status control utilizes the internal numeric status ID, the following table may be used to translate application status to the correct numeric attribute.

Command Center Updates

Template Management

In an effort to reduce issues where store users are editing or modify messaging templates we have made this role based. Going forward you must be a client admin role in order to create or edit messaging templates.

Order Inspector Order Management

As the Command Center Order Inspector page is becoming more of an order management tool, we have recently added in new functionality that allows Store Managers or Client Admins to perform certain order management tasks. From the Order Inspector order level menu, Store Manager users will be able to Cancel or Auto Complete orders. Both functions require a user comment and updates will flow back to commerce. Users may now also view the order status history of the order as well as delivery status history. 

Lead Time alert email improvement

By customer request, the Lead Time Alert email format has been modified to include Promise Date for the order as well as any relevant item level comments.

ShopperKit Mobile Improvements

Show Customer info on Container Screen

In an effort to make multi-order picking more efficient, ShopperKit Mobile now shows the customer name and order number when putting an item to a container to make it easier for a store associate to visually locate the container.

Reset Substitutions 

Similar to how you are able to reset order items that have been marked as Shorted, you are now also able to reset items that have been Marked as substituted. When reseting a substituted item, it's important to understand that ShopperKit doesn't automatically remove any item that you have already picked as a sub item. To remove any items that have already been substituted on the order you would first need to unpick and short the sub item, then reset the original item to either sub for a new item or pick as originally intended.

Supported Devices

ShopperKit Mobile adds support for the Datalogic Memor20 on Android and Honeywell Captuvo SL22 and SL42 on iOS.

Payment Type Overrides

Today when an order fails to authorize during the payment settlement process due to an error at the payment gateway, ShopperKit will allow users to change the payment type on the order to an in-store payment method. Occasionally some retailers have a need to change the payment type ahead of processing the order for settlement. To facilitate this need, we are introducing a new PaymentOverrideChangePriorToSettlement store level attribute. When this attribute is set to True, users will be allowed to change the payment type at any point before the order has been settled from the POS screen within the client applications.

Promise Time offset

The Promise Time data that is displayed in ShopperKit is based on the starting time for a given orders pickup or delivery time slot. In some cases, based on order type or function, it may be desirable to offset the time to more accurately reflect the time that the order needs to be ready. To facilitate this we have added 3 new Promise Time offset attributes. Promise Time overrides are set in HH:MM format and will be applied as a mask to the times displayed in ShopperKit. So if a delivery order had a promise time of 10:00 AM, but we want the order to be ready for a 9:30 AM pickup time, then we would set the DeliveryPickupOffset attribute to 00:30.

SpokePickupOffset - Applies to spoke orders within the Hub store. Once these orders have been received by the Spoke store, the offset will no longer apply.

PrepPickupOffset - Applies to orders with prepared items only. The offset is only visible from the prepared item order list.

DeliveryPickupOffset - Applies to delivery orders only. 

Label Template Overrides 

ShopperKit utilizes a default 3"x2" label format for all ShopperKit labels. As access to printers and label media availability and preferences varies from retailer to retailer, we are introducing the ability for client admin users to define label template overrides at both client and store level. The overrides are defined as label and locale specific attributes. To change the label size or layout, simply edit the default label ZPL using your favorite editor and paste the new ZPL as the attribute value for the specific label attribute override. ShopperKit provides locale specific overrides for the following labels:

Check out this article for more information on editing label templates.


  • ShopperKit Classic - Order Type attribute in text templates is not getting set correctly.
  • Hide Customer Credit input when no credits are defined for client instance.
  • ShopperKit Mobile should not prompt for Food Safety Type during Sub or Add when the Food Safety Type of the item is known.
  • ShopperKit Mobile not loading customer details.
  • Prevent users from changing roles and permissions to their own accounts in the Client Portal.
  • Command Center - The hover over tool tip for the unpick exception is incorrectly reporting as POS exception.
  • Client Portal - Unable to define user restrictions from User setup path.