Initializing secure environment…
Initializing secure environment…
Run a counter on a browser. Ring up items against a product catalogue, apply discounts, take payment, and print a GST-compliant thermal receipt — 80 mm or 58 mm, with the CGST/SGST split and an HSN summary on the receipt itself. A day's takings, a GSTR-1 style summary and an XLSX export are all one click away, and the catalogue and the day's sales live in your browser. Free, no account, no subscription, nothing uploaded.
Free point-of-sale billing for Indian retailers — GST-compliant thermal receipts, a product catalogue and cart. Runs in the browser, 100% local, no upload, no subscription, no sign-up.
Open the print dialog, choose the roller's paper size — 80 mm or 58 mm — set margins to none, and turn off headers and footers. Then scale to 100% so the receipt is not stretched. Those four settings, once, and every receipt after it comes out correctly.
Because the data lives in a browser profile, the end-of-day XLSX export is the backup, not a nicety. Export every day, keep the file with your accounts, and a cleared browser, a replaced machine or an accidental profile reset costs you a day rather than a month.
Add every product you sell regularly, with the correct HSN and tax rate, so a sale is a search and a quantity. A catalogue of your fifty fastest movers removes almost all typing from a busy hour, and it is a one-time setup that pays for itself in the first day.
Because inventory needs a database, a reconciliation model and a migration path, and those cost money to build and to run. Billing a sale does not. Rather than ship a half-working stock system, this does one job properly and says what it does not do — which is more useful than a feature that quietly miscounts.
Yes, 80 mm and 58 mm, through the browser's print dialog. Choose the paper size, disable headers and footers, and set the margins to none — those three settings are what make a browser print look like a thermal receipt instead of an A4 sheet.
In your own browser's local storage, on that device. No server, no account, nothing transmitted. That is genuinely private, and it also means the data lives on one machine — which is a real operational consideration if that machine is formatted or replaced.
The catalogue and the day's sales are gone. This is the honest limitation of a no-server, no-account design, and it is why the daily XLSX export exists. Export at the end of every day, and the loss of a browser profile is an inconvenience rather than a catastrophe.
Not on one device simultaneously — it is a counter application, not a multi-user server. For a shared till, one machine with one till is the normal arrangement. A genuinely multi-user system needs a server, and a server needs to be paid for; that is a different product from a free one.
It carries the supplier and customer details, GSTINs, an invoice number, HSN or SAC codes, and the tax shown separately as CGST plus SGST or IGST. Compliance is a legal matter and this is a tool, not advice — have anything unusual checked by your accountant.
No, and it says so rather than pretending. Stock levels, reorder points and supplier records are a different piece of software. This bills sales; if you need inventory, you need something that models it.
Yes, once the page has loaded, and that is a genuine advantage for a shop with an unreliable connection. A counter application that stops working when the internet drops is not much use at a busy till.
Yes. No account, no subscription, no per-receipt fee and no watermark. There is no paid tier here to upgrade to, because there is no server and no database behind it.
More business tools — all free, no upload.