The words people use
Seat map, seating chart and seat picker
Three words, one job, and the differences are habits of language rather than differences of substance.
- Venues and box offices
- Seating chartSeating chart is the older phrase, and the one box offices, venues and organizers reach for first. It usually means the document: the room as drawn, with its sections, rows, tables, aisles, accessible positions and price zones.
- Developers and product teams
- Seat mapSeat map is what developers and product teams say, and what tends to appear in API and SDK documentation. It means the same document seen from the integration side: something you render, query and sell against. Airlines popularised it, which is why searches for it mix travel and event intent.
- The buyer on the page
- Seat pickerSeat picker is narrower again: the buyer-facing control itself, the thing on the page where a person chooses their seats. A seat picker is one way of rendering a seat map, which is one way of reading a seating chart.
Treat them as interchangeable in conversation, but check which one a contract or a price list means. SeatLayer publishes one document and renders it as all three: the seating chart a venue designs, the seat map a developer embeds and the seat picker a buyer uses.
The requirements
What a good interactive seat map must do
Rendering the room is the easy half. These are the things that decide whether you can actually sell from it.
- 01Live availabilityEvery seat's state comes from the server, per event, and updates while the buyer is looking. A map that loads availability once will sell seats twice on a busy on-sale.
- 02Holds, so two buyers cannot take one seatSelecting a seat places a short, server-owned hold with an expiry, and only one hold can exist per seat. The decision has to be made in one place, and the loser told immediately.
- 03Best availableMost buyers want four seats together, near the front, under a price. Best available has to honour adjacency, aisle boundaries and party size rather than picking the first free identifiers.
- 04Ticket tiers and price zonesSeats belong to categories with prices, and the map has to show the tier, filter by it and refuse selections the buyer is not entitled to make.
- 05A 3D seat viewA 3D venue and a view from the chosen seat answer what the buyer will actually see, without leaving the map.
- 06Mobile touch behaviourMost buyers are on a phone. Pinch, pan, momentum, fingertip-sized tap targets and a tray that does not cover the map decide whether the sale happens.
- 07AccessibilitySeats must be operable by keyboard and screen reader, each with a name a person can act on, and wheelchair and companion positions must be real inventory rather than a note.
- 08Large venuesA 300-seat room and a 60,000-seat bowl are not the same rendering problem. Big venues need zone-to-seat navigation rather than every seat drawn at once.
Requirement 02, played out: two buyers ask for one seat at the same moment, and exactly one hold wins.
Two routes
Two ways to use the SeatLayer interactive seat map
SeatLayer is interactive seating chart software built for stadium scale. Platforms embed the white-label seat picker with their own checkout; organizers sell seated events on their own website with their own payment gateway.
For platforms · SDK
Embed it, and keep your own checkout
If you already run a ticketing product with a cart and order records, you do not want another checkout. Install the web or mobile SDK, render the seat map against an event, and let your own system take the money. SeatLayer owns the chart, live inventory, holds and confirmed booking. Billing is per confirmed sold seat, starting at $0 with 100 free credits each month.
For organizers · Hosted
Sell on your own website, with your own gateway
If you are an organizer or a venue, you probably do not want to build a checkout at all. Hosted Ticketing puts the seat map on the site you already publish, runs checkout on your own connected payment gateway, issues QR and PDF tickets, and adds box office and door check-in, with the SeatLayer iPhone app or a phone browser, on the same inventory. It costs $0.50 per confirmed ticket.
Both routes read the same published chart, so a venue that starts hosted and later builds its own product does not redraw anything. Both include the 3D seat map and the view from every seat, at no extra cost.
For developers
Seat map API and SDKs
The REST API owns charts, events, inventory, holds and bookings and is described by an OpenAPI 3.1 document. The client SDKs render the interactive seat map against it; the server SDKs call it from your backend. Signed webhooks report booking and inventory changes.
Web
Mobile
All four web packages ship from the open seatlayer-sdk repository around one shared renderer, so the map behaves the same in every framework.
WordPress
The WordPress seating chart plugin adds an interactive seat map to a page or post through a block or a shortcode, with the secret key held on the server. Install it from the plugin directory.
Start from the quickstart, or read the seating chart API and SDK overview. Every repository above is public, so you can read the source first.