Clover POS not working? Common problems & how to fix them.
Published: 08 Sep 2026
Clover POS station setup at a Brisbane hospitality venue.
Clover is a POS and payments platform owned by Fiserv, sold in Australia primarily through banks and payment providers — NAB, Westpac, CommBank, and others offer Clover hardware as part of their merchant services packages. That sales model means many venue owners find themselves with Clover hardware but unclear on who to call when something goes wrong — their bank’s merchant services team handles payments, but not on-site technical problems.
This guide covers the most common Clover POS problems in hospitality venues and how to fix them.
1. Clover POS won’t connect or keeps going offline
Clover is a cloud-dependent system. All transactions, menu data, and reporting communicate with Clover’s servers via the internet. If your internet drops or becomes unstable, Clover either stops working or goes into a limited offline mode.
Common causes: internet connection dropped; the device’s Wi-Fi connection is unstable; or Clover’s servers are experiencing an outage. The device may show as connected to Wi-Fi but still not reaching Clover’s servers if DNS resolution is failing.
- Test internet from another device (phone, laptop) — if that’s also not working, the problem is your internet connection, not Clover.
- On the Clover device: Settings → Wi-Fi → forget the current network → reconnect. This forces a fresh connection and new DNS lookup.
- Check Clover’s server status — search “Clover POS status” or visit status.clover.com to see if there’s a platform outage.
- Restart your router — hold the power button off for 30 seconds, then back on. Wait 2 minutes before testing Clover again.
- If dropouts happen regularly during service: put Clover devices on a dedicated Wi-Fi SSID separate from customer devices, and upgrade to a business-grade router. Customer Wi-Fi congestion is the most common cause of intermittent Clover dropouts in venues.
2. Clover printer not printing receipts or kitchen orders
Clover network printers communicate via a fixed IP address stored in the Clover device’s printer settings. If the router rebooted and reassigned the printer a new IP, Clover can no longer reach it — but won’t always show an obvious error.
- Print a self-test page from the printer: hold the feed button while the printer is on. The IP address will print on the ticket.
- On the Clover device: Settings → Printer → find the affected printer → update the IP address to match the self-test printout.
- In your router’s admin interface, set up a DHCP reservation for the printer using its MAC address — this permanently assigns the same IP every time and prevents this recurring.
- If the printer is Bluetooth-connected: check that it hasn’t been paired to a different device. Clover Bluetooth printer pairing can be disrupted if another device attempts to connect to the printer.
- Power cycle the printer completely (off, wait 10 seconds, on) — some thermal printers get stuck in a fault state that only a full restart clears.
3. Clover card reader not connecting or payments failing
Clover’s payment hardware — the Clover Flex, Clover Go, or integrated Station card reader — communicates directly with Clover’s payment servers. Payment failures can be hardware, software, or merchant account issues.
Three distinct causes: the reader’s Bluetooth or network connection to the Clover device has dropped; the reader needs a firmware update that is blocking payments; or the merchant account has an outstanding compliance or verification requirement.
- For the Clover Flex or Go: check that Bluetooth is active on the Clover Station/Mini and that the reader shows as paired in Clover’s device settings. If not: Settings → External Payment Devices → re-pair the reader.
- Restart the card reader by holding the power button for 10 seconds — this clears most transient errors and firmware update states.
- Check for pending firmware updates on the reader. Clover pushes firmware updates automatically — if an update is in progress or failed, the reader may decline payments until it completes. Allow the update to finish fully before attempting further transactions.
- If the reader is connected and updated but payments are still failing: contact your bank or Clover provider to check whether there are any merchant account holds or verification steps outstanding.
- Run a $1 test transaction with a card that’s definitely not expired or blocked — to confirm whether the decline is from Clover, the issuing bank, or the card itself.
4. Clover Station freezing or running slowly
Clover Station runs Android. Like any Android device in continuous use, memory builds up over time and performance degrades if the device is never fully restarted.
- Fully restart the Clover Station at the start of each trading day — hold the power button, select Restart. Not just screen lock or sleep — a full restart.
- Check for pending software updates: Clover app updates sometimes queue during service and consume processing resources. Set updates to download overnight.
- Close any apps running in the background — swipe up from the bottom to see open apps on the Clover Station and close any not needed for POS operation.
- If the Station is more than 3–4 years old and slowness persists, the hardware may need replacing. Clover’s software continues to be updated but older hardware generations don’t keep pace.
- Check internal storage — if the Clover Station’s storage is more than 80% full, performance degrades. Remove any stored photos, videos, or unused apps from Settings → Storage.
5. Clover apps or integrations not working
Clover runs on an app marketplace model — functionality like loyalty programs, reporting add-ons, table management, and delivery integrations are added via the Clover App Market. These apps are third-party and have their own setup and troubleshooting paths.
Third-party apps in the Clover App Market are maintained by their respective developers. App failures are usually caused by: the app needing an update; an expired or cancelled subscription to the app; or a Clover platform update breaking compatibility with an older version of the app.
- Check the Clover App Market for an update to the affected app — open the Market, find the app, and look for an update option.
- Check that the app subscription is still active — some Clover apps have separate monthly subscriptions that may have lapsed.
- Uninstall and reinstall the app from the Clover App Market — this often resolves compatibility issues after a Clover platform update.
- If the app has its own support team (most Clover App Market apps do), contact them directly — they will have better visibility into issues specific to their app than Clover’s general support.
6. Staff can’t access manager functions or permissions are wrong
Clover uses a Role-Based Access Control system configured through the Clover web dashboard. Simply setting someone as “Manager” in the app may not grant all permissions — each permission must be individually enabled in the role settings.
- Log into dashboard.clover.com → Employees → Roles → find the relevant role → check every permission toggle individually.
- For refunds: “Issue Refunds” must be explicitly enabled. For reports: “View All Reports” must be enabled. These are off by default for many roles.
- After changing permissions, the staff member must log out and back in on the Clover device for changes to take effect.
- If using a PIN-based login: confirm the staff member’s PIN in dashboard.clover.com → Employees → find the employee → PIN section.
When to call a technician
- Internet or network issues persisting after basic troubleshooting — often a router, switch, or cabling fault needing physical diagnosis
- Card reader not pairing after multiple reset attempts — may indicate a hardware fault requiring replacement
- Multiple devices behaving inconsistently across the venue — network infrastructure audit needed
- Clover system installed by a bank or provider but not properly configured for the venue’s actual workflow — reconfiguration visit
- New venue installation with cabling, network setup, and full Clover configuration needed before opening
Frequently asked questions
Why is my Clover POS not connecting after setup?
Clover is a cloud-based system that requires an active internet connection to operate. If Clover won’t connect, first check that your internet connection is working from another device. If the internet is fine, check that Clover’s servers aren’t experiencing an outage (search ‘Clover POS status’). If both are fine, the issue is likely the device’s network settings — try forgetting the Wi-Fi network and reconnecting, or connect via ethernet if the Clover Station supports it.
Why is my Clover printer not printing receipts?
The most common cause is that the printer’s IP address has changed since it was added to Clover’s settings. Print a self-test page from the printer (hold the feed button) to find its current IP, then update this in your Clover device’s printer settings. To prevent the issue recurring, assign the printer a static IP address via your router’s DHCP reservation settings using the printer’s MAC address.
Who do I contact for Clover POS support in Australia?
Clover in Australia is typically sold through banks (NAB, Westpac, CommBank) and payment providers rather than directly — so your first support contact is usually the institution that provided your Clover system. If you need on-site technical support for hardware, network, or installation issues, HospoDoc provides on-site Clover support across Brisbane, Gold Coast, and the Sunshine Coast.
Clover POS causing problems?
HospoDoc provides on-site POS support across Brisbane, Gold Coast, and the Sunshine Coast.
Call 1300 467 761 Talk to our team