When you set up ticket dependencies (where one ticket requires another ticket to be purchased first), dependent tickets will only appear as sold out if the ticket they depend on is also sold out or hidden.
How it works
For example, let's say you're selling a VIP upgrade ticket, but you need ticket buyers to purchase a Standard ticket too to qualify for this:
Your 'Standard ticket' is the required ticket.
Your 'VIP upgrade ticket' is the dependent ticket.
If your standard ticket is sold out, your VIP upgrade ticket will automatically show as sold out, too.
The below screenshot demonstrates what this may look like for your ticket buyers, presuming there are other ticket types available for your event.
Note: If these were the only two ticket types available within your event, you wouldn't see this - the whole event would be marked as sold out.
đĄ Things to note
Dependent tickets do not become sold out simply because the required ticket hasnât been added to the basket.
The dependency rule still applies at checkout - customers must meet the dependency requirements to complete their purchase.
This doesnât affect your actual ticket inventory - itâs only about how ticket availability is displayed.
If you need to review or change your ticket dependencies, you can do this in your 'Ticket types' section when editing your event.
If you're an authorised box office operator placing an order on behalf of a customer and need to override dependency requirements, you can use the admin bypass option.
The order will show a notice confirming that an admin bypass option was applied.
This option is only available to those who have permission to take operator payments at checkout.