Build 2.4.6 - 04/10/2017
Due to changes in the security model, this is a mandatory upgrade.
ShopperKit takes security and data security seriously. That is why with this release, we are now requiring that any device that will be used to run the ShopperKit application first be authenticated with a unique Client Password. The client password will be provided to by ShopperKit support. The first time you log into ShopperKit after install or upgrade, you will be prompted to enter the client password along with your username and password. After you have logged in with this value, the client password control will be hidden and you will no longer be required to enter this value. You will receive a Device Authorization instructions document from ShopperKit support that will contain your unique client password.
In addition to the changes in the ShopperKit mobile application, the ShopperKit admin portal has also changed. Previously you required to use your username and password. Since User names may not be unique across all ShopperKit customers, we are now requiring that you log into admin.shopperkit.com using the email address associated to your account.
POS Exception Management
Occasionally, there are problems when attempting to settle against the customer's pre-authorized credit card. While pre-authorization against the estimated order total helps, it is still not uncommon for cards to be declined by the payment gateway service provider due to fraud, over limits or other credit card problems. We have now introduced a few changes to help improve visibility and operational flexibility when it comes to managing these failures.
The first thing you will notice is that orders that have failed to authorize will appear in the order list with a red cash register icon. This icon indicates that ShopperKit received a payment error from the gateway provider and that it needs attention. Orders with an unresolved payment errors will not be eligible for carryout, so you'll want to make sure to correct these as quickly as possible.
To see the actual error message that was returned by the payment gateway, you will need to select the order from the list and navigate to the order details for that order and tap on the red cash register icon.
If the order has a payment error, it will be displayed beneath the ChargeID value and barcode.
How you resolve payment errors will be determined by your operational procedures. You may want to attempt settle the order again in the event the failure was caused by a temporary error on the payment gateway. Provided your ecommerce provider allows it, you may want to instruct the customer to use a different credit card and try again. If you are unable to resolve the issue through either of these, you will then need to manage the exception outside of the system and collect payment direct from the customer. Once you have collected the funds from the customer, you may release the order order from ShopperKit by updating the payment type. To do this, simply select the new payment type from the dropdown and tap the Change Payment Type button. Once the payment type of an order is changed, ShopperKit will send the payment type update back to you ecommerce provider and the order will become eligible for carryout.
You must be a User with a manager role or above to change payment type of an order.
By default, ShopperKit only shows orders that have not been completed and delivered to the customer. ShopperKit does allow you to apply a filter to view orders that have been completed, but that list is limited to a 48 hour window. Now users who are Managers or above will be allowed to bring up orders that have aged off by using the Search Orders function that is access from the menu.
You may search for orders either by Customer name or by order number. Customer name is a concatenated value of First and Last name though you may search for a customer by entering partial values of both first and/or last name. The search is case insensitive and will return all orders that have a matching customer value. You may also search for orders using partial values. I.e. a search for order 153 will bring back every order in the system that start with 153. It's important to understand that the more exact your search criteria, the faster your search will execute.
- Increased timeout settings on ShopperKit analytics so that report requests do not time out before results are returned. (682)
- Refactor POS Exception page to improve performance so that page will not timeout when loading. (687)