Number of sold tickets does not match the number in the Check-in app
you ran a check-in event, and the count of sold tickets in your Tickera dashboard doesn’t match what Checkinera shows. Either Checkinera is short (you’re worried it missed sales) or it shows more than dashboard says (rare but happens). Either way, before the doors open, you need to know it’s accurate.
The two real causes
In our experience this comes down to one of two things almost every time.
Cause 1: caching
If a caching plugin (WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache) is caching the REST API endpoints Checkinera reads from, the app pulls a stale snapshot — tickets sold in the last hour aren’t visible.
Fix: exclude Tickera pages and the REST API from caching. Every major caching plugin has an “Exclude URLs” or “Never cache these pages” setting. Add at minimum:
/wp-json/*(the REST API root)/tickera-*(Tickera pages — events, checkout, account)
See configuring caching plugins for plugin-by-plugin specifics.
Cause 2: deleted ticket types
If you deleted (or set to private) a ticket type after tickets of that type were already sold, those tickets become unusable — they don’t have a valid ticket-type record to attach to. They show in the order history but Checkinera can’t match them against a current ticket type.
Do not delete ticket types — or, in Bridge for WooCommerce mode, the WooCommerce products that act as tickets — until after the event has finished check-in. If you need to stop selling a ticket type mid-campaign, set the sale-window end date to the past instead of deleting the type — sale stops, existing tickets remain valid.
Other things worth checking
- Refunded tickets. Tickera marks refunded tickets as canceled — they don’t count in Checkinera’s expected total. Reconcile by subtracting refunds from raw sold count.
- Pending orders. Orders in “Processing” or “Pending” status haven’t generated tickets yet. They show in dashboard reports but aren’t in Checkinera until paid.
- Checkinera sync state. The app caches data locally. Pull-to-refresh in the app forces a fresh sync — useful before the doors open.
- Multiple Checkinera installs. If you have three iPads scanning at three doors, each has its own local sync. Each device should refresh before doors.
Best practice: refresh just before doors open
Sales often spike in the last hour before the event. Make a habit: pull-to-refresh every Checkinera install ~10 minutes before doors. Whatever drift existed clears, and the count matches reality at door-open.
Related
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.