Ticket Availability Problems
Ticket availability problems usually happen when Eventixa determines that a ticket cannot currently be selected or purchased.
A ticket can become unavailable because of more than just completed sales. Eventixa also evaluates the ticket’s configuration, remaining capacity, sale schedule, quantity rules, booking state, checkout reservations, and recurring occurrence context.
Use this guide when a ticket:
- Shows as sold out unexpectedly
- Does not appear on the event page
- Shows no availability even though capacity appears to remain
- Becomes unavailable during checkout
- Is available for one recurring occurrence but not another
- Appears to have incorrect remaining capacity
- Does not reopen after a booking is cancelled
- Sends visitors to a waitlist when you expected normal checkout
Before You Begin
Before changing ticket settings:
- Identify the exact event and ticket affected.
- If the event is recurring, identify the exact occurrence.
- Check whether the problem affects all visitors or only one checkout session.
- Review the related booking records before manually changing capacity.
- Clear relevant frontend caches after making configuration changes.
- Test again in a private/incognito browser window.
Avoid increasing ticket capacity only to hide an availability problem. First determine why Eventixa considers the ticket unavailable.
How Eventixa Determines Ticket Availability
Eventixa ticket availability is influenced by several parts of the registration workflow.
A simplified availability flow is:
Ticket Configuration → Sale Schedule → Quantity Rules → Remaining Capacity → Checkout Reservation → Booking State → Availability
For recurring events, Eventixa must also keep the selected occurrence in the correct registration context.
This means a ticket can be unavailable even when the configured capacity value itself looks correct.
Quick Diagnosis
| Symptom | First Check |
|---|---|
| Ticket is missing completely | Ticket sale schedule and event date |
| Ticket shows Sold Out | Capacity, pending bookings, active checkout reservations |
| Final remaining ticket cannot be purchased | Remaining capacity and requested quantity |
| Ticket becomes unavailable after another visitor starts checkout | Temporary checkout reservation |
| Availability changes after a browser refresh | Existing checkout session and reservation timeout |
| Ticket is unavailable for only one recurring date | Selected occurrence and occurrence-aware capacity |
| Ticket remains unavailable after cancellation | Booking status and released capacity |
| Waitlist appears instead of checkout | Ticket capacity and Waitlist configuration |
| Customer cannot select desired quantity | Minimum, maximum, and remaining quantity rules |
Check the Ticket Configuration
Go to: Eventixa → Events → Edit Event
Open the ticket configuration for the affected ticket.
Review:
- Ticket name
- Ticket status
- Price
- Capacity
- Sale start date
- Sale end date
- Minimum quantity
- Maximum quantity
- Attendee collection settings
- Recurring occurrence context where applicable
Save the event after correcting any configuration.
Check Ticket Capacity
Ticket capacity controls how many registrations can be accepted for that ticket.
If the ticket has a configured capacity, Eventixa rechecks availability during the booking workflow.
Do not compare capacity only with the number of completed payments.
Relevant pending booking states and active checkout reservations can also affect the capacity that remains available.
Completed Sales Are Not the Only Capacity Usage
Suppose a ticket has:
Capacity: 20 and you see: Completed registrations: 18
It may appear that two places remain.
However, if another visitor is actively holding two places in checkout, Eventixa can temporarily treat those places as reserved.
In that situation, another customer should not be allowed to purchase the same final capacity at the same time.
Pending Bookings Can Affect Capacity
Eventixa accounts for relevant pending registration states when protecting limited ticket inventory.
A pending booking can therefore affect the remaining availability even before the booking reaches its final paid state.
This behavior helps prevent the same capacity from being sold twice.
When availability looks incorrect, review: Eventixa → Bookings and inspect bookings associated with the affected event and ticket.
Active Checkout Reservations
Eventixa checkout uses a temporary reservation system to protect limited ticket capacity while the visitor completes registration.
The checkout session lasts: 10 minutes
During that session, selected limited-capacity places can remain temporarily reserved.
If another visitor tries to select the same final capacity, Eventixa can correctly report that the places are no longer available.
Refreshing Checkout Does Not Reset the Reservation
Refreshing the checkout page does not start another full 10-minute reservation.
The existing checkout session continues from its original expiration time.
This prevents customers from keeping limited capacity reserved indefinitely by repeatedly refreshing the browser.
When an Abandoned Reservation Expires
If the visitor leaves checkout without completing the booking, the temporary reservation remains only until the checkout session expires.
After expiration, the held capacity can become available again.
If a ticket appears sold out because another visitor abandoned checkout, wait for the reservation to expire and test again.
Last Available Ticket
Eventixa should allow the final valid remaining place to be purchased.
For example:
Remaining capacity: 1
Requested quantity: 1
This is a valid purchase.
The over-capacity protection should block the request only when the requested quantity exceeds valid remaining capacity.
If the last place cannot be selected, check:
- Requested quantity
- Minimum quantity
- Maximum quantity
- Pending bookings
- Active checkout reservations
- Recurring occurrence context
Requested Quantity Exceeds Remaining Capacity
Checkout validates the selected quantity against remaining availability.
For example:
Remaining capacity: 2
Requested quantity: 3
The booking should not complete because the request exceeds available inventory.
Reduce the requested quantity or increase ticket capacity only if the event genuinely has more places available.
Minimum and Maximum Quantity Rules
A ticket can have quantity rules that prevent a customer from selecting an otherwise available amount.
For example:
Minimum quantity: 2
Remaining capacity: 1
Even though one place technically remains, the customer cannot satisfy a minimum quantity of two.
Similarly: Maximum quantity: 4 prevents a customer from selecting five tickets even when sufficient overall capacity remains.
When customers report that the quantity selector is restricted, verify the ticket’s minimum and maximum quantity settings.
Check the Ticket Sale Schedule
A ticket can be unavailable because its sale period has not started or has already ended.
Review the ticket’s:
- Sale start date
- Sale start time
- Sale end date
- Sale end time
A ticket can have remaining capacity and still be unavailable outside its configured sale period.
Ticket Sales Have Not Started Yet
If the current time is before the configured sale start, the ticket should not behave as an open ticket.
Confirm:
- Sale start date
- Sale start time
- Event timezone
- WordPress timezone fallback where relevant
Timezone differences can make a correctly configured sale schedule appear early or late if the site timezone is wrong.
Ticket Sales Have Ended
If the sale end date or time has passed, the ticket can become unavailable even when capacity remains.
Extend the sale end time only if registrations should genuinely remain open.
Do not confuse:
- Remaining capacity
- Sale availability
They are separate conditions.
Check Event Date and Time
An event’s date and time can also affect the expected registration workflow.
Verify: Eventixa → Events → Edit Event and review the event schedule.
If the event date is incorrect, expired, or using an unexpected timezone, ticket availability can appear inconsistent with your intended schedule.
Check Event Timezone
Eventixa uses the Event Timezone setting for event date and time behavior.
Review: Eventixa → Settings → Display → Date and Time
If no custom Event Timezone is selected, Eventixa follows the WordPress site timezone.
An incorrect timezone can make:
- Ticket sales open too early
- Ticket sales open too late
- Ticket sales close unexpectedly
- Recurring occurrence dates appear inconsistent
Recurring Event Ticket Availability
Recurring events require occurrence-aware ticket registration.
When troubleshooting a recurring ticket, verify the exact occurrence rather than only checking the parent event.
A recurring event can have several individual dates, and ticket availability can differ by occurrence.
Always confirm:
- Parent event
- Selected occurrence
- Occurrence date/time
- Ticket assignment
- Booking occurrence
- Capacity context
Parent Event vs Specific Occurrence
Do not assume that availability for the recurring parent event automatically describes every occurrence.
For example:
Saturday 1: Sold out
Saturday 2: 8 places available
Saturday 3: 12 places available
If a customer reports a sold-out ticket, confirm which occurrence they selected.
Checkout Rechecks Capacity
Ticket availability is not validated only when a visitor first sees the event page.
Eventixa rechecks capacity during checkout.
This is necessary because availability can change between:
- Ticket selection
- Attendee information entry
- Payment
- Booking completion
If another customer secures the remaining capacity first, the later checkout can be prevented from completing.
This is expected over-capacity protection.
Ticket Was Available but Became Unavailable During Checkout
This can happen when multiple visitors are purchasing the final places at the same time.
For example:
- Two places remain.
- Visitor A selects both places.
- Visitor B still has an older event page showing availability.
- Visitor A enters checkout and holds the two places.
- Visitor B tries to continue.
- Eventixa rechecks capacity and blocks the unavailable quantity.
Refreshing the original event page should show the current state.
Booking Status and Capacity
When ticket availability looks wrong, review the related booking status.
Go to: Eventixa → Bookings
Identify bookings for the affected event and ticket.
Capacity behavior can depend on whether a booking is still active, pending, completed, cancelled, or otherwise no longer eligible to hold inventory.
Do not manually delete booking records simply to change capacity.
Use the supported booking cancellation/refund workflow so Eventixa can apply the correct side effects.
Cancellation and Capacity Release
When a booking is cancelled through the supported Eventixa workflow, capacity should be released according to the booking and ticket state.
If availability does not return after a cancellation:
- Confirm the booking is actually cancelled.
- Confirm the correct ticket was associated with the booking.
- Confirm the correct recurring occurrence where applicable.
- Refresh the frontend after cache clearing.
- Review whether a waitlist reservation immediately claimed the released place.
Waitlist Can Affect Newly Released Capacity
Eventixa Pro Waitlist can immediately reserve newly available capacity for an eligible waitlisted customer.
This is important when troubleshooting a ticket that remains unavailable after a cancellation.
The sequence can be:
Booking Cancelled → Capacity Released → First Waitlisted Customer Reserved → Ticket Still Appears Unavailable
In this situation, capacity was released correctly but was immediately reassigned through the Waitlist workflow.
Review: Eventixa → Waitlist before assuming the cancellation failed to restore capacity.
Waitlist Instead of Normal Checkout
If a ticket has no available capacity and Eventixa Pro Waitlist is enabled for the event/ticket, visitors can be offered the waitlist workflow instead of normal checkout.
Check:
- Ticket capacity
- Active bookings
- Checkout reservations
- Waitlist settings
- Existing waitlist reservations
If the ticket should have normal availability, resolve the underlying capacity state rather than disabling Waitlist as a workaround.
Free Tickets Still Use Availability Rules
A ticket does not become unlimited just because its price is zero.
Free standard tickets can still use:
- Capacity
- Sale schedules
- Quantity rules
- Checkout reservations
If a free ticket shows sold out, troubleshoot it using the same capacity and booking checks as a paid standard ticket.
RSVP Availability
RSVP uses a different registration workflow from standard commerce tickets.
Do not assume standard ticket availability behavior applies identically to RSVP responses.
For RSVP-specific problems, review:
- RSVP capacity
- Going / Not Going state
- RSVP attendee count
- Recurring occurrence where applicable
Use the dedicated RSVP documentation when the problem is specific to RSVP registration rather than standard ticket checkout.
Cached Availability
An event page can display outdated ticket availability if it is served from an aggressive cache.
After changing ticket, booking, or capacity data, clear:
- WordPress page cache
- Server cache
- CDN cache
- Browser cache
Then test in a private/incognito browser window.
Dynamic event, ticket, checkout, and account pages should not be cached in a way that prevents current availability from being displayed.
Page Shows Available but Checkout Says Sold Out
This usually means the event page is displaying stale information or availability changed after the page loaded.
Because Eventixa rechecks capacity during checkout, the checkout result is the safer indication of current availability.
Try:
- Clear frontend cache.
- Reload the event.
- Check current bookings.
- Check active checkout reservations.
- Verify the selected occurrence.
- Retry with the valid remaining quantity.
Admin Capacity and Frontend Capacity Look Different
When comparing values, make sure you are comparing the same thing.
Possible measurements include:
- Configured ticket capacity
- Completed ticket quantity
- Pending booking quantity
- Active checkout reservation quantity
- Remaining availability
- Occurrence-specific availability
These values are not expected to always be identical.
Example: Unexpected Sold Out Status
Suppose a ticket has:
Capacity: 50
Completed registrations: 47
but the frontend shows no availability.
A useful diagnosis is:
- Open Eventixa → Bookings.
- Check for relevant pending bookings.
- Test whether another checkout session is holding capacity.
- Wait for abandoned checkout reservations to expire.
- Confirm the event/occurrence being tested.
- Clear frontend cache.
- Test the ticket again.
If three places are currently protected by pending or active checkout state, the sold-out result can be correct even though only 47 completed registrations are visible.
Example: Capacity Does Not Return After Cancellation
Suppose one ticket was cancelled but the event still appears sold out.
Check:
- The booking status is actually cancelled.
- The cancelled booking contained the affected ticket.
- The booking belonged to the expected recurring occurrence.
- Eventixa Pro Waitlist did not immediately reserve the released place.
- Frontend cache is cleared.
If the waitlist promoted another customer immediately, the capacity was released and then reassigned as designed.
Recommended Diagnostic Workflow
When a ticket has unexpected availability:
- Open Eventixa → Events.
- Edit the affected event.
- Review the exact ticket.
- Confirm ticket capacity.
- Confirm sale start/end schedule.
- Confirm minimum/maximum quantity rules.
- Confirm event date and timezone.
- If recurring, confirm the exact occurrence.
- Open Eventixa → Bookings.
- Review active and pending bookings for that ticket.
- Consider active checkout reservations.
- Review Eventixa → Waitlist if Waitlist is enabled.
- Clear relevant caches.
- Test again as a visitor.
- If checkout still rejects an apparently valid ticket, continue with the Checkout Problems guide.
Important Notes
- Ticket availability is not based only on completed payments.
- Relevant pending bookings can affect capacity.
- Active checkout sessions can temporarily reserve capacity.
- Eventixa checkout uses a 10-minute reservation session.
- Refreshing checkout does not restart the reservation timer.
- Eventixa rechecks capacity during checkout.
- The final valid remaining place should be purchasable when quantity rules allow it.
- Requests above remaining capacity should be blocked.
- Ticket sale schedules can make a ticket unavailable even when capacity remains.
- Minimum and maximum quantity rules can restrict an otherwise available quantity.
- Recurring-event tickets must be checked in the correct occurrence context.
- Supported booking cancellation can release capacity.
- Eventixa Pro Waitlist can immediately claim capacity released by a cancellation.
- Cache can make frontend availability appear stale.
Troubleshooting
Ticket Shows Sold Out but Capacity Remains
Check:
- Pending bookings
- Active checkout reservations
- Selected recurring occurrence
- Waitlist reservations
- Frontend cache
Do not compare only configured capacity with completed payments.
Ticket Does Not Appear on the Event Page
Check:
- Sale start date/time
- Sale end date/time
- Event date
- Event timezone
- Ticket status
- Selected occurrence
- Frontend cache
The Last Ticket Cannot Be Purchased
Confirm:
- Remaining capacity is actually 1
- Requested quantity is 1
- Minimum quantity does not require more than 1
- No pending booking is holding the place
- No active checkout session is holding the place
- The correct recurring occurrence is selected
Ticket Becomes Unavailable During Checkout
Another customer may have reserved the remaining capacity first.
Eventixa rechecks availability during checkout to prevent overselling.
Reload the event and select a quantity that is still available.
Availability Does Not Return After Checkout Is Abandoned
Eventixa holds temporary checkout capacity only until the checkout session expires.
The session duration is 10 minutes.
Wait for the original reservation to expire and then retest.
Refreshing Checkout Keeps the Ticket Reserved
Refreshing checkout does not create a new 10-minute reservation.
The existing reservation continues until its original expiration.
Capacity Does Not Return After Booking Cancellation
Check:
- Booking is actually cancelled
- Correct ticket
- Correct occurrence
- Waitlist promotion
- Cache
If Waitlist is active, released capacity can be immediately reserved for the first eligible waitlisted customer.
Ticket Is Available for One Recurring Date but Not Another
This can be correct.
Recurring occurrences can have different registration and availability contexts.
Confirm the selected occurrence and review its related bookings.
Event Page and Checkout Show Different Availability
Clear the frontend cache and reload the event.
Checkout performs a fresh capacity validation, so it can reject a quantity that was available when an older event page was loaded.
Related Documentation
- Troubleshooting Overview
- Ticket Capacity and Availability
- Ticket Sale Schedule
- Ticket Quantity Rules
- Checkout Overview
- Managing Bookings
- Event Waitlist Overview
Frequently Asked Questions
Why does a ticket show sold out when completed registrations are below capacity?
Pending bookings or active checkout reservations can also protect capacity. If Eventixa Pro Waitlist is active, newly released capacity can also be immediately reserved for a waitlisted customer.
How long does checkout hold ticket capacity?
The Eventixa checkout session holds the temporary reservation for 10 minutes.
Does refreshing checkout restart the reservation timer?
No. Refreshing the checkout page does not create a new 10-minute reservation.
Can Eventixa sell the final remaining ticket?
Yes. The final valid place should be purchasable when the requested quantity and ticket rules permit it.
Why is my recurring ticket available on one date but sold out on another?
Recurring events use occurrence-aware registration. Different occurrences can have different registration and capacity states.
