Offline Scanning Without an Internet Connection

Scan tickets offline with the Seaty mobile app: pre-download event data, validate QR codes locally without internet, and auto-sync on reconnection.

Offline scanning enables ticket validation when internet connectivity is unreliable or unavailable. Download event data in advance, validate tickets locally, and sync results when you reconnect.

At its simplest, offline scanning answers one question: How do I scan tickets when my venue has unreliable or no internet?

Who uses this: Event staff scanning tickets at venues with unreliable internet, outdoor events, or locations with poor mobile coverage.

Key capabilities:

Download ticket data before your event whilst you have reliable internet
Validate tickets locally on your device without needing a connection
Automatically fall back to offline mode when your connection drops
Sync your scan results to the server when you reconnect

How It Works

At a glance: Download your event's ticket data in advance, scan tickets using that local copy when offline, then sync your results when you're back online.

1. Prepare Your Data

Before the event, whilst you have reliable internet, download your ticket data to your device. You can choose to download tickets for a specific performance, a whole day, or your entire event run.

2. Scan Tickets Offline

When you lose internet connection (or choose to work offline), the app validates tickets against the data stored on your device. You'll see an offline indicator confirming you're using local validation.

3. Sync Your Results

When your connection returns, manually sync your offline scans to record them on the server. This ensures your attendance records are complete and accurate.

Think of it this way:

Downloading creates a snapshot of your tickets on your device

Offline scanning checks tickets against that snapshot

Syncing sends your scan results back to update the main records

Venue Challenges Offline Scanning Solves

Unreliable Venue Internet: Sports venues, historic buildings, outdoor locations with poor Wi-Fi or mobile coverage
High-Volume Events: Network congestion when hundreds of attendees arrive simultaneously
Backup Strategy: Safety net if venue internet fails unexpectedly during an event
Remote Locations: Events in areas with limited or no internet infrastructure
Cost Control: Avoid expensive temporary internet installations for one-off events

How Offline Scanning Works

Three Operating Modes

Online Only (Default):

All scans validated against server in real-time
Requires active internet connection
Full audit trail and immediate reporting
Check-in status updated instantly
No local ticket data required

Hybrid Mode (Recommended):

Attempts online validation first
Automatically falls back to offline if connection fails
Best of both worlds approach
Requires offline data downloaded in advance
Seamless switching between online/offline

Force Offline Mode (Testing):

Always validates locally, never contacts server
Scans NOT recorded on server
Useful for testing and rehearsals
Requires offline data downloaded
Privacy-focused option

Validation Process

When scanning offline, the app:

Reads QR Code: Captures ticket barcode via camera
Searches Local Database: Looks up ticket in downloaded data
Validates Ticket: Checks ticket is for correct event and date
Checks Status: Verifies ticket hasn't been cancelled
Records Scan Locally: Stores scan result on device for later sync
Shows Result: Displays ticket details with offline indicator

Important: Offline validation cannot check if the ticket has already been checked in. This prevents duplicate entry detection when scanning offline.

Downloading Ticket Data

Before the Event

Download ticket data whilst you have reliable internet:

Navigate to event in the app
Tap "Scan & Attendance"
Tap "Scan settings"
Enable "Offline scanning"
Tap "Manage Offline Data"
Select your event
Choose download options
Monitor download progress

Best Practice: Download data the night before the event, not immediately before doors open. This gives time to troubleshoot any issues and ensures data is fresh.

Download Options

By Event Date:

Download tickets for a specific performance time
Smallest download size
Use when scanning only one show
Example: "Saturday 7:30pm performance"

By Day:

Download all performances on a calendar date
Medium download size
Use for multiple shows per day
Example: "All performances on Saturday 23rd November"

By Section:

Download only tickets for specific seat categories
Reduces download size for large venues
Use when scanning entrance to specific section
Example: "Stalls and Circle only"

Full Event:

Download all tickets for entire event run
Largest download size
Use for multi-date tours or when unsure which dates needed
Example: "All performances across two-week run"

