Menu Models for SkyTab Venue

Article author
Jaime Baker
  • Updated

Description:
Explore the different menu models available for mobile, POS, kiosk, and autonomous service flows. This article outlines how each model supports unique ordering, payment, and fulfillment experiences to meet a variety of venue needs.

 


 

Mobile Menu Models

[Mobile] Pickup

The [Mobile] Pickup menu model is used for the traditional pickup menu. When a guest places an order, it is automatically placed in the processing order state and appears on Xpedite. When the order is ready for pickup, the expo marks the order as ready, which updates the guest’s order confirmation screen on their personal device. Upon completion, the payment for the order is settled.

High-Level Service Flow

  • A guest places a Mobile Pickup order.

  • The order is placed into the processing state and appears on Xpedite.

  • The order is prepared by staff.

  • The order is marked as ready by the expo.

  • The guest’s order confirmation screen is updated to tell them to pick up their order.

  • The guest arrives at the location and picks up their order.

  • The expo completes the order on Xpedite.

  • The order payment is settled.

  • The guest’s order confirmation screen updates to a completed status.


[Mobile] Delivery

The [Mobile] Delivery menu model is used for traditional in-seat or table delivery locations. When a guest places an order, it is automatically placed in the processing order state and appears on Xpedite. When the order is ready for delivery, the expo marks the order as out for delivery, which updates the guest’s order confirmation screen on their personal device. Upon completion, the payment for the order is settled.

High-Level Service Flow

  • A guest places a Mobile Delivery order.

  • The order is placed into the processing state and appears on Xpedite.

  • The order is prepared by staff.

  • The order is marked as ready by the expo.

  • The guest’s order confirmation screen is updated to tell them their order is out for delivery.

  • The runner arrives at the guest’s location and delivers their order.

  • The expo completes the order on Xpedite.

  • The order payment is settled.

  • The guest’s order confirmation screen updates to a completed status.


[Mobile] Pre-Order Pickup

The [Mobile] Pre-Order Pickup menu model is used when guests can order several days before a scheduled event. When a guest places a pre-order, it is automatically placed in the completed order state and settled immediately. When the guest arrives at the venue, they make their way to the pickup location.

High-Level Service Flow

  • A guest places a Mobile Pre-Order Pickup order for a scheduled event.

  • The order is placed into the completed state and settled immediately.

  • A manager runs a pre-order report from DataNow for staff.

  • The order is prepared by staff on the day of the scheduled event.

  • The guest arrives at the location and picks up their order.


[Mobile] Pre-Order Delivery

The [Mobile] Pre-Order Delivery menu model is used when guests can order several days before a scheduled event. When a guest places a pre-order, it is automatically placed in the completed order state and settled immediately. When the guest arrives at the venue, they make their way to their seat, table, or suite. A runner delivers the order at a given time.

High-Level Service Flow

  • A guest places a Mobile Pre-Order Delivery order for a scheduled event.

  • The order is placed into the completed state and settled immediately.

  • A manager runs a pre-order report from DataNow for staff.

  • The order is prepared by staff on the day of the scheduled event.

  • The guest arrives at their seat, table, or suite.

  • A runner delivers the order at a given time.


[Mobile] Self Checkout

The [Mobile] Self Checkout menu model is used when guests place orders by scanning product barcodes on their personal device. When the guest places an order, it is automatically placed in the completed order state and settled immediately. The guest may leave the area without interacting with a cashier.

High-Level Service Flow

  • A guest enters a Self Checkout location and scans product barcodes on their personal device.

  • The guest submits the order with their preferred payment method.

  • The order is placed into the completed state and settled immediately.

  • The guest leaves the Self Checkout location with the items.


[Mobile] QuickPay

The [Mobile] QuickPay menu model is generally used in hawking service flows. The guest approaches a hawker and scans a QR code, which navigates them to a hidden menu. They select their item, submit the order, and present the order confirmation screen to the hawker. The hawker provides the items shown on the confirmation screen, and the guest can return to the event.

High-Level Service Flow

  • A guest approaches a hawker and scans a QR code on their personal device.

  • The guest submits the order with their preferred payment method.

  • The order is placed into the completed state and settled immediately.

  • The guest presents the confirmation screen to the hawker and receives their items.

  • The guest returns to the event.


POS Menu Models

[POS QS] Belly Up

The [POS QS] Belly Up menu model is used for traditional concessions service, where the guest places, pays for, and receives their order from the cashier.

High-Level Service Flow

  • A guest walks up to a cashier at a concession stand, portable, or bar and places their order.

  • The guest pays for their order immediately.

  • The order is placed into the completed state and settled immediately.

  • The guest receives their order from the cashier.

  • The guest returns to the event.


[POS QS] Order-Pay-Fulfill

The [POS QS] Order-Pay-Fulfill menu model is used for traditional concessions service, where the guest places and pays for their order with the cashier, then picks up their order from another location. This menu model supports cloud kitchen printing.

High-Level Service Flow

  • A guest walks up to a cashier at a concession stand, portable, or bar and places their order.

  • The guest pays for their order immediately.

  • The order is placed into the completed state and settled immediately.

  • The guest receives their order from the pickup area when ready.

  • The guest returns to the event.


[POS FS] Wait Staff

The [POS FS] Wait Staff menu model is used for service flows where the guest may keep a tab open. This model is more commonly used in premium clubs, bars, and table service. It supports cloud kitchen printing.

High-Level Service Flow

  • A guest places their order with a server or bartender.

  • The server or bartender either opens a tab or closes the order immediately.

  • The order is routed through kitchen or bar printers.

  • A runner delivers the order to the guest.


Kiosk Menu Models

[Kiosk] Belly Up

The [Kiosk] Belly Up menu model is used for the self-service flow where the guest places and pays for their order at the kiosk, then receives their order from the cashier.

High-Level Service Flow

  • A guest walks up to a kiosk at a concession stand, portable, or bar and places their order.

  • The guest pays for their order immediately.

  • The order is placed into the completed state and settled immediately.

  • The guest receives their order from the expo.

  • The guest returns to the event.


[Kiosk] Order-Pay-Fulfill

The [Kiosk] Order-Pay-Fulfill menu model is used for the self-service flow where the guest places and pays for their order at the kiosk, then walks over to the pickup area to receive their order.

High-Level Service Flow

  • A guest walks up to a kiosk at a concession stand, portable, or bar and places their order.

  • The guest pays for their order immediately.

  • The order is placed into the completed state, settles immediately, and prints at a cloud kitchen printer.

  • The guest receives their order from the pickup area when ready.

  • The guest returns to the event.


Autonomous Menu Models

[Autonomous] Zippin and [Autonomous] Amazon Just Walk Out

The [Autonomous] menu models are used with Zippin and Amazon Just Walk Out technologies. These models require additional setup by the VenueNext team. If the venue is already set up with either of these technologies, one of the menu models can be selected to quickly add a new revenue center and menu.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.