The things people ask first

Yes — that is the quickest way to see whether any of this suits you. Zuuvy POS opens at pos.zuuvy.in in any modern browser, and there is an installer for Windows and Mac if you want it in its own window. What it does is set out on its own page. You will need an account to sign in, which we create for you.

No. It runs on the computer already on your counter, and payment is by UPI — the customer scans a code carrying the exact amount. A barcode scanner and a receipt printer help if you have them, and it works without either.

The till carries on. Your catalogue and prices are already held on the machine, so the sale is billed and kept, and it goes through the moment the connection returns. Every sale waiting to be sent is listed, so you can see exactly what is outstanding — and a retry cannot bill the same sale twice.

Yes, and that is one of the better reasons to use it. Scan one code with any phone, tablet or spare monitor and it becomes a customer-facing screen showing every line, the quantity and the running total, with the payment code beside it. The device does not have to be on your Wi-Fi.

The apps themselves take minutes — install and sign in. What takes time is your data: products, prices, customers and what everyone currently owes. For a business with a tidy product list that is usually days rather than weeks, and we load it with you rather than handing you a spreadsheet template and wishing you luck.

No, and most do not. Start with one module — billing is the common one — and add the rest when the warehouse or the salesmen are ready. See the platform.

A salesman or a counter operator is usually working within their first shift. That is the whole point of separate apps: nobody has to hunt for their own job inside a menu built for somebody else's.

Products, customers and balances, yes — from a spreadsheet or a database export. Historical transactions are usually not worth moving; the old system stays readable for reference and Zuuvy starts from opening balances.

The counter keeps selling and reconciles when the connection returns. The field apps queue what they cannot send and flush it when signal comes back — a retry cannot double-count a sale, because every movement is claimed before it is made.

Location is recorded while a salesman is checked in, and stops when they check out. They can refuse the permission in Android's settings — attendance still works, the route does not. What is collected is set out in the privacy policy.

Yes — that is assumed rather than bolted on. Shops, dealers and distributors each see their own price, and offers are published per audience at each one's price.

Returns are settled, not just approved. Each returned line goes back on the shelf, gets written off, or is handed to the shop — and one line can split across all three. Nothing moves in the stock figures until somebody settles it.

Pricing is quoted per business, based on the modules you switch on and how many people use them. There is no card-on-file signup and no per-seat surprise — write to rishav@zuuvy.in and you will get a number, not a discovery call.

Yes. Your customers, prices, orders and records belong to you; we hold them to run the service and nothing else. You can export in a machine-readable format during the subscription and for 30 days after it ends. See the terms.

No. Isolation is enforced in the data layer rather than remembered by each screen, and an automated test walks every endpoint on every build to prove it. The detail is on the security page.

You export your data and we delete it, except records the law requires us to keep. The deletion route is here, and it works without the app or a login.