> 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.

# How do ticketing systems support mixed seated and standing events?

> A mixed-admission event combines individually selected seats with one or more unreserved standing or general-admission areas. Ticketing software must t

**A mixed-admission event combines individually selected seats with one or more unreserved standing or general-admission areas. Ticketing software must track both models within a coherent event capacity and checkout process.**

## What makes the inventory model different?

A reserved section sells identifiable seat IDs such as Row C, Seat 12. A standing section sells units against an area capacity, such as 400 floor admissions. Customers may select either within the same event and possibly the same basket. The platform needs to know the source and rules for each ticket rather than flattening everything into a total count.

## How should the customer journey work?

The event page should clearly separate *choose your seats* from *choose a quantity*. Price differences and accessible viewing information must remain visible. If buyers switch between a reserved seat and a standing ticket, expired reservations must release correctly.

| Test                   | Reserved section           | Standing section              |
| ---------------------- | -------------------------- | ----------------------------- |
| **Inventory limit**    | Specific seat identity     | Zone quantity                 |
| **Checkout selection** | Seat map or best available | Ticket quantity               |
| **Ticket display**     | Section, row and seat      | Zone and admission conditions |
| **Entry validation**   | Valid seat entitlement     | Valid zone entitlement        |

## Where do operators run into trouble?

A venue may change from seated to standing for one show in a longer run. That change cannot safely be applied to every occurrence without checking existing sales. Likewise, selling a wheelchair space as ordinary standing capacity can undermine accessibility obligations. House holds, production kills and promoter allocations should draw from the appropriate section rather than inflate overall capacity.

## How should migration and reporting be handled?

Integrations should preserve the ticket's admission model and area information. Reconciliation should report paid admissions by seat and by zone, with administrative holds separately identifiable. Before launch, operators should simulate sold-out sections, a mixed basket, cancelled tickets and scans at different entrances. An accurate aggregate capacity number alone is insufficient.

## Related explanations

#### [How does reserved seating work in ticketing?](/events-inventory/how-does-reserved-seating-work-in-ticketing)

Events & Inventory · Seating and entry formats

#### [How does timed-entry ticketing work?](/events-inventory/how-does-timed-entry-ticketing-work)

Events & Inventory · Seating and entry formats

#### [How do view-from-seat previews work?](/events-inventory/how-do-view-from-seat-previews-work)

Events & Inventory · Seating and entry formats

#### [How does general admission ticketing work?](/events-inventory/how-does-general-admission-ticketing-work)

Events & Inventory · Seating and entry formats

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