About

Software for shops,
not for slide decks.

Kadai exists because the software sold to small Indian retailers is either a ₹15,000 terminal from 2009 or an 'all-in-one commerce platform' that needs a consultant. The counter deserves better than both.

Why we're building this

“A kadai is the pan every Indian kitchen actually cooks in. Not fancy. Used every single day. That is the bar for this software.”

Walk into a busy kirana or a chai counter and watch the owner work: one hand on the UPI QR stand, one eye on the queue, dues in a notebook, stock in their head. They are running a real-time system — entirely from memory.

Kadai takes exactly that workload — the ticket, the split payment, the udhaar page, the end-of-day total — and makes it a five-minute setup on a tablet the shop already owns. Nothing more. The features we have not finished are labelled “Coming Soon” in the product, not sold on this website.

We are a small team, and we would rather stay small and finish things than grow fast and sell roadmaps.

Principles

Five rules we build by.

01

The counter is the customer

Every design decision is judged at the counter during a rush. If a feature slows down the next ticket, it does not ship — no matter how good it looks in a demo.

02

Ship what is finished

The beta sells six features because six features are done. Anything half-built stays behind a "Coming Soon" label instead of a sales pitch. Our landing page and our codebase are required to agree.

03

Never lose a sale

Drafts live on your device first and back up to the server in the background. A dropped connection, a page reload, a dead battery — none of them should cost you a ticket.

04

Count like an accountant

All money math runs in paise — integer arithmetic, no floating-point drift. Invoices are numbered sequentially, tax splits into CGST and SGST, and significant actions leave an audit trail.

05

Built for India, not localized to it

UPI next to cash, udhaar on the ticket, GST on the invoice, amounts in lakh and crore, store hours in IST. These are not translations bolted on — they are the starting point.

Under the hood

Boring where it counts.

The interesting engineering in a POS is the part you never notice: money that adds up, drafts that survive, records that hold. That is where the effort goes.

Money mathInteger paise, never floats
SyncReal-time, offline-tolerant drafts
IsolationEvery shop is its own tenant
InvoicesSequential, CGST/SGST, words in lakh & crore
AccessInvite-only, owner/staff roles
RecordAudit trail on significant actions

Judge us at your counter.

Not on this page. Set up your shop, run a real rush, and see if we kept our word.

Start selling free