Rule-based loyalty, tickets, and redemptions.
Programs you compose, not templates you settle for. Every ticket, coupon, and redemption is a rule — time, zone, item, staff, customer tier, spend threshold, stacking logic. Compose them, ship them, change them mid-show.
Paper tickets and clipboards don’t scale.
At a 50,000-person festival, comps and coupons run in the thousands per shift. Sponsors expect itemized redemption data the morning after. Auditors want it down to the second.
The old way: print drink tickets at a Kinko’s, hand a stack to a vendor, and reconcile a pile at 4am. Every missing ticket is a missing dollar. Every fake ticket is a theft you can’t prove. Sponsor reporting is a spreadsheet built from memory.
The Zerobeat way: tickets and coupons are first-class objects in the POS. Issued from the operator console, scoped to zones, items, or time windows, and redeemed at the terminal exactly like a card payment. The redemption stream is auditable to the second, by staff, by zone, by ticket lot.
A redemption stream you can watch.
Every ticket and coupon punch lands on this list within seconds. Filter by zone, vendor, sponsor, or ticket program. Export to CSV at wrap.
Three primitives. A thousand programs.
Tickets, coupons, and redemption tracking. Compose them to run any program your promoter, sponsor, or operations team can dream up.
Ticket programs
Pre-paid bundles for sponsors, staff, vendors, VIPs. Issued in batches, scoped to a zone or an item, redeemed at any terminal in seconds.
- Sponsor activations (5,000 Modelo drink tickets)
- Staff & crew comp programs
- VIP bundles (e.g. 4 drinks + 1 meal)
- Group sales (corporate, hospitality)
Coupons
One-time or unlimited-use codes, scoped to items, zones, vendors, or time ranges. Issued in advance or generated on the floor.
- Pre-purchase bundles (ticket + drink credit)
- Re-engagement codes (return-customer offers)
- Manager-triggered comps (apology, service recovery)
- App push promos with redemption windows
Redemption tracking
Every punch logged with timestamp, staff PIN, zone, terminal, and value. Per-vendor, per-sponsor settlement drops out of the system at wrap.
- Live stream visible on operator dashboard
- Per-sponsor itemized reports
- Per-zone reconciliation
- CSV export with full provenance
From idea to live in 45 seconds.
Watch a sponsor activation come together. Type the name, set the value, layer in the rules. The same flow runs in the operator portal — what you see here is the actual shape of it.
Programs are rules, not templates.
Every ticket and coupon is a composition of rules. Change the rule, change the program — live, no redeploys. Stack rules to model anything from a one-night sponsor activation to a multi-day VIP tier.
Time windows
Active 9pm–11pm. Day 2 only. Last 30 minutes of the show. Schedule, expire, blackout — to the second.
Per-zone scoping
Redeemable at the VIP bar but not the main gate. Only food trucks 3 and 7. Different rules per zone.
Per-item targeting
Only Modelo. Only beer. Only items tagged 'sponsor menu'. Item-tag matching with regex if you need it.
Vendor honors
Sponsor coupon redeems against Burger Co. only. Vendor sees per-coupon settlement at wrap.
Redemption caps
Max 2 per customer. Max 5 per cashier per shift. Max 50 per zone. Limits enforce in real time across the mesh.
Customer tier
VIP wristband only. Crew badge only. Press pass only. Tier checks at the terminal via RFID, app token, or QR.
Spend thresholds
10% off when order > $50. Free dessert with any entrée. Buy 4 drinks get the 5th — math that adapts to the order.
Stacking logic
Coupon + drink ticket: yes. Coupon + comp: no. Define exactly which rules can combine. Conflicts resolve at the terminal in one rule pass.
Live overrides
Manager taps Override. Cashier types a PIN. Manager approves at their terminal. Logged to audit. The program adapts to the night.
The rules engine evaluates in milliseconds at the terminal, not on a round-trip to the cloud. The cashier hits Apply, the rules run, the eligible programs surface, the order updates — all under one frame. When the venue is dark, the mesh holds the rule set in sync across every device so the math comes out the same no matter who rings the order.
From ticket issued to dollar settled.
Five steps, end to end. Each one ties back to a PIN, a terminal, a second.
- 01
Issue
Operator creates a program from the console. Type, quantity, value, scope (zones / items / time / customer tier). Tickets generate with unique IDs and a barcode or QR.
- 02
Distribute
Print at intake, email to attendees, hand off to a sponsor as a digital batch, or push to the app as a wallet pass. Whatever the distribution channel, the codes flow through one source of truth.
- 03
Redeem
Cashier rings the order, hits Apply, scans or keys the ID. The POS evaluates the rule set in milliseconds, applies the value, confirms — even when the venue uplink is down.
- 04
Track
Redemption logged in real time on the operator dashboard, streamed to anomaly detection, and tied to the staff PIN. Live across every site in the org.
- 05
Settle
At wrap, per-sponsor and per-vendor settlement reports drop. CSV export for accounting. Sponsor sees what they paid for. Vendor sees what they owe.
What operators ask first.
Can tickets be scoped to specific items, zones, or vendors?
Yes. Every program defines its scope at creation — which items it applies to, which zones can redeem it, which vendors honor it, and what time window it's live in. The POS enforces all of it at the terminal in real time.
What's the difference between a ticket and a coupon?
Tickets are pre-paid bundles — typically issued at intake or sold up-front, with a defined number of redemptions per ticket. Coupons are codes — typically issued on the marketing or service-recovery side, redeemable per the rules of the code. The redemption tracking is the same primitive underneath.
Can we report on what a specific sponsor delivered?
Yes. Each ticket program ties to an owner — sponsor, vendor, internal department. Per-sponsor reports show issued count, redeemed count, dollar value, where redeemed, when. Drop it in a deck the morning after the show.
How do we prevent fake or duplicate tickets?
Every ticket has a unique ID with a checksum. The POS validates against the live database at redemption — duplicates and unknowns are rejected. Even when the venue uplink drops, the mesh holds a consistent view of redeemed IDs across terminals.
Can a staff member issue a comp on the floor?
If you give them the permission. Role-based access controls who can issue comps and at what dollar threshold. Manager-level can comp up to $X without approval, lead-level a smaller amount, cashiers none. All comps log to the audit trail.
Does it work offline?
Yes. Tickets and coupons issue, validate, and redeem through the mesh. Even when the venue is fully dark, redemption state stays consistent across terminals and reconciles when connectivity returns.