Electronic ticketing has brought radical changes to the entertainment and event planning businesses. With electronic ticketing and barcode, access control comes challenges like easy duplication of tickets and unstable Internet connectivity at crowded venues. Fortunately, with the invalidation of duplicate tickets, offline authentication, manual barcode value entry, and database search, codeREADr can solve all of these problems for events and venues large and small.
We have created a guide to our smartphone app and web interface that’s specific to electronic ticketing. We hope this helps put into perspective some of the best ways to deploy codeREADr for barcode access control – whether using the most sophisticated features or the simplest ones.
Electronic ticketing companies or service providers would generally create one service for each event.
Real-time services require good Internet access (either Wi-Fi or 3G/4G) at your scanning location. If you lose connectivity while scanning, the app will default to on-device recording as a backup. Consider that some venues have good Internet access but NOT necessarily at the doors or when lots of ticket holders are also trying to access the Internet simultaneously. Therefore, if in doubt, use codeREADr’s on-device services or bring your own, dedicated 4G Hot-Spot which can enable very fast connections for 5+ devices simultaneously. There’s a growing number of such low-cost devices on the market with month-to-month connectivity plans.
Note: Each codeREADr scan only posts 1kb of data up to the server and 1kb of data back to the device, so total data usage is quite low.
With an on-device database, scans are quickly validated against a database downloaded to iOS and Android devices because there’s no connection latency. What’s special about auto-sync is that scans from all devices are automatically uploaded (‘posted’) to a shared online database and the synced database is automatically downloaded to each device. The default setting for posting scans is every two (2) seconds. The default setting for downloading databases is every two (2) minutes.
Both processes are completed in the background so the person doing the electronic ticketing can keep scanning without interruption. If connectivity is completely lost, then the scans are queued and synced when connectivity is restored. Select the Auto Sync option on the Advanced tab when creating or editing your services.
Record Scans On-Device. This is the easiest service to deploy. Although this service type will not check for invalid or duplicate tickets, people may assume you are simply because you are making the effort to scan them. Of course, you should always visually examine each ticket to verify its authenticity. If Internet access is available, you can view scan data within the app and upload your scans to our servers after the event is over.
Validate Scans On-Device. Best for these scenarios: if Internet connectivity may be unstable at the event, if ticket sales are stopped before the event, or if all potentially valid ticket IDs are known in advance. With this service type, ticket IDs are uploaded to our servers and then to your devices before the event. Those purchasing tickets at the event can be directed to a different entrance, or be issued a unique paper ticket that is collected at the entrance.
If the event venue has multiple entrances and at least some Internet connectivity, an app user can periodically upload scans and download a new database to the device. This enables more accurate duplicate checking and capacity counting, resulting in better barcode access control.
Validate Scans Online. If you are absolutely certain you will have stable Internet connectivity at the event venue, this is the best choice. Electronic ticketing IDs will be validated against our servers and results are posted back instantly to the device.
Postback URL / APIs. Best for these scenarios: if an electronic ticketing company is selling tickets online (or via mobile) up to and beyond the start of the event, or if catching invalid or duplicate tickets is a high priority and the venue has multiple devices/entrances. Using our APIs or implementing a Postback URL requires technical integration with the codeREADr platform.
Record Scans Online. Generally not used for electronic ticketing or barcode access control, unless you want to view scan data on the Web while deploying multiple devices.
When you create a service, you have the option to specify the duration it will appear on the device of an authorized app user. This can be especially useful when managing services for other companies or managing many events.