Event Ticket Setup: Seated, General Admission and Barcodes

• Choose between seated tickets (with seating plans), general admission tickets (with quantities), or both
• Enable QR code barcodes for ticket scanning at entry
• Set up a ticket request system for events requiring approval
• Offer box office collection for customers who prefer physical tickets
• Define how customers must present their tickets (printed, mobile, or custom instructions)
• Control when tickets stop being available relative to event start time, or at a fixed date and time across every event date
• Decide whether payment processing fees are absorbed or passed to customers

The Ticket Setup editor showing the toolbar with Save button, the Seated tickets section with seating plan and prevent single seats toggles, General admission tickets toggle, and Barcodes section with both barcode toggles enabled

At a glance: You choose your ticketing approach, configure entry options, and set sale timing. Each choice shapes what customers see when booking and what they need at the door.

Think of it this way:

• Ticketing approach determines WHAT customers can buy (specific seats vs entry tickets)
• Entry options determine HOW customers prove they have tickets (scanning, printed, mobile)
• Sale timing determines WHEN customers can no longer purchase

Not sure which approach is right for your event? Our guide on reserved seating vs general admission walks through the trade-offs — accessibility, queueing, perceived value, operational overhead — so you can decide before you commit to a layout.

• Theatre productions with assigned seating
• Concert venues with numbered seats
• Sports events with specific seat assignments
• Formal galas and award ceremonies
• Any event where seat location matters

• Create visual seating plans in the Seating Plan section
• Define seat categories (e.g., Stalls, Circle, Balcony)
• Set prices for different seating areas
• Optionally prevent single isolated seats

• Customers see a visual seating plan
• They click to select their preferred seats
• They can see which seats are available or taken
• Their tickets show exact seat locations

• Standing-room events (concerts, nightclubs)
• Festival-style events with open seating
• Workshops with flexible seating arrangements
• Community events without assigned seats
• Events where arrival order determines position

• Create ticket categories (Adult, Child, VIP, etc.)
• Set quantities available for each category
• Set prices for different categories
• Optionally allow ticket categories to share capacity
• Optionally mark a category as an add-on (e.g. Accessibility, Car Parking) so it only appears once the customer adds an eligible main ticket

• Customers see ticket types and quantities
• They select how many of each type they want
• No seat selection is involved
• Their tickets show ticket type but no seat number

• Events with seated areas plus standing room
• Theatres with reserved seating plus general admission balcony
• Concerts with VIP seated areas and general admission floor
• Multi-zone events with different ticketing needs

• Set up both seated and general admission systems
• Customers can choose between seated and general admission options
• Each approach has separate pricing and configuration

• Customers see both seating plan and general admission options
• They can book either type depending on preference
• Orders can mix both ticket types

• "Yes, use a seating plan" - Enables seated ticketing with seating plans
• "No seating plan" - Disables seated ticketing

• A default seating plan is automatically created
• New sections appear in the Event Editor menu:
  • Seating plan - Design your visual seating chart
  • Seated tickets - Configure seat categories and pricing
• You can design your seating layout using the visual editor

• "Yes, stop single seats" - Blocks bookings that create isolated single seats
• "No, allow single seats" - Allows any booking combination

• Row A has seats 1-10 available
• Customer tries to book seats 2-9
• This would leave seats 1 and 10 isolated
• System blocks the booking and suggests seats 1-8 or 3-10 instead

Note: This only affects customer bookings through the website. Administrators can still book seats that create single seats.

• Theatre productions where most seats should be filled
• Events with high demand where every seat matters
• Venues where single seats are difficult to sell

• Small venues where flexibility is more important
• Events with low expected attendance
• Situations where customer choice is prioritised over optimisation

• "Yes, enable sections" - Allows multiple seating plans per event
• "No, disable sections" - Single seating plan only (recommended)

Note: We strongly recommend keeping this disabled unless you have a large venue that cannot fit comfortably in a single seating plan.

• Simpler customer checkout experience
• Easier event management for administrators
• Faster booking process
• Less complex configuration
• Customers see all seats in one view

