Buying a till outright: what a one-time payment actually buys

Most restaurant software is rented. You pay every month, and on the month you stop paying, the till stops ringing — not because anything broke, but because the software was never on your side of the wire.

The Local Edition is the other arrangement. You pay once, the software installs on a computer in your shop, and it keeps working whether or not we are still in business. This article is about what that sentence includes, and what it very deliberately leaves out.

What one payment buys

A perpetual licence for one branch. Bought once from your GoSufra account, tied to one machine, with no renewal date and no expiry. Concretely:

• The dashboard, the POS, the kitchen display and the waiter app — all four served by the same Windows PC over your own WiFi.
• A PostgreSQL database on your own disk, holding the sales, the recipes, the costs, the staff and the customers.
• A nightly backup at three in the morning, written to a folder on that machine.
• The installer, which you can re-run on new hardware if the machine is replaced.

No per-user fee, no seat count, no “premium” tier holding a module back. A restaurant with eleven staff pays the same as one with three.

What it deliberately does not buy

This is the half most one-time-payment pages leave out, and it is the half that decides whether you will be happy in six months.

Online ordering, the customer app and the driver app are not included. Not as an upsell — they cannot work. Those three need an address on the public internet that a customer’s phone can reach from the street, and a PC behind a shop router does not have one. If people order from you online, you want the hosted platform, and this page is not for you.

A second branch is a second licence, and the two cannot see each other. Two machines in two buildings with no server between them are two independent islands: no shared stock, no staff moving between them, no consolidated report on Monday. That gap is real and it is not a configuration you have missed.

We do not hold a copy of your data. That is the point of the arrangement, and it is also its risk: if the disk dies and nobody ever copied the backup folder to a USB stick, the data is gone. Nobody can restore what nobody has.

The arithmetic, honestly

The comparison people expect is “licence price ÷ monthly price = months to break even”. It is the right shape and the wrong inputs, because the two products are not the same product.

Run it on what you would actually use:

For a single branch that sells over the counter and does not take online orders, the total usually crosses somewhere in the second year. Before that point you are not buying savings — you are buying certainty: a fixed cost, a machine you control, and no supplier who can change the price or switch you off.

If you are taking online orders, or you expect a second branch inside a year, the arithmetic never gets there, because half the product you would be comparing against is not on the table.

The three jobs you take on

Owning the software means owning the operational work that a hosted platform quietly does for you. There are three, and they are all small until the day they are not.

1. The machine. One Windows PC — normally the cashier’s — is now a server. It should be the machine that stays on, not the laptop somebody takes home. Give it a reserved address on the router, or the bookmark every tablet saved stops working the first time the router restarts.

2. The backup copy. A backup written every night to the same disk that holds the database protects you from a mistake, not from a dead SSD. Copy the backup folder to a USB disk as part of closing up. It is under forty files — every night for a week, weekly for a month, monthly for a year — and it takes less time than counting the drawer.

3. Deciding when to update. Nothing updates itself. A new version arrives as a new installer, and you run it when you want it — which means you also choose not to run it, and a version left alone for two years is a version nobody is testing against your data. Update between services, never before one.

Who this is actually for

Buy it once if: you run one branch, the counter is where the money is made, your internet is unreliable or expensive, and you would rather own a fixed asset than carry a monthly line item.

Rent it monthly if: you take online orders, you run more than one branch or expect to, you want your customers to have an app, or you would rather somebody else owned the backup problem.

And if you buy locally and outgrow it, that is not a wasted decision. The local build and the hosted platform share one database schema and key every record by a GUID, which is what lets a whole branch be exported from the machine and imported into a cloud account as one of its branches — without two independent databases colliding on the same id. The door stays open in both directions.