Note: The features mentioned in this article are only available on Regular events . Features mentioned below are not available on Timed-Entry events. Unsure of the difference? Please see here: Regular events vs. Timed-entry events
Tiered ticketing allows you to make future ticket types (or tiers) available if an initial tier sells out sooner than expected. This is commonly used when you have different ticket types that you want to sell based on time. For example, you want to reward early ticket buyers with a lower price compared to those who would buy tickets last minute.
If this feature is greyed out, please click on the 'Contact us to upgrade' button and someone from Universe will be in touch shortly.
Note: Tiered ticketing cannot be enabled on events with locked ticket types.
Note: Tiered ticketing cannot support listings that have more than one timeslot.
To set up tiered ticketing:
First, we will need to define an initial tier as a ticket type that needs to sell out or reach its ‘ticket sale ends’ time before a future tier (another ticket type), can be made available.
Note: You can have as many initial tiers and future tiers as you need, but a future tier can only have one initial tier.
- Create a ticket type that you will set as your initial tier. The initial tier will need to have the following setup:
- A max quantity to ensure future tiers are shown once the initial tier(s) are sold out
- A sales end time to ensure that the ticket type is automatically hidden if the initial tier does not sell out
- Create a ticket type that you will set as a future tier that will go on sale after your initial tier sells out or reaches the ‘ticket sale ends’ time. The future tier should have the following setup:
- No start time, unless you want to ensure this tier does not go on-sale until a specific time even if the prior tier sells out. NOTE: if tiered ticketing is enabled for this ticket, the start time will be removed, and it will instead abide by set tiered ticketing parameters
- The ticket status is set active; hidden tickets will never be shown on checkout
In the examples above, the initial tier (General Admission (Early Bird) ) is set to go on sale immediately. It will become unavailable when either 20 tickets are sold or on June 30th at 12:30pm, whichever one comes first. The future tier (General Admission) does not have a set start time, and it would be available immediately. On our next step, we will configure it so that the future tier will only appear once the initial tier is no longer available.
- After creating your event, go to the Advanced Settings section and click on 'Configure' under 'Tiered ticketing'
- In the tiered ticketing settings, you can choose which future tier should show up based on which initial tier sells out.
Note: This step is crucial for allowing tiers to appear if a different tier sells out earlier.
Note: As the organizer, when you are logged in, you will see your checkout screen differently than a buyer. Please log-out or open an incognito window to test the buyer-facing view.
Why didn’t my future tier show up after my initial tier sold out?
There could have been a number of reasons. To troubleshoot, check the following:
- Make sure that you have a maximum quantity of tickets set on your initial tier. The maximum quantity will indicate how many tickets can be purchased before the initial tier sells out and your future tier goes on sale.
- Make sure that your initial tier has a ‘ticket sale ends’ time configured
- Make sure you have linked your future tier to an initial tier from the 'advanced settings' tab in your event manager page.
Why can’t I set up an initial tier for a certain ticket type?
You can only set an initial tier for a ticket type if the initial tier has the following settings:
- A max quantity to ensure future tiers are shown once the initial tier(s) are sold out.
- A sales end time to ensure that the ticket type is automatically hidden if the initial tier does not sell out.
Why can't I have locked ticket types and tiered ticking on the same event?
Unfortunately, this is a technical limitation which we are looking to resolve in the near future.
Article is closed for comments.