---
title: "Khushi POS: Seven branches, one offline-first POS. Commercial POS hardware + sub-second sync."
description: "Retail POS systems break in the worst place: at the checkout counter when the internet goes down. We built Khushi POS on commercial POS hardware with offline-first architecture, real-time inventory sync across seven branches, and a deployment story that doesn't require a tech team on site."
source: "https://www.kensink.com/cases/khushi-pos/"
---
RETAIL · POS · HARDWARE + SOFTWARE Khushi POS (BD) · BD

# Khushi POS.  
Seven branches, one offline-first POS.

Commercial POS hardware + sub-second sync.

7

Branch deployment

OFFLINE-FIRST POS RETAIL · POS · HARDWARE + SOFTWARE

## Khushi POS: Seven branches, one offline-first POS. Commercial POS hardware + sub-second sync.

Retail POS systems break in the worst place: at the checkout counter when the internet goes down. We built Khushi POS on commercial POS hardware with offline-first architecture, real-time inventory sync across seven branches, and a deployment story that doesn't require a tech team on site.

[View .md](https://www.kensink.com/cases/khushi-pos.md)

7

Branch deployment

Offline-first

Sales never blocked on connectivity

Real-time

Inventory sync when connected

< 30 min

Per-store install time

01 · THE PROBLEM

## Where they were stuck.

Multi-branch retail in Bangladesh has a connectivity problem. Internet at the store level is unreliable. Existing POS solutions assumed always-online. When the connection dropped, sales stopped. The owner had seven storefronts running on a different ad-hoc Excel + cash system because no SaaS POS worked reliably.

02 · OUR APPROACH

## How we built it.

-   01 Offline-first transaction model: every sale persists locally first; sync to central inventory + reporting is an eventual operation, not a blocking one
-   02 CRDT-style conflict resolution on inventory across branches: if branch A and branch B both sold the last unit, the system handles the conflict gracefully and alerts the owner
-   03 Commercial POS hardware integration via the vendor's official SDK; receipts, barcode scanning, card payments all native
-   04 Per-branch reporting that works offline and rolls up to a central dashboard the owner reads on their phone
-   05 Deployment: one-person install per store, under 30 minutes including hardware setup

> “Our internet has gone down four times this month. We didn't lose a single sale. That's worth more than the entire system cost.”

_Store Owner

Khushi POS pilot branch_

\[TECH STACK\]

-   TypeScript
-   React Native
-   POS hardware SDK
-   SQLite (offline)
-   Postgres
-   Redis

\[ENGAGEMENT\]

Duration Multi-year (2017 – 2019)

Client Khushi POS (BD)

Shape OFFLINE-FIRST POS

Handoff Full ownership · 90-day warranty

START YOUR OWN PROJECT

## Bring a real problem.  
We’ll bring code on day one.

[Start your own project →](https://www.kensink.com/contact) [Book a 15-min intro](https://www.kensink.com/contact)

[← All cases](https://www.kensink.com/cases) CASE · KHUSHI-POS