[NEW] Menu Models

Article author
Nick Renard
  • Updated

Background Information

Managing a sports & entertainment venue comes with its unique challenges, especially when configuring various locations and menus. Misconfigurations can lead to operational hiccups and, worse, dissatisfied fans. The new Menu Models feature aims to simplify this complexity. With a single selection, operators can now apply a standard set of configurations, streamlining operations and reducing the risk of errors.

So, what does this mean exactly? It means that operators/managers will not need to configure menu settings in order for their locations to function in a specific way. Menu Models can be seen as a collection of settings and values that automatically apply to a menu. This exponentially reduces configuration errors and standardizes the functionality of menus. 

For example, configuring a menu to the [Mobile] Pickup Menu Model will ensure the order is placed into the processing order state by default, the usage type on the menu is set to pickup, order cards are created automatically with dynamic verbiage, and tax settings are applied appropriately. There is no need to worry if the menu will function as intended. Every menu with the [Mobile] Pickup Menu Model will operate in the exact same way throughout all of VenueNext.

Prerequisites:

  • Canopy 2.0 -> Menu Manager Access
  • Item-level tax rates and rules (Venue-level taxation is not supported)
    • Tax rates must be defined on every Item.
    • Tax rule (add-on, inclusive, or non-taxable) must be defined on every Item.
  • Full-venue Shift4 processing (FreedomPay & Braintree are unsupported)

Default Global Settings on all Menu Models:

All of the global settings below are unable to be edited to ensure global standardization across VenueNext menus.

  • Display Categories are used to group like items on POS/Kiosk/Mobile
  • Reporting Categories are used for DataNow
  • Item-level taxation rates and rules
  • Personalized order cards are created for each Menu Model
  • Order submission state is defined per Menu Model

Configure Menu Models

When either adding a new menu or editing an existing menu in a Revenue Center, Menu Models will now be the sole option going forward.

General Rules:

  • Adding a new menu in Canopy 2.0 requires a Menu Model selection.
  • Editing an existing menu in Canopy 2.0 that is currently utilizing a legacy Service Type may be upgraded to a Menu Model.
  • A Menu may switch between a Menu Model to another Menu Model, but not back to a legacy Service Type

After saving the new or existing menu, the collection of settings for that specific Menu Model will apply immediately. You will not need to manually adjust the Skip POS Submission State setting or any other related settings. They have already been set via the Menu Model selection.

High-Level Supported Features

Below is a high-level matrix of supported features for each Menu Model. This will aid in selecting a comparable model for your existing menus. 

 

Jump to Full Definitions:

 

Mobile Menu Models

[Mobile] Pickup

The [Mobile] Pickup Menu Model is used for the traditional pickup menu. When a guest places an order, it will automatically be placed in the processing order state and appear on Xpedite. When the order is ready for pickup, the expo will mark the order as ready which will update the guest's order confirmation screen on their personal device. Upon completion, the payment for the order is settled.

High-Level Service Flow

  1. A guest places a Mobile Pickup order.
  2. The order is placed into the processing state and appears on Xpedite.
  3. The order is prepared by staff. 
  4. The order is marked as ready by the expo. 
  5. The guest's order confirmation screen is updated to tell them to pick up their order.
  6. The guest arrives at the location and picks up their order.
  7. The expo completes the order on Xpedite.
  8. The order payment is settled.
  9. The guest's order confirmation screen updates to a completed status. 

 

[Mobile] Delivery

The [Mobile] Delivery Menu Model is used for the traditional inseat or table delivery locations. When a guest places an order, it will automatically be placed in the processing order state and appear on Xpedite. When the order is ready for delivery, the expo will mark the order as out for delivery which will update the guest's order confirmation screen on their personal device. Upon completion, the payment for the order is settled.

High-Level Service Flow

  1. A guest places a Mobile Delivery order.
  2. The order is placed into the processing state and appears on Xpedite.
  3. The order is prepared by staff. 
  4. The order is marked as ready by the expo. 
  5. The guest's order confirmation screen is updated to tell them their order is out for delivery.
  6. The runner arrives at the guest's location and delivers their order.
  7. The expo completes the order on Xpedite.
  8. The order payment is settled.
  9. 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 will automatically be placed in the completed order state and settled immediately. When the guest arrives at the venue, they will make their way to the pickup location. 

