# Box office software that sells online and at the counter from one live house. SeatLayer is a box office ticketing system for reserved seating: online checkout, counter sales, tickets, refunds, reporting and door check-in run on one live seat inventory. Run the whole flow in SeatLayer, or keep your own point of sale and use SeatLayer for the seats. [Request Managed Ticketing](https://app.seatlayer.io/) [Connect your own POS →](https://seatlayer.io/developers/) First 200 confirmed Hosted Tickets free once per organization; then $0.50 USD or ₹25 INR each. The Hosted Ticket wallet is separate from Platform/SDK credits. Managed Ticketing requires a request, staff approval, and Hosted Checkout (hosted_checkout) enablement. The organizer's connected provider controls processing fees, applicable taxes, and payout timing; SeatLayer bills Hosted Ticket usage separately. Counter sales, per-seat tickets, house blocks and door check-in are released today, not on a roadmap. _Every sale — web, walk-up or comp — moves the same seats._ ## Box office software that runs the whole sale — or just the seats Pick one owner for the money. Either SeatLayer sells, tickets and refunds for you, or your own point of sale keeps that job and SeatLayer keeps the house honest. ### SeatLayer runs the box office The recommended path for a venue without a ticketing system it wants to keep. Online payment runs through the venue's own eligible connected Stripe or Razorpay account. - Online checkout and the counter sell from the same house - SeatLayer creates orders and per-seat tickets, printed or emailed - Refunds, house blocks, reporting and the door all read one performance [See the hosted buyer journey →](https://seatlayer.io/sell-tickets-on-your-website/) ### Keep the point of sale you already use For teams with a ticketing or POS product they are not replacing. Your system reads live availability, takes the money, and confirms the exact seats server-side with a stable booking reference. - Your POS owns the order, the ticket, the refund and the patron record - box-book is atomic across the requested seats and idempotent on replay - Cancellation is not a refund: you handle the money, SeatLayer returns the seats [Read the counter-sale API →](https://docs.seatlayer.io/server-api/cancellations-and-box-office/) Either way, one thing never splits: the seats. In SDK mode the shared result is inventory only — your point of sale stays the authority for commerce and fulfilment. ## One record follows the patron to the door. Five steps, one performance. No step keeps a seat allocation of its own. 1. Put the performance on sale Set the date, the prices, the published chart and when sales open and close. **Put the performance on sale** 2. Sell online Patrons pick their exact seats and pay through the venue's eligible connected Stripe or Razorpay account. **Sell online** 3. Sell at the counter Serve the walk-up from live availability and record how you were paid — cash, card taken on your own terminal, or a comp. **Sell at the counter** 4. Look after the order Find the booking, resend or reprint the tickets, and refund an online payment with the seats released back to the house. **Look after the order** 5. Work the door Scan the ticket on a phone, admit the patron, and keep attendance separate from what was sold. **Work the door** ## Everything after the sale, on the same house. What a duty manager actually reaches for on a show night. ### Orders and tickets Find a booking by name or reference, check what was paid, resend the confirmation, or open and print the per-seat tickets. ### The counter Serve the walk-up queue from current availability, record cash, an external card or a comp, and hand over tickets on the spot. ### Control Room Watch the house fill in real time, block and release house seats, close a section, and read the audit trail behind every change. ### Door and reporting Scan at entry on staff phones, then read authorized performance totals and export them for the finance office. - Valid - Used - Void - Wrong event Want these controls inside your own product? SeatManager mounts in the same page with a short-lived, event-scoped, origin-bound manage session. Account secrets stay on your server. [Embed the operator board →](https://docs.seatlayer.io/platform/seat-manager/) SeatLayer covers the reserved-seat journey from first selection to the door. Fixed Renewable Seasons are available on the separate SDK path. SeatLayer is not a theatre CRM, membership, donor, fundraising, email-marketing, concessions, merchandise, accounting, volunteer, scheduling, or general-admission suite. Managed Ticketing includes the first 200 confirmed Hosted Tickets free once per organization, then $0.50 USD or ₹25 INR each; its wallet is separate from Platform/SDK credits. Access requires a request, staff approval, and Hosted Checkout (hosted_checkout) enablement. On the Platform/SDK path you get 100 free SDK seat credits every month, then prepaid credits from 10¢ down to 5¢ per confirmed sold seat, which never expire, with no subscription. [Compare Managed Ticketing and SDK pricing →](https://seatlayer.io/pricing/) ## Questions a box office manager asks first. ### Can online and box-office sales share one seating chart? Yes. One performance holds one live house. Online checkout, the counter, active holds, house blocks and sold seats all read and write the same reserved-seat inventory, so a walk-up sale takes the seat off the buyer's screen at once. There is no second box-office allocation to reconcile. ### Does the counter take card payments? Not inside SeatLayer. Online checkout charges through the eligible connected Stripe or Razorpay account assigned to the performance. At the counter, authorized staff record cash, card already taken on the organiser's own terminal, or a complimentary sale; the SeatLayer counter does not charge the card. ### Can staff print or email tickets at the counter? Yes. A counter sale creates a real order and per-seat tickets with QR credentials. Staff can email the patron, or open and print the tickets when a walk-up gives no address. An email address is optional for a counter sale. ### Can I scan tickets at the door with a phone? Yes. Door check-in runs in the browser on a staff phone or tablet, with no app to install. Every scan is scoped to the performance and answers valid, used, void or wrong event, and check-in stays separate from sale state so admitting a patron never changes what was sold. ### Can I hold house seats or issue comps? Yes. Authorized staff block seats for house seats, press, production or accessibility holds and release them again through guarded actions, and a blocked seat is off sale everywhere at once. A comp is recorded at the counter as a complimentary sale, so the guest still gets a real per-seat ticket. ### Does it cover CRM, subscriptions or general admission? Fixed Renewable Seasons cover immutable 2–20-event Plans, same-seat booking, incumbent Seat Rights, and renewal offers through the SDK path. The host keeps pricing, checkout, orders, tickets, refunds, and patron identity. SeatLayer is not a theatre CRM, membership, donor, fundraising, email-marketing, concessions, accounting, volunteer, scheduling, or general-admission suite. ## Open the house on one inventory. Request Managed Ticketing for a staff-approved hosted flow, or wire your existing counter to the same seats. [Request Managed Ticketing](https://app.seatlayer.io/) [Connect your own POS →](https://docs.seatlayer.io/server-api/cancellations-and-box-office/) [Theatre ticketing The performing-arts workflow](https://seatlayer.io/performing-arts/) [Sell on your site The hosted buyer journey](https://seatlayer.io/sell-tickets-on-your-website/) [SDK & API Keep your own checkout](https://seatlayer.io/developers/) [Pricing Hosted tickets and credits](https://seatlayer.io/pricing/) --- _Machine-readable site index: [/llms.txt](https://seatlayer.io/llms.txt) · full corpus: [/llms-full.txt](https://seatlayer.io/llms-full.txt)_ _Source page: [https://seatlayer.io/box-office/](https://seatlayer.io/box-office/) · Questions: [Contact SeatLayer](https://seatlayer.io/contact/) · hello@seatlayer.io_