Every pain in the shop has a cause in the system.

"The line dropped and the shop stopped"

This is the sharpest one, and it always arrives at the worst moment — the busiest evening of the week, a long queue, and a router that hangs. A fully cloud system needs the line to raise an invoice, and an hour of standing still during a rush is not an hour: it is half a day of sales.

The cure is a branch that is not waiting on anybody. Every branch has one small machine that runs it completely, and the tills talk to it over the shop’s own network rather than over the internet. Line down? Selling continues, receipts print, the shift closes normally. Line back? Everything reaches head office in the order it happened, without anyone pressing a button.

"A whole day was wiped with the browser data"

This happens more than you would think, in four ways: somebody cleared the browser data, or the browser cleared it under storage pressure, or the machine restarted mid-update, or a private window was opened by accident and used all day.

The cure is almost too simple to remember: the till here is a program installed on the machine, not a page open in a tab. The sale is recorded in the branch the moment it happens. Clear the browser, close any tab, swap the till mid-shift — not one sale is touched.

"The drawer comes up short and nobody is answerable"

Shop owners are rarely robbed in one large theft. They lose money to small, repeated differences nobody is answerable for. The system hands you a report showing the difference, and a report is not an action — the missing money stays missing, and it happens again.

Here the drawer is counted without the expected figure on screen, so a count is a real count rather than a number copied across. And a shortage does not simply pass: it becomes a debt in the cashier’s name, it cannot be closed without a second person’s named approval, and the next shift is blocked until an action closes it — repaid, recovered through payroll, written off, or cancelled because it was a miscount.

"Change just gets passed between cashiers"

A daily scene: one drawer runs out of small notes and the colleague next to it has plenty. A handful of cash crosses the counter and nobody writes anything down. At closing one is short and one is over, there is no explanation, and the two of them argue about it.

The cure is to make that transfer a movement like any other: out of one shift and into the other, with both names on it, inside a ceiling head office set for how much may move that way. The change reaches the drawer that needs it in seconds, and neither one closes short.

"The customer wants to pay several ways and the system says no"

A real counter is not the demo. A customer with some cash and the rest on a card. A customer holding dollars. A customer with loyalty points who wants to use them and pay the difference. Most systems assume one customer paying one way.

On one invoice at the same time: part cash and part card · cash in more than one currency, each at the branch’s own rate · loyalty points as part of the payment · a voucher against part of the bill — with change calculated correctly across all of it.

And underneath it, discipline that prevents expensive mistakes: a payment method the branch may not take is not offered at all rather than offered and refused · a stale exchange rate is refused rather than guessed at · a method needing a reference number cannot pass without one, and the reference is scanned rather than typed · and card slips are counted against card sales when the drawer closes.

"We type weights, batches and serials by hand"

This is what separates a real till from one in a slide deck. Any system sells a bottle of water. The pain starts at the awkward items:

1. Scales — weighed goods read straight off the scale label, price and weight from the barcode, with no typing and no keypad ritual.
2. Batches and expiry — you know which batch went out on which sale. That is the difference between a recall you can execute and one you watch happen.
3. Serial numbers — captured at the sale and checked at the return, so a unit that never left your shop cannot be refunded into it.
4. Units — the same product by piece, by pack and by case, each with its own barcode and price. Scanned, not looked up.
5. Sizes and colours — without turning one product into forty records a cashier hunts through during a rush.

"The order went out with the rider and the money never came back"

Delivery is where money goes quietly missing, because an order that left the shop is stock out of the door **and** cash that has not returned. Most systems stop at "mark as delivered".

The cure is to put a name on both. The order goes out with a named rider, and a live board shows what is out right now — which order, with whom, since when, where it is going. When the rider returns, the money is counted and signed for against the orders it belongs to, not dropped into a drawer and hoped for.

And a trip can end more than one way: delivered, refused at the door, partly returned — each with different consequences for the stock and the money, each recorded as what it was. A delivery return is a real return, back into stock and onto the books, not a manual correction somebody remembers to make.

"The staff see no reason to sell more"

In a shop with more than one cashier or a rep on the floor, the biggest difference in sales does not come from the system — it comes from the person selling knowing they are paid for what they sold.

There is a commissions app you can switch on for point of sale: commission for a cashier or a rep in the branch, by item group or on the whole invoice, configured per branch — and invoices group by salesperson on their own, without anyone sorting them at month end.

"The cashier wiped the machine and the day went with it"

The machine at the counter is the easiest thing in the shop to lose. It gets dropped, stolen, reimaged, swapped because it got slow, and wiped by an unhappy employee on their way out. If the day’s work lived on it, it leaves with it — and you do not even know what left.

The cure is for that machine not to be holding your business in the first place. The till is a screen, and a sale is recorded in the branch the moment it happens. Delete the program, swap the machine, reinstall Windows from scratch — the branch still holds every sale, every shift and every drawer movement.

"Every month end we fix a spreadsheet"

This is not an accounting pain; it is a symptom of a disease somewhere else. When the till is an island, somebody has to build a bridge by hand every month between it and the books. That bridge breaks, and every time it breaks you pay twice — once in time and once in an error that got through.

Sales, refunds and cash movements land in the accounting books themselves. Your accountant works in a real accounting system, not in a file exported from the till and reconciled by hand.