Shopperkit command center login

Command Center – ShopperKit

Command Center

Redirecting to client login system, please wait… Email Email is required. Password Password is required. Login. Forgot password? © ShopperKit 2019 v2.37.

ShopperKit – Client Portal

Login to the support portal. Enter the details below. Remember me on this computer. Forgot your password? Login. Are you an agent? Login here …

Sign into – ShopperKit Support

Build stronger brand loyalty and customer relationships with ShopperKit — the best-in-class fulfillment platform for retail. Get Case Study.

Home | ShopperKit, Inc.

Command Center can be accessed at by using your Admin Portal credentials. Communications. Command Center Communications allows you …

ShopperKit is now part of Applied Data Corporation’s suite of store ops solutions.

July 2018 | Build 3.8.8 – ShopperKit Support

July 2018 | Build 3.8.8 : ShopperKit Support

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 …

Improvements Command Center With this release, we are very excited to announce our newest addition, the ShopperKit Command Center. As your online fulfillment operations continue to grow, the need to have real-time, operational visibility across all of your stores becomes ever more important. While it’s always been possible to look into ShopperKit client application to see real-time order performance within a given store, there hasn’t been anyway to see this data across stores. ShopperKit Analytics does provides roll up data, but that has always been historical. This is where Command Center fits in. Command Center is focused on reporting and analyzing real-time ShopperKit data so that you can keep your operations running as smoothly as possible.   Command Center can be accessed at by using your Admin Portal credentials. Communications Command Center Communications allows you to view and participate in any customer communications that have been initiated by the stores, either within a specific store or across all stores. From the Communications view, you will have access to all of the individual active SMS communications. As new messages come in, they will update in real-time, flashing the individual chat client windows so you know where to look and clicking on a given chat will allow you to participate in that communication directly from the browser. Order Inspector Command Center Order Inspector helps you to answer the question of “How are we doing today?”. By rolling up order fulfillment progress and exception data, you’ll easily be able to quickly see overall order activity and progress across all of your stores as well as which of stores might require some assistance in managing their work load. Inventory Inspector Command Center Inventory Inspector helps you spot and understand potential inventory problems and how they may be impacting your fill rates. The inspector will show you all items that have been ordered and are being picked for a given day, and more importantly, those items that may be experiencing higher than normal rates of Out of Stock or Substitutions.  Basket Size Increase Widget Command Center Basket Size Increase widget allows you to see how well your stores are doing in Add-On items. Starting from the top, you will see how each of your stores stacks up to each other in terms of increased baskets due to add-on items. From here you can then drill into any one store to see which orders have been impacted and by how much. Issues Carryout SMS notifications that originate from a phone number other than the order’s phone number will now correctly route the “We’re on our way” confirmation message to the originating phone number instead of the phone number associated with the order. Order list will no longer infinitely spin when loading list view that contains no orders. Do not allow users to enter Alpha characters or UPCs values greater than 14 chars when subbing or adding items in ShopperKit. Do not allow default weight values from type 2 barcodes to exceed weight thresholds without triggering warning and confirmation step. Force the Picking UI to refresh anytime a quantity exceeded error is encountered. Change the sort or of stores in the client Store list to order stores by name in ascending order.

October 2018 | 4.2.6 Release – ShopperKit Support

October 2018 | 4.2.6 Release : ShopperKit Support

Incorrect Templates appearing in Command Center Hub We have fixed an issue … Corrected issue in ShopperKit Mobile preventing customer order type filter …

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: Event Type Trigger New Order Fires when a new SAME DAY order is received Carryout Here     Fires when a customer texts the word HERE to notify the store of their arrival Carryout Taken     Fires when a store associate TAKES the carryout notification in the client application Lead Time Alert     Fires when ever any of your configure item or order status lead time alerts are triggered. Includes the Name of the Lead Time Rule that triggered the alert. 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 l

June 2021 – ShopperKit Support

June 2021 : ShopperKit Support

Once defined, custom order types may be used as filter criteria in the mobile client or Command Center Order Inspector, as criteria on Lead Time Rules or as …

