Welcome
Login  Sign up

September 2018 | 4.1.9 Release

Improvements

ShopperKit available on iOS

We are very pleased to announce that ShopperKit is now available for the iOS platform through Apple's VPP for Business. Customers who are interested in running ShopperKit on iOS devices will first need to enroll for VPP with Apple. Once you have enrolled, you will need to supply the email associated to your VPP account to ShopperKit in order to be able to access the ShopperKit app from the VPP App Store. While there is no difference in functionality between the two platforms, there are some additional hardware restrictions with Apple devices. At the moment, the Honeywell  Voyager 1602G is the only iOS supported scanner and label printers must either be Low Energy Bluetooth or they must explicitly support Apple MFI. 

Delivery Partner Integrations

As anyone who has spent any time talking with us will know, We at ShopperKit are very proud of our API first architecture. We built ShopperKit so that it could easily plug into different systems and providers. Integrations make us happy, and it seems that this release brings with it a reason to celebrate as we pleased to announce two new Delivery Partner integration options for you to choose from.

The first of the Delivery Partner integration options is with Shipt. Using the Shipt Envoy interface, ShopperKit can now create delivery requests with Shipt for your delivery orders and track them through to completion based on final delivery notification from the Shipt driver. With the Shipt Envoy integration enabled at a store, ShopperKit will automatically create a delivery in Shipt for every delivery order, as soon as the order is received. Then as the order is picked and staged, it will be carried out to the Shipt driver. Shipt Delivery orders will not require signature capture on the order summary, and assuming the delivery queue feature has been enabled, will remain in the delivery queue until final confirmation has been received from Shipt. To leverage this integration, you will need to have an account established with Shipt, and you will need to configure the store with the Endpoint URL and Authorization Token provided to you by Shipt.

The second Delivery Partner integration is a little more old-school. As some retailers still rely on services from traditional courier services, ShopperKit now makes it possible to automatically communicate delivery order information with these partners via CSV file. By configuring the Generic option, you will be required to provide the email address where the delivery file for that store should be sent. In addition to email address, you will also need to select how you want the file to be delivered. The default option of on-receipt will send a new file for each delivery order received. If you would like to limit the amount of emails your delivery partners receive you configure the digest mode option. With this option enabled you will specify a time value in minutes before Promise Time to send the email. When the file and email is sent, all orders that are due at a set promise time will be included in the file.

Click here to download an example of the generic delivery CSV file.

Prepared Items Lite

While ShopperKit has long sought to solve the service counter problem through our Prepared Items feature, it has become clear over time that not all retailers are ready or able to equip their service counter departments with the hardware required to fully take advantage of the feature. To aid with these retailers, we are introducing Prepared Items Lite. Prepared Items Lite leverages the existing Prepared Items setup functionality that allows ShopperKit to understand and visually distinguish which orders contain prepared items, but instead of managing these items through a dedicated workflow, you will be able to print labels that contain all of the preparation instructions required for the order.

When setting up your Merchandise Sections or Shelves for prepared items, you will now notice a new option has been added.

After enabling Prepared Items mode, you will be required to select a Prep Option Type; regular for full featured and Lite for Prepared Items Lite. 

With Prepared Items Lite enabled, orders that are flagged as containing prepared Items will display in the order list with the Closed Box Prepared Items icon. To generate the Prepared Item Lite labels, you will drill into the order details of the order and tap the new Prepared Items Lite icon . This icon will only appear when there are Prepared Item Lite items on the order, and will print labels group by each Prepared Item Lite section or department.

A Prepared Item Lite label will print for each item that requires preparation. The label contains the Customer Name, Promise Time, Order Number, Department Name, The SKU that needs to be prepared, the Product Description, Unit Quantity, Weight and any item customization comments that the customer provided.

With everything for an order printed, the shopper will deliver the labels to the various departments for prep. Once all prep has been completed, the shopper will complete the pick as they normally would by scanning the individual items. This is a departure from the full Prepare Items feature where you would complete the pick by scanning the prepared item label.

It is worth mentioning here that Prepared Item Lite can be used in conjunction with regular Prepared Items feature as well. 

System Messaging integrated into Chat Client

Based on feedback, all customer SMS activity will now be recorded and visible in the ShopperKit chat clients. In the past you would only be able to see the user initiated SMS discussions, but with this release we have also added all system generated communications to the thread history. This includes the automated order notification texts that your customers receive as well as the Carryout arrival notification when customers send the HERE keyword. This change also applies to the Command Center Communications page as well.

Order Summary and Detail Exceptions Visibility 

In an effort to make it easier to spot and communicate with customers regarding order fulfillment exceptions, we have made a few changes to the order in which the Order Details and Order Summary views appear. With this release, you will notice that order lines with exceptions will appear at the top of the lists. Shorted items will appear first, followed by Substituted items, Added items and finally the remaining order items.

User Defined Client App timeout

Another simple one that is bound to please a few folks is we have now made the Idle logoff user definable. In case it's not clear, the idle logoff is the amount of time that the ShopperKit can be idle before it forces the user to log back in. In the past, this has been set to a 60 minute default. While the default remains the same, you may now override this by setting the 

ClientIdleLogoffTimeoutInSeconds in the App Attributes settings. As the attribute name implies, the value must be in seconds.

Label Changes

In an effort to improve readability and scannability you will notice a few minor changes to both the container and prepared item labels. Since these 2x3 labels have a fixed amount of characters that can print before running off the edge, we have changed the order in which we print the customer names. Going forward, customer name will print as Last Name, First Name. Now if anything gets cut off, it will very likely only be the tail end of the customers first name. 

The barcode on the prepared item label has been repositioned to the left side of the label and appears before any of the text. This allows for the barcode to be a little large and will prevent text characters from interfering with the barcode.


Issues

  • Fixed problem where Images where disappearing from chat client, causing users to accidently send multiple images.
  • Fixed issue that prevented containers from being staged correctly after the Food Safety Type name value had been changed.
  • Fixed issue that would cause updates to Store attributes in the admin portal to fail.
  • Fixed issue that incorrectly flagged an order as Changed Requiring update through Shipt Interface.