Cash control that fits your shop.

2026-06-23 · 8 min read · by the thola team

It's 9:20 PM and Lakshmi is counting the till at her provision store in Madurai.

She does this every night. Notes in one pile, coins in another, a number scribbled on the back of a delivery slip. Tonight the number is ₹1,400 short of what she thinks it should be. She doesn't know if that's a miscount, a wrong-change moment during the evening rush, the UPI sale she may have rung as cash, or her nephew — who minded the counter for an hour while she took a call — slipping something. She has no way to tell. So the ₹1,400 becomes a small, quiet worry she carries to bed, and the suspicion of her nephew, which she'll never say out loud, becomes a slightly colder relationship.

This is the real problem with shop cash. It's not theft. It's not knowing — and the way "not knowing" slowly poisons trust between an owner and the people who help her.

Most cash software is built for the wrong shop. It assumes a supermarket with four trained cashiers, login PINs, and a manager. Lakshmi is a solo owner who sometimes has a helper. Force her into the supermarket's workflow and she'll be "blocked at checkout" by a drawer-count screen she doesn't need — so she'll turn the whole thing off and go back to the delivery slip.

So we started somewhere else: one question.

"Who handles the cash?"

That's the entire setup. No jargon, no "configure your cash management policy." You answer it once, and the system shapes itself:

• Just you? Your cash is an always-on running position. You're never blocked, never asked to "open a shift." You tap it when you want to see the breakdown, and that's it.
• You plus a family helper? Your till stays open the way it always was. The helper's hour at the counter is tracked, but nobody gets a login ceremony.
• A team of cashiers? Now drawer accountability switches on — each cashier counts their drawer at the door, at login, and owns it for their shift.

The same product scales from Lakshmi's one counter to a four-till supermarket without her ever seeing a setting meant for the supermarket. When she does add her first real cashier, the app asks her gently — "You added a cashier. Want drawer accountability for them?" — a one-tap prompt at the moment the question actually matters. Her own till is never touched by that choice.

The key decision underneath: the count happens at login, never mid-sale. The old way — and the way most POS apps still work — interrupts a cashier in the middle of a queue to reconcile. That's the "blocked at checkout" moment everyone hates. We moved it to the door.

The end-of-day that reassures, not accuses

Here's the part we're most careful about. The day-close is emotionally loaded — it's the moment an owner finds out if money is missing, and the moment a cashier finds out if they're about to be blamed. Get the design wrong and you've built an accusation machine.

So the close is count-then-reveal. The cashier counts the till first and enters the number. Then the system shows the difference. There's no peeking at the expected figure beforehand, which means there's nothing to fudge toward — and the count becomes the cashier's alibi rather than a test they can game.

And the language is deliberately calm. Not red alerts and "DISCREPANCY." Just "Short by ₹240" or "Over by ₹60," in amber. A difference is a fact to explain, not a crime to confess.

Then the AI does the explaining. Instead of leaving Lakshmi to invent a theory at 9:20 PM, it offers one: "Two UPI sales near 6 PM may have been rung as cash — that accounts for ₹1,400 of the shortfall." She can attach a reason tag — miscount, wrong change, till error — and move on. For bigger shops, an optional denomination grid (count by notes: how many ₹500s, how many ₹100s) makes the count tighter. It's off for small shops, never forced.

The ₹1,400 that used to follow Lakshmi to bed now has an explanation before she locks up.

AI that watches the cash for you

The cash intelligence runs quietly underneath:

• Smart alerts that learn your normal. It only pings when a difference is unusual for your shop — a ₹50 wobble in a cash-heavy provision store isn't worth a notification; the same ₹50 in a tightly-run pharmacy might be. The threshold is learned, not a fixed rule you have to tune.
• A plain-English daily cash summary — what came in, what the close looked like, anything worth a second glance.
• A predicted opening float and a suggested cash-drop, computed on-device and private. It's a sensible default you can edit, not a mandate.
• A nightly "do the books balance?" check that flags when cash-in-hand doesn't add up to the day's recorded movements.

There's also an anomaly review that surfaces patterns worth a look — refund spikes, after-hours activity, no-sale drawer pops. The on-device detection of these patterns ships today; the deeper cloud-side classification that ranks how worried you should be is building now (more on what's still in flight below — we'd rather you hear it from us).

Trust, built into the ledger itself

Two protections aren't features you turn on — they're properties of how the cash log works:

1. The cash log is tamper-proof. Entries can never be edited or deleted. A correction is recorded as a tracked reversal, not an overwrite. That's what makes the ledger audit-grade: the history is the truth, not a number someone can quietly fix later.
2. Counted cash flows to the owner automatically at each shift close — at the counted amount, never inflated to cover a shortfall. If a drawer is short, the owner's position reflects the short reality, not a polite fiction.

What's rolling out right now

In the spirit of every thola post: here's what's shipping but not fully in your hands yet, so you know exactly where the line is today.

• Manager approval for big refunds, cash-outs, and float top-ups. The backend that enforces and records the approval is shipped; the approval screen the manager taps is being built now.
• Optional cashier PIN. Off by default — it's a supermarket-grade upgrade, not something we'll push on a small shop. The backend is shipped; the PIN entry screen is in build.
• Owner "confirm your cash" + a freshness badge, so an owner's running number stays dated and trusted rather than quietly drifting. The backend is shipped; the card you'll see is being built.
• Cloud anomaly classification — the deeper ranking of which flagged patterns actually deserve your attention. On-device detection is live; the cloud layer is in progress.

What we're not pretending to do yet

And the honest roadmap — planned, not shipped. If you need these today, we're not there:

• Cashier-to-cashier handover at shift change, where the outgoing and incoming cashier count together and both agree before the drawer changes hands.
• A tamper-evident shift chain for audit and GST defence — cryptographically linking each shift to the last.
• GST cash-limit warnings — flagging the ₹2,00,000 single-bill and ₹10,000 cash-payout thresholds before you cross them.
• Ask your ledger in plain English — "how much did Ravi's counter short this week?" — answered conversationally.
• Cash-register export straight to your CA or the GST module.
• Restaurant-style day close by payment mode — reconciling cash, UPI, and card as separate, balanced columns.

These are real plans with real designs behind them. They're just not in the build you'd download today, and we won't dress them up as if they were.

Get started

If you run the counter yourself, you don't have to do anything — your cash is already an always-on running position, no shifts, no ceremony. The day you bring on a cashier, the app will ask you the one question that matters and switch on exactly as much accountability as you want.

The POS mobile guide walks through the counter end to end. The point of all of this isn't to police your shop. It's so that the ₹1,400 never follows you to bed again — and your nephew stays your nephew.