Planned Release to Production is July 13 FreshIQ Made To Order Integration For the June release, we are very please to announce a a new Prepared Items mode that leverages the robust Made to Order functionality within our sister product, FreshIQ. Now when the “Made to Order” prepared items mode is selected, ShopperKit will create a discrete order in your FreshIQ Made to Order instance via web service interface. Once the order is in FIQ, your service counters will have multiple options by which to prepare the Made to Order items. This can be as simple as preparing from a ticket that is automatically printed from a department located receipt printer, similar to what you’d find in a restaurant kitchen, or by using the dedicate made to order FIQ work flows. Since FIQ already understand the required preparation times for you various items, along with all the preparation steps and customization options, you can be assured that you Service Counters will no longer have to worry about timing or instructions when it comes to preparing these items. To leverage this new feature you must also have a FIQ Made to Order subscription. Please contact or your FIQ account rep for more information. Private Information | GDPR Support In order to better support our EU based and privacy conscious customers, ShopperKit is now introducing Private Information management so that you may control how and when private customer information is displayed and retained within the application. The ShopperKit Private Information management functionality is broken down into three main features. First off is the Private Information profile management page. From this page in the Client Portal you will now be able to determine by Private Information attribute type, one of three behaviors that is required by each unique ShopperKit role. The default option of Display will continue to display the private information attributes as they are today. When Obfuscate is selected, the actual value will be replaced with random character data when presented in the UI. When Hide is selected, the actual value is removed from the UI. The settings on this page only determine how these values are rendered in the UI. They do not influence how data is persisted in the database. The second element to the Private Information management is the ability for Admins to schedule automatic private information data obfuscation via the new ObfuscateHistoricalPIData application attribute. This attribute accepts an integer value that represents the number of days after order completion in which to obfuscate the persisted customer private information. Once the threshold passes, all customer private information data persisted in the database will be replaced with random character data, rendering it useless from an identification perspective. The third and final element of the Private Information management is the ability for third party systems to request obfuscation of private information via a POST to a new web service method by passing in the Customer sourcekey (ID). https:///api/v1/customer/obfuscate/{sourcekey} Client Version number add to API headers With this release we have made a change to the external facing interfaces to include the ShopperKit client version data as part of the HTTP request header. Prevent non-empty containers from being deleted We have fixed an issue that could occur when multiple lead shopper or store manager roles were shopping the same order, where one user would delete a container in their pick session that belonged to the other user shopping the order. This is possible as lead shoppers and above are allowed to see all “On Cart” containers for a given order. Now if a user attempts to delete a non-empty container, they will be presented with an error message indicating that the container can not be deleted. Edits to Customer Management screen is not reflecting We have fixed an issue where when editi

May 2021 – ShopperKit Support

May 2021 : ShopperKit Support

The United States Central Command ( USCENTCOM or CENTCOM) is one of the eleven unified combatant commands of the U.S. Department of Defense. It was established …

Planned Release to Production is May 25 Custom Order Type The custom order type feature allows users to create one or more user defined order types that are subordinate to the primary order types of Pickup or Delivery. Once defined, custom order types may be used as filter criteria in the mobile client or Command Center Order Inspector, as criteria on Lead Time Rules or as exception/selection rules for Auto Assignment rules.  Custom Order Types are defined from the Customer Order Type menu in the Client Portal by providing a name, source key and Icon. The name of the order type is how the order type will appear in any filter or selection criteria. The source key is expected to exactly match the Order:OrderSubTypeId attribute in the order payload and the icon is what will appear as the optional, secondary icon for the order. In practice, Custom Order Types are subordinate to the primary order types of Pickup or Delivery and would be used anytime you may need to further filter order data. As an example, let’s say we have separate team of people that are responsible for managing catering orders. With a Custom Order Type of Catering, you will be able to easily distinguish these orders from the Order list, while also allowing users to set filters in their clients so that they only see catering type orders.  Container Estimate Overrides When using the pre-printed label feature, ShopperKit relies on a rolling 7 day estimate to determine how many items by Food Safety Type will fit in a given container. While this method generally performs well when a store has a robust container order history, this can produce very odd results when launching new stores. With the Estimate overrides you may set a default count as well as Min and Max values by Food Safety Type. The default count value will be used when there is insufficient history to estimate the number of items that may fit in a container of the same Food Safety Type. The Min and Max counts will act as overrides to any system calculated estimates. To set the overrides you will need to define the ContainerEstimateOveride attribute at either the client or store level. Below is an example.  [ { “FoodSafetyTypeName”: “Ambient”, “DefaultCount”: 5 }, { “FoodSafetyTypeName”: “Frozen”, “MinCount”: 2 }, { “FoodSafetyTypeName”: “Cooler”, “MaxCount”: 6 }, { “FoodSafetyTypeName”: “Bulk”, “DefaultCount”: 1, “MinCount”: 1, “MaxCount”: 2 }] Auto-Assignment enhancements The auto-assignment functionality has seen several enhancements with this release. To start with, auto-assignment will now automatically ignore any order that has been previously assigned to a shopper via the Reserve Order option. Along these same lines, we have added a new Filter rule type that will allow you to define explicit exclusion/inclusion rules based on one or more custom order type values. The Limit Rule type has been updated to include total product weight as a limiting factor so as not to overload equipment. The Rank Rule type has also been updated to include the custom order type and Lead Time rule as potential ranking options. When using Lead Time Rule as a rank option, you will select the lead time rule name as the Rank Rule option. If the selected lead time rule is applicable to the order at the time of assignment, then it will be used as ranking criteria. Edit Orders from Order Inspector With this release it is now possible to enable order inspector to allow Managers and admins to either add new items to orders or edit items on an order. Items added to an order in Order Inspector are added differently than they are through the client application. When adding an item to an order in Command Center, the item is added in an unpicked status as though it came down from commerce vs. the handheld where the item is added and picked in a single transaction. Another key difference is that while the client application allows for adding items that do not resolve in the product lookup, you may only add items

Hyvee Huddle Login

shopperkit command center – Luxist – Content Results

Keywords: shopperkit command center login