Cloud EPOS for trade merchants

What a back-office server actually costs

The traditional merchant setup is a server in a back room running a database, with tills connected to it over the local network. It works, and it has been working for twenty years. The costs are just not on an invoice.

• Hardware that has to be replaced every five to seven years
• Backups that depend on someone remembering, and are rarely tested
• Upgrades that are projects, scheduled around an engineer’s availability
• A single point of failure sitting in a room nobody checks
• No access to your own numbers unless you are physically on site

The failure mode is well known: the server dies on a Friday, the last verified backup is older than anyone expected, and the business spends a week rebuilding what it already had.

What cloud changes

Nothing to maintain

There is no server on your premises. Hosting, patching, capacity and security are handled centrally, and continuous backup is part of the subscription rather than a task assigned to whoever is in on Friday.

Updates that just arrive

Improvements ship regularly and are live for everyone. There is no version you get stranded on because upgrading was quoted as a project, and no engineer visit to schedule.

One set of numbers, from anywhere

Branches share one system, so group reporting does not require consolidating exports from three sites. You can look at today’s takings, margin or debtor position from home, from a supplier’s office, or from the van.

Growth without a project

Adding a till or a branch is configuration rather than procurement. There is no additional server, no VPN between sites, and no separate database to reconcile.

The objection that actually matters

Every merchant asks the same question, and it is the right one: what happens when the internet goes down?

For most cloud point of sale products, the honest answer is that the till stops. That is a genuinely bad trade — swapping a server you control for a broadband line you do not.

PlanIt EPOS is cloud-hosted but offline-first, which is a different architecture rather than a marketing phrase. Products, prices and customer records are held on the device. Sales are rung through, priced, discounted and receipted locally with no connection at all, then queued. When the line returns, the queue synchronises automatically in order, each sale carrying its own identifier so it can never post twice, with invoice numbers assigned by the server so the sequence stays gapless.

Data, security and ownership

Data is held in a managed cloud database in the UK region, with continuous backup and encryption in transit and at rest. Access is controlled by named user accounts with role-based permissions, so a counter hand and a director do not see the same screens.

Every tenant’s data is isolated at the database level rather than filtered in the application, which is the difference between a boundary and a convention.

And your data remains yours. Products, customers and transactions export in standard formats whenever you want, including on the way out. A system you cannot leave is not a system you chose.

Hardware and what you can keep

PlanIt EPOS runs in a browser, so the till can be the Windows PC you already have, a Mac, an iPad or an Android tablet. Standard keyboard-wedge barcode scanners, thermal receipt printers and label printers all work, and your existing card terminal stays exactly where it is.

In practice most merchants replace nothing on day one. The tablet in the yard is usually the only new purchase, and it is optional.

Moving across

1. Export products and customers from your current system to CSV.
2. Import supplier price files — PDF, Excel or CSV — to establish current costs.
3. Configure branches, tills, VAT, price bands and account terms.
4. Enter opening account balances so aged debt is correct from day one.
5. Go live on a quiet day with support on hand.

Onboarding, data import and training are included in the subscription, which is monthly and carries no long-term contract. Priced on tills, branches and users — never on a percentage of turnover.

Comparing the two models honestly

Server-based systems are not bad software. Many of them do the job. The difference is where the cost, the risk and the effort sit.

The only column where the traditional model wins outright is a broadband failure — which is precisely the gap offline-first closes. That is why the two decisions belong together: cloud hosting for the maintenance, the updates and the access; offline-first tills so the counter never depends on the line staying up.