Reports the operator actually opens.
Live during the show. Ready before the lights come up. Sales, items, staff, tax — all of it reconciles to the PIN, to the terminal, to the second. Custom queries in plain English.
Reports that drop next week don’t change what you do tonight.
The traditional POS report is a CSV the back office gets on Monday for a show that ended Saturday. By then the bartender who was comping their friends is gone, the sponsor who needed redemption proof has moved on, and the over-ordered keg is already paid for. Reporting that arrives after the fact has the wrong half-life.
Zerobeat is built on the opposite stance. Every transaction streams to the dashboard the moment it clears. Every redemption, void, comp, break, and tip lands in the same ledger. The operator decides during the show, not after.
Eight reports your operator opens before midnight.
Live during the show, exportable to CSV at wrap. Every row ties back to a PIN, a terminal, a zone, a second.
Sales
Daily, weekly, monthly summaries. Live drill-down by zone, station, vendor, item. Every dollar reconciles to a specific terminal and a specific PIN.
Top items
Per-item revenue, units, attach rate. Compare against last show, last weekend, last year. Catch a slow seller before you over-order it next week.
Staff
Per-staff sales, hours, breaks, tips, voids, speed. Tied to PIN authentication so accountability lands on the actual cashier.
Payments
Method breakdown by zone and shift — card, cash, ticket, coupon, comp. Reconciliation rows that match the deposit your bank actually receives.
Tax
Collected tax by jurisdiction and category. Export ready for filing. Multi-state, multi-rate, multi-tax-class all handled inline.
Custom queries
Ask your data anything. Natural language with Pulse, or raw SQL if you have it. No BI seat, no data team standup, no Looker dashboard to build.
CSV export
Every report exports to CSV. Standard accounting integrations work in minutes. Quickbooks, NetSuite, Xero — open the file, do the rest.
Operator dashboard
The 6 numbers an operator looks at first: revenue, tickets, avg ticket, gross margin, active terminals, anomaly count. Live on every device.
Plain English in. Data out.
Pulse queries the operational store directly. No SQL, no BI seat, no dashboard to wire up. Ask what you want to know; the answer lands with the numbers, the source, and the action chip.
CSV out. API for the rest.
Every report exports to CSV. Standard accounting integrations work in minutes. For deeper integrations, the REST API and webhooks deliver the same data in real time.
CSV export
Every report. Standard headers. Opens in Excel, Sheets, Quickbooks, NetSuite, Xero. No conversion, no scripts.
REST API
Programmatic access to the same data the dashboard reads from. Token auth, pagination, rate limits, the whole standard set.
Webhooks
Outbound events for orders, refunds, comps, alerts, shift transitions. Subscribe to what you care about, ignore the rest.
Scheduled drops
End-of-shift reports auto-emailed to the finance team. Per-sponsor settlement reports to each sponsor. Set once, runs every event.
What operators ask first.
How fresh is the dashboard data?
Live. Transactions stream from the terminal to the dashboard the moment they clear. There's no batch window. The number you're staring at on the dashboard is the number that just rang at the bar.
Can I query data that spans multiple sites?
Yes. Reports roll up across the organization. Pulse queries can scope to one site, to a portfolio, or to the full org. Per-sponsor reports span every site the sponsor's tickets were valid at.
Does Pulse just write SQL under the hood?
Pulse generates a structured query, runs it against your operational store, returns the answer, and shows you the source rows on request. If you want raw SQL, the same store is queryable through the API.
How does tax reporting work for multi-state events?
Tax rules attach to the menu item and the location. Sales emit tax lines per jurisdiction. The tax report rolls up by state, county, city, and category. Drop the CSV into your filing tool of choice.
Can I customize the operator dashboard?
Yes. Each org can pick which KPIs surface on the overview, which charts pin to the top, and which alerts route where. Per-user dashboards are also supported for venues with distinct manager roles.
What about retention and audit?
All reporting data retains for the lifetime of your subscription. Underlying transaction records are immutable and chained to the audit log. You can export the lot at any time.
How do reports work when the venue was offline?
The mesh queues transactions and reconciles when connectivity returns. The dashboard catches up automatically; reports stamp the original transaction time, not the sync time. Time-of-sale stays accurate.