How does availability status work?

This article explains how TickX calculates availability status for both individual time slots and full calendar days. It covers how the limited availability threshold is applied, how “Good”, “Selling Fast”, and “Sold Out” statuses are determined, and how overrides work in the Availability Manager. For timed-entry flows, the guide outlines how TickX uses performance-level statuses to ensure customers see an accurate reflection of real availability. Includes scoring examples and explanations of why the availability logic prevents misleading calendar states.

At time slot / performance level

The availability for an individual time slot / performance is based on the % of tickets remaining.

The global limited availability threshold is set inside the Availability Manager in the dashboard.

So if this is set to 20%, once 80% of tickets have sold, leaving 20% remaining, the performance will switch from Good Availability to Limited Availability / Selling Fast

When the number of tickets available is less than the desired quantity of the customer the performance will be marked as Sold Out.

The availability status for a time slot / performance can be overridden using the Availability Manager in the dashboard which if used forces it to be Limited or Sold out regardless of the number of tickets sold.

At the calendar level

This section is only applicable if the calendar shows a grouped view of multiple time slots / performances. I.e. Timed Entry purchase flows.

The availability shown at the calendar level is based on the availability logic the customer will experience when they click through the time selection screen.

Why we use availability logic and not % ticket sold?

We do this as relying on % tickets available aggregated up to a whole day can cause situations where a lot of time slots / performances are sold out or Limited but a few less popular times with a lot of availability keep the overall percentage high. 

As an extreme example if you had 10 time slots and the Limited availability threshold was set to 10% even if 9/10 times were completely sold out the date would still show as Good Availability. 

The customer after clicking it wouldn’t feel like there was good availability though as the 10% of tickets available were only available in a single time slot.

How we calculate availability

When calculating the availability the logic centres around the availability status of the time slots / performances contained in that day. So a Selling Fast performance with 10% of tickets available is treated identically to a Selling Fast performance with 50% of ticket available.

Each performance is given a score based on the below:

🟩 Good Availability Performance = 1

🟧 Selling Fast Performance = 0.5

🟥 Sold Out Performance = 0

These are then added together and divided by the total number of performances to provide an end score between 0 & 1.

If the score for the day was 0 that means all performances are sold out and the day will also appear as Sold Out.

If the score is < 0.7 then the day will appear as Selling Fast.

If the score is >= 0.7 then the day will appear as Good Availability.

Examples:

Based on a day with 10 performances:

🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟩 = 1.00 = Good Availability

🟩 🟩 🟩 🟩 🟩 🟩 🟩 🟧 🟧 🟧 = 0.85 = Good Availability

🟩 🟩 🟩 🟩 🟩 🟩 🟧 🟧 🟥 🟥 = 0.70 = Good Availability

🟩 🟩 🟩 🟧 🟧 🟧 🟧 🟧 🟧 🟧 = 0.65 = Selling Fast

🟩 🟩 🟩 🟩 🟩 🟧 🟧 🟥 🟥 🟥 = 0.60 = Selling Fast

🟩 🟩 🟩 🟩 🟩 🟥 🟥 🟥 🟥 🟥 = 0.50 = Selling Fast

🟥 🟥 🟥 🟥 🟥 🟥 🟥 🟥 🟥 🟥 = 0.00 = Sold Out