Appearance
Activity
Activity is the operational timeline for taps, QR visits, manual adjustments, WooCommerce and Shopify order actions, failures, blocked attempts, and store-level events.
What To Look For
- Successful point awards
- Failed tap attempts and error messages
- Blocked attempts such as repeat taps stopped by a cooldown window
- QR store visits
- Manual point corrections
- WooCommerce and Shopify order rewards and reversals
- Store and TapiCube context
- Customer identity where available
Filtering
Use filters to narrow by store, TapiCube, status, source, or time period. Source filters include TapiCube taps, manager QR visits, WooCommerce, and Shopify. When opening Activity from a TapiCube, the page should focus on that device’s events.
Common source types:
- NFC TapiCube tap
- manager QR scan
- manual correction
- WooCommerce order points
- WooCommerce reversal
- Shopify order points
- Shopify reversal
- reward claim application
Store and customer identity should be visible whenever available. This matters when a customer earns points at multiple stores.
Blocked Attempts And Failures
Cooldown-protected repeat taps are shown as Blocked, because the platform deliberately stopped a duplicate visit from earning points. These rows are useful for explaining customer behaviour, but they should not be treated as device failures.
Failure rows are useful for support. Common causes include expired tokens, inactive stores, disabled TapiCubes, invalid signatures, and store/device mismatches.
Commerce refunds and cancellations are shown as Reversed so point returns are visible without being confused with new awards or failed scans.
When investigating a failure, check:
- Did the customer receive points anyway?
- Is there a matching successful event near the same timestamp?
- Was the TapiCube assigned to the expected store?
- Was the attempt blocked by a cooldown or threshold?
- Did the mobile app show a success screen or error screen?
- Did the TapiCube console log show an NFC or remote config issue?
Exports
Activity exports should respect the current role, store scope, search, and filters.
Use exports for reconciliation, support investigations, campaign analysis, and store reporting. Avoid exporting more personal data than needed.