# Why an offline-first ledger matters for small shops - URL: https://ck.abdohoo.app/blog/why-an-offline-first-ledger-matters-for-shops - Product: Credit Khata (https://ck.abdohoo.app/) - Section: Explainers - Updated: 2026-10-11 > An offline-first ledger saves each entry on the device first and uploads it later, so the counter never waits for the network, and a careful sync makes sure nothing is lost or doubled. An offline-first ledger writes every entry to the shop's own device first and sends it to the server later, whenever there is a connection. The counter never waits for the network, a sale is never lost because the signal dropped, and a careful sync makes sure each entry arrives once, in order. For a shop that sells on credit, that is the difference between a record you can trust and one full of gaps. Many apps are online-only: every tap goes to a server and waits for an answer. That works in an office with good Wi-Fi. A shop counter is a different place. ## Why counters lose signal Anyone who runs a shop knows the list: - **Power cuts** that take the router down. - **Weak mobile data** inside a shop with thick walls, in a basement market, or at the back of a crowded bazaar. - **A data package that runs out** in the middle of the month. - **Busy hours**, when everyone in the market is on their phone at once. None of these is rare. And they tend to happen exactly when the counter is busiest. ## What goes wrong with an online-only ledger When the network drops and the app cannot save, the shopkeeper has three bad choices: 1. **Make the customer wait**, while the queue grows behind them. 2. **Write it on a slip "for later"**, and hope it gets typed in. Some slips never do. 3. **Skip it**, and rely on memory. Each one leaves a gap in the record. Gaps turn into wrong balances, and wrong balances turn into arguments with the customer, which is exactly what a khata is meant to prevent. There is a subtler problem too. If a sale is sent, the network drops before the answer comes back, and the shopkeeper taps save again, an online-only app can record the same credit sale twice. The customer is then charged for the same bag of atta two times. ## What offline-first means in practice An offline-first ledger turns the model around: 1. **Write locally.** The entry is saved on the device the moment you tap save. The counter moves on to the next customer. 2. **Queue it.** Entries waiting to upload sit in an ordered queue, and the screen shows that they are pending. 3. **Sync in the background.** When the connection returns, the queue uploads by itself, oldest first. 4. **Exactly once.** Each entry carries a unique key. If an upload is retried, the server recognises the key and does not record it again. 5. **Never drop a refusal.** If the server refuses an entry, for example because the customer has since been removed, it is set aside for the shopkeeper to review, not silently thrown away. That last point is easy to overlook. A sync that quietly discards what it cannot save is almost as bad as no sync at all. ## What offline cannot do Being honest about limits matters. Some things need the server's answer and wait for a connection: - **The customer's view.** The shop sees an offline entry at once; the customer sees it only after it syncs. - **Confirming a payment claim**, which has to be written on the server. - **Reminder links**, which the server creates. - **Reports** across all your customers. A good offline-first app keeps the counter working, and is clear about what is waiting. ## How Credit Khata does it Credit Khata was built for counters with patchy signal: - **The counter app** (in a browser, installable on a computer or phone) keeps its screens, your language and your customer list on the device, so it opens even with no internet once it has been used online. Sales rung up on the **Sales** screen are saved to a queue on the device, each with its own key. - **A sync pill** at the top of the Sales screen says **All synced**, how many are pending, or **Syncing**, and tapping it shows the queue. - **Refused sales are parked**, not dropped, under **Could not be saved**, with **Try all again** and **Discard**. Signing out with sales still queued asks you first, because it would discard them. - **The Android app** stores new customers and all entries, credit, paid and cash, on the phone and syncs them in the background. ![The Sales screen in Credit Khata's counter app with the All synced pill at the top right](https://ck.abdohoo.app/storage/content/library/web-counter.webp)The sync pill shows at a glance whether every sale has reached the serverThe practical steps, including what to do when a sale could not be saved, are in [Work offline and keep your ledger in sync](https://ck.abdohoo.app/help/work-offline-and-sync). ## Questions to ask any ledger app Whatever you use, test it before you rely on it: 1. Turn on flight mode and record a sale. Does it save? 2. Close the app and open it again, still offline. Is the sale still there? 3. Turn the internet back on. Does it upload by itself? 4. Record a sale while the signal is flickering. Does it appear once, not twice? 5. What happens to an entry the server refuses? Can you see it? If an app passes all five, the counter can keep working on the worst network day of the month. ## The bottom line A credit ledger is only useful if it is complete. At a busy counter with an unreliable connection, the only way to keep it complete is to write first and sync later, carefully. That is what offline-first means, and it is why it matters more in a small shop than almost anywhere else. To see how this fits the rest of a digital khata, read [What is a khata book? Digital khata vs the paper register](https://ck.abdohoo.app/blog/what-is-a-khata-book-digital-vs-paper-register), or start with [Book a credit sale at the counter](https://ck.abdohoo.app/help/book-credit-sale-at-counter). ## Frequently asked questions ### What does offline-first mean? The app writes each entry to the device first and treats the internet as something that comes and goes. Entries upload in the background when there is a connection. ### Can an offline entry be recorded twice when it syncs? Not in a well-built app. Each entry carries a unique key, so if the upload is retried the server recognises it and records it only once. ### Does the customer see an offline entry straight away? Not until it syncs. The shop sees it at once on its own device; the customer's view updates when the entry reaches the server. ### What cannot be done offline? Anything that needs the server's answer, such as confirming a customer's payment, generating a reminder link or running reports.