POS Software for Small Retail Shops in India: What to Actually Check Before You Buy One

A client of ours runs a two-floor grocery-and-general-store in a Tier 2 town outside Lucknow, the kind of shop that does ₹40,000 to ₹60,000 in daily sales on a normal Tuesday and double that around festivals. In early 2025 they switched from a local billing software they'd used for six years to a newer, more polished cloud POS system after a smooth 20-minute demo from a regional sales rep. The software looked genuinely better: nicer dashboard, WhatsApp bill sharing, a loyalty points module. What the demo didn't show, because demos never show it, was what happened when the shop's internet connection dropped, which in that part of town happens for a few minutes most afternoons and for an hour or more during heavy rain. The billing screen simply froze. Staff went back to handwriting bills on a pad for the first two months until we got involved and helped them migrate to a system with proper offline queuing. That gap, offline billing, cost them roughly three weeks of messy reconciliation and at least one irate customer who waited eleven minutes for a bill that should have taken ninety seconds.

We're a web and software agency, not a POS reseller, so we don't have a system to push on you here. What we do have is a pattern, from helping half a dozen retail clients pick, migrate off, or fix a point-of-sale system over the past two years. Almost every regret we've seen traces back to one of four things that never come up in a sales pitch: offline behavior, what happens when you want to leave, hardware costs bolted on after the fact, and GST reporting that looks fine until your accountant actually tries to file with it.

Offline mode is not a nice-to-have outside the big metros

Every POS vendor will tell you their product "works offline." Ask what that actually means before you believe it, because the phrase covers three very different levels of functionality and vendors are not consistent about which one they mean. The weakest version lets you view existing data offline but blocks new billing until connectivity returns, which is functionally useless for a retail counter. The middle version lets you create bills offline and queues them to sync once you're back online, which is workable but can create duplicate invoice numbers or stock-count conflicts if two terminals go offline and sync at slightly different times. The version you actually want runs its core billing and inventory logic locally on the device or a local server, treating the cloud sync as a background job rather than a dependency. If you're in a metro with fibre broadband and a 4G backup hotspot, this matters less. If you're anywhere outside the top eight or ten cities, or your shop is on the ground floor of a building with patchy signal, ask the vendor to genuinely disconnect the demo device from WiFi and mobile data in front of you and bill three items. Watch what actually happens, not what the brochure claims happens.

GST compliance that survives an actual audit, not just a demo

Nearly every POS product marketed in India today claims to be "GST-ready," and nearly all of them can generate a bill with a GST number and tax breakup on it. That's the easy 80% of GST compliance. The harder 20%, the part that actually matters when your accountant sits down to file GSTR-1 and GSTR-3B, is whether the software correctly handles HSN/SAC code mapping per product, splits CGST/SGST versus IGST based on the buyer's state, generates e-invoices if your turnover crosses the mandatory threshold, and exports a GSTR-ready report your CA can actually use without manually re-entering line items into separate software. We've seen two clients discover, only at filing time, that their POS exported a generic Excel sheet with none of the fields their accountant needed formatted correctly, turning a task that should take an hour into a half-day of manual cleanup every single month. Before signing anything, ask your own accountant, not the vendor's support team, to look at a sample export and confirm it's usable as-is. If a vendor won't produce a sample export before you've paid, that's worth noting on its own.

• Test true offline billing by disconnecting the demo device yourself, don't take the vendor's word for it
• Get a sample GST report export and have your own accountant review it before you commit
• Ask exactly what happens to your sales history and product catalogue if you cancel the subscription
• Price out barcode scanner, thermal printer, and cash drawer hardware separately, since these are rarely included
• Confirm how many billing counters or devices are included in the base price versus charged per additional terminal
• Check whether inventory syncs in real time across counters, or only on a periodic refresh

The hardware line item nobody quotes upfront

Software pricing pages love to advertise a monthly number, often somewhere between ₹499 and ₹2,000 per month for a single-counter plan. What they tend to leave off the page entirely is hardware. A functioning retail counter usually needs a barcode scanner (₹1,200 to ₹3,500 for a decent wired one), a thermal receipt printer (₹3,000 to ₹6,000), and frequently a cash drawer with an auto-open trigger (₹2,500 to ₹4,000), plus a tablet or PC to run the software on if you don't already have one. Add it up and a shop expecting to spend ₹1,000 a month can easily be looking at ₹10,000 to ₹15,000 in one-time hardware costs before they've billed a single customer. None of this is unreasonable, retail hardware genuinely costs what it costs, but budget for it going in rather than discovering it line by line during setup week. Some vendors bundle a hardware kit into a slightly higher monthly plan, which can work out cheaper than buying separately if you're not planning to shop around for the printer yourself, so it's worth asking for both quotes side by side.

Cloud POS versus a local-server setup, and when each one actually makes sense

Cloud-hosted POS systems are the default recommendation for most small shops now, and for a single-location business with decent connectivity, that default is usually correct. You get automatic backups, updates that don't require an IT visit, and the ability to check sales from your phone while you're not on-site. But cloud isn't automatically the right answer for every retail setup. A shop running three or four billing counters that all need to see live, shared inventory with zero lag, in a location with unreliable connectivity, is often better served by a local-server or hybrid setup where the core database lives on-premise and syncs to the cloud opportunistically rather than depending on it for every transaction. This is a smaller and more technical category of POS product, and most retail owners have never heard of the option because the loudest marketing budgets in this space all belong to the pure cloud players. If your business genuinely needs custom logic, multi-location stock transfers, a specific loyalty scheme, or an integration with an existing accounting system that off-the-shelf POS products don't support cleanly, this is closer to a custom software conversation than a pick-a-plan-off-a-pricing-page one, and it's worth having that conversation before you commit to a rigid product that'll fight you on every customization request.

The best question to ask any POS vendor isn't "what does your software do." It's "what happens to my data the day I decide to leave you." The answer tells you more about the vendor than the entire feature list does.

Exit terms matter more than launch terms

Retail owners almost never ask about this before signing, and it's the single biggest source of regret we hear about a year or two later. Ask, specifically: can you export your full sales history and product catalogue in a usable format, not a locked PDF, if you switch systems? Is there a lock-in period, and what's the penalty for leaving early? Does the vendor own your customer data, including phone numbers collected for loyalty programs, or is that genuinely yours to take with you? We worked with a boutique clothing retailer who'd built a loyalty list of around 4,000 customer phone numbers over three years inside a POS system that, it turned out, had no bulk export function for customer data at all, only for individual transaction records. Switching systems meant starting that list from zero. It's a fifteen-minute question to ask before you sign, and it can save you years of accumulated data if you ever need to move on.

How this connects to the rest of your back office

A POS system rarely lives in isolation for very long. Once a shop is past its first year, most owners want their billing data talking to their inventory management, their accounting, and sometimes a basic CRM for repeat customers. Check whether your shortlisted POS options offer real API access or pre-built integrations with the accounting software your CA already uses, Tally is still the default for a huge share of Indian small retail, rather than assuming you'll figure out data transfer later. If you're running billing and invoicing across multiple business lines rather than pure retail, it's also worth reading through what we've written on billing and invoicing software more broadly, since a lot of the same GST-export and lock-in questions apply there too, and the two categories overlap more than vendors like to admit when they're trying to sell you a single all-in-one platform.

What this actually costs, all in

For a single-counter retail shop in India, budget roughly ₹800 to ₹2,500 a month for the software subscription itself, depending on whether you need multi-user access, advanced inventory, or loyalty features bundled in. Add ₹8,000 to ₹15,000 as a one-time hardware cost if you're starting from nothing. Multi-counter or multi-location setups scale up from there, often ₹1,500 to ₹4,000 per additional counter per month, plus the hardware cost repeated per counter. If a vendor is quoting a flat annual figure well below this range, look closely at what's excluded, usually support response time, the number of SKUs you can catalogue, or the number of monthly transactions before overage charges kick in. A number that looks unusually cheap on a comparison table is rarely cheap once your actual sales volume shows up.

None of this needs to be complicated to get right, it just needs to happen in a specific order: test offline behavior yourself, get a real GST export reviewed by your own accountant, price hardware separately, and ask about your exit terms before you ask about the discount for paying annually. Do those four things and you'll avoid the version of this story where a shop is back to handwritten bills during the first monsoon storm after go-live. If your retail operation has outgrown what off-the-shelf POS products can reasonably do, whether that's a specific stock-transfer workflow across locations or an integration your shortlisted vendors keep saying "isn't supported yet," our team is happy to talk through what a custom build would actually involve, reach out and we'll tell you honestly whether it's worth it or whether an off-the-shelf product is still the smarter call for where your business is today.