Explanation
Offline first and what syncs
The booth sells, prints, and takes credits with no internet at all. The cloud adds monitoring, remote changes, and copies of the records. This page explains what crosses the line, when, and what you see on each side.
A BoothIQ kiosk is a complete photo booth on its own. Everything a customer touches, from the welcome screen to the printed strip, runs on the kiosk's own computer against its own database. The cloud account you link it to is a layer on top: it watches the booth, carries changes to it, and keeps copies of what it records. If the venue's internet drops, the booth does not notice until it needs the cloud for something specific.
What works with no internet
- Selling and printing: the whole customer session, in either mode.
- Credits added on the kiosk, cash collection, and the sales records of all of it.
- Every template that is already on the booth, whether it came from a USB drive or from the cloud earlier.
- The license, until it runs out. It is stored on the kiosk and checked there, so an activated booth keeps running while offline; a subscription license expires on its end date and needs the cloud to renew, so plan an offline event inside the current period. See Activation and licensing.
- The admin area, including exports to a USB drive.
Anything the booth would normally send to the cloud waits in a queue and goes when the connection is back.
What needs the internet
- Activating the booth, and renewing a subscription license when it reaches its end date. See Activation and licensing.
- The admin area's Subscription tab.
- Emailing an export (a USB export works offline).
- An emergency password the first time it is used. See Emergency access.
- Deleting one of your own cloud templates from the kiosk. The kiosk refuses while offline so that the cloud copy and the booth never disagree.
- Receiving anything from the cloud: a marketplace purchase, a template uploaded on the web, a price change sent from the app, a remote command.
How the booth talks to the cloud
Two channels run from the moment the kiosk starts.
- A heartbeat every thirty seconds, the first one straight away. It carries the booth's status: printer, paper and ribbon levels, camera, payment board, disk, memory, uptime, errors, prints today and in total, how many records are waiting to upload, the credit balance, the mode, cash in the box, the last backup, the prices, and the business settings. The reply brings things back: refunds recorded in the cloud, business settings and theme, whether cloud sync is on, a new API key when the cloud rotates it, and any commands waiting for the booth.
- A persistent connection for commands that cannot wait for the next heartbeat. If it drops, the kiosk reconnects every five seconds, up to ten times, then keeps trying on a timer. Commands also ride on the heartbeat reply, so a booth without the persistent connection still gets them within thirty seconds.
Records go up separately. Sales, credit changes, and cash collections queue on the kiosk and upload every thirty seconds, fifty at a time and up to a thousand per run, with five retries for anything the cloud refuses. The admin area's Cloud Sync tab shows the queue under Sync Status, with Sync Now to push it immediately and Sync Historical to send older records that predate the link.
Templates come down the other way. On its first contact with the cloud the booth pulls categories, layouts, and templates; after that, the cloud tells it when something changed and it fetches the difference. A removal is held back while a customer is mid-session.
Remote commands, and what the operator sees on the booth
| Command | Where it comes from | On the booth |
|---|---|---|
| Add credits | App or web | A "Credits Added" toast with the amount and the reason |
| Update prices | App | A "Prices Updated" toast |
| Restart the booth app | App or web | An "App restarting in" toast with the delay and the reason, "or when the current session finishes"; five seconds from the app and the web. With a customer mid-session, or an operator in the admin area, the booth waits for them to finish, up to ten minutes, and shows "App will restart when the current session finishes" |
| Reboot the system | App or web | A "SYSTEM RESTARTING in" toast with the delay and the same wait; fifteen seconds from the app and the web |
| Cancel a restart | App or web | An "App restart cancelled" or "System restart cancelled" toast with the reason, or "No pending restart to cancel" when nothing was waiting |
| Back up now | App or web | Nothing on screen; the backup runs in the background |
| Download logs | App or web | Nothing on screen; the booth zips its app, error, and hardware logs (the last twenty-four hours by default) and uploads them |
| License update or revoke | BoothIQ | A "License Updated" or "License Revoked" toast |
| Refresh settings | Cloud | Nothing on screen; the booth sends a heartbeat at once |
| Sync templates, layouts, or categories | Cloud (after a purchase or upload) | Nothing on screen; the content appears |
A booth on kiosk version 0.1.17 or earlier does not wait: it restarts once the delay is up, whoever is using it.
There is no command that changes the booth's mode. Coin Operated and Free Play are set on the kiosk, in Products, and nowhere else; see Set prices and switch between Coin Operated and Free Play. A new API key is not a command either: it arrives inside a heartbeat reply and the booth switches to it on its own.
How to tell a booth is connected
- On the kiosk, Cloud Sync shows "Connected" at the top right once the booth is linked, and "Not Registered" before it is linked. The badge says whether the booth has a cloud identity, not whether heartbeats are arriving; a linked booth with no internet still reads "Connected". Sync Status shows the last sync time and the total synced. For whether the cloud is hearing from the booth, use the app or the web.
- In the app, the booth's card carries Online, Warning, or Offline. Offline means heartbeats have stopped arriving.
- On the web, the Booths page shows the same status beside each booth, and the counts of online and offline booths at the top.
Because the heartbeat is every thirty seconds, a booth that loses its connection shows as offline within a minute or two, and comes back just as quickly.
What the cloud never does
- It does not run the booth. An activated booth that never reaches the cloud again still sells and prints until its license runs out (never, for a perpetual license); it has no monitoring, no remote changes, and no backups.
- It does not hold your photos. Backups are of the booth's database; see Backups.
- It does not take templates from a booth that is not linked. A USB upload on an unlinked booth stays on that kiosk; a linked booth sends its USB uploads to the cloud, which passes them to your other booths. See Put a template on a booth.
Last verified against the software on 2026-11-12.