Scan Settings: Configuring Mobile Door Scanning

• Control camera torch for low-light venues
• Choose between front and rear cameras
• Enable audio and vibration feedback for scan results
• Set delays between scans to prevent double-scanning
• Enable offline scanning for venues with unreliable internet
• Synchronise preferences across all your devices

At a glance: You adjust settings once, and they apply immediately to scanning. Your preferences synchronise to all devices signed into your account.

Think of it this way:

• Camera settings control how you capture QR codes
• Feedback settings tell you what happened without watching the screen
• Behaviour settings control the scanning workflow
• Offline settings prepare for unreliable internet

• Enabled: Torch activates when you start scanning
• Disabled: Torch remains off during scanning

• Low-light venues (theatres, evening events)
• Outdoor events after dark
• Dimly lit entrance areas
• Reading printed QR codes with low contrast

• Well-lit entrances with natural/artificial lighting
• Daytime outdoor events
• Battery conservation required
• Front camera in use (torch not available)

Note: The torch automatically turns off when you release the scan button to conserve battery.

• Higher quality camera sensor
• Better focus and low-light performance
• Torch support available
• Natural scanning angle for door staff

• Self-service scanning by customers
• Face-to-face interaction with staff visible
• No torch support
• May struggle with focus in some lighting

• Rear camera: Standard door scanning by staff
• Front camera: Customer self-check-in kiosks

• Compact preview for experienced scanners
• More screen space for scan history
• Lower battery consumption
• Faster on older devices

• Balanced view of camera and history
• Good QR code targeting without strain
• Moderate battery usage
• Suitable for most scenarios

• Maximum visibility for QR code alignment
• Helpful for new staff learning to scan
• Higher battery consumption
• Less visible scan history

Note: Medium provides the best balance. Use large for training or high-precision scanning.

• Success chime for valid tickets
• Neutral tone for warnings
• Alert sound for errors
• Helps staff scan without watching screen

• Silent operation
• Rely on visual feedback only
• Suitable for quiet venues or formal events

• Noisy entrance areas
• High-volume scanning (audio confirms each scan)
• Multiple staff members sharing devices
• Training new scanners

• Theatre performances in progress
• Formal events requiring discretion
• Quiet venues where sound is disruptive
• Staff preference for silent operation

• Vibration feedback for warnings and errors
• Helps confirm scans without watching the screen

• No vibration feedback
• Rely on visual and audio feedback only

• Very noisy environments where audio feedback is inaudible
• Discreet feedback required (can feel vibration without sound)
• Battery not a concern
• Staff prefer tactile confirmation

• Battery conservation required
• Device in pocket or holder (vibration not felt)
• Staff find vibration distracting
• Using shared scanning device

• Immediate scanning available after previous scan
• Fastest throughput for high-volume entry
• Risk of accidental double-scans if QR code remains visible

• Brief pause prevents most double-scans
• Good balance for standard entry flows
• Countdown visible on screen

• Recommended for less experienced staff
• Gives time to check result before next scan
• Prevents rushed scanning

• Maximum protection against double-scans
• Time to verbally interact with each attendee
• Slower throughput but more deliberate

• Countdown timer shows on screen
• Camera remains active but scans are ignored
• Release scan button to cancel delay early

Recommendation: Start with 0 seconds for experienced staff. Use 1-2 seconds during training or for venues where customers might present tickets multiple times.

• Valid tickets are automatically marked as checked in
• Fastest workflow for door entry
• Timestamp and scanner recorded automatically
• Attendee appears in attendance reports immediately

• Scanning only validates the ticket
• Manual check-in required via toggle
• Useful for pre-scanning tickets before doors open
• Testing mode without affecting attendance data

• Standard door scanning operations
• Real-time attendance tracking required
• Automated workflow preferred
• Event in progress

• Testing scanner setup before event
• Pre-validating tickets before entry time
• Training staff on scanning workflow
• Validating tickets without recording attendance

Note: This setting only affects regular tickets. Merchandise vouchers are never automatically redeemed - manual redemption always required.

• Allows downloading ticket data for offline validation
• Enables hybrid mode (online with offline fallback)
• Shows offline data management options
• Ticket data stored locally on device

• Online-only scanning
• Requires internet connection for all scans
• No local ticket data storage
• Simpler setup if internet is reliable

• Venue has unreliable internet connectivity
• Backup strategy for potential network failures
• Remote locations with poor cellular coverage
• Large events that may overwhelm venue bandwidth

• Venue has reliable, fast internet
• Preference for always-online validation
• Device storage space limited
• Simplified scanning preferred

Important: Enabling offline scanning does not force offline mode. Scans will still attempt online validation first unless "Force offline mode" is also enabled.

• All scans validated locally, never sent to server
• Scans are NOT recorded on server
• Useful for testing without affecting production data
• Requires offline data to be downloaded

