When an event has multiple entrances, check-in devices should normally remain online so that every gate has access to the latest ticket status. If connectivity is unreliable, the Aplicación FooEvents Check-ins can continue processing check-ins in Offline Mode, but additional planning is required to reduce the risk of the same ticket being accepted at different gates.

Recommended approach: Use a dedicated staff network as the primary connection and prepare Offline Mode as a fallback. Do not rely on multiple offline devices sharing check-in information in real time.

How check-in synchronization works

When connected, the FooEvents Check-ins app communicates with your WordPress website using the REST API. Each check-in is recorded against the ticket in your WooCommerce database, allowing other connected devices to retrieve the updated ticket status. Refer to Conectarse a su tienda para más información.

When a device is placed in Offline Mode:

• Check-ins are stored locally on that device.
• The device does not receive check-ins performed on other devices.
• Changes are uploaded to your WooCommerce database when the device reconnects.
• Devices operating offline will not synchronize with one another until they are back online.

As a result, the same ticket could be accepted by two different offline devices because neither device knows that the other has already checked it in. Offline Mode is therefore best treated as an emergency fallback, particularly when using multiple devices. Learn more about this limitation in the Offline Mode documentation.

Recommended network setup

Provide a dedicated network for check-in staff rather than relying on public or guest Wi-Fi.

Where possible, your setup should include:

• A dedicated staff Wi-Fi network covering every entrance.
• A primary internet connection, such as venue broadband.
• A secondary connection, such as a cellular router or mobile hotspot.
• Portable power banks or continuous power for check-in devices and networking equipment.
• A connected support desk for ticket searches, duplicate-ticket queries, and newly purchased tickets.

Test both the primary and backup connections from every gate before the event. A connection that works inside the venue office may not work reliably at an outside entrance or in an area with large crowds.

A local Wi-Fi network without internet access is not sufficient if your WooCommerce website is hosted elsewhere. Devices must be able to reach the website for check-ins to synchronize.

Prepare your website

Complete the following checks several days before the event:

1. Install the latest versions of FooEvents para WooCommerce y el Aplicación FooEvents Check-ins.
2. Confirm that the FooEvents REST API is accessible by visiting:https://www.yourwebsite.com/wp-json/fooevents/v1
3. Confirm that security, CAPTCHA, or privacy plugins are not blocking the REST API.
4. Check that your hosting environment can handle simultaneous requests from all check-in devices.
5. Create suitable WordPress accounts for check-in staff. Where practical, avoid sharing a full Administrator account across every device.

Véase Problemas de conexión for API, permissions, security plugin, and login troubleshooting.

Limit unnecessary ticket data

If your website contains many past events or tickets, configure the Check-ins app to load only the data needed for the event. This reduces initial loading times and makes it easier for staff to find the correct event.

Ir a FooEvents > Settings > Check-ins App and review:

• Opciones de listado de eventos
• Tickets loaded
• Include older tickets that have not been checked in

Ensure that the selected ticket period includes tickets purchased far in advance. These settings use the ticket creation date rather than the event date. Refer to Limit the tickets loaded in the FooEvents Check-ins app for configuration guidance.

If the server struggles to load a large event in a single request, tickets can also be loaded in smaller batches.

Prepare every check-in device

Each device must complete its initial data download while it still has a reliable internet connection. Offline Mode cannot be prepared correctly if the relevant event and attendee data have not already been downloaded.

On every device:

1. Install or update the Aplicación FooEvents Check-ins.
2. Sign in using the correct WordPress account.
3. Open the event and allow all relevant tickets to finish loading.
4. Confirm that recent test or attendee tickets are visible.
5. Activar Auto Check-in if attendees should be checked in immediately after scanning.
6. Test the camera or connected Bluetooth barcode scanner.
7. Confirm that a test check-in performed on one device appears as checked in on the other devices.
8. Test Offline Mode, reconnect the device, and confirm that the offline check-in synchronizes successfully.

Auto Check-in avoids returning to and refreshing the ticket list after every scan, which can make high-volume admission faster. A Bluetooth barcode scanner can also improve scanning speed and accuracy, particularly in low-light conditions. See Escanear billetes con la aplicación.

After testing, reset the test tickets to their intended status.

Assign tickets to specific gates

If all devices remain online, attendees can generally use any entrance because check-in statuses are recorded centrally.

If several gates may need to operate offline, divide attendees into non-overlapping groups before the event. This will reduce the possibility of the same ticket being used at multiple entrances. Assign gates according to ticket type, seating area, membership category, booking slot, or another value that staff can verify before scanning.

Use clear signage and include the assigned entrance in pre-event communication where possible. Staff should redirect attendees to the correct gate before scanning their tickets.

Each offline device should remain assigned to its designated gate or ticket group until its check-ins have synchronized. Do not move an unsynchronized device between gates.

If tickets cannot be divided into exclusive groups and preventing duplicate entry is essential, multiple fully offline scanners are not recommended. Restore connectivity, route attendees through a connected gate, or temporarily use a single offline validation point.

Ticket filters can help staff focus the attendee list by ticket status or product variation, but operational gate assignment and signage are still important. See Filtros de billetes.

Event-day procedure

Before opening the gates

• Connect every device to the primary network.
• Open the correct event and refresh its ticket data.
• Confirm that each device has completed loading.
• Perform a test scan at every gate.
• Confirm that the test status appears on another device.
• Check the backup network and power supplies.
• Brief staff on the offline procedure and assigned ticket groups.

Complete this process as close to opening time as practical so that devices contain recently sold, canceled, or updated tickets.

While connectivity is available

Keep all devices online and process check-ins normally. A supervisor should periodically confirm that devices are connected and that ticket statuses are updating.

If a gate loses connectivity

1. Attempt to connect the device to the backup network.
2. If the connection cannot be restored, pause briefly and note the time of the outage.
3. Enable Offline Mode.
4. Continue scanning only the tickets assigned to that gate or device.
5. Send exceptions, newly purchased tickets, and attendees at the wrong gate to the connected support desk.

Tickets sold, canceled, or updated after a device goes offline will not be reflected on that device until it reconnects. If you continue selling tickets during an outage, route those customers through a connected entrance or support desk.

Reconnect and synchronize devices

When connectivity returns:

1. Temporarily stop scanning on the affected device.
2. Export its offline changes as a backup.
3. Disable Offline Mode or select Vuelva a conectar.
4. Allow the device to upload its changes.
5. Confirm that its check-ins appear in WooCommerce or on another connected device.
6. Resume scanning only after synchronization is complete.

For easier reconciliation, record the device name, gate, operator, and offline period for each exported file.

If automatic synchronization fails, the app can export its offline changes as an XML file. Import this file using the FooEvents import tool in the WordPress admin area. Unique offline changes are imported only once, so previously imported changes are skipped if the same file is processed again. Follow the steps under Importar/exportar cambios sin conexión.

Do not sign out, uninstall the app, clear its data, or reset a device until all offline check-ins have been successfully synchronized or exported.