Use Concurrent Sales Events in Canopy Menu Manager

Description: Learn how to configure and manage Concurrent Sales Events in Canopy, including scheduling multiple events on the same day, assigning Revenue Centers, enabling mobile pre-ordering, and understanding how event attribution affects DataNow reporting.

Concurrent Sales Events expand how venues can schedule and report on events in Canopy. Unlike the previous model, which supported a single event per day, venues can now configure multiple Sales Events on the same day, including events that run at the same time in different areas of the venue.

The feature also supports new DataNow reporting that uses more precise Sales Event attribution to better separate and report activity across multiple events.

This is especially useful for venues hosting a main event alongside premium, private, conference, or other experiences operating from separate Revenue Centers.

How Concurrent Sales Events work

A Sales Event defines when an event operates and which areas of the venue participate in it.

When creating a Sales Event, you can configure:

• Internal Name: The internal identifier used to distinguish the event in Canopy.
• Display Name: The customer-facing or operational name of the event where applicable.
• Start Date & Time: When the Sales Event begins.
• End Date & Time: When the Sales Event ends.
• Revenue Centers: The areas of the venue associated with the event.
• Price Level: An optional selection used to categorize the Sales Event by event type. Will change pricing in a future release.
• Allow Mobile Pre-Ordering: Determines whether eligible mobile ordering menus can accept pre-orders for the event.

Event times are evaluated using the venue's configured time zone.

Revenue Center assignments

Revenue Centers determine which parts of the venue belong to a Sales Event.

For example, a venue could configure:

• Main Concert — Main Concourse Revenue Centers
• Premium Club Event — Club Revenue Centers
• Private Suite Event — Selected Suite Revenue Centers

All three events can take place at the same time because they operate from different Revenue Centers.

A Revenue Center cannot be assigned to multiple conflicting Revenue Center-scoped events covering the same time period. Canopy helps prevent configurations that would create an ambiguous event assignment. 

Venue-wide Sales Events

Leaving Revenue Centers unassigned creates a venue-wide Sales Event.

Use a venue-wide event when the same event should apply broadly across the venue rather than only to specific Revenue Centers.

Venue-wide events can coexist with appropriately scoped Revenue Center events. However, two venue-wide events should not be scheduled for overlapping time periods.

Concurrent scheduling

Concurrent events are designed around two dimensions:

Time + Location

Two Sales Events may occur at the same time when their applicable venue areas do not create a scheduling conflict.

For example:

These events can run concurrently because they are assigned to different areas.

By contrast, two events attempting to use the same Revenue Center during the same period create a conflict and should be scheduled differently or assigned to different Revenue Centers.

Event status

Canopy automatically evaluates the event status according to its configured schedule.

An event moves through its lifecycle as its start and end times are reached, allowing Canopy and connected ordering experiences to determine which event is currently applicable.

Accurate start and end times are important because they affect:

• Revenue Center availability
• Event selection
• Transaction attribution
• Reporting
• Mobile pre-ordering
• Other event-aware venue functionality

When editing an event, always verify both the date and time before saving.

Price Levels

Today, Price Levels continue to be managed venue-wide rather than by individual Sales Event. Venue-wide Price Levels can be configured and changed in Venue Settings.

Selecting a Price Level on a Sales Event does not currently change pricing for that event. Instead, the selection categorizes the Sales Event by an event type, which can be used to identify and distinguish different types of events.

Support for configuring and applying separate Price Levels to individual Sales Events is planned for a future release.

Mobile pre-ordering

Concurrent Sales Events can also support mobile pre-ordering.

When Allow Mobile Pre-Ordering is enabled, an eligible future Sales Event can be made available to guests through supported mobile ordering experiences.

The Revenue Center must also have the appropriate pre-order menu configuration. Enabling pre-ordering on the Sales Event does not by itself create a pre-order menu.

A typical configuration requires:

1. A future Sales Event.
2. The appropriate Revenue Center assignment.
3. Allow Mobile Pre-Ordering enabled.
4. A compatible pre-order pickup or delivery menu for the Revenue Center.
5. The event to fall within the venue's supported advance ordering period.

If an event should only become available on the same day of the event, leave mobile pre-ordering disabled.

Orders, reporting, and event attribution

When an order is placed while a Sales Event is active, Canopy associates the transaction with the applicable Sales Event based on the event schedule and Revenue Center.

This allows transactions from concurrent events to remain separated even when the events occur at the same venue and at the same time.

For example:

• Orders from Main Concourse Revenue Centers can be attributed to the main event.
• Orders from a Premium Club Revenue Center can be attributed to the club event.
• Reporting can distinguish the activity associated with each Sales Event.

This more precise event attribution also supports DataNow reporting, making it easier to review performance across multiple events that occur on the same day or at the same time. This report can be found in: 