• Very large venues (500+ seats) that don't fit in one visual plan
• Multi-level venues where floors are completely separate
• Complex venues with distinct areas that need different layouts
• Venues where customers expect to choose their level first

• You can create multiple seating plans
• Each plan can have different seat layouts and categories
• The editor menu shows each section separately
• Customers choose their section before selecting seats
• Each section can have unique pricing and availability

• Its own name (e.g., "Stalls", "Dress Circle", "Upper Circle")
• Separate seating layout and design
• Independent seat categories and pricing
• Individual background images if needed

1. Customer selects which section they want (Stalls, Circle, etc.)
2. Seating plan for that section loads
3. Customer selects seats from that section
4. They can add seats from other sections separately

• "Yes, I want general admission tickets" - Enables general admission ticketing
• "No general admission tickets" - Disables general admission

• A new section appears in the Event Editor menu:
  • General tickets - Configure ticket types, quantities, and pricing
• You can create multiple ticket categories (Adult, Child, Student, VIP, etc.)
• Each category can have its own quantity and pricing

• Create ticket categories with names and descriptions
• Set available quantities for each category
• Configure pricing for different categories
• Choose whether categories share capacity or have independent quantities
• Assign categories to specific event dates

• "Yes, show barcodes" - Adds QR codes to all tickets
• "No, disable barcodes" - Tickets have no barcodes

• Quick ticket validation at venue entrance
• Prevents ticket fraud and duplication
• Track which tickets have been scanned
• Reduce queuing time at entry
• Mobile app provides real-time scanning reports

• Professional events with organised entry management
• Events where ticket fraud is a concern
• Venues with staff who can use the mobile scanning app
• Multiple entry points that need coordination

• Informal community events
• Very small gatherings where everyone is known
• Events without smartphone-equipped door staff

• "Yes, include barcodes on email" - QR codes appear in confirmation emails
• "No, do not include" - Emails contain order details but no barcodes

• Customers can show email on mobile device at entry
• No need to print tickets or visit separate ticket page
• Convenient for customers who book on desktop but attend with mobile
• Reduced support queries about "where's my ticket"

• Email file size increases slightly with QR code images
• Some email clients may not display images correctly
• Customers should still be directed to view full tickets on Seaty website as backup

The Ticket Setup editor showing Ticket requests with password protection enabled and requesting password field, Waiting list toggle, and the start of Ticket collection details

• "Yes, let users request tickets" - Enables the ticket request system
• "No ticket requests" - Only direct ticket purchases allowed

1. Logged-in Seaty users visit your event
2. They submit a ticket request specifying quantity and preferences
3. You receive requests in the Seaty app or website admin panel
4. You manually approve or decline requests
5. You collect payment outside of Seaty
6. You manually allocate tickets to approved requesters

• Free events where you want to track interest
• Internal company events with manual allocation
• Member-only events with approval workflows
• Events where payment is collected separately (e.g., on the door)
• Community events with limited capacity requiring approval
• Events when those participating sell most of your tickets

Note: Requesters must have a Seaty account and be logged in. You must manually process all requests, and payment collection is your responsibility.

• "Yes, password protect requests" - Requires password to request
• "No anyone can make a request" - Any logged-in user can request

• Limit requests to specific groups (staff, members, invitees)
• Prevent spam requests from random users
• Control who knows about the event
• Invitation-only events with controlled access

• You set a password in the "Requesting password" field (up to 100 characters)
• Users must enter this password before submitting a request
• Organisation members can always request without password
• Password is shared separately with eligible requesters

Note: If your organisation has "Member Only Requests" enabled in organisation settings, the password option is hidden and only organisation members can request tickets.

• "Yes, enable waiting list" - Customers can register interest when tickets are unavailable
• "No, disable waiting list" - No waiting list option shown

1. Tickets sell out or become unavailable for a date
2. Customers see an option to join the waiting list
3. They register their interest with their contact details
4. You can view and manage waiting list entries from the admin panel
5. When tickets become available, you contact waiting list customers directly

