These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Theme Park Management
- Features
- Admissions and gates
Admissions and gates
Ticket reservations and one-time admission scans.
OverviewAdmission lines×
Theme Park Management · Admissions and gates
New
Admission lines
Admissions
| Parent | Line number | Attendee reference | Quantity | Price USD | Reserved at | |
|---|---|---|---|---|---|---|
| EVN-56063 | 580 | AR-310 | 680 | 80 | 05 Oct | |
| EVN-63281 | 570 | AR-444 | 710 | 310 | 13 Oct | |
| EVN-42025 | 890 | AR-779 | 460 | 260 | 06 Oct | |
| EVN-79495 | 250 | AR-209 | 240 | 660 | 12 Oct | |
| EVN-72806 | 810 | AR-766 | 160 | 660 | 05 Oct |
6 of 6 records
AR-310Admissions · ADM-62449
ParentEVN-56063
Line number580
Quantity680
Price USD80
Reserved at05 Oct
What you can do
Every ticket admits once, and never beyond capacity
Admission lines record each ticket against an event: the attendee reference, quantity, price, when it was reserved and, at the gate, when the guest was admitted along with the provider’s receipt. Reservations are accepted only while the event is open and within its remaining capacity. Each line has its own number, so a ticket can always be traced.
At the gate, a ticket admits once. The first scan records the admission; a second scan of the same ticket is refused, which stops shared screenshots and passed-back tickets. A ticket counts as paid only when a verified payment capture covers its amount. The gate does not decide that a ticket is settled; the payment record does.
How the work is organized
Gate attendants reserve and scan; the payments clerk verifies payments.
- Within capacity. Reservations stop when the event is full.
- One scan. Repeat scans are refused.
- Paid means captured. Settlement depends on verified capture.
What to agree during setup
Agree how tickets reach the system: sold here, imported from your ticketing channel, or both. Agree how group tickets are recorded (one line with a quantity or one line per guest) and what gate staff do with a refused scan. Prepare examples of a normal entry, a repeat scan, a sold-out event and a ticket whose payment never captured.
Check the handoff on an actual case
On a busy Saturday the event reaches capacity at 11:30 and further reservations are refused. At the gate a family’s ticket scans in at 10:05. Half an hour later the same ticket is scanned again at another gate and refused, and the attendant can see when and where it was first used. At close, admitted guests are reconciled against verified payments for the day.
Group tickets work the same way. A school group of forty on one line admits forty people once, and the line records when they came through, so the gate team can answer a teacher’s question about a missing pupil’s ticket from the record.
What your team sees
- Admission lines — Reserved and admitted tickets with attendee, quantity and times.
- Event schedule — Capacity for the day.
Follow the work through
- Admission and payment: From reservation to a settled admission.
Plan integrations with your ticketing channels.
What it keeps track of
Data model- Admissions
- Guest admission lines reserved and admitted against an event.
- Events
- Park operating events with capacity, lifecycle and revision control.
- Payment evidence
- Provider payment events reconciled against event admissions.
Who uses it
Permissions- Gate Attendant
- , Payments Clerk.
- Attendants reserve and scan; the payments clerk verifies payments.
Set up Theme Park Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.