Reporting
Live now, and down to the line.
Two layers that work together: live figures read straight from carts, orders and scans, and a full snapshot rebuilt through the day.
The problem
Reporting is either live but shallow, or detailed but a day old, and the numbers never quite reconcile with the bank.
What we built
Live figures and a full snapshot, built at the level of every cart line, with payouts matched to the orders inside them.
What is actually in it.
Live, as it happens
Read straight from carts, orders and scans.
- Revenue, orders and tickets today against the last trading day
- Active carts and an hourly sales pulse
- Today’s events with capacity, sold and scanned
- The week ahead in expected people
- Alerts for slow pacing, days with no sales, abandoned carts above normal
- Gate-day attendance counting people, not tickets
The snapshot
Rebuilt every two hours, 5am to 9pm, seven days a week.
- Every cart line, ticket, scan, refund line, booking and membership card
- A refresh reports button for an update on demand
- Items that never sold are included, so zero-sales reporting works
- Revenue counted once per cart line, so nothing is double-counted
- Fees split out to every line, with and without GST
- Written inside your own dedicated cloud account
Reports
Built from data that is already there.
- Sales summary by day, item and event, and by run date
- Revenue, quantity or people, by day, week or month
- Group by date, item, category, event, month or financial quarter
- Event dashboards with capacity use, show rate and arrival hours
- An abandoned-cart funnel with lost revenue
- Report access granted per user, so staff see only what they need
Exports
Five full-detail files, back to the very first sale.
- Sales, catalogue, orders, refunds and scans
- Any date range works, because it is built from the snapshot
- Pick a date range and column groups
- Downloaded as one zip, recording how current the data is
- Optional password-protected files
- Sensitive columns only for roles allowed full exports
Analytics and payouts
Sales ad blockers hide, and payouts matched to orders.
- Server-side purchase tracking catches sales ad blockers would hide
- Afterpay purchases tracked even though the customer leaves to pay
- Purchases are never double-counted
- Payments matched to orders every 15 minutes
- Card type, country, receipt, refunds and fraud risk on the order
- A payout report matching each payout to its orders and items
Live from the carts
Revenue, orders and active carts, right now.
Rebuilt through the day
Every two hours, 5am to 9pm, seven days.
Down to the cart line
Fees split out, with and without GST.
Counted once
Revenue per cart line, so nothing doubles up.
Five files, any range
Sales, catalogue, orders, refunds, scans.
Payouts matched
Every payout against the orders inside it.
Reporting questions
How current are the numbers?
Live figures are read straight from carts, orders and scans as they happen. The full snapshot is rebuilt every two hours from 5am to 9pm, with a refresh button for an update on demand.
How detailed does the data go?
To each cart line, ticket, scan, refund line, booking and membership card. Items that never sold are included too, so zero-sales reporting works.
Can we reconcile against the bank?
Yes. Payments are matched to orders every 15 minutes, and a payout report matches every payout to the orders and items in it with gross, fees, refunds and net.
Can we get the raw data out?
Yes. A self-serve export builder produces five full-detail files, for any date range back to the very first sale, downloaded as one zip.
Will ad blockers hide our online sales?
No. Purchase tracking runs server-side, which catches sales that ad blockers and closed tabs would hide, without ever double-counting.
See it running for your venue.
Every demo is built around your venue. We base it on your own website, events and prices, so you can see exactly what changes for your guests and your team.
Request a demo
An honest conversation with the people who built it.