The internet goes down. Your counter doesn’t.

It is 7 PM on a Saturday. There are six customers at the counter, two more deciding between shades of the same suit piece, and the broadband light on the router turns red. In most shops, that is the moment billing stops — out comes the duplicate book, and tomorrow somebody spends an hour keying yesterday into the computer, hoping the stock still tallies.

Kapda Stock is built for shops where the line is not always reliable. When the server cannot be reached, the POS does not fail — it parks the sale on the device, clears the cart, and lets you serve the next customer. The bill becomes a real invoice the moment the connection returns.

What actually keeps working

We would rather be precise than make a big promise. Offline support covers the counter — the one screen that cannot wait. This is the honest list:

• Completing a sale on a POS screen that is already open — works offline.
• Seeing the list of sales still waiting to sync — works offline.
• Opening a page you have not loaded yet, or refreshing the tab — needs the connection.
• Printing the receipt for an offline sale — needs the connection, because the invoice number does not exist until it syncs.
• Invoices, reports, customers, stock edits, WhatsApp and payment links — all need the connection.

Which leads to the single habit worth teaching your staff: keep the POS open on the counter device all day. If the line drops, carry on billing in that window — just do not refresh it.

What an offline sale looks like

Nothing about the checkout changes. You add items, take the payment and finish the sale as always. Instead of a failure, you get a calm message — “📴 No internet — sale saved as OFFLINE-… It will sync automatically when you’re back online” — and the cart clears.

An amber bar then sits at the top of POS showing how many sales are waiting, each with its temporary receipt number, item count, total and customer. You always know exactly how much of the evening is still sitting on the device.

Sync happens on its own

The moment the browser reports that the connection is back, the app replays the queued sales in order. Each one becomes a proper invoice with a normal invoice number, and stock is deducted at that moment. You see a short confirmation listing the new invoice numbers — that is the whole ceremony. If you would rather not wait, there is a “Sync now” button on the amber bar.

And when the server says no

Stock and validation checks run when a sale syncs, not when it was rung up. So if the last two pieces of a design sold on another counter while you were offline, that sale gets rejected. It stays in the list with the reason written next to it, so you can re-create it with a corrected cart and then discard the rejected entry. Sales that synced cleanly are never affected by one that did not.

“The line in our market goes twice a week. We stopped noticing. The bills are simply there in the morning, with the stock already adjusted.”

Three habits that make it bulletproof

• Install Kapda Stock as an app on the counter device and leave POS open from morning.
• Sync before you close up — the queue lives in that device’s browser until it syncs, so never clear site data or uninstall with sales still waiting.
• Ring up offline sales on one device, not three — the queue is not shared between devices.

None of this is a feature customers ever see, and that is the point. The shop keeps selling, the khata stays correct, and nobody spends Sunday morning typing yesterday back into the computer.