• Hybrid mode: online validation with offline fallback
• Scans recorded on server when internet available
• Best of both worlds approach

• Testing scanning workflow without recording real scans
• Rehearsing event procedures
• Demonstration mode
• Privacy-focused scenarios where server recording not desired

• Normal event operations
• Server recording and reporting required
• Prefer online validation when available

Warning: Scans performed in force offline mode will NOT appear in server-side reports, analytics, or audit trails. Only use for testing or when server recording is explicitly not required.

1. Select event and date/time range
2. Choose specific sections (if desired)
3. Download ticket data whilst online
4. Monitor download progress
5. Data stored locally and expires after 7 days

• By Event Date: Download tickets for specific performance
• By Day: Download all performances on a calendar day
• By Section: Download only certain seat categories
• Full Event: Download all tickets for entire event run

• Each ticket requires a small amount of storage
• Large events with thousands of tickets need more space
• Expired data is automatically cleaned up

• See which events have offline data available
• Check how many tickets are cached
• View last download timestamp
• Check data expiry date
• Navigate to specific tickets

• Event completed and data no longer needed
• Storage space required on device
• Refreshing data after significant order changes
• Troubleshooting offline validation issues

1. Select the event
2. Choose "Scan entire day"
3. Pick the date from calendar
4. Scanner accepts tickets for any performance on that date

• Multiple performances per day
• Don't know exact performance times
• Customers arriving early or late
• Flexible entry policies

• Tickets for any performance on selected day are valid
• Tickets for other dates show clear error message
• Attendance tracking recorded per performance, not per day

1. Select the event
2. Choose "Scan event date & time"
3. Pick the specific performance from list
4. Scanner only accepts tickets for that exact performance

• Strict performance separation required
• Reserved seating for specific times
• Multiple concurrent performances
• Need precise attendance per show

• Only tickets for selected performance are valid
• Tickets for other performances show "wrong date/time" error
• More strict validation than day mode

• Torch enable/disable
• Camera selection (front/back)
• Scan sounds enable/disable
• Scan haptics enable/disable
• Scan delay (0-3 seconds)
• Check-in on scan enable/disable
• Camera preview size
• Offline scanning enable/disable
• Force offline mode enable/disable

• Camera permissions (OS level)
• Downloaded offline data (stored locally)

• Settings automatically saved to server when changed
• Other devices check for updates when opening scan screen
• Settings reload when returning to scan screen
• Deleted settings revert to defaults across all devices

• Consistent scanning experience across devices
• Share scanner devices without reconfiguring
• Team-wide preference management
• Settings persist even if app reinstalled

• Torch: Enabled (for low-light entrance)
• Camera: Rear facing
• Preview Size: Medium
• Sounds: Enabled (confirms each scan in busy entry)
• Haptics: Disabled (not needed with sound)
• Delay: 1 second (prevents double-scans)
• Check-in: Enabled (automatic workflow)
• Offline: Enabled (backup for Wi-Fi issues)
• Force Offline: Disabled (prefer online when available)

• Torch: Disabled (daylight conditions)
• Camera: Rear facing
• Preview Size: Large (easier targeting outdoors)
• Sounds: Disabled (too noisy to hear)
• Haptics: Enabled (tactile confirmation)
• Delay: 0 seconds (high-volume entry)
• Check-in: Enabled (automatic workflow)
• Offline: Enabled (cellular may be overwhelmed)
• Force Offline: Disabled (prefer online when available)

• Torch: As needed for venue
• Camera: Rear facing
• Preview Size: Medium
• Sounds: Enabled (helpful during testing)
• Haptics: Disabled (not critical for testing)
• Delay: 2 seconds (deliberate scanning)
• Check-in: Disabled (don't affect real data)
• Offline: Enabled (may test without internet)
• Force Offline: Enabled (don't record test scans to server)

• Torch: Disabled (customers control device)
• Camera: Front facing (face customer)
• Preview Size: Large (customers need visual guidance)
• Sounds: Enabled (clear feedback for customers)
• Haptics: Enabled (multi-sensory confirmation)
• Delay: 2 seconds (give time to understand result)
• Check-in: Enabled (automatic workflow)
• Offline: Disabled (kiosk has wired internet)
• Force Offline: Disabled (need server recording)

• Check internet connection for sync
• Ensure signed in to account (not device sign-in)
• Try toggling setting off and on again
• Check app has permission to write to storage

• Another device or user may have changed settings
• Settings deleted remotely revert to defaults
• App update may have reset preferences (rare)
• Sign out and sign back in to force sync

• Check offline scanning is enabled in settings
• Ensure sufficient storage space on device
• Download ticket data whilst online first
• Verify offline data hasn't expired (7-day limit)

• Check using rear-facing camera (front camera has no torch)
• Verify camera permissions are granted in your device settings
• Try toggling torch setting off and on
• Restart app if torch appears stuck