High-Level Service Flow

  1. A guest places a Mobile Pre-Order Pickup order for a scheduled event.
  2. The order is placed into the completed state and settled immediately.
  3. A manager runs a pre-order report from DataNow for staff.
  4. The order is prepared by staff on the day of the scheduled event. 
  5. 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 will automatically be placed in the completed order state and settled immediately. When the guest arrives at the venue, they will make their way to their seat, table, or suite. A runner will deliver the order at a given time.

High-Level Service Flow

  1. A guest places a Mobile Pre-Order Delivery order for a scheduled event.
  2. The order is placed into the completed state and settled immediately.
  3. A manager runs a pre-order report from DataNow for staff.
  4. The order is prepared by staff on the day of the scheduled event. 
  5. The guest arrives at their seat, table, or suite.
  6. A runner will deliver the order at a given time.

 

[Mobile] Self Checkout

The [Mobile] Self Checkout Menu Model is used when guests can place orders by scanning product barcodes on their personal device. When the guest places an order, it will automatically be placed in the completed order state and settled immediately. The guest can leave the area without any interaction with a cashier.

High-Level Service Flow

  1. A guest enters a Self Checkout location and scans product barcodes on their personal device.
  2. The guest submits the order with their preferred payment method.
  3. The order is placed into the completed state and settled immediately.
  4. The guest leaves the Self Checkout location with the items.

 

[Mobile] QuickPay

The [Mobile] Self Checkout 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 hands the guest the items on the confirmation screen and the guest can return to the event.

High-Level Service Flow

  1. A guest approaches a hawker to scan a QR code on their personal device.
  2. The guest submits the order with their preferred payment method.
  3. The order is placed into the completed state and settled immediately.
  4. The guest presents the confirmation screen to the hawker and receives their items.
  5. The guest returns to the event.

 

POS Menu Models

[POS QS] Belly Up

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

High-Level Service Flow

  1. A guest walks up to a cashier at a concession stand, portable, or bar and places their order.
  2. The guest pays for their order immediately.
  3. The order is placed into the completed state and settled immediately.
  4. The guest receives their order from the cashier.
  5. The guest returns to the event.

 

[POS QS] Order-Pay-Fulfill

The [POS QS] Order-Pay-Fulfill Menu Model is used for the traditional concessions service flow where the guest places and pays for their order with the cashier, and picks up their order from another location. This Menu Model supports Cloud Kitchen Printing.

High-Level Service Flow

  1. A guest walks up to a cashier at a concession stand, portable, or bar and places their order.
  2. The guest pays for their order immediately.
  3. The order is placed into the completed state and settled immediately.
  4. The guest receives their order from the pickup area when ready.
  5. 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 need to keep a tab open. This is more commonly used in premium clubs, bars, and table service. This Menu Model supports Cloud Kitchen Printing.

High-Level Service Flow

  1. A guest places their order with a server or bartender.
  2. The server or bartender either opens a tab or closes the order immediately.
  3. The order is routed through kitchen/bar printers.
  4. 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

  1. A guest walks up to a kiosk at a concession stand, portable, or bar and places their order.
  2. The guest pays for their order immediately.
  3. The order is placed into the completed state and settled immediately.
  4. A chit will print from the USB receipt printer for fulfillment (if needed).
  5. The guest receives their order from the cashier.
  6. 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

  1. A guest walks up to a kiosk at a concession stand, portable, or bar and places their order.
  2. The guest pays for their order immediately.
  3. The order is placed into the processing state, settles immediately, and prints at an Xpedite printer.
  4. The guest receives their order from the pickup area when ready.
  5. The expo marks the order as complete.
  6. The guest returns to the event.

 

Autonomous Menu Models

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

The [Autonomous] Menu Models are intended to be used with Zippin' and Amazon Just Walk Out technologies. These models require additional setup by the VenueNext team. If your venue has already been set up with either of these technologies, you may select one of the Menu Models to quickly add a new Revenue Center and Menu. 

 

If you would like additional assistance, please reach out to us at help@venuenext.com.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.