Point of Sale Systems: Choosing One and Connecting It to Everything Else
Key takeaway
A POS must keep selling when the internet drops — that single requirement eliminates many options. After that, the decision is about integration: if stock, pricing, and sales don't flow to your other systems automatically, staff will reconcile by hand forever.
The till interface is the part everyone demonstrates and the part that matters least. What determines whether a POS works for a growing retailer is what happens around it — during an outage, at stock count, and at month end.
Non-negotiables
- Offline mode that can complete a sale and card payment, then sync when connectivity returns. Losing an afternoon of trade to a broadband fault is unacceptable.
- Payment integration with the terminal, so amounts aren't keyed twice — double keying is a persistent source of discrepancies.
- Fast search and checkout on a busy Saturday, with hardware that survives retail use.
- Clear, restricted permissions for refunds, discounts, and voids, with everything logged to a named user.
Integration is where it pays off or doesn't
- Inventory in both directions — a sale decrements stock and the same stock figure is visible online.
- Pricing and promotions defined once and pushed everywhere, not maintained per channel.
- Sales to accounting, summarised daily with a reliable reconciliation to takings.
- Customer records shared with your CRM or loyalty system, so in-store and online purchases are the same customer.
- An API that exposes transactions, not just a nightly report export.
Multi-store considerations
- Stock visibility across locations, and a transfer process that's usable by store staff.
- Central price and product management, with controlled local exceptions.
- Consolidated reporting that compares like with like, including per-hour and per-employee views.
- Rollout and training — every store will hit the same problems, so fix them once and document them.
Evaluate on the boring things
Ask what happens when the card terminal disconnects mid-transaction, how a partial refund across mixed payment methods is handled, and how a day's takings are reconciled when the count disagrees. Those answers separate systems built by people who have worked in retail from ones that haven't. Then run a full trading day in a single store before committing to a chain-wide rollout.