One POS across 12 branches: lessons from POS Kuwait

Kuwait Retail Group runs a retail chain with multiple branches. Day to day, that means sales at every till, stock moving between a warehouse and the shop floor, and management needing one reliable picture of the whole business.

They asked us for a full-featured Point of Sale and Warehouse Management System that would handle sales, inventory and multi-branch reporting in one place. The project ran over eight months and was delivered in 2023.

When several branches sell from the same stock, inventory has to stay in sync in real time. If it doesn’t, counts drift. Items get oversold in one branch while sitting unsold in another, reorders are placed that were never needed, and before long nobody trusts the reports.

That drift rarely shows up as one big failure. It builds quietly, one mismatched count at a time. So the first design priority was not the checkout screen — it was making sure every sale, transfer and delivery updated one shared inventory.

For management, the cost shows up as decisions made on the wrong numbers: buying stock you already have, or missing sales because the system says an item is out when it is still on a shelf in another branch.

A checkout cannot pause because the network does. Customers are standing at the counter, and a till that freezes on a dropped connection costs sales and goodwill immediately.

We treated offline capability as a first-class requirement, not a fallback. Each POS terminal keeps selling when the connection drops, then reconciles with central inventory once it is back online. Real-time sync and offline resilience had to work together, and the system was designed around that combination from day one.

Reconciliation is where the careful work happens. When a terminal reconnects, its offline sales need to be applied to central stock in a way that keeps counts correct across every branch, so the figures managers see reflect what was actually sold.

• Terminals keep trading without a connection
• Sales made offline reconcile with central stock when the link returns
• Inventory stays aligned across branches as sales happen

Point of sale and warehouse management often live in separate tools, connected by exports or manual updates. Every handover between them is a chance for stock records to diverge.

In POS Kuwait, warehouse management sits in the same system as point of sale. Stock received, moved and sold is recorded against one source of truth, so the number on the screen at the till and the number in the warehouse report are the same number.

It also simplifies training. Staff learn one system instead of several, and managers no longer need to compare exports from different tools to understand where stock has gone.

We built the system as a web application on React and Node.js, with PostgreSQL as the central data store. Retail data is deeply relational: products, branches, stock movements and sales all connect to each other, and reliable reporting depends on those relationships staying consistent.

A relational database enforces that consistency at the core, which is exactly what multi-branch reporting needs. Getting the data model right early made every later feature — from transfers to reports — simpler to build and easier to trust.

• Point of sale with fast checkout at every branch
• Offline-capable terminals
• Real-time inventory sync across branches
• Warehouse management from receiving to shop floor
• Multi-branch sales and inventory reporting

The system was deployed across 12 branches. Stock discrepancies fell by 80%, and checkout time was cut significantly. With sales, inventory and warehouse data in one place, the business now reports from a single, consistent source.

Behind those figures are simpler days for staff and managers. Counts match what is on the shelves, stock moving between the warehouse and the shop floor is recorded in the same system, and reports come from one consistent source instead of several partial ones.

If you run more than one branch from spreadsheets, disconnected tills or separate stock tools, the pattern is the same: one source of truth, offline-ready terminals and live inventory. That combination is what turns stock counts back into numbers you can act on.

A good first step is to map where stock lives today and how it moves: deliveries, transfers, sales, returns and stock takes. That map usually shows exactly where counts start to drift, and which parts of the system matter most.

We would be happy to look at how your branches work today and map out what a single system could look like. Get in touch, or use the project estimator at /pricing/ to get a first sense of scope.