• DataNow -> Dashboard -> Day over Day -> Event over Event tab

The Sales Event associated with an order may also be displayed when reviewing supported order details.

Accurate Revenue Center assignments are therefore important not only for event operation, but also for downstream reporting.

Editing and deleting Sales Events

Exercise additional care when changing an event after operations have begun.

Changes to dates, times, Revenue Centers, or other event settings can affect which event future transactions are associated with.

Canopy may display additional warnings or restrictions depending on the status of the event.

As a best practice:

• Make configuration changes before the event starts whenever possible.
• Review Revenue Center assignments before saving.
• Avoid deleting events that have already processed transactions unless there is a clear operational reason to do so.
• Retain completed events to preserve historical event and reporting context.

Existing or legacy Sales Events

Sales Events created under the previous event model are treated as legacy Sales Events.

Legacy events retain their original behavior rather than automatically becoming Concurrent Sales Events. In particular, they are not automatically converted into Revenue Center-scoped events simply because new Concurrent Sales Events exist.

Legacy events are also excluded from the standard Concurrent Sales Event overlap evaluation.

For venues transitioning to Concurrent Sales Events, the recommended approach is to allow existing legacy events to complete and create new events using the Concurrent Sales Events model.

Avoid intentionally mixing large numbers of legacy and concurrent configurations for future operations when the same result can be achieved entirely with new Concurrent Sales Events.

Use case 1: Two events happening at the same venue

Scenario

A large arena is hosting a basketball game while a separate corporate reception takes place in a premium club.

The basketball game uses:

• Main Concourse
• Upper Concourse
• Food Hall

The corporate reception uses:

• Premium Club East
• Premium Club Bar

Both events operate from 6:00 PM to 9:00 PM.

Recommended configuration

Create two separate Sales Events:

Basketball Game

• Start: 6:00 PM
• End: Appropriate post-event time
• Revenue Centers: Main Concourse, Upper Concourse, Food Hall

Corporate Reception

• Start: 6:00 PM
• End: 9:00 PM
• Revenue Centers: Premium Club East, Premium Club Bar

Because the events use different Revenue Centers, they can run concurrently.

Transactions from the club can be attributed to the reception while transactions from the concourses remain associated with the basketball game.

Best practices

• Group Revenue Centers according to their actual operational event, not simply their physical location.
• Review Revenue Center assignments before event day to make sure the same Revenue Center was not unintentionally included in conflicting events.
• Give each event a clear Internal Name and Display Name so operators can distinguish them quickly.
• Use the Price Level selection to categorize the appropriate event type when needed.
• Confirm event end times instead of relying on staff to manually end the operational period.

Use case 2: Main event with advance mobile ordering

Scenario

A stadium is preparing for a concert on Saturday evening. Guests should be allowed to place food pickup orders before arriving at the venue.

The stadium also has several premium spaces that are operating separately during the concert.

Recommended configuration

Create the concert Sales Event and assign the Revenue Centers participating in the concert.

Configure:

• The correct concert start and end times.
• The participating Revenue Centers.
• Allow Mobile Pre-Ordering for the event.
• Pre-order-compatible menus for Revenue Centers that should accept advance orders.
• The appropriate Price Level selection if the event should be categorized by a specific event type.

Premium spaces that need separate transaction attribution can be configured as their own Sales Events using their respective Revenue Centers.

Best practices

• Enable mobile pre-ordering only for events that should be visible to guests before the event begins.
• Verify that each participating Revenue Center has an eligible pre-order menu; the Sales Event setting alone is not sufficient.
• Test the guest ordering experience before publishing the event.
• Use event-specific Revenue Center assignments when premium areas need separate reporting.
• Avoid creating a second overlapping venue-wide event to represent a premium or private experience. Create a Revenue Center-scoped event instead.
• Review your event calendar before major event days so outdated or unnecessary event configurations do not create operational confusion.

Recommended event setup checklist

Before publishing or using a Concurrent Sales Event, confirm:

• The Internal Name and Display Name clearly identify the event.
• Start and end dates and times are correct.
• Times reflect the venue's configured time zone.
• The correct Revenue Centers are assigned.
• No unintended Revenue Center scheduling conflicts exist.
• The appropriate Price Level is selected for event-type categorization, if applicable.
• Mobile pre-ordering is enabled only when needed.
• Pre-order Revenue Centers have compatible menus configured.
• Event configuration has been reviewed before the event begins.

Summary

Concurrent Sales Events allow venues to operate multiple events per day, including simultaneous events in different areas of the property.

The key principle is to configure events according to when they occur and where they operate.

Using accurate schedules and Revenue Center assignments helps ensure the correct menus, mobile ordering experience, transaction attribution, and DataNow reporting are associated with each event.