Large gaming centers — 30+ seats, multiple zones, a food counter and a manager's desk — can't run on a single billing terminal. You need multiple access points, all looking at the same live data.
Here's how to do it with Airavoto POS on a local network.
The architecture
Airavoto POS is a web application that runs on Node.js with a PostgreSQL database. You install it once on one machine (the server), and every other terminal in the center accesses it through a browser on the local network.
No software installation on billing terminals. No sync issues. No data duplication. Every counter, the food station and the manager all see the same live data.
Step 1: Pick your server machine
The server machine doesn't need to be powerful — a mid-range PC or even an old laptop with 8GB RAM and a SSD will handle 50+ concurrent seats without breaking a sweat.
What matters: a wired ethernet connection to your router. Wi-Fi for the server introduces latency and failure risk. Wire it.
Step 2: Assign a static local IP to the server
By default, your router assigns IPs dynamically — meaning the server's IP could change after a reboot. You need a fixed local IP (e.g. 192.168.1.100) so billing terminals can always find the server.
Do this in your router's DHCP settings by binding the server's MAC address to a fixed IP. Any IT person can do this in 5 minutes.
Step 3: Install and start Airavoto POS on the server
Follow the standard installation: download, configure, run migrations, start the app. By default it runs on port 3000.
Once running, the server is accessible on your local network at http://192.168.1.100:3000 (replace with your fixed IP).
Step 4: Open billing terminals
On each billing counter PC, open a browser and navigate to the server's IP and port. Log in with the appropriate staff account. Done — each counter is now a live terminal.
Create separate staff accounts with appropriate roles: billing staff can start/stop sessions and take food orders; managers can access reports and settings.
Step 5: Kitchen display (optional)
A cheap Android tablet or old PC at the food counter runs the kitchen display view in a browser. Food orders placed from any terminal appear here instantly. No separate hardware, no integration — it's just another browser window.
Common mistakes
- Using Wi-Fi for the server: don't. Wire it.
- Forgetting the static IP: terminals break whenever the router reboots.
- Sharing one staff login across counters: creates accountability gaps. Create individual accounts.
