Store Operations Audit: The Complete Guide and Free Checklist for Indian Retail Chains (2026)

What a store operations audit is, and how it differs from a visit or an inspection

The word audit is borrowed from accounting: an independent check, against a written standard, that produces evidence. In a store the standard is the manual, the docket and the compliance register; the evidence is a live photo, a count or a document; the output is a score, gaps and tasks with owners and dates.

Of the three things chains call an audit, only one is. The visit is a relationship, the inspection is a reaction, and only the audit is repeatable, comparable across stores and months, and able to say whether the chain is improving.

Why audits fail today

Most chains already audit. Last quarter's scores exist, usually in a spreadsheet, usually above 90, and usually unconnected to what the stores looked like to a customer. Four failures explain the gap.

• The clipboard. Paper or spreadsheet audits are typed up later, from memory, often by the person being audited. Items get ticked because the auditor believes them, not because they were seen.
• Backdated photos. Once photos are required, the gallery upload follows: last week's window, the same mannequin on three Mondays. A photo without a live timestamp and location is a claim with a picture attached; see /learn/how-to-stop-backdated-store-photos-and-fake-checklists/.
• No closure. A gap found is not a gap fixed. Most programmes end at the score, and the dead demo unit sits in a report until the next audit finds it again. Without an owner, a due date and a re-photo, the audit is a diary.
• Scores nobody reads. The score lives in a file the operations team keeps, not in the Monday sales review. Store managers learn that a 72 has no consequence and a 94 no reward, and the audit becomes a formality.

The six types of store audit

Store audit is one label for six checks, run by different people at different frequencies; chains that fold all six into one 200-item list do none of them well. Most run the first three. The sixth moves sales, and almost no programme includes it.

What to assess: the 72-item checklist, group by group

The downloadable checklist has 72 weighted items in eight groups, each with a photo to take and a yes-or-no question; the table shows eight per group, and the file adds weights, fatal flags, owners and a scoring sheet totalling 100. Walk the groups in trading-day order. An item without a photo is an opinion and a 1 to 5 scale is a negotiation; almost done is a no.

How to run a store operations audit in seven steps

The checklist is the easy part; the programme around it decides whether the score means anything.

1. Fix the standard before the checklist. Every item must trace to a line in the manual, the current docket or the compliance register; write the standard first if it is missing, then turn each item into a yes-or-no question with a named photo.
2. Weight the items to total 100. Customer-facing failures pull the score down harder: a dark window costs more than an unlabelled cupboard. Mark four to six items fatal, typically the fire NOC, MRP display, the recording notice where recording runs, closing cash and the customer washroom; a no on any of them caps the audit at 69.
3. Set the pass mark and the bands: 85 and above green, 70 to 84 amber, under 70 red is a working start. Recalibrate after three months; a band nobody reaches or nobody fails means the weights are wrong, not the stores.
4. Announce the cadence, not the date. Stores should know that audits happen daily, weekly, monthly and quarterly, but not which Tuesday; an audit the store prepared for measures the preparation.
5. Walk the customer's route with live photos, from the road inward in checklist order, each photo taken in the app at the moment of the check with timestamp and location, gallery upload disabled. For counts and documents, photograph the sheet or certificate itself.
6. Close every gap as a task. The audit ends when the last gap is closed, not when the score is saved: each no becomes a task with an owner, a due date and a required re-photo, closed by the re-photo and never by a message. Repeat failures escalate automatically.
7. Read the score in the sales meeting, next to conversion, average bill and the selling score, and trend it by store, region and item. An item failing in forty stores is a head office problem, not forty store problems.

Cadence: who audits what, and how often

Four cadences share the load. The daily self-audit is the store manager's own check; the quarterly HQ audit adds the sales-execution audit the others leave out. Between them, all 72 items are seen at least monthly by someone from outside the store.

Reading the score, and what to do with it

A single score is a signal, not a verdict; three readings turn it into decisions. The store's own trend: a 78 that was 66 two months ago is a different problem from a 78 that was 91. The item view across the chain: if the demo unit item fails in half the stores, the problem is the charger supply, not the managers. Regional variance: a twelve-point gap between regions with the same formats is an area manager difference, and the better routine should be copied.

The reading most chains skip is the operations score next to the selling score: the first says the store is right, the second says the conversation is right, and together they explain the sales number. High operations, high selling is the model store: train from it. High operations, low selling means the floor is right and the conversation is wrong: the fix is coaching, and the sales-execution audit shows which step of the pitch is skipped. Low operations, high selling is a strong team carrying a weak store: fix the store before the team tires. Low and low is next week's diary for the area manager.

For the first three months, publish scores and keep them out of appraisals; managers punished for an honest 64 learn to produce a dishonest 90. Once the scores are believed, tie the monthly audit to the store manager's review and the quarterly audit to the area manager's.

Tools: checklist app, audit app or AI verification

Three kinds of software carry a store audit. A checklist app digitises the list and collects ticks and photos. An audit app adds weights, scores, fatal items, scheduling and task closure. AI verification checks the evidence itself: is the photo live, does it show what the item asked for, does it match the docket. Wooqer, Pazo and others are compared in /learn/best-retail-store-audit-apps-india-2026/, the AI category in /learn/ai-based-store-audits/.

BorentisOps: the measured way to run the audit

BorentisOps is built for brands that run their own showrooms and exclusive brand outlets. It carries the 72-item checklist on the store phone, captures every photo live with time and location, and its visual AI, Drishti, scores the photo against the docket or display standard: is the window the campaign window, is the mannequin dressed as specified, is the price board beside the display car. Fatal items cap the score, every failed item becomes a task with an owner and a due date, and the task closes only on a verified re-photo. Drishti checks a phone photo against a docket, not shelf facings; BorentisOps is not built for general-trade shelves or distributor visits.

The second half of the platform is the difference. The same store phone, with consent and the DPDP notice displayed, records the sales conversation, and Borentis scores it against the pitch in Hindi, English and Hinglish: greeting, need discovery, launch of the month, objection handling, and whether a number was taken from the customer who did not buy. The operations score and the selling score sit on the same page. Nothing is sent to customers automatically; follow-ups are actions for the advisor and the manager. Camera-based footfall and visit signals are on the roadmap. Details at /solutions/products/borentisops/.