Download Progress

During download:

Progress bar shows percentage complete
Current count / total tickets displayed
Cancel button available to stop download
Background download continues if you navigate away
Notification when download completes

Typical Speeds:

100 tickets: 5-10 seconds
500 tickets: 20-30 seconds
1000 tickets: 40-60 seconds
5000 tickets: 3-4 minutes

Factors Affecting Speed:

Internet connection quality
Server load
Device performance
Ticket data complexity (notes, flags, etc.)

Storage Management

Storage Requirements

Downloaded ticket data typically requires:

Per Ticket: 1-2KB (basic ticket data)
100 tickets: ~100-200KB
1000 tickets: ~1-2MB
Large tour (10,000 tickets): ~10-20MB

Additional Data:

Seat categories, pricing tiers
Order information (attendee names)
Event details and dates
Venue and organisation data

Checking Storage Usage

View offline data storage:

Open "Manage Offline Data"
See total tickets stored
View total storage used (MB/GB)
Check number of events with offline data

Storage Display:

Total tickets across all events
Storage size in MB or GB
Per-event breakdown showing ticket counts
Last download timestamp for each event

Data Expiry

Offline data is automatically cleaned up 24 hours after each event date passes:

Why automatic cleanup?

Prevents stale data from accumulating on your device
Frees storage space after events complete
Reduces risk of outdated ticket information being used
Keeps your device running smoothly

How it works:

Data for past event dates is removed automatically
The app checks daily and cleans up expired data
You'll see a warning if storage exceeds recommended limits
You can also manually clear data in "Manage Offline Data"

Scanning Offline

Activating Offline Mode

Offline mode activates automatically when:

Internet connection not available
Network reachable but server unreachable
Force offline mode enabled in settings
Hybrid mode with failed online validation

Visual Indicators:

Offline icon shown at top of scan screen
"No Network Connection" or "Offline Validation Only" message
Blue/amber status indicator (depending on mode)
Ticket count showing available offline tickets

Offline Validation Results

Scanned tickets show:

Valid Tickets:

Green indicator with ticket details
"Ticket validated offline (not checked in)" message
Full ticket information from cached data
Order number and attendee name
Seat and category details

Invalid Tickets:

Red indicator with error message
"Ticket not found in offline data" (not downloaded)
"Ticket was cancelled" (known cancellation)
"Ticket is for different date" (wrong performance)

Limitations:

Cannot detect if already checked in elsewhere
Cannot show real-time scan history
Cannot validate tickets ordered after download
Cannot check current order payment status

Offline Ticket Details

Tap "More Info" on offline-validated tickets to view:

Ticket GUID and order number
Attendee name
Seat location (group, name, category)
Ticket category and pricing
Event date and time
Cached at timestamp
Offline validation indicator

Missing When Offline:

Real-time check-in status
Recent scan history
Admin notes added after download
Ticket flags created after download
Payment status changes

Syncing Offline Scans

Automatic Sync

When internet connection is restored:

Offline scans do NOT automatically sync to server
Manual sync required via Offline Scans modal
Scans remain stored locally until synced
Unsynced count visible on scan screen

Why Manual Sync:

Gives control over when scans are recorded
Allows review of offline scans before submitting
Prevents accidental duplicate submissions
Provides confirmation of sync success

Viewing Unsynced Scans

Tap "X offline scan(s)" button on scan screen to view:

List of all unsynced offline scans
Timestamp of each scan
Ticket information (if available)
Validation result (success/failure)
Scanner name and device

Sync Options:

Sync all scans to server
Review individual scans
Delete failed scans
Export scan list (future feature)

Sync Process

When syncing offline scans:

Validate Sync: Check internet connection available
Prepare Data: Format scan records for server
Upload Batch: Send all unsynced scans to server
Process Results: Server validates and records each scan
Update Local Status: Mark scans as synced
Show Summary: Display success/failure count

