Create one reusable venue chart, publish it to each event, and keep buyer selection, house blocks, counter sales, and seating status on one live event state.
SDK first: keep checkout, payment, orders, tickets, refunds, customer records, and scheduling in your systems. A hosted reserved-seating path is available when the venue needs the event page and operating tools too.
Keep the stable venue geometry separate from event-specific inventory. Publish a reviewed chart version, attach it to an event, then operate that event’s live seat state.
Store published and draft floor plans for fixed seats, curved rows, sections, tables, booths, general-admission areas inside a reserved-seat chart, accessibility, pricing categories, and multiple floors.
Explore the Venue Designer →Pin a published chart version to an event, keep that event’s status and inventory separate, and reuse the venue again for the next performance or on-sale.
Read publishing and versioning ↗Inspect free, held, sold, and blocked places; manage house inventory; and make authorized counter sales against the same event state used by the embedded buyer picker.
Explore box-office operations →Both paths use the same venue chart and live event inventory. The difference is who owns checkout, payment, orders, tickets, refunds, and customer records.
Embed reserved seating in your platform →The complete 2D Map remains the baseline. Optional 3D uses the same published geometry where height and spatial context help; intentionally flat rooms remain flat by design.
See the managed website embed →Only confirmed sold seats use Platform credits; designing charts, buyer browsing, temporary holds, house blocks, and unsold inventory do not. Each organization gets 100 confirmed sold seats free every month, then credit packs start at $0.10 per seat. Purchased credits do not expire, and the standard Platform plan has no subscription.
Managed Ticketing is available for eligible assigned-seat events after a request, staff approval, and Hosted Checkout enablement. Its separate wallet includes the first 200 confirmed Hosted Tickets once per organization, then costs $0.50 per ticket on the USD catalog or ₹25 on the INR catalog.
One published chart per room, reused for every event in it. What changes between venue types is the geometry the room needs and the operation around it.
Tiered bowls, stands and decks are modelled as sections with their own rows, so a large room stays navigable for a buyer and countable for the house. Section-level structure carries into the optional 3D view of the same published chart. House blocks, holds and confirmed sales stay on one live event state, which is what keeps a large on-sale consistent between the website and the counter.
Arena and stadium seating →Curved and segmented rows, multiple levels, boxes and accessibility marks are ordinary chart objects rather than special cases. A published version pins to each performance, so a run of dates shares one venue source with separate seating states. Price categories travel with the chart, so the same room can be sold differently for a matinee and an opening night without redrawing it.
Performing arts and theatre seating →Small rooms are mostly tables, mixed seating and general-admission space, with capacity that changes by night. The same chart handles tables and rows together, and house blocks keep the seats you are not selling out of the buyer’s view. Designing, holding and blocking cost nothing — only a confirmed sold seat does — so a room can be re-cut for each night without a per-layout charge.
Comedy club seating →Counter sales, house blocks, holds and confirmed bookings act on the same live event state as online buyers, so the two never diverge. Staff work the seating chart rather than a separate list. In the SDK path your own system still creates the commercial order; in the hosted Box Office, SeatLayer records the order and tickets while staff record payment taken elsewhere.
Box office operations →Buyers ask what they will see before they pay, and the venue is the only place that can answer with its own room. Where the venue has uploaded photos or panoramas the picker shows those from the chosen seat, and where it has not, a clearly labelled generated preview stands in — see view from seat previews.
Open the released buyer SeatPicker, then bring us the venue workflow if you need to choose between SDK and hosted operations.