October 2018 | 4.2.6 Release

Improvements

Command Center Events

Keeping on top of your fulfillment operations can be a challenge. As things get busy, it can be difficult to keep an eye on everything that is going on. And while you may be doing your best to stay informed, you really need a way to make sure your entire team stays on the same page. This is where Command Center Events comes in. Command Center Events is a real time event board. As certain key events in your stores workflow occur, they will be automatically broadcasted to the event board. New events will always appear at the top of the list and they will describe the event type, the order number, customer and pickup time associated with the event, as well as the time the event was generated. 

To minimize the amount of noise that you may see, only the following event types are currently being fed to Command Center Events:

If not all of these events are of interest to you, you can disable or enable event types as desired through the event filter options. From here you can also choose the number of events to allow to be displayed in the in the list. Once the number of events surpases the number, the oldest events will drop from the list.

While Command Center Events displays in browser, it is intended to be displayed on as large of a display as possible, which is why we've included a Full Screen button in the upper right hand corner.

Event WebHooks

Piggybacking on the Command Center Events is the ability to broadcast these events outside of the ShopperKit world via WebHooks. WebHooks provide an easy and powerful way to expose ShopperKit events to the outside world. With WebHooks you can now configure ShopperKit to broadcast events to any number of external services and or devices. Common use cases could be broadcasting Carryout Events to an IOT enabled flashing light, or sending New Same Day order events to a slack channel. Your only limit here is your imagination.

Webhooks are configured by store, as each store may have different devices or services they may want to publish to. To create a new webhook, you will need to start by generating a CATCH Url from the service that ShopperKit will publish the event to. With that in hand, you will create a new WebHook store attribute in the Store management screen in Admin Portal. You can define as many webhooks for a given store as you would like.

While the content of each event type will vary, all ShopperKit WebHook events will adhere to the same schema as shown below.

Sample WebHook payload:

{
  "ccEventId": 200289,
  "clientId": 5,
  "storeId": 30,
  "eventTypeId": 1,
  "eventTypeName": "CCEventOrderCreated",
  "data": "{"orderId":360509,
        "orderSourceKey":"9700",
        "promiseTime":"2018-10-31T18:00:00-04:00",
        "updatedByUserId":"0651c944-0ddd-4472-bf2c-60d01084ebde",
        "customerName":"Steve Paro"}",
  "eventDateTime": "2018-11-01T21:08:28.0450513+00:00",
  "summary": "New Order Received 9700 for Steve Paro"
}

Command Center Inspectors Excel Export

With this release, we have upgraded the Command Center Order and Inventory inspectors to include the ability to export inspector data to excel. Even if a given inspectors data spans multiple pages, the excel export will include all data. Due to the way the inspectors load data, you will only be able to export the data for a single store. If you need to gather data across stores, you will need to export for each store separately. Exporting at the Client level will only export the aggregate data displayed at that level. 

Picking Gift cards

As the holiday season rapidly approaches, some of our ShopperKit customers have expressed interest in the ability to be able to add gift cards to their item assortments. To facilitate this, ShopperKit has added new functionality that will allow you to shop for gift cards just as you would any other item. To use this, you will setup gift card items as normal items online, along with their UPC. Then to pick the gift card in ShopperKit, you will scan the 30 char code 128 gift card barcode. ShopperKit will strip out the UPC value from the gift card to validate that you are picking the correct item, but it will save the full gift card barcode value so that the card may be activated when the completed order is sent to POS. To use this, you will need to make sure that your scanners are configured to scan Code 128 barcodes, which they should be unless you've disabled this.

Display SKU or UPC

It is now possible to configure ShopperKit to display the SKU value in the Shopping flow instead of the UPC value that it has always been displaying. To Configure ShopperKit to show the SKU value, you will need to set the ShowSKUInsteadOfUPC attribute to True. When this attribute is not defined or the value is False, UPC will be shown instead. Regardless of the selected display option, products will still be picked by scanning or entering the UPC or PLU.

Tabular Reporting | Daily Transactions by Customer Report

With this release, we have added a new Reports menu to Admin Portal. The Reports menu, looks and behaves similar to the Analytics menu, but instead of presenting data visualizations, Reports shows data in a tabular format that can easily be downloaded and saved to Excel. The Reports menu utilizes the same data warehouse as analytics as well as the same date range filters. The first report that we have added here is the Daily Transactions by Customer Report. This report can be queried by date range and is meant to be an order accounting reconciliation tool, showing Estimated and Actual order totals, along with Payment Type and Customer info by order. Over the coming weeks we will be moving many of our existing email ad-hoc reports to this new reports feature. 

UPH Calculation

Previously ShopperKit would calculate Shoppers UPH based on an assumed workday. To do this, we would calculate the total time between the users first pick of the day and their last pick, divided by the number of units picked during that time. Obviously, as none of your shoppers spend their entire day picking items, this has proven to be less accurate than we would hope. To improve the UPH accuracy, we are now introducing the concept of Recorded Pick Sessions. Now whenever a user picks an item into a container, ShopperKit will test to see if that user already has an open container that was created on that day, that contains at least one item. If the user does not have an active container, then a new pick session is started. This pick session will remain open until the user stages their last active container, or they log off the system. ShopperKit will now use the sum of time spent in pick sessions when calculating UPH for the user.

Issues

• Several fixes to Command Center Inventory and Order Inspectors to improve accuracy.
• Make the Order Inspector the default view for Command Center Orders.
• Fixed issue that prevented stores from being deleted through Admin Portal.
• Fixed issue that prevented Lead Time Alerts from being deleted once they had been triggered.
• Added missing timestamps to Command Center Communications.
• Corrected Shelf set up so that Prep Item mode will inherit correctly from the Section.
• Allow price value from Type 2 embedded barcodes to update product total that is sent back to online.
• Fully implemented Honeywell Voyager SDK to resolve pairing issues on iOS with Honeywell Voyager Scanner.
• Certified ShopperKit 4.1.9 and forward on iOS 12.