• Events likely to sell out
• Events where cancellations may free up tickets
• Events where you want to gauge additional demand
• Situations where you may release more tickets later

• Events with plenty of available tickets
• Events where you do not plan to release additional capacity

• "Yes, offer collect at box office" - Adds box office collection option
• "No, we do not offer this service" - Digital/printed tickets only

1. During checkout, customers see an option to collect at box office
2. If selected, they complete their order online but collect tickets at venue
3. You receive a notification that tickets need preparing
4. On event night, tickets are available at box office
5. You're responsible for having tickets ready for collection

• Prepare physical tickets for collection
• Staff box office appropriately
• Verify customer identity at collection
• Track which tickets have been collected
• Handle collection on the correct event date

• Traditional venues with established box office operations
• Events where some customers prefer physical tickets
• Venues with pre-event box office opening hours
• Events with older demographic who expect this option

• Events without physical venue presence
• Pop-up or temporary venue situations
• Events with limited staff for box office
• Modern events targeting digital-native audiences

The Ticket Setup editor showing Ticket collection details with box office toggle, Admission options with four mutually exclusive types, and Tickets off-sale timing with Minutes input

Note: You must choose exactly one admission type for your event. These are mutually exclusive options.

• You accept both printed and mobile device tickets
• You want maximum flexibility for customers
• Your entry staff can scan or view tickets from screens
• You use barcodes for ticket validation

• You only accept physical printed tickets
• Mobile devices cannot be accommodated at entry
• Your scanning equipment requires paper tickets
• Traditional venue with established printed ticket policy

• Seaty is used only for allocation and payment
• Venue issues its own official tickets separately
• There's a pre-event box office exchange process
• Venue requires its own branded tickets

• None of the standard options fit your needs
• You have unique entry requirements
• You need to provide specific instructions
• Your venue has special admission procedures

• "Show this ticket on your phone at entrance. ID may be required for age-restricted events."
• "Bring this ticket on your mobile device. Exchange for wristband at entry desk."
• "Present this confirmation at registration desk to receive your access badge."

• 0 minutes - Tickets go off sale exactly when the event starts
• Negative number (e.g., -30) - Tickets go off sale 30 minutes BEFORE event starts
• Positive number (e.g., +60) - Tickets remain on sale 60 minutes AFTER event starts

• Use for: Events where you need time to prepare final counts
• Example: Catered events requiring final numbers in advance

• Use for: Most traditional events
• Example: Theatre productions, concerts with strict start times

• Use for: Events that can accommodate late arrivals
• Example: Film screenings, exhibitions with flexible entry

• Use for: Events with late seating or rolling entry
• Example: Exhibitions, networking events, some concerts

• Use for: All-day events or events with continuous entry
• Example: Festivals, day-long workshops, open-house events

• Food events: Consider -60 to -90 minutes for catering counts
• Theatre: Typically -30 minutes for house management
• Festivals: Often +60 to +180 minutes for rolling entry
• Workshops: Depends on whether late arrivals disrupt others

• Customers see "Tickets no longer available" after cutoff time
• Last-minute bookings may be prevented
• Creates urgency for advance booking

• Provides time to prepare final arrangements
• Reduces last-minute administrative burden
• Allows late sales if your event supports it

• "Sales end at a specific date and time" - Choose a date and time when sales close across the whole event
• "No absolute cut-off" - Sales follow only the per-date Minutes rule (default)

• When the chosen date and time arrives, ticket sales stop for every date attached to this event
• Administrators can still place orders after the cut-off (the same way they can after the Minutes cut-off)
• Customers see "Ticket sales for this event have ended" instead of the per-date message
• Event listings show a "Sales ended" badge and disable the Get Tickets button
• Before the cut-off, customers see "On sale until..." on listings and at checkout

• Multi-day camps and courses - One registration deadline for the whole programme (e.g. rugby camp running across five dates, but registration closes on a single Friday)
• Open-day style events - Multiple drop-in sessions sharing one RSVP deadline
• Conferences and retreats - Sign-ups close at one fixed moment regardless of which day a person plans to attend
• Group package events - When you need final numbers committed by a specific date for catering, accommodation, or kit ordering

