Ai-Menu POS not working? Common problems & how to fix them.
Published: 22 Sep 2026
Ai-Menu POS server and terminal setup at a Brisbane venue.
Ai-Menu POS runs on a local server installed at your venue — meaning the installation is more involved than a cloud-only system, and when something goes wrong, the failure point is usually the local network or server rather than the internet connection.
This guide covers the Ai-Menu POS issues HospoDoc technicians see most often across Brisbane and Southeast Queensland.
1. Tablets or terminals can’t connect to the server
All Ai-Menu POS terminals and tablet menus connect to a local server installed at the venue. If the server is unreachable, nothing works.
Either the server has lost its network connection, its IP address has changed, or the server software isn’t running.
- Check the server unit — look for network activity lights on the ethernet port. No blinking means the cable or switch connection has failed.
- Reboot the server: hold the power button for 5 seconds, wait 30 seconds, then power on. Allow 2–3 minutes for the server service to fully start before testing terminals.
- On a working device on the same network, try to access the Ai-Menu admin interface via browser — if the server’s IP has changed, it won’t load. Check your router’s device list for the server’s current IP.
- If the IP has changed, set a static IP on the server — a one-time fix that prevents recurrence.
- Confirm all devices are on the same Wi-Fi network — not one on the main SSID and another on a guest network.
2. Tablet menus not syncing or showing outdated content
Tablets cache the menu locally. If a tablet hasn’t successfully synced with the server recently, it continues displaying its cached version even after menu updates.
- From within the Ai-Menu tablet app, access settings and tap the sync/refresh option — the tablet should pull fresh data immediately.
- If sync fails, check the tablet’s Wi-Fi — tablets further from access points often have intermittent signal causing sync failures without fully disconnecting.
- Fully close the app (don’t just minimise) and reopen — forces a fresh connection attempt to the server.
- If one specific tablet keeps failing while others are fine, the issue is that tablet’s Wi-Fi signal at its physical location.
- After any major menu update, manually sync all tablets and do a visual check before opening service.
3. Kitchen printers not receiving orders
In Ai-Menu, every menu category must be assigned to a printer group. If a category has no printer assigned, orders with those items process silently without printing anywhere.
Likely a category routing gap — specific menu categories have no kitchen printer assigned.
- Ai-Menu Admin → printer configuration → check every active menu category has a printer group assigned.
- Print a self-test page from the kitchen printer (hold the feed button) — check the IP on the printout against what’s in Ai-Menu Admin.
- Set static IPs for all kitchen printers via your router’s DHCP reservation to prevent IP changes.
- If the printer shows online but still doesn’t print, power cycle it — some thermal printers need a full restart to clear a stuck queue.
- Send a test order for a single item from the affected category, with someone watching the printer, to confirm the exact failure point.
4. Ai-Bump kitchen display screen not updating
Ai-Bump connects to the local server over the network. If the screen device loses connection or the app crashes, orders keep processing but kitchen staff lose visibility.
- Check the bump screen’s Wi-Fi signal at its kitchen location — appliance interference commonly disrupts Wi-Fi in kitchens. Wired ethernet is more reliable for bump screens.
- Close and reopen the Ai-Bump app — forces a reconnection to the server and usually resolves a stalled screen within 30 seconds.
- If the app shows a connection error, the server may have restarted since the bump screen last connected. Restart the Ai-Bump app after any planned server restart.
- After any network change at the venue, reconfigure the bump screen’s server connection in the Ai-Bump settings.
5. POS terminal freezing or running slowly
Almost always a hardware memory issue, not a software bug. Ai-POS accumulates memory usage over time. A terminal that’s been running continuously for weeks without a restart will inevitably slow down.
- Restart the POS terminal at the start of each trading day — fully power off, wait 30 seconds, power on. Takes under 2 minutes and prevents most performance issues.
- On Android terminals: close or disable background apps that aren’t needed for POS operation.
- Check internal storage — Ai-POS needs adequate free space to cache menu images and transaction data.
- If the terminal is more than 4–5 years old and slowness persists after a restart, the hardware may need replacing.
- Never run other applications (browsers, YouTube) on POS terminals.
When to call a technician
- Ai-Menu server won’t start after a reboot — may indicate a hardware or OS issue on the server unit
- Multiple devices keep losing connection to the server despite the server being online — typically a network switch or access point fault
- Printers or bump screens reconfigured but still not working after following setup steps
- EFTPOS integration not re-establishing after a network change
- New venue installation needing the full stack set up — server, network, printers, tablets, bump screens — before going live
Ai-Menu POS causing problems during service?
HospoDoc provides on-site support for Ai-Menu and all major POS systems across Brisbane, Gold Coast, and the Sunshine Coast.
Call 1300 467 761 Talk to our team