Lightspeed POS not working? Common problems & how to fix them.
Published: 18 Aug 2026
Lightspeed POS setup at a Brisbane hospitality venue.
Lightspeed Restaurant is one of the more capable cloud-based POS systems in the Australian market — but like any POS, the installation phase and ongoing operation can throw up problems that stop service cold. A misconfigured network, a printer that won’t pair, or a floor plan that won’t load during a busy service are situations HospoDoc technicians see regularly across Brisbane and Southeast Queensland.
This guide covers the most common Lightspeed installation and post-install problems, what causes them, and how to fix them.
1. Lightspeed won’t connect after installation
Lightspeed Restaurant is a cloud-dependent system. Unlike local-server POS platforms that run entirely on-site, Lightspeed requires a reliable internet connection to function properly. If the connection drops or doesn’t meet Lightspeed’s network requirements, the system either won’t load or behaves erratically.
Lightspeed enters a degraded offline mode when it can’t reach its cloud servers. Split billing, loyalty lookups, and live reporting stop working entirely.
- Verify your connection is at minimum 25 Mbps synchronous — Lightspeed recommends this for multi-terminal setups.
- Put POS devices on a dedicated Wi-Fi SSID or wired ethernet — never share with customer Wi-Fi.
- Set your router DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) — ISP DNS can cause latency spikes that drop the connection.
- If using 4G backup, set it to automatic failover — Lightspeed sessions won’t recover if failover is manual and delayed.
- Check status.lightspeedhq.com to rule out a platform outage before assuming it’s local hardware.
2. Receipt or kitchen printers not working
Printer issues are the most disruptive problem in any POS setup. In Lightspeed, printers communicate via IP (network) or USB and are configured through Back Office under Devices. Both methods have their own failure points.
Usually a network assignment issue, not a hardware fault. If your printer is on DHCP (automatic IP), the router may assign it a different IP after a reboot, silently breaking the connection.
- Assign a static (fixed) IP to every printer — either through the printer menu or by reserving its MAC address in your router’s DHCP settings.
- In Lightspeed Back Office → Devices, delete and re-add the printer using the new static IP.
- Confirm all devices are on the same network subnet — mixing 192.168.1.x and 192.168.0.x breaks communication.
- For USB printers, try a different port and cable — USB print drivers can corrupt after Windows updates.
- Run a test print after every change, before reopening for service.
3. Floor plan not saving or tables showing wrong status
Lightspeed syncs floor plan status through the cloud. If one terminal is slightly out of sync, it shows stale table data.
- Force a sync by logging out and back in on the affected terminal — triggers a fresh data pull from the cloud.
- For a stuck table: Back Office → Orders → find the table → manually close or reassign the order.
- After building your floor plan in Back Office, always hit Publish and confirm the push to all terminals before opening.
- For multi-room venues, create separate sections with staff assigned accordingly — reduces cross-section sync issues.
4. EFTPOS integration not processing payments
Lightspeed Payments requires the merchant account to be fully verified before transactions process — even if the terminal appears connected.
- Check the Lightspeed Payments portal for outstanding identity verification or bank account confirmation steps.
- Confirm the terminal’s serial number is registered to your merchant account in the Payments dashboard.
- For third-party EFTPOS (e.g. Tyro): confirm the pairing code matches — codes expire quickly.
- Check that terminal firmware is up to date — outdated firmware causes integration failures after pairing.
- Always run a $1 test transaction before going live.
5. Staff permissions not working correctly
Lightspeed uses a permission matrix in Back Office. Assigning the “Manager” role doesn’t automatically grant all permissions — each toggle must be manually enabled.
- Back Office → Employees → Roles → check every permission toggle individually.
- For voids and refunds: enable “Allow order modification after payment” and “Allow refunds” under Operations.
- Confirm the staff member’s profile is correctly linked to the role — reassign if needed.
- Staff must log out and back in after any permission change for it to take effect.
6. Lightspeed running slowly on the terminal
Lightspeed is browser-based and memory-intensive. Running it on a device with less than 3GB RAM or heavy background app usage causes persistent slowness regardless of internet speed.
- On iPads: Settings → Background App Refresh → Off for all apps except Lightspeed. Clear Safari cache before each service.
- On Android: use the dedicated Lightspeed Android app rather than a browser — better optimised for lower-spec hardware.
- Fully restart the terminal at the start of each shift — don’t just lock the screen.
- If the device is more than 4 years old, it needs replacing — Lightspeed requires iPad 6th gen or later equivalent.
- On Windows, use Chrome — Lightspeed is optimised for Chrome’s rendering engine.
When to call a technician
- Network issues that persist after basic troubleshooting — often a router, switch, or cabling fault needing physical diagnosis
- Multiple printers dropping simultaneously — usually a network infrastructure problem, not Lightspeed configuration
- System behaving inconsistently across different terminals
- Lightspeed Payments integration not processing after all setup steps are complete
- New venue installation needing cabling, network, and hardware all set up correctly before going live
Lightspeed POS causing problems during service?
HospoDoc provides on-site POS support across Brisbane, Gold Coast, and the Sunshine Coast. We come to your venue and fix it properly.
Call 1300 467 761 Talk to our team