
A complete self audit for owners and operations heads of retail chains, supermarkets, apparel groups, pharmacy chains and restaurant groups.
Diwali was on 8 November. For most chains it was the busiest stretch of the year, and every part of your billing, stock, pricing and reporting setup was tested under real pressure.
The results are sitting in your data and in your managers’ memories right now. In two weeks the memories fade, the next busy season gets closer, and the same problems repeat.
If you have been wondering whether your POS software is good enough, you do not need a vendor to tell you. You need honest answers to fifteen questions. This guide gives you those questions, explains why each one matters, shows you how to score yourself, helps you estimate what the problems cost, and lays out a step by step plan for what to do next.
You can finish the audit in about an hour. Doing it properly this week is the most useful thing you can do for next year’s festive season.
A health check is only as good as the information behind it. Spend the first hour gathering inputs.
Person | What they know |
Cashiers and counter staff | Where the system was slow, froze or needed workarounds |
Outlet managers | Stockouts, offer problems, customer complaints, manual bills |
Store keepers and purchase team | Where stock records did not match shelves |
Accounts and GST team | How long reports took, where totals did not match |
Head office or operations | What you could and could not see during the festival |
Kitchen and delivery staff (restaurants) | Missed orders, wrong orders, ingredient shortages |
Data | Why it helps |
Daily sales by outlet for the last 30 days | Shows which outlets and days were strongest and where gaps may be hiding |
Bills per hour by outlet during peak days | Shows where counters were saturated |
List of items out of stock at any point | Shows where availability failed |
Offers configured and the dates they ran | Shows consistency problems |
Credit notes and returns after Diwali | Shows how returns are handled |
Time taken to prepare your October GST data | Shows reporting and reconciliation effort |
Ask open questions: “What slowed you down most during Diwali week?” and “What did you have to do by hand?” Then listen for repeated answers. If three outlets mention the same thing, treat it as a finding.
Answer Yes or No for each question. After each one, read why it matters.
1. Did any counter stop or slow down badly during peak hours?
Why it matters: A slow counter is a visible queue, and a visible queue sends customers to the next store. If slowness appeared on the busiest days at several counters, the system cannot keep up with your peak load.
Look for: complaints from cashiers, long waits for products to load, delays at payment.
2. Did billing stop at any outlet when the internet dropped?
Why it matters: Network drops happen in busy commercial streets during festivals. A system that cannot bill without internet turns a short outage into lost sales and manual bills.
Look for: any outlet where staff switched to paper or waited for the network to return.
3. Were paper or manual bills used at any outlet?
Why it matters: Manual bills are slow, error prone and often entered late, which causes stock and tax mismatches that you pay for during reconciliation.
Look for: a pile of manual bills at the end of the day, and the time it took to enter them.
4. Did your top selling items run out at one outlet while another outlet had spare stock?
Why it matters: This is the clearest sign that stock is not visible across outlets in real time. You lose sales at one outlet and carry dead stock at another.
Look for: items repeatedly out at your busiest outlets with stock sitting elsewhere.
5. Did you learn about stockouts from customers or staff instead of from an alert?
Why it matters: If the system does not warn you before shelves empty, you are always reacting. During a festival the gap between “low” and “empty” can be a few hours.
Look for: how many of your stockouts were announced by a person rather than a system alert.
6. Do you now have leftover festive stock that you cannot see by outlet?
Why it matters: Leftover festive stock loses value every day. If you cannot list it by outlet within minutes, you cannot decide quickly about transfers or markdowns.
Look for: how long it takes to produce a report of remaining festive stock by outlet.
7. Did any offer start late, end late or run at only some outlets?
Why it matters: Customers notice. An offer missing at one outlet creates arguments at the counter and damages trust. An offer that runs too long costs you margin.
Look for: offers that depended on someone at each outlet switching them on or off.
8. Did any customer complain about different prices at different outlets?
Why it matters: Price differences between outlets of the same brand signal that prices are managed outlet by outlet instead of centrally.
Look for: complaints on social media, in reviews or at counters.
9. Did staff have to apply an offer by hand?
Why it matters: Manual offers cause mistakes, delays and inconsistent discounts. During a rush, they are the first thing to go wrong.
Look for: any offer that needed a cashier to remember a rule.
10. Did outlet totals fail to match your system totals?
Why it matters: If totals do not reconcile, you cannot trust your reports, and your accountant spends days hunting differences.
Look for: gaps between what outlets say they sold and what the system shows.
11. Is your October GST data taking more than a day to prepare?
Why it matters: Return preparation should be a review, not a project. If it takes days, data is probably scattered, items have wrong settings, or reports cannot be trusted.
Look for: how many people and how many files it takes to produce your return figures.
12. Were returns and exchanges recorded outside the billing system?
Why it matters: Returns handled on paper or in side files break the link between the original sale and the correction, which affects stock, tax and customer records.
Look for: exchanges recorded in notebooks, messages or spreadsheets.
13. Did you depend on phone calls to know how outlets were doing?
Why it matters: Phone calls give you opinions, not numbers. If you could not open a screen and see every outlet, you were managing blind.
Look for: how many calls you made to outlet managers each day during the festival.
14. Did any problem reach you hours after it started?
Why it matters: The earlier you know, the cheaper the fix. A stockout, an offer error or a counter fault found in the first hour costs far less than one found at night.
Look for: the gap between when a problem began and when head office learned of it.
15. Was there a time during the festival when you could not see every outlet’s sales on one screen?
Why it matters: A single live view of all outlets is the foundation of managing a chain. Without it, every decision depends on delayed reports.
Look for: whether you could check sales from your phone while travelling.
Give yourself one point for every Yes.
Score | What it usually means | What to do |
0 to 3 | Mostly process issues such as training or discipline | Fix the specific points. Review again after the next peak. |
4 to 8 | The system is under strain and costing you time and sales | Start evaluating alternatives now. Run the demo tests in Section 10. |
9 to 15 | The system is limiting how fast your chain can grow | Make a replacement decision this quarter. |
How to read the score by section. Add up Yes answers in each of the five groups. If most of your Yes answers sit in one group, that tells you where to focus.
Group with most Yes answers | Likely priority |
Counters and Uptime | Offline billing and counter speed |
Stock | Multi outlet stock visibility and alerts |
Offers and Prices | Central offer and price control |
Reports and GST | Reporting, returns handling and reconciliation |
Visibility | A live dashboard for all outlets |
A caution. A high score does not automatically mean software is the only cause. Some failures, such as a manager forgetting to reorder, are about people and process. That is why Section 6 helps you separate the causes.
If you run one of these formats, add these questions. Count them separately as bonus points.
Three or more Yes answers in your format specific list is a strong signal that your current system was not built for the way you trade.
Before blaming the software, check the cause. Use this table for each problem you found.
Pattern | Likely cause | First action |
Problem at one outlet only | People or process at that outlet | Training and supervision |
Problem at all outlets, same way | System limit | Test the system for the missing capability |
Problem only at peak hours | Capacity or speed limit | Test the system under peak load |
Problem only on certain days | Scheduling or planning | Review staffing and reorder rules |
Problem is “we could not see it” | Reporting limit | Check reports and dashboards |
Problem is “someone forgot” | Missing automation | Ask whether the system can do it automatically |
The last row matters. Many failures blamed on people are really processes that depend on memory. If a system can do the task automatically, a person should not have to remember.
Every Yes answer should become a written requirement, which you test in demos.
If you answered Yes to | Write this requirement | How to test it |
1 to 3 | Billing must continue at full speed with no internet | Switch off the network and bill a full basket with a UPI payment |
4 to 6 | Stock for every outlet visible together, with alerts before items run out | Ask to see two outlets’ stock on one screen and set an alert |
7 to 9 | Offers set once at head office, starting and ending automatically at every outlet | Configure an offer and verify it at a second outlet |
10 to 12 | Reports built from billing data, with returns handled inside billing | Ask for a live report from sample bills with no export |
13 to 15 | A live view of every outlet on a phone | Open the dashboard on a phone during the demo |
Add your priorities. Mark each requirement as Must Have, Important or Nice To Have. A system that fails a Must Have is out, however good it looks otherwise.
This list is the most valuable thing you will bring to a vendor. It stops the conversation drifting into features you do not need.
Use your own numbers. The formulas are simple.
Lost sales from one disruption = minutes lost × bills per minute × average bill value
Item | Assumed value |
Disruption across counters | 40 minutes |
Bills you would normally raise per minute | 1.5 |
Average bill value | Rs 900 |
Estimated sales affected | 40 × 1.5 × 900 = Rs 54,000 |
Item | Assumed value |
Missed or delayed delivery orders in one evening | 8 |
Average order value | Rs 350 |
Directly affected sales | 8 × 350 = Rs 2,800 |
Extra cost of remakes and refunds | Rs 1,200 |
Cost to your rating and repeat orders | Hard to measure but real |
Item | Assumed value |
Daily sales of a top item at one outlet | Rs 6,000 |
Days it was out of stock during the festival | 3 |
Sales lost at that outlet for that item | 3 × 6,000 = Rs 18,000 |
Same item at other outlets | Unsold surplus you may now discount |
Not every affected bill is lost. Some customers wait and some come back. But some walk away and some never return.
Now count how many evenings like this you had in the last month and how many outlets were affected. That total is the real cost of keeping a struggling system through another year. Compare it to the cost of a better system and the decision usually becomes clear.
Do not rely on impressions after a demo. Score every vendor the same way.
Criterion | Weight out of 100 | How to judge |
Offline billing works fully | 15 | Pass or fail in the demo |
Stock visible across outlets with alerts | 15 | Seen live with two outlets |
Central offers and pricing | 12 | Offer created and verified at a second outlet |
Reports and GST data from billing | 12 | Live report with no export |
Live dashboard on a phone | 10 | Opened during the demo |
Speed under peak load | 10 | Several bills in quick succession |
Fit for your format | 8 | Your own products and cases |
Support and response time | 8 | Written commitment and references |
Total three year cost | 5 | Written quote |
Ease of rollout | 5 | Written plan |
Score each criterion from 0 to the weight, then total. Any Must Have failed in the demo should disqualify the vendor, whatever the total.
What good answers look like: the vendor does it live, on your data, without leaving the screen to look for something.
Red flags: “we can show that in the next demo”, a slide instead of a live system, or a workaround when you ask to test something.
Question | What you are checking |
How many chains of my size and format use your system today? | Real experience in your segment |
Can I speak to three of them? | Willingness to be checked |
What happens to my data if I leave? | Lock in and data ownership |
What is the written total cost at my three year outlet count? | Hidden costs |
Who does the implementation and how many people will be assigned? | Delivery capacity |
What is your support response time for a counter that is down on a Saturday evening? | Real support commitments |
How are updates and tax changes delivered? | How the system stays current |
What is the rollout plan for a chain like mine? | Realistic timelines |
What do you need from us before we start? | Your own workload |
What does not work well in your product? | Honesty |
The last question is the most revealing. A good vendor will answer it clearly.
A reference call is where real information comes out. Prepare short questions and listen carefully.
Note whether the reference sounds relaxed or careful. Ask for a reference of a similar size and format to yours, not the vendor’s biggest customer.
Do not compare monthly prices alone. Build a three year view for each vendor.
Cost item | What to include |
Software subscription | Per outlet, per counter, per module, over three years |
Hardware | Terminals, printers, scanners, scales, kitchen screens, handhelds |
Implementation | Setup, data migration, configuration |
Training | Per outlet and for new staff later |
Support | Anything beyond the base subscription |
Add on modules | Loyalty, analytics, delivery, kiosk and more |
Internal effort | Staff time during rollout |
Cost of problems left unsolved | Manual work, lost sales and reconciliation time |
Ask each vendor for the three year total at the outlet count you expect, in writing. The cheapest monthly price is often not the cheapest total.
When | Step |
This week | Run the audit. Pull the data. Complete the scorecard and the extra questions. Write your requirements list and rank them. |
By 20 November | File your October return. Note every manual step it needed. |
Late November | Attend two or three demos using your own data and the eight tests. Fill in the scoring sheet for each. |
Early December | Shortlist. Call references. Ask for a written three year cost and a written rollout plan. |
Mid December | Decide. Sign a written scope. Begin data preparation. |
Second half of December | Train a core team. Pilot at one or two outlets if possible. |
January | Roll out in phases with a parallel run where needed. Finish well before your next major sale or festival. |
Timelines depend on how many outlets you run and how clean your data is. Ask any vendor for a written plan that fits your chain.
Mistake | Better approach |
Switching in the middle of a busy period | Plan the change for a calm window |
Moving every outlet at once | Pilot at one or two outlets first |
Skipping the parallel run | Run both systems briefly and compare totals |
Migrating messy data | Clean products, prices and tax settings first |
Training only managers | Train cashiers and store staff as well |
Choosing on price alone | Compare the three year total and the demo results |
Not testing offline mode | Test it yourself in the demo |
No written plan | Agree scope, timeline and responsibilities in writing |
RetailPOS is built by Unipro Tech Solutions, headquartered in Chennai, with more than 20 years of experience and over 10,000 businesses served. It covers three areas: a Retail Suite, a Restaurant Suite and a Distribution Suite.
Need | Product |
Billing, stock, GST, returns and loyalty across outlets | |
Fast checkout for supermarkets and grocery | |
Live view of sales, stock and outlet performance on a phone | |
More than 350 live reports across outlets | |
Stock audits and purchase orders from a handheld device | |
Compact counters in bakeries and sweet shops | |
Weighing scale automation and weighing mismatch detection | |
Field sales and pop up selling | |
Branded customer ordering and delivery | |
Restaurants, cafes and QSRs | |
Distribution businesses |
How to use a RetailPOS demo. Bring your scorecard and your requirements list. Tell us your hardest evening of the festival and ask us to show you how the system handles it, with the network switched off if you like. Bring your own product list and offers and run the eight tests in Section 10. Ask for references from chains of your size and format.
You do not need to guess whether your system is good enough. The festival has already produced your evidence. Score it, write your requirements, test any vendor against them, count the real cost, and plan the change for a calm window.
If your score is above three, the next ten days are the best time to start.
Book a free demo and bring your scorecard. Visit retailpos.co.in/register-demo | Call 044-421 421 40 / 95660 44300 | Email salesenquiry@uniprotech.co.in
Look for patterns. If the same failure appears at several outlets and the explanation is that the system could not do something, it is a software limit. If it happens at one outlet with one manager, look at process and training first. Section 6 gives a quick way to sort the causes.
Evaluate now and implement in a planned window. Choose a time when sales are lower and your team can be trained properly. Rushing a change into the next busy period often creates new problems.
Your scorecard, your requirements list, a sample of your product list with tax codes and prices, a sample of festival offers, and your expected outlet count in three years.
Ask for a written total at your three year outlet count, including software, hardware, implementation and training. Add the cost of manual work and downtime that a cheaper option leaves you with.
It depends on the number of outlets and the quality of your data. Ask for a written plan with a pilot outlet, a training schedule and a phased rollout.
It should. Test it yourself in the demo by switching off the network and billing a full basket.
Yes. Use the restaurant questions in Section 5 and add one on whether delivery orders reached the kitchen without manual entry.
Trust the data but look deeper. Check peak hours specifically, since many systems pass on quiet days and fail on busy ones. Also check how quickly you could answer simple questions such as “which outlet sold the most yesterday”.
Yes. Start with the 15 questions and your managers’ answers. Use whatever reports you have and note what you could not pull, since that is a finding too.
Within about two weeks of the last demo. Waiting longer lets the urgency fade and pushes the rollout into a busy period.
Scored your system? See how RetailPOS handles your hardest festival evening. Book your free RetailPOS demo today →