Sync Duration:

10 scans: < 5 seconds
50 scans: 10-20 seconds
100 scans: 30-60 seconds
500+ scans: 2-5 minutes

Sync Failures

If sync fails:

Scans remain stored locally
Retry button available
Clear error message shown
Individual scan failures identified
Partial sync possible (some succeed, some fail)

Common Sync Failures:

Internet connection lost during sync
Server timeout or error
Ticket not found on server (ordered after download)
Duplicate scan (already scanned by another device)

Managing Offline Data

Viewing Offline Tickets

Navigate to "Offline Tickets" to browse downloaded data:

List of all cached tickets
Search and filter capabilities
View ticket details without scanning
Check which tickets are available offline
Verify data freshness

Useful For:

Confirming specific tickets are cached
Troubleshooting "ticket not found" errors
Verifying download completed successfully
Checking which seat categories are available

Clearing Offline Data

Remove downloaded ticket data when:

Event Completed:

Event finished and data no longer needed
Free up storage space
Clear old event data

Order Changes:

Significant ticket changes since download
Cancelled orders need removal
Refresh with latest ticket data

Troubleshooting:

Validation behaving unexpectedly
Suspect corrupted data
Fresh start needed

Clear Options:

Clear specific event data
Clear all offline data
Clean up expired data only

Refreshing Data

Update offline data when:

New tickets purchased after initial download
Orders modified or transferred
Tickets cancelled or refunded
Attendee names updated
Admin notes or flags added

Refresh Process:

Clear existing data for event (optional)
Download data again whilst online
New data overwrites previous download
Latest ticket information now cached

Recommendation: Refresh data on event day if significant orders processed since initial download.

Offline Scanning Best Practices

Planning

Before Event Day:

Test offline mode with small event first
Download data 12-24 hours before event
Verify data includes all expected tickets
Check storage space sufficient on devices
Train staff on offline workflow differences

Event Day:

Refresh data morning of event (latest orders)
Verify offline mode working on all scanning devices
Have backup online-capable device available
Brief staff on no duplicate detection limitation

During Event

Monitor Connectivity:

Check if hybrid mode falling back to offline
Count unsynced scans accumulating
Test online validation periodically
Be ready to switch to online when possible

Manage Expectations:

Inform staff offline mode won't detect duplicate check-ins
Rely on visual recognition for repeat scanners
Trust ticket validity over check-in status
Use order lookup for suspicious cases

After Event

Sync Promptly:

Sync offline scans as soon as internet available
Don't wait until next day (risk of data loss)
Verify sync completed successfully
Review any sync failures for patterns

Clean Up:

Clear offline data if event complete
Free storage space for next event
Review which tickets weren't scanned (no-shows)

Troubleshooting Offline Mode

"Ticket not found in offline data"

Causes:

Ticket ordered after data downloaded
Ticket from different event
Data download incomplete or corrupted
Ticket transferred to different event date

Solutions:

Re-download data to include recent orders
Verify scanning correct event and date
Check ticket is valid in admin system
Clear and re-download if corruption suspected

"Cannot scan tickets while offline"

Causes:

Offline scanning not enabled in settings
No offline data downloaded for this event/date
Offline data expired (event date has passed)
Network detected as offline but offline mode disabled

Solutions:

Enable offline scanning in Scan Settings
Download ticket data whilst online
Refresh expired data
Enable "Force offline mode" if network unreliable

Download Fails or Stalls

Causes:

Unstable internet connection
Server timeout (large ticket counts)
Insufficient storage space
Device background restrictions

Solutions:

Use Wi-Fi instead of cellular if available
Download in smaller batches (by date, not full event)
Clear storage space on device
Keep app in foreground during download
Try download during off-peak hours

Sync Fails After Event

Causes:

Internet connection lost
Server errors or maintenance
Scan data corrupted
Duplicate scans rejected by server

Solutions:

Retry sync when internet stable
Contact support if persistent failures
Export scan list for manual entry (future feature)
Check error messages for specific issues

Limitations of Offline Mode

What Offline Mode Cannot Do

Duplicate Detection:

Cannot detect if ticket already checked in elsewhere
No real-time cross-device sync
Risk of same ticket scanned on multiple devices

Order Status:

Cannot check if order paid, pending, or cancelled since download
No refund or transfer status updates
Payment disputes not reflected

Real-Time Updates:

Admin notes added online won't appear
Ticket flags created after download not visible
Attendee name changes not reflected
Seat changes not updated

Reporting:

Offline scans don't appear in real-time reports until synced
Attendance statistics incomplete until sync
No instant visibility for administrators

When Not to Use Offline Mode

Don't Use Offline If:

Venue has reliable, fast internet (use online instead)
High risk of ticket fraud or duplicate scans
Real-time reporting critical to operations
Staff unfamiliar with offline workflow limitations
Orders changing frequently up to event time

Better Alternatives:

Hybrid mode for most scenarios (automatic fallback)
Multiple online scanners with load balancing
Dedicated internet circuit for scanning devices
Mobile hotspot with unlimited data plan

Use Case Examples

Community Theatre Production

Scenario: 200-seat venue, unreliable Wi-Fi, weekend shows Solution:

Download tickets Friday for weekend shows
Use hybrid mode (prefer online, fallback offline)
Sync after each performance
Refresh data between matinee and evening shows

Outdoor Music Festival

Scenario: 5000 attendees, remote location, no reliable cellular Solution:

Download all tickets week before event
Use force offline mode (no internet available)
Multiple scanning devices at different entrances
Sync all devices when returning to office next day

School Event Series

Scenario: 10 performances over 2 weeks, school Wi-Fi overloaded during entry Solution:

Download full event run in advance
Hybrid mode (school Wi-Fi often works but congested)
Refresh data daily to include late purchases
Sync at end of each evening
Clear data after event series complete

Theatre Tour

Scenario: Different venue each night, varying internet quality Solution:

Download tickets for each venue day before performance
Hybrid mode (adapt to each venue's connectivity)
Download by performance (not full tour) to minimise storage
Sync immediately after each show
Test connection before doors open each night

Common Questions

Downloading Data

How much storage space do I need? Ticket data is compact - typically 1-2KB per ticket. A 1,000-ticket event needs roughly 1-2MB. Even a large tour with 10,000 tickets requires only 10-20MB.

Can I download tickets for multiple events? Yes. Each event's data is stored separately, and you can manage them individually in "Manage Offline Data".

What if new tickets are purchased after I download? Those tickets won't be in your offline data. Refresh your download before doors open to capture recent orders.

Scanning Offline

Can I detect if someone has already been checked in? No. This is the main limitation of offline scanning. Your device only knows what's in its local data - it cannot check if another scanner has already validated that ticket. Brief your staff to watch for repeat attempts.

What happens if I scan a ticket for the wrong date? The app checks the ticket date against your selected scanning date and shows a clear warning if they don't match. A multi-day pass (a ticket sold against a date spanning more than one day, such as a "Full Weekend" pass) is treated as valid on every day within its range, even offline - it is only flagged if scanned outside that range.

Do scans get recorded automatically when I'm back online? No. You must manually sync your offline scans. This gives you control and lets you review before submitting.

Syncing Results

What if sync fails? Your scans remain stored on your device. You can retry when you have a stable connection. Individual failures are identified so you can address specific issues.

Can I delete offline scans without syncing? Yes, though this means those scans won't be recorded in your attendance records. Only do this if you're certain the data isn't needed.

Choosing a Mode

Which mode should I use? For most venues, use Hybrid mode. It prefers online validation but automatically falls back to offline when your connection drops. Only use Force Offline if you have no internet at all or are testing.

Should I always download data "just in case"? Yes, if your venue has any history of connectivity issues. Having offline data ready provides a safety net with minimal effort.