Event Ticketing
v1.0.0
Open live demo → Screens
Overview
A general-admission box office for a venue: shows go on sale with their own ticket types and capacities, a cart holds its tickets for ten minutes so the remaining count drops the moment somebody starts checking out and goes back up if they walk away, and the door answers a scanned code with one of four honest verdicts — good, already checked in and when, another night’s, or never issued. The manifest scaffolds the room, event, ticket-type, order and ticket tables into your connected database and generates the back office around them: every record with full CRUD, refunds and exchanges, and reporting across seasons and rooms. The app you deploy is the box office; the dashboard Adminium builds is the office behind it, from the same data.
Capabilities
- Payments
- Email receipts
- Realtime
What you get
Tables it adds7
- venues
- events
- ticket_types
- orders
- order_items
- tickets
- promo_codes
Created fresh, or mapped onto your existing tables at install.
Pages your dashboard gains4
- DashboardTickets issued, door count and takings, with the sales pace and who just came through.
- EventsA card gallery of shows, with child tabs for ticket types and issued tickets.
- OrdersAn order list beside a detail with what was bought and the tickets it issued.
- DoorValid, checked-in and void tabs, with one-tap check-in and an undo.
Roles it pre-builds2
- organizerPut shows on sale and run them: events, ticket types, orders, issued tickets and promo codes. No settings or role access.
- door-staffRead tonight’s tickets and mark them checked in. Nothing else, and never a price.
Settings you configure4
- Venue name
- Time zone
- Order code prefix
- Cart hold (minutes)
Deploy it
Event Ticketing is a static frontend. Deploy it in one click, or grab the source and host it anywhere. It runs on built-in demo data today and connects to your Adminium instance when the publishable-key API lands.