> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# What is ticket inventory?

> Understand ticket inventory, capacity versus availability, held and sold tickets, seat maps, timed entry and how inventory changes during an onsale.

**Ticket inventory is the stock of tickets or admission rights that an event business can manage and offer for sale or distribution.** It may consist of numbered seats, general-admission quantities, timed-entry places or other reservable units. A ticketing platform tracks that inventory alongside rules determining who may buy it, when it can be sold and whether it is still available.

**Inventory, capacity and availability are different.** A venue may have capacity for 2,000 people, inventory configured for 1,800 tickets, and fewer than 1,800 tickets currently available to a particular customer because of sales, holds, allocations or access restrictions. Ticket Tailor documents [event-wide capacity limits across ticket types](https://help.tickettailor.com/en/articles/1549453-how-do-i-set-a-capacity-limit-across-multiple-tickets); Spektrix separately documents [reserved seats, general admission and restricted seats](https://support.spektrix.com/hc/en-us/articles/11012056320541-Introduction-to-Events-and-Instances).

## What counts as ticket inventory?

Ticket inventory represents **admission rights or reservable capacity, not necessarily physical tickets already issued**. Different event formats require different representations of stock.

| Event type                    | Typical inventory unit                           | How availability is checked                 |
| ----------------------------- | ------------------------------------------------ | ------------------------------------------- |
| **Reserved-seat performance** | Individually identifiable seat                   | Seat status, price band and sales rules     |
| **General-admission concert** | Quantity within a ticket category or area        | Remaining quantity and any channel limits   |
| **Museum or attraction**      | Entry places for a particular time               | Remaining capacity for the selected slot    |
| **Festival**                  | Day passes, weekend access or camping allotments | Product-specific and linked package stock   |
| **Hospitality event**         | Table, suite or package entitlement              | Reservable unit and associated restrictions |

A ticket product and an inventory unit are not always identical. One package might include admission plus parking, or a group product might reserve several individual places. If those products share underlying capacity, the platform must stop separate sales paths from using the same stock twice.

## What is the difference between capacity, inventory and availability?

**Capacity is a limit; inventory is the stock being managed; availability is what can currently be purchased under applicable rules.** The numbers can differ for valid operational reasons.

Consider a hypothetical 1,000-capacity venue:

* Capacity: 1,000 people.
* Ticket inventory released for the event: 900 places; the operator has retained 100 places for operational or other permitted use.
* Of the 900, 500 have been sold, 40 are temporarily reserved in baskets, 20 are held back and 30 are assigned as complimentary admissions.
* In this simplified example, **310 places remain otherwise uncommitted** in that 900-unit inventory: 900 − 500 − 40 − 20 − 30 = 310.

Those 310 places may still not all be visible to every buyer. Some might be in a partner allocation, restricted to members, outside the customer's eligible price band or unavailable at the selected onsale time.

The arithmetic above is an illustration, **not a universal stock formula**. Different systems count complimentary allocations, holds, released inventory and unused capacity differently. Reports may distinguish *sold*, *reserved*, *complimentary*, *held* and *remaining* instead of combining them into a single availability number.

## How does ticket availability change during an onsale?

Availability changes whenever an action affects the right to purchase or use inventory. A typical lifecycle is:

1. **Configured:** A seat or quantity exists in the event's inventory but may not yet be on sale.
2. **Available:** The relevant customer or sales channel is permitted to select it.
3. **Reserved:** A basket or authorised workflow temporarily claims it, so another buyer cannot take the same stock during the reservation period.
4. **Sold or confirmed:** An order completes under the applicable payment and order rules.
5. **Released or changed:** An expired hold, approved cancellation, exchange or operational reallocation may make some stock saleable again.
6. **Used:** Admission is recorded when a ticket is validated; this is a ticket-validity state, not necessarily a change to what could have been sold earlier.

![Illustrative inventory lifecycle: configured, available, reserved in a basket, sold or confirmed, and used at entry. An expired hold, cancellation, exchange or reallocation can release stock so that it becomes saleable again. State names and rules differ between platforms.](/_fern-files/nuweb-group.docs.buildwithfern.com/02b396e53342629fde2cbb49b956e9bb737f5cac12a54c429473b313c3e033f1/assets/diagrams/inventory-states.svg)

A failed payment does not always mean stock becomes available immediately. Some payment methods are asynchronous, and the platform may need to establish the final status before it safely releases an order's inventory.

**Showing availability is not the same as reserving inventory.** An availability feed may be cached or subject to change. A separate booking or reservation operation is often required before a seat is actually secured. Ticketmaster's partner documentation explicitly distinguishes availability enquiries from purchase-time inventory control.

## How do ticketing platforms organise inventory?

Platforms commonly relate inventory to several organisational layers:

* **Event or performance:** Which specific date or session the inventory belongs to.
* **Ticket type or sale item:** What the customer is buying, such as adult admission, a premium seat or a package.
* **Price band or seating area:** Which seats or places share a pricing or operational rule.
* **Timeslot:** Which admission window a visitor can book.
* **Channel or allocation:** Which seller or partner may offer certain quantities.
* **Eligibility:** Which customer group can access the product, such as members during a presale.

Those layers can overlap. For example, an attraction might have an overall daily limit, a maximum number of entries per hour and a separate cap on discounted student tickets. A sale can be valid only if **all relevant constraints permit it**.

A system can apply event, item-type, timeslot, sale-item, shared-stock and seating limits at the same time. In such an arrangement, a sale is only permitted if the relevant limits all allow it. That is why one capacity field rarely explains the full picture.

Inventory may also be divided between direct sales and other distributors. A **ticket allocation** assigns stock or selling rights to a particular party, whereas a **basket reservation** normally protects a customer's selection while checkout is underway. They solve different problems even if both reduce immediately available stock.

Spektrix also documents [operational locks that set seats aside for access, promoters and other restricted uses](https://support.spektrix.com/hc/en-us/articles/9651230222877-Introduction-to-Locks). These restrictions can change which seats are sellable without changing the physical size of the venue.

## Why does inventory accuracy matter?

**Accurate inventory management protects the promise made to the customer at checkout.** If a platform shows a seat as available but cannot reserve it, a buyer may reach payment only to discover the seat is gone. If multiple channels confirm the same underlying admission right, the event risks overselling and disputes at entry.

Inventory errors can also affect revenue and reporting. A misplaced hold can leave good seats unsold. An unreleased partner allocation can make an event appear sold out when inventory is still unused. A reporting system that mixes sold, reserved, cancelled and complimentary places may give a misleading view of demand or attendance.

When evaluating a platform, ask how it handles simultaneous seat selection, expired baskets, payment reversals, separate allocations and reconciliation between online sales and box-office operations. The important questions are not just *how many tickets remain?* but **available to whom, through which channel, at what point in the transaction?**

**The key distinction:** ticket inventory is the managed stock of admission rights. Capacity establishes limits; reservations, orders, holds, allocations and eligibility rules determine what is actually available to each buyer.

## Related explanations

#### [How do ticket basket holds and reservations work?](/events-inventory/how-do-ticket-basket-holds-and-reservations-work)

Events & Inventory · Inventory and availability

#### [How should ticketing operators manage inventory changes after onsale?](/events-inventory/how-should-ticketing-operators-manage-inventory-changes-after-onsale)

Events & Inventory · Inventory and availability

#### [How does ticket inventory synchronisation work between systems?](/events-inventory/how-does-ticket-inventory-synchronisation-work-between-systems)

Events & Inventory · Inventory and availability

#### [How do ticketing platforms prevent tickets being sold twice?](/events-inventory/how-do-ticketing-platforms-prevent-tickets-being-sold-twice)

Events & Inventory · Inventory and availability

[More in Events & Inventory →](/events-inventory)