Note: The cut-off uses your event's time zone, the same as every other date setting on the event.

The Ticket Setup editor showing Tickets off-sale timing with Minutes input field, and Online payment options with fee absorption toggle and real-time fee example calculation panel

• You include the payment processing fee in your ticket price
• Customers pay the ticket price you set
• Your payout is reduced by the processing fee
• Simpler pricing for customers

• Two £10.00 tickets = £20.00 customer pays
• Seaty fee (e.g., 5%) = £1.00
• You receive = £19.00

• Customers pay ticket price PLUS payment processing fee
• Fee is added at checkout
• Your payout is the full ticket price
• Fee is shown separately to customers

• Two £10.00 tickets = £20.00 ticket cost
• Seaty fee (e.g., 5%) = £1.00
• Customer pays = £21.00
• You receive = £20.00

• You want simple, transparent pricing
• Your margins can accommodate the fee
• You want to reduce checkout abandonment
• Your customers expect the price shown to be the price paid

• You need every penny of the ticket price
• Your customers understand processing fees are normal
• You're comfortable with slightly higher checkout totals
• You want to maximise revenue

• Many commercial events pass fees to customers
• Non-profit events often absorb fees to appear more accessible
• There's no single "correct" approach

• Seated tickets on or off
• General admission tickets on or off
• At least one ticketing approach enabled

• Both seated and general admission are disabled (event needs at least one ticket type)

1. Configure your ticket setup options
2. Click "Save" button in the top right
3. Wait for "Saving event..." then "All done!" messages
4. Your event reloads with saved changes

Note: You must save manually - there is no auto-save. Unsaved changes are warned when leaving the page. Changes apply to the entire event across all dates.

• Disabling seated tickets when orders exist will cause issues
• Changing admission types affects customer expectations
• Always save carefully when events have existing orders

• Seat location matters to customers
• You have a traditional theatre or venue with numbered seats
• You want to prevent overselling specific areas
• Customers expect to choose their seat

• It's standing room or flexible seating
• Seat location doesn't matter
• You want simpler booking process
• Event has open seating arrangement

• You have distinct seated and standing areas
• You offer premium seated tickets plus general admission
• Venue has multiple zones with different ticketing needs

• Simpler for customers to understand
• Faster booking process
• Easier for you to manage
• Less complex configuration

• Venue is genuinely too large for one plan (500+ seats)
• Completely separate physical areas (different floors)
• Customers specifically expect to choose their section first

• You have staff with smartphones who can scan
• Entry management and validation is important
• You want to prevent ticket fraud
• You need to track which tickets have been scanned

• Informal event where everyone is known
• Very small gathering
• No smartphone-equipped door staff
• Manual checking is sufficient

• Food/catered events: -60 to -90 minutes for final counts
• Traditional theatre: -30 minutes for preparation
• Exhibitions/festivals: +30 to +120 minutes for rolling entry
• Workshops: Depends on whether late arrivals disrupt

• Too early: Customers frustrated they can't buy last-minute
• Too late: You struggle with last-minute logistics
• Sweet spot: Enough time to prepare, close enough to capture impulse buyers

• You have many event dates but need one shared deadline (e.g. a registration window that closes once)
• You need final numbers locked in by a specific calendar date for catering, kit, or accommodation
• The natural deadline is unrelated to any single event date

• You want simple, transparent pricing
• Your margins support it
• Customer-facing prices matter more than backend revenue
• You want to reduce checkout abandonment

• You need every penny of ticket revenue
• Industry standards support it
• Customers in your sector expect processing fees
• You want to maximise revenue

• Choose admission type that matches your entry process
• If using custom wording, be specific and helpful
• Consider how customers will actually present tickets
• Match technology expectations (mobile vs printed)

• Only offer if you genuinely have staffing and process
• Ensure collection hours are clear
• Have backup plan for missed collections
• Consider cost vs customer benefit

• Only enable if you'll actually process requests promptly
• Make password available to intended users
• Set expectations about approval timing
• Remember payment is your responsibility