He Spent ₹22,000 on Software He Stopped Using in Five Weeks
Most shop software fails on fit, not features. Here are the questions that predict whether you will still be using it next year.
Naveen paid ₹22,000 upfront for a retail system with an impressive feature list. He stopped using it in the fifth week. The software was not defective — it was built for a shop about six times his size, and every daily task assumed staff and processes he did not have.
Shop software almost never fails on capability. It fails on fit, and fit is harder to evaluate from a demo than a feature list is.
The Questions That Actually Predict Fit
How long does one ordinary sale take?
Not a demo sale. A real one, with a loose item, a discount and a customer changing their mind. If a routine transaction takes more than a handful of taps, you will abandon it during your first genuine rush.
Does it work with no internet?
Test it in aeroplane mode before you buy. Complete a full sale, reconnect, and confirm it appears exactly once. This single test eliminates a large share of candidates.
How do I get my data out?
If there is no straightforward export, you are not a customer, you are a hostage. Ask this before paying, and be suspicious of a vague answer.
What happens when I stop paying?
Some tools lock historical records behind an active subscription. Your own sales history should remain readable regardless.
Who answers when something breaks on a Saturday?
Support that operates on weekdays is support that is absent during retail's busiest hours.
The demo took four minutes and looked wonderful. My actual counter is not a demo.
Pricing Traps Worth Knowing
- A large one-time fee removes the vendor's incentive to keep improving the product
- Per-user pricing punishes you exactly when you grow
- Free tiers with hard product-count limits force a migration at the worst moment
- Separately priced "modules" mean the advertised price is rarely the real one
- Compulsory hardware bundles inflate the entry cost for capability you may not need
A modest monthly cost you can stop paying is nearly always safer than a large upfront payment you cannot recover.
Evaluating software at 3 p.m. on a Wednesday tells you almost nothing. Use it during your Saturday evening rush, when you are hurried and the queue is real. Software that survives that is software you will still be using next year. This one habit would have saved Naveen ₹22,000.
Features Worth Paying For, and Ones That Are Noise
For a shop under roughly 2,000 products and three staff, this is a reasonable division.
- Worth it: offline billing, barcode scanning, automatic stock deduction, low-stock and expiry alerts, per-product margin, GST-rate handling, credit tracking, data export
- Usually noise at this size: loyalty point engines, elaborate CRM, employee scheduling, complex promotion rule builders, hourly analytics, integrations with tools you do not use
Every feature in the second list is something you pay for, navigate around, and are trained on. Complexity has an ongoing cost even when unused.
A Sensible Evaluation
- Shortlist two or three, no more
- Add your fifty fastest-moving products to each
- Use each for one full week, including a weekend
- Test offline behaviour deliberately
- Ask a support question and time the reply
- Confirm you can export your data before paying anything
Two weeks of honest evaluation is cheaper than a year of the wrong tool, and considerably cheaper than ₹22,000.
Arali is built for shops of exactly this size — offline billing, barcode scanning, expiry and low-stock alerts, margin per product and credit tracking, without the enterprise features that make software heavy. Whatever you shortlist, run the Saturday-evening test before you commit.
Frequently asked questions
How do I choose billing software for a small shop in India?
Judge fit rather than features. Time one ordinary sale including a loose item and a discount, test it offline in aeroplane mode, confirm you can export your data, check what happens to your history if you stop paying, and find out whether support operates at weekends. Shortlist two or three and use each for a full week including a Saturday.
Is one-time payment or monthly subscription better for shop software?
A modest monthly cost you can stop paying is usually safer than a large upfront fee you cannot recover — a one-time payment also removes the vendor's incentive to keep improving the product. Watch for per-user pricing that punishes growth, hard product limits on free tiers, and separately priced modules that make the advertised price unreal.
Which features does a small shop actually need?
Offline billing, barcode scanning, automatic stock deduction, low-stock and expiry alerts, margin per product, GST-rate handling, credit tracking and data export. Loyalty engines, elaborate CRM, employee scheduling, promotion rule builders and hourly analytics are usually noise below about 2,000 products and three staff — and complexity costs you even when unused.
How should I trial retail software properly?
Add your fifty fastest-moving products and use it during your busiest hours, not at 3 p.m. on a Wednesday. Software evaluated while calm tells you nothing about whether you will abandon it during a Saturday rush. Also test offline behaviour deliberately and time a support reply before committing.