Checking of 2000 Tickets using Using Built-In QRCODE Scanner

Hi there

I was wondering if anyone has experience with the built in QRCODE Scanner. We have about 2000 Tickets to scan within 1.5 hours. What i plan to do is:
- Use 5-10 mobile devices
- connect to our homepage and use the built in QRCODE Scanner
- Use the same user for alle the mobile devices
- Change the Checkin Interval to 4 seconds.

Has anyone experience with a setting like that? Will the use of only one user or the short interval cause problems?

Thanks for any responce

Hi Hans

As the developer who wrote the code to handle this feature, I would say that it will be fine. It is just 5 to 10 concurrence requests at a time and that's a small number, the server should be able to handle it easily

Regards,

Tuan

Great, thank you!

Another question. If we use a different User for each mobile device in the setting discribed in the first topic, is there a way to see by which user and at what time a certain ticket (or QRCODE) was scanned in the backend? Or even if a ticket is already scanned?
Thanks!

Hi Hans

Currently, we do not store checked in User ID, so this is not possible, sorry

Tuan

We scanned yesterday the 2000 Tickets (more or less) with 6 mobile devices without any problems. Wonderful, thanks!
One question similiar to the last one: Can we see after the scanning process somewhere how many tickets over all for an event are checked in? This would be very helpful for us.
Thanks

Great. Happy to hear that, Hans

For checked in count, not sure how you want it to be shown but it should be possible because when a registrant is checked in, his checked in status is stored in database

If we want to show that count statistic somehow, it should be doable

Regards,

Tuan

It is probably not the checked in registrant but the checked in Ticket. We had sold 2000 Tickets, but there had been no shows. So our question is how many tickets have been scanned (or not scanned).

It should be countable. But we do not have that information show anywhere at the moment

Regards,

Tuan

I am surprised that nobody else asked for this feature, for us it is quite important. It does not matter if we see this information in the backend somewhere, maybe on the event. Do you think this coud be added sometimes in the future?
Kind regards
Hans