Home › Knowledgebase › KB-1502

Cloud Pos And Inventory Management For Small Business

Summary

This guide helps you troubleshoot and resolve: Cloud Pos And Inventory Management For Small Business. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Moving your point-of-sale (POS) and inventory management from a single back-office PC to the cloud removes the risk of hardware failure, data loss, and unexpected downtime. For retail and shopfront operators, cloud-based retail systems provide secure sales data, real-time stock visibility, and automatic backups. However, these systems depend entirely on your business internet connection and local network infrastructure. This guide covers the network requirements, connectivity considerations, and internet infrastructure needed to support cloud POS and inventory systems in a retail environment.

Network Requirements for Cloud POS and Inventory

Cloud POS platforms require a stable, low-latency internet connection at every sales counter. Before migrating, assess your current network against the following minimum requirements.

Recommended Bandwidth

Run a speed test from the counter location during trading hours using a wired connection to verify actual throughput. Wi-Fi signal strength at the sales counter should be at least -65 dBm with minimal packet loss.

Failover Internet Connection

Retail businesses cannot afford to stop trading if the primary internet service drops. Configure a failover connection using one of the following:

Test failover monthly by disconnecting the primary WAN cable and confirming that counter terminals remain connected to the cloud POS platform.

Router and Firewall Configuration

Your business router and firewall must prioritise POS traffic over general internet browsing and guest Wi-Fi. Use the following configuration steps as a baseline.

  1. Log in to your router administration page, typically at 192.168.1.1 or 192.168.0.1.
  2. Navigate to QoS > Traffic Prioritisation or Bandwidth Management.
  3. Create a rule for POS traffic using the static IP addresses of your counter terminals.
  4. Set POS traffic to High priority and guest Wi-Fi to Low priority.
  5. Enable UPnP only if required by your payment terminal vendor; otherwise keep it disabled for security.
  6. Ensure outbound HTTPS (port 443) is not blocked by firewall rules or content filtering.

If your router is provided by your internet service provider, you may need to request administrative access or ask them to apply QoS rules on your behalf.

Retail Hardware and Network Integration

Cloud POS systems connect to several retail-specific peripherals. Confirm the following before go-live:

Internet Outage Procedures and Offline Mode

If your internet connection fails during trading hours, cloud POS systems may be unable to process card payments, update inventory, or sync sales data. Do not proceed with cash sales unless your platform supports offline mode and you have tested the offline-to-online sync process.

Before going live, verify the following with your POS vendor:

Create a printed outage procedure for staff that includes:

  1. Switching to the failover internet connection if available.
  2. Processing cash sales using offline mode, if supported.
  3. Recording card payments manually using EFTPOS paper receipts where permitted.
  4. Reconciling offline transactions once the primary connection is restored.

Troubleshooting Connectivity Issues

POS Terminal Cannot Connect to Cloud Platform

  1. Check that the terminal has an IP address on the business LAN, not the guest Wi-Fi network.
  2. Ping the cloud POS domain from a connected device to verify DNS resolution.
  3. Restart the router and confirm the failover connection is not active unless intended.
  4. Check the POS application status page for reported outages.
  5. If the issue persists, Open a Ticket.

Payment Terminal Integration Fails

  1. Verify the EFTPOS terminal is connected to the same network segment as the POS terminal.
  2. Check that port 443 is open and not blocked by firewall rules.
  3. Confirm the payment terminal has the latest firmware and is paired with the correct POS station ID.
  4. Process a test transaction for a low value to confirm end-to-end communication.
  5. Escalate to your payment provider if the terminal displays a communication error.

Inventory Sync Errors During Migration

  1. Compare stock counts between the legacy system and cloud POS after each business day.
  2. Check the migration log in the cloud POS admin panel under Settings > Data Import > Sync History.
  3. Re-export product lists from the legacy system as CSV files if records are missing.
  4. Re-import using the cloud POS import tool, mapping fields such as SKU, product name, supplier, and reorder point.
  5. Do not delete legacy data until synchronisation is verified across all counters.

Security and Access Controls

Protect transaction data and customer records with the following measures:

Ongoing Support

Cloud POS and inventory systems reduce hardware maintenance, but they rely on a stable internet connection and correctly configured network equipment. If you experience connectivity issues, failover problems, or need help configuring access for your retail team, Open a Ticket.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket