Cloud POS: what it fixes and what it risks

Ask an operator what worries them about moving to a cloud point of sale, and the answer is almost always the same: what happens when the internet goes down? It is a fair question. A till that stops taking orders in the middle of a Saturday service is every manager's nightmare.

But the same operators often run a legacy POS that causes problems of its own: a server in the back office that nobody understands, software that has not been updated in years, reports that can only be read on one computer, and a support contract that costs more each year. A cloud POS fixes many of those, and brings risks that are real but manageable.

This guide covers what a cloud POS is, what it fixes, what it risks, how to judge its reliability, what to ask about offline working, and how to protect a service against the failure everyone fears. Every venue and figure in it is an example.

A cloud POS is a point of sale whose software and data live on the provider's servers, reached over the internet, rather than on a computer in the venue. The tills, tablets and kitchen screens in the venue run an app or a web browser that connects to those servers.

It is a form of software as a service: the venue pays a subscription, and the provider runs, updates and backs up the system. The venue's job is to provide the devices and a reliable connection.

That is different from a legacy POS, where the software runs on a server in the venue, often installed and maintained by a local reseller, and the data lives on that server.

A legacy POS typically has a server in the back office, terminals wired to it and software that was installed years ago. It works without the internet, because everything happens inside the building.

But it has costs that grow with age. Updates are rare, expensive or both. Reports often need someone in the office at the server. Adding a terminal means calling the reseller. When the server fails, the whole system stops until someone can repair it, and backups depend on someone remembering to take them.

Many venues stay with a legacy POS because it works and switching feels risky. Our guide to one system or several: the honest comparison covers the wider choice between connected and separate systems.

The first thing a cloud POS fixes is updates. The provider updates the software for everyone, usually without the venue doing anything. New features, security fixes and changes to tax rules arrive automatically, rather than through a paid visit from a reseller.

That keeps the system current without effort, and removes a whole category of problems: software too old to run on new devices, security holes left open for years and features the venue paid for but never received.

The other side is that updates arrive whether the venue wants them or not. A good provider tests changes carefully and avoids changing how things work in the middle of service.

The second thing a cloud POS fixes is access. Owners and managers can see sales, bookings and reports from anywhere, on a phone or a laptop, without being in the venue or at the back-office server.

That matters for owners who are not on site every night, for managers who want to check the day's figures from home, and for anyone responsible for more than one venue. A question that used to wait until tomorrow morning can be answered in a minute.

It also makes setup easier. Adding a new device usually means signing in on it, not calling a reseller to install software.

The third thing a cloud POS fixes is running a POS across venues. With a legacy POS, each venue often has its own server, its own data and its own reports, and comparing them means exporting files and combining them by hand.

A cloud POS can hold every venue in one system. Sales, covers and performance can be compared across venues in one place, and menus and settings can be shared or copied, so a change does not have to be made separately in each building. Our guide to menu management when you run four venues covers the menu side.

For a group, that alone can justify the move.

The fourth thing a cloud POS fixes is the fragile back-office server. With the data on the provider's servers, a failed device in the venue loses nothing: replace it, sign in, and carry on. Backups are the provider's job.

A cloud POS also often runs on ordinary devices: tablets, phones and computers, rather than expensive dedicated terminals. Our guide to tablet POS: cheaper until it is not covers when ordinary devices save money and when they do not.

That flexibility lowers the cost of starting and of replacing hardware later.

The main risk is the one every operator names: the connection. A cloud POS depends on the internet to reach its servers. If the venue's connection fails, the system may stop, slow down or work only partly, depending on how it is built.

That risk is real, but it can be reduced a great deal. Most connection failures come from the venue's own line or equipment, not from the internet as a whole, and a second connection from a different provider covers most of them. Our guide to restaurant internet: two lines, one service covers how to set one up.

The question is not whether the internet will ever fail, but what happens when it does, and how quickly the venue carries on.

Some cloud systems offer a POS offline mode: when the connection drops, the tills keep taking orders locally and send them when the connection returns. Others stop until the connection is back. Ask exactly which yours does, and test it.

Ask what works offline: can servers ring in orders, do orders still reach the kitchen, can payments be recorded? Ask what happens to orders taken offline when the connection returns, and whether anything can be lost or duplicated. Ask how long the system can run offline.

A system without an offline mode is not necessarily a bad choice, but it makes a backup connection and a paper fallback essential rather than optional.

The second risk is the provider's own reliability. If the provider's servers have a problem, every venue on the system is affected, whatever the state of its own connection.

Ask about pos uptime: how often the system has been unavailable, for how long and at what times of day. Ask how the provider tells customers about problems, and how quickly it responds. Ask when updates and maintenance happen, and whether they ever fall during service hours.

No provider can promise perfect uptime, but a good one is open about its record and its plans.

A cloud POS holds the venue's data on someone else's servers. Ask who owns the data, how it is protected, where it is stored and how you can get it out if you leave.

The last question matters more than most venues realise. A provider that makes it hard to export your sales history, your menus or your guest records makes it hard to leave. Check before signing what you can export, in what form and at what cost.

Dependence also means price. A subscription can rise, and switching costs time and effort. Read the contract terms on price changes and notice periods.

A cloud POS can feel slower than a local system if each tap waits for a reply from a distant server. On a good connection the difference is small, but on a weak one it can make a busy till frustrating.

Test the system in your own venue, on your own connection, at your busiest time. Count how long it takes to ring in an order, open a check and close a bill, and compare it with what your team is used to.

A slow till costs seconds on every order, which adds up to minutes per table and frustration for the team.

A cloud POS is reached over the internet, so access must be protected. Every member of staff should sign in as themselves, with a code that is not shared, and managers' accounts, which can see takings and change settings, deserve stronger protection, such as a second step when signing in from a new device.

Ask the provider how data is protected in transit and at rest, how often security is reviewed and what happens if a device is lost or stolen. A lost tablet should not mean lost data or open access: it should be possible to sign it out or remove it from the account at once.

Review who has access every few months. Staff who have left should be removed on their last day, and permissions should match each person's current role, not the one they had when they joined.

Card payments add another dependency. Some cloud systems process cards themselves, through terminals linked to the POS; others record payments taken on a separate terminal. Each approach has trade-offs: an integrated terminal saves keying the amount, while a separate one can keep taking cards even if the POS is unavailable, as long as it has its own connection.

Ask how payments work with the system, what happens to a payment if the connection drops mid-transaction, and whether your terminals can carry on through a broadband fault.

A cloud POS usually costs a monthly subscription per venue or per device, with lower upfront hardware costs. A legacy POS usually costs more upfront, for the server, terminals and installation, with lower monthly fees but higher costs for support, updates and repairs.

Compare the two over three to five years, including hardware, software, support, updates, a backup connection, repairs and the time spent on the system. Our guide to how much does a POS cost in the first year covers the full first-year sum.

Many venues find the cloud option cheaper over time, but it depends on the venue, the provider and the contract.

A cloud POS runs on devices the venue chooses, which is a strength and a responsibility. Devices need updating, batteries replacing and screens protecting. A tablet that has not been updated for two years may stop working with the system, or work slowly.

Keep the devices used for service for service only, with the system open and other apps closed or removed. A till that is also used for browsing, music and messages is a till that will be slow or unavailable at the wrong moment.

A POS rarely works alone. It may connect to bookings, accounting software, payroll, delivery platforms or a loyalty scheme. With a cloud POS, those connections are often easier to set up, because both systems are online, but each one is another dependency.

List the connections you need before choosing, check which ones the system supports and how they are maintained, and ask what happens to each when one side changes. A connection that breaks quietly can leave the accounts wrong for weeks.

Whatever system you choose, plan for the outage. Install a second connection, with a router that switches over automatically. Keep power to the network equipment protected with a small backup battery. Know what your POS does offline.

Keep a paper fallback: order pads at the pass and the till, a printed menu with prices, a way to record payments and a plan for entering everything once the system returns. Practise it once, on a quiet afternoon, so nobody is learning it during service.

A venue with a backup connection and a practised fallback can ride out most outages with little disruption.

Before signing for a cloud POS, ask a short list of questions and write down the answers:

Compare the answers across providers. Vague answers to any of them are a warning.

Staff notice different things from owners. Owners notice reports and remote access; staff notice speed, how the screen is laid out and whether the system does what they expect when they tap it. A cloud POS that owners love and servers find slow will be worked around.

Involve a few experienced servers and a chef in the choice. Their view of a system during a trial is the best predictor of how it will work on a busy night.

Moving from a legacy POS to a cloud POS is a project, not a weekend task. Plan the menu, the tables, the staff and their permissions, the devices and the connection. Run the two in parallel if you can, or switch on a quiet night.

Train every member of staff before their first shift on the new system, and have someone who knows it well on site for the first few services. Keep the old system's reports, because past sales rarely move across.

Our guide to POS migration without losing a Saturday covers the steps in order.

Much of the case for a cloud POS concerns groups: reporting across venues, shared menus and remote access for owners who cannot be everywhere. But a single venue gains too: updates without visits from a reseller, devices that can be replaced quickly, reports on a phone and no back-office server to fail.

A single venue with a poor connection and no way to add a second one has more reason to hesitate. For most single venues with a reliable line, the case is strong, as long as the offline plan is clear. If in doubt, ask for a trial in your own venue, on your own connection, over a busy weekend, with the offline plan tested once on a quiet afternoon.

An invented group of three restaurants runs a legacy POS in each, with a server in each back office. Comparing the three means exporting reports every Monday. One server fails on a busy night, and the venue takes orders on paper for two days while a replacement is found.

The group moves to a cloud POS. Each venue gets a second internet connection from a different provider, with a router that switches automatically, and a paper fallback kit at each pass. The owner can now see all three venues' sales each evening on a phone, and menus are changed once and copied to the others.

In the first year, the group has one connection failure. The backup line takes over within a minute, and service carries on.

servearound is a cloud POS: the point of sale, the kitchen screens, the host stand and the reports all run in a browser and reach servearound over the internet, so updates arrive without anything to install and owners can see the day's figures from anywhere. It has no offline mode. When a screen loses its connection, it says it cannot reach servearound and keeps trying until the connection returns, so a backup line and a paper fallback belong in every venue's setup, and a tablet on a mobile connection can stand in for a till whose network has failed.

Several venues sit under one business, with a network dashboard across all of them that can be narrowed to one venue, and a menu built at one venue can be copied to the others, after which each venue's copy is its own. Bills for any range of dates can be downloaded as a spreadsheet. See Order Fulfillment.

A point of sale whose software and data live on the provider's servers, reached over the internet, rather than on a server in the venue.

Updates, access from anywhere, reporting across venues, backups and the fragile back-office server.

It depends on the system. Some keep working offline; others stop until the connection returns. Ask, and test it.

A second connection from a different provider, a router that switches automatically, protected power and a practised paper fallback.

How often the system has been unavailable, for how long, when maintenance happens and how problems are reported.

Check the contract, and check what you can export and how before you sign.

Often over three to five years, once support, updates and repairs are counted, but compare your own figures.

Sometimes, in a single venue with a poor connection and a system that still works well. Compare the long-term costs honestly.

A cloud POS fixes many of the problems of a legacy POS: updates arrive automatically, owners can see the business from anywhere, several venues can share one system, and a failed device loses nothing. Its main risk is the connection, followed by the provider's own uptime, your dependence on its terms and the speed of the till on your own network.

Ask exactly what works offline, check the provider's record and the data export before signing, and protect every service with a second connection, protected power and a paper fallback the team has practised.