How Bookitive works
The mental model behind Bookitive — organizations, events, and venues, how money flows, what the commission covers, and what happens automatically.
Five minutes here saves hours later. This page explains the concepts the rest of the documentation builds on.
The three building blocks
- Organization — your company, school, or team. It owns everything: events, customers, venues, money settings, email branding, and your team's access. You can belong to several organizations and switch between them.
- Event — one show, ball, conference, or festival day. Each event has its own ticket types, orders, seating, staff, and settings. Events move through a lifecycle: draft → on sale → past (or cancelled).
- Venue — a reusable description of a place you run events at, with arrangements: named seating layouts (zones, sections, seats) you design once and apply to any number of events. An event gets its own copy, so later edits to the venue never disturb a live event.
Two scopes follow from this. Organization-level pages (customers, payments, team, settings) affect everything; event-level pages (orders, check-in, seating, discounts) affect one event. The sidebar switches between the two automatically as you navigate — see Navigating the app.
How the money flows
Bookitive deliberately never holds your money:
- Buyers pay directly to your bank account — by bank transfer with a QR code and payment reference, or in person at your box office.
- If you connect your bank, incoming transfers match to orders automatically and tickets go out the moment the money arrives.
- There is no payout schedule, no held balance, and no middleman between your buyer's bank and yours.
Bookitive earns a commission per paid online ticket — a small percentage with a per-ticket cap, invoiced monthly. Box-office sales and free tickets cost nothing. The exact rates live in Billing.
"Card" as a payment method means a card terminal at your box office. Bookitive does not process online card payments today — online buyers pay by bank transfer with a QR code, which in the Czech banking world settles quickly and costs you no processing fees.
What happens automatically
A lot of Bookitive runs in the background so you don't have to:
| Automation | What it does |
|---|---|
| Payment matching | Incoming bank transfers settle matching orders and send tickets, around the clock. |
| Reservation expiry | Unpaid reservations release their seats when the deadline passes. |
| Payment reminders | One "don't forget to pay" email per reservation, at your chosen lead time. |
| Waitlist offers | Freed capacity is offered to the queue, first come, first served. |
| Operational alerts | Sold out, near capacity, refund spikes, weekly sales digest — to a shared inbox. |
| Webhook delivery | Order and check-in events pushed to your own systems, with retries. |
Each of these has its own page in the docs; the point here is that once an event is on sale, the selling machine runs itself — you watch the dashboard and run the event.
Who can do what
Access is role-based, at two levels: organization roles (Owner, Admin, Member) cascade to every event, while event roles (Event manager, Box office, Scanner) grant access to a single event — that's how a volunteer gets scanning rights for one night and nothing else. You can also build custom roles from the full permission catalog. See Team.