Check-in rules
you want to control precisely how each ticket may be used at the door — once, several times, only in a window, or once per day.
Check-in rules decide whether a ticket is allowed in right now. They’re part of the Venuera core, so they behave identically in the Check-in app, the POS and the admin — and offline.
Three rules, three layers
Each ticket is governed by three rules, resolved from a global default → a per-event override → a per-ticket-type override. Set the broad policy once and override only where needed.
1. Max entries
How many times a ticket may be used: single (1), a fixed number (N), or unlimited (0). A single-entry ticket scanned again returns Already used; an N-entry pass returns Max reached once it’s spent.
2. Availability window
When the ticket may be scanned at all. The modes, all computed in UTC so they’re correct across time zones:
- Open-ended — always valid.
- Event window — from N minutes before the start to N minutes after.
- Upon start — from the event start onward.
- Time after order — valid for N minutes after purchase (timed-entry vouchers).
- Time after first check-in — once first used, valid for N more minutes (re-entry passes).
- Date range — only between two specific dates/times.
Outside the window a scan returns Not open yet or Window closed.
3. Per-time-basis limit
A cap like one entry per day for a multi-day pass — configurable per hour, day, week or month, and either rolling (the last 24 hours) or calendar (resets at local midnight). Hit the cap and the scan returns Limit reached until the next period.
Recurring events
For a recurring series, each ticket knows its occurrence, so the wrong-night ticket returns Wrong event and time-based windows open and close around the correct date automatically.
Every result
A scan returns one of: Entry allowed, Already used, Max reached, Not open yet, Window closed, Limit reached, Wrong event, or Invalid (refunded/cancelled). The same codes drive the colour and message on the door screen.