The VenueNext application - now branded as SkyTab - allows shoppers to shop at Zippin-powered stores by scanning a QR code at the store entrance.
Shopper experience
Shopper scans the VenueNext QR code at the QR scanner at the entry.
Zippin calls VenueNext endpoint to authorize the code. VenueNext returns “Allow” or “Deny” decision. If VenueNext allows the user to enter, it sends a user-token.
For a successful authorization by VenueNext, Zippin opens the turnstile.
Shoppers shops and leaves the store.
Zippin builds the cart (user-token and items) and submits it to the VenueNext endpoint.
VenueNext applies pricing, taxes, promotions, bills the shopper, and sends the receipt.
VenueNext codes do not auto-refresh and may expire before they are scanned. Shopper is required to refresh the app to get the new code. Retailers and VenueNext are responsible for installing clear signage in the store to guide shoppers on how to refresh their QR code.
-
QR code validation is done by calling the VenueNext endpoint.
If store network is down, shoppers using VenueNext codes cannot enter.
Turnstile opening may be delayed because of network issues or issues in VenueNext API endpoint.
VenueNext user-tokens (aka ‘nonce’) are set to expire in 7 days as per VenueNext support ticket 14310 and communicated to Zippin by Shift4.
- The receipt is not available in the Zippin receipt microsite.
Tip - Does your site offer mobile orders using SkyTab (VenueNext)?
If so, the orders for Zippin-powered stores should not be closed when this order window ends. Zippin-locations continue to submit carts hours after the event ends. Closing the orders prematurely may lead to rejected sales.
Billing and Promotions
Typically, a store allows multiple entry & payment methods. For example, a store may allow VenueNext codes as well as physical card readers managed by Zippin.
Zippin builds the cart for all shoppers.
For shoppers using VenueNext codes to enter the store, Zippin passes the cart to VenueNext. VenueNext applies the correct prices, taxes, discounts to compute the final amount and charge the shopper. VenueNext is responsible for the receipts and handling any billing related disputes.
For shoppers using payment methods controlled by Zippin, e.g. Zippin Shopper App or credit card readers; Zippin applies the correct prices, taxes, discounts to compute the final amount and charge the shopper. Zippin is responsible for the receipts and handling any billing related disputes.
If retailer wants to run any promotions for all shoppers in the store, they have to be configured in both the systems - VenueNext and Zippin.
Catalog
Retailer is responsible for keeping SKUs (including price and tax) in sync between Zippin and VenueNext systems.
If the item in the cart is not in the VenueNext system, billing fails. Retailer should create the missing SKU in the VenueNext system and reach out to Zippin support to have the cart submitted again.
Reporting
To see all sales for the store, retailer should combine the sales report from Zippin and VenueNext.
Zippin report shows only the amount billed by Zippin, however item and cart level reports include all carts and items.
Q: Retailer API error “Sku not found: …“ as in this screenshot. What should I do?
A: It is retailer’s responsibility to keep SKUs in sync between Zippin and VenueNext. This error message is coming from VenueNext API. As the message says “Sku not found: 4061”, this error occurred because VenueNext does not have sku 4061 in their system. Request retailer to report the issue to help@venuenext.com and ensure all SKUs are in sync.
Refunds
The Orders Dashboard < Refunds self-service feature is not part of the SkyTab Venue integration. SkyTab Venue transactions are to be refunded from SkyTab Venue.
Signage
VenueNext and retailers are responsible for creating and installing appropriate signage to guide shoppers.
Signage should guide shoppers on:
How to enter the store?
How to access receipts?
How to seek support for receipt disputes and refunds?
Limitations:
VenueNext accepts one shopping cart per user token.
In rare situations, Zippin creates multiple carts for the same shopping session to account for any items missed in the initial cart. These carts are submitted to the Venuenext. If VenueNext cannot charge for additional carts, it results in lost revenue for retailer.
Here are a few examples of when multiple carts are created for the same shopping session.
Purchase events from third-party systems e.g. coffee-dispensing events from DraftServ. System accounts for delays, however, if Zippin receives a purchase event after the cart has been submitted to the VenueNext, it creates another cart and submits again.
Cart corrections. In rare cases, if items are missed in the original cart, Zippin creates an additional cart and send it to VenueNext for billing to ensure all items are accounted for.
Shopper dispute and refund requests process
Zippin Support retailer-support@getzippin.com
VenueNext Support help@venuenext.com
-
Requests should be routed to Zippin or VenueNext as per the area of responsibility.
All cart disputes are investigated by Zippin. For example, extra, missing, or incorrect items in the cart.
All billing disputes for shoppers using VenueNext codes are handled by VenueNext.
All billing disputes for shoppers using Zippin controlled payment methods are handled by Zippin.