What is a cloud-based point of sale?

A cloud-based POS stores your data online, so your staff can ring up sales from any device and see the same records everywhere.

With cloud-based, you can run at a counter, on a handheld device, on a tablet or across multiple locations. Losing one device doesn't lose your records and changing a price in one place updates all your connected devices. From a management perspective, owners and managers can view sales, stock and other records without standing at the till.

While a local device may hold enough to show a catalogue and build a sale, the online service keeps your main account records and syncs approved changes between connected devices.

The device handles the work in front of your staff. The cloud keeps the shared record.

A cloud-based POS moves information between your devices and an online business account in five stages, happening around the transaction without replacing checkout and payment.

1. Your business account holds shared information: products, prices, staff permissions and locations.

2. An authorised POS device connects and receives what it needs to sell.

3. A staff member records a sale, return, price change or other action.

4. The device sends that change to the online service straight away, or queues it until a connection is available.

5. The cloud record updates, and the change becomes available to other devices, reports and connected tools.

Records don't all move at the same speed or in both directions. A sale may appear quickly in a dashboard while a connected accounting tool updates later. When considering a system, ask the provider what synchronises, how often it moves, and which system is treated as the final source of truth in the case of conflicts.

In contrast to a cloud-based system, a local POS system (On-premise) records sales only on that machine. You can't sync changes to other devices, and you must visit the machine to access reports. A cloud-based POS keeps your main record on the provider's online service. An on-premise POS keeps it on computers or servers at your business.

Some POS systems are hybrid. They use an online service for shared records while keeping enough information on a device or local network to support selected work. Ask your provider which work and keeps running under real trading conditions.

A cloud-based POS stores working data on your device and queues changes until they sync to the online service, which keeps your main account records and syncs approved changes between connected devices. Because your data doesn't live in one place, you can access information from anywhere and one device failure doesn't wipe out your business data.

Two screens can briefly show different values during a connectivity break. One may display its last downloaded information while another has a newer record. A reliable system reconciles those differences when the connection returns.

Your provider manages the hosted service - the online servers that store your shared records. You stay responsible for user access, devices, permissions and lawful collection of information.

In South Africa, POPIA requires a responsible party to protect the integrity and confidentiality of personal information using appropriate technical and organisational measures. The Information Regulator provides guidance on the Protection of Personal Information Act.

Business records and payment-card data are two different things. A POS system may record the payment method and a transaction reference without storing the full card details. Use approved payment technology, and understand the payment-security responsibilities that apply to your setup.

Cloud describes how the POS service and records are delivered. It doesn't tell you the system runs in a browser, is mobile, is integrated, is secure or sells across every channel. It doesn't describe the hardware shape either. A cloud-based POS can run at a counter, on a handheld device, on a tablet or across multiple locations.

The value of a cloud POS comes from shared access and central coordination: 

• You and your authorised managers may be able to see current sales without being at your business.

• Product, price or staff changes can be sent to connected devices from one account.

• Several devices or locations can work from one shared set of approved records.

• The provider can manage more of the hosting, service maintenance and update delivery.

• A replacement device may be able to reconnect to your business account instead of depending on records held only on the old device. Losing one device does not necessarily mean losing your business record.

• An online service can make it easier to pass selected information to compatible accounting, ecommerce, loyalty or other tools.

These are potential benefits, not guarantees. Remote access, synchronisation, integrations and recovery all depend on what the provider has built, what you have switched on or what you are paying for.

Running your point of sale system on an online service brings five risks: provider dependence, changing costs, no control over updates, how much of your data you can access if you switch, and one wrong change reaching every connected device.

Provider dependence. You rely on your provider's service availability, support, update process and account controls - if they have downtime, you will be down too. Similarly, if they are set up in another country, your support relies on their business hours.

Subscription and scaling costs. Charges may change with plans, devices, users, locations, integrations or stored data.

Less control over update timing. Central updates can reduce maintenance, and a change may still affect your workflow or your older hardware. Ask how major updates are communicated and tested, particularly if the provider is from a different time zone.

Data access at exit. If the service ends, you need to know what you can export, in which format, and for how long your account stays available.

Shared mistakes. A wrong price or product change can travel to several connected devices. Permissions and review steps matter more when one change has a wider reach.

Offline mode is not a single yes-or-no feature. Your POS app can keep working offline for tasks like viewing products and building a sale, but a cloud POS system does need a connection to synchronise. If synchronisation fails, live access, remote reporting, updates and synchronisation may pause. Test what your system does in four layers.

When selecting a POS system, don't only test a simple cash sale. Try a refund, discount, split payment, product change and a sale from two devices. Then reconnect them in a different order and check your final sales, stock and payment records.

Electronic payment acceptance has different connectivity rules from the POS app. Your device might show products while card authorisation is unavailable, or a payment device might connect through mobile data while the POS screen cannot reach the cloud service.

An internet outage and a power cut are different failures. The cloud service may still be running while your POS device, Wi-Fi router, printer or local network has no electricity.

Map the power needs of every part of your setup. Check battery life, charging, router backup, mobile data and how staff confirm whether a payment or sale completed before trying again. Backup power cannot restore an unavailable online service, and backup connection cannot help hardware with no power.

Synchronisation moves approved changes between your devices and the shared service, backup keeps recoverable copies, and export gives you a usable file of your own records.

A system can synchronise quickly without giving you a useful export. It can also keep backups the provider controls without letting you restore individual records. Ask separate questions about each process.

A cloud-based POS system suits you if you need to see your sales away from the business, run more than one device or location, or want to change products, prices and staff access from one account.

• An owner who needs visibility without being at the business.

• A team using more than one POS device, or selling from changing locations.

• A business that wants central product, price or staff changes.

• A growing business that may add devices or locations over time.

• A business that wants the provider to manage more of the hosting and update delivery.

• A team prepared with backup connectivity, power and offline procedures for important trading tasks.

A cloud-based POS needs more careful evaluation where connectivity isn't reliable, where you depend on highly specialised local equipment, or where rules require unusually strict control over data location and infrastructure. A hybrid or on-premise system may fit some of those cases better.

Trace one change all the way through the system. A feature list won't tell you what you need to know.

1. Create or change a product, and check when the update reaches every intended device.

2. Complete a sale, and confirm when it appears in the shared report.

3. Interrupt the connection, and test what staff can see, sell and synchronise.

4. Create conflicting changes on two devices, and ask which record wins.

5. Remove a staff member, and check when their access ends on every device.

6. Export your business records, and confirm that the file is complete and usable.

Then ask who supports each failure. If the POS screen works but the payment device does not, or the sale appears on one device but not another, your staff need to know who to call: the POS provider, the payment provider, the network provider or your own administrator.

Ask which information is stored where, which system wins when records disagree, what works without a connection, and what you can export when you leave. These eleven questions cover the ground before you sign.

• Which information is stored in the cloud, on the device, and on any local network?

• Which system is the source of truth when records disagree?

• How quickly do products, prices, sales, stock and permissions synchronise?

• What can staff see, sell and update without an internet connection?

• How are queued sales protected from duplication after reconnection?

• What backup, retention and recovery processes are included?

• What data can the business export, in which format, and at what cost?

• What access remains when the subscription or contract ends?

• Where is personal information processed, and which party is responsible for each safeguard?

• How are provider outages, security incidents and major updates communicated?

• Which costs change when devices, users, locations or integrations are added?

The six common mistakes are treating cloud as a feature, assuming real time means instant, confusing synchronisation with backup, ignoring the exit path, and giving every user broad access.

Treating cloud as a feature. Cloud is a delivery and storage model, not a feature in itself. The value comes from the access, synchronisation and recovery behaviour it gives you.

Assuming real time means instant. Real time doesn't mean instant. Different records and integrations update on different schedules, so confirm the delay that matters to your business.

Confusing sync with backup. Synchronisation is a different job from backup. Fast synchronisation spreads an accidental change quickly, and recovery needs a separate process.

Accepting "works offline" as a complete answer. Test seeing products, creating sales, taking payments and reconnecting separately.

Ignoring the exit path. Plan the exit path early. A cloud service is easier to join when it is also clear how your data and records can leave if you are no longer satisfied.

Giving every user broad access. Give each person their own account and only the access they need. Remote availability raises the importance of permissions, and of removing old access promptly.