Part of our guide to Custom POS software in India: cost, features, and when to build your own.
Your billing system cannot handle peak season if, during the Diwali rush, queues grew because billing was slow, stock stopped matching, GST bills needed manual fixes, or branch figures arrived days late. Those are four of the eight signs below. Each one comes with what it costs you and what to fix first, before you buy anything new.
Diwali fell on Sunday, 8 November 2026 (India Post holidays list 2026). The fortnight after it is the best time to review your billing, because the problems are fresh, your staff remember the workarounds, and the data is still on the counters. If you are already comparing options, our guide to custom POS software in India covers features, hardware and cost.
Start with your three worst hours
Pick the three busiest hours of the season and reconstruct them. Do this before you read the signs, so you are looking at facts rather than impressions.
- Pull the bill count by hour from your billing system for each branch.
- Ask each cashier what slowed them down, and write their answers word for word.
- List every manual fix your accounts team made afterwards: corrected bills, stock adjustments, re-entered sales.
- Note every outage: internet, power, printer, payment terminal, and how long each lasted.
You now have the raw material. The eight signs below are grouped by where they show up.
Signs at the counter
1. Queues that grow faster than footfall
If the queue grew while the counters were staffed, billing itself was slow. Common causes are searching for items by name because barcodes do not scan, keying prices by hand, waiting for a card or UPI confirmation, and slow printing.
- What it costs: customers who leave the queue, and staff who start cutting corners to clear it.
- Fix first: time five real bills with a phone stopwatch and note where the seconds go. Fix barcodes and item masters before anything else. If the system itself is slow with a full basket, that is a software limit.
2. Discount errors
Festive offers stack: a store discount, a bank offer, a combo, a staff override. When the system cannot express the rules, cashiers apply them by hand. For example, applying a 10% discount twice to a ₹5,000 basket gives ₹4,050 instead of ₹4,500, a ₹450 loss on one bill.
- What it costs: margin, quietly, across hundreds of bills; and arguments at the counter when a customer expected a different price.
- Fix first: write each offer as a rule before the season, test it on sample baskets, and require a manager’s approval for manual discounts above a set limit.
Signs in the stock room
3. Stock that does not match
After the rush, the system says you have twelve of an item and the shelf has four, or the other way round. Usually it is a mix of items billed under the wrong code, returns not put back into stock, transfers between branches not recorded, and goods received but not entered.
- What it costs: lost sales on items the system thinks you have, dead stock you reorder by mistake, and hours of counting.
- Fix first: a cycle count of your top 50 items, and a rule that every movement (sale, return, transfer, receipt) is entered in the system, never on paper. If the system has no way to record transfers or returns properly, that is a software gap.
Signs in the accounts
4. Manual GST corrections
Every tax invoice has to carry the right details, including the taxable value, rate and tax amount, and a serial number “unique for a financial year” (Rule 46, CGST Rules). It also needs the HSN code, although a business with turnover up to ₹5 crore may leave it off bills to unregistered customers (Notification 78/2020-Central Tax). If your accountant spent the week after Diwali fixing wrong tax rates on items, missing GSTINs on B2B bills or duplicate invoice numbers across counters, your billing system is creating compliance work rather than removing it.
- What it costs: your accountant’s time, and the risk of errors reaching your returns.
- Fix first: clean the item master so every item has the correct HSN code and tax rate, and make the GSTIN field mandatory when a bill is marked B2B. Ask your chartered accountant to review a sample of peak-day bills.
5. Slow day-end reconciliation
On a normal day, closing the counters takes half an hour. During Diwali it took until midnight, because cash, card settlements, UPI receipts and the system’s totals did not agree.
- What it costs: late nights for managers, and short or excess cash nobody can explain.
- Fix first: record every payment against the bill with its method, separate pending payments from confirmed ones, and run a cash-up per shift, not just per day. If the system cannot show payments by method and by cashier, that is a software limit.
Signs across branches
6. Branch data that arrives late
Head office wanted to move stock from a slow branch to a busy one, but the figures arrived the next morning by WhatsApp or email. By then the busy branch had run out.
- What it costs: lost sales and stock sitting in the wrong place during the days that matter most.
- Fix first: agree what head office needs during a peak (sales and stock of the top items, by branch, every few hours) and how it gets there. If each branch runs its own copy of the software with no central view, that is the system’s limit.
7. Outages that stop billing
The internet went down, the billing system stopped, and staff wrote bills by hand. Or the one printer jammed and the counter stopped.
- What it costs: sales during the outage, plus the hours spent entering handwritten bills later, often with errors.
- Fix first: a backup internet connection, a spare printer, and a UPS for the router as well as the computers. If the software cannot bill at all without the internet, that is a design limit that only a change of system fixes.
Signs in how staff work
8. Staff workarounds
The clearest sign is a notebook beside the counter, a spreadsheet on the manager’s phone, or a WhatsApp group where branches post their stock. Staff build workarounds when the system does not do what the job needs.
- What it costs: every workaround is data outside the system, so your reports are wrong in ways nobody can see.
- Fix first: ask each workaround’s owner what it does that the system cannot. Some are training gaps. The rest are your requirements list. Our five-question test for replacing Excel helps you tell which spreadsheets should become software.
Fix, replace or rebuild?
Most businesses should start with the cheap fixes. Here is each sign, what it costs and the first fix in one view.
| Sign | What it costs | Fix first |
|---|---|---|
| Counter queues | Walk-outs, rushed bills | Time real bills; clean barcodes and item masters |
| Discount errors | Margin leaks | Offers written as rules; approval for manual discounts |
| Stock mismatch | Lost sales, wrong reorders | Cycle count; every movement recorded |
| Manual GST corrections | Accountant time, return errors | HSN and tax rate on every item; GSTIN required for B2B |
| Slow day-end | Late nights, unexplained cash | Payments by method; cash-up per shift |
| Late branch data | Stock in the wrong place | Agreed peak-day reporting |
| Outages | Lost sales, re-entry | Backup internet, spare printer, UPS |
| Staff workarounds | Hidden data | Turn each workaround into a requirement |
Clean data, clear permissions and backup hardware often ease peak-season pain without any new software.
If your problems were mostly setup, training or hardware, fix those and run your next sale on the system you have. A new POS will not fix a messy item master.
Replacement is worth scoping when three or more signs come from the system itself, rather than from how it was set up. That usually shows up as billing that is slow even with clean data, no offline billing, no central view of branches, or no way to express your discount and stock rules.
Then the choice is between a subscription POS and a custom one. A subscription suits a single store with standard billing. A custom system makes sense when your stock, pricing or branch rules do not fit the tool, or when it must feed Tally, an online store or a CRM. Our custom POS development work starts by mapping exactly these peak-day problems.
Before your next peak: a checklist
Work through this list while Diwali is still fresh, and set a date to finish before your next sale season.
- Write down your three worst hours, with bill counts, outages and every manual fix.
- Clean the item master: barcodes, HSN codes, tax rates and units for every active item.
- Write each recurring offer as a rule, and set a manager-approval limit for manual discounts.
- Make the GSTIN mandatory on B2B bills, and ask your CA to review a sample of peak-day bills.
- Set up a cash-up per shift, with payments recorded by method.
- Agree what head office needs to see from each branch during a peak, and how often.
- Add a backup internet connection, a spare printer and a UPS for the router.
- Collect every staff workaround and decide which are training gaps and which are requirements.
- If three or more signs remain after these fixes, scope a replacement now, so it is live and tested well before the next rush, not during it.
