Store operations
Store Operations KPIs for Brand Outlets: The Twelve Numbers an Area Manager Should See Daily
Store operations KPIs for brand outlets are the twelve numbers that tell an area manager, before 10:30 every morning, whether each store opened to standard, is staffed, is dressed to the docket, is fixing what broke, and is handling cash and stock correctly. They differ from selling KPIs such as walk-ins, conversion and average bill because they measure whether the store was ready to sell, not whether it sold. This guide gives the twelve as a table with the formula, the data source, a working target range and the owner, shows how they roll up into one operations score out of 100, and explains why that score should sit beside the selling score on the same store scorecard rather than in a separate report read by a separate team.
Why twelve, and why daily
More than twelve and the morning read stops happening; fewer and something that matters goes unwatched. Twelve is what fits on one phone screen per store and one table per region. Daily because the failures they measure cost the day they happen: a window undressed on the first morning of a launch, a store that opened late on a Saturday, a cash variance unexplained at closing. A weekly report tells the area manager what was lost; a daily read lets them stop it by lunchtime.
The twelve fall into two families. Readiness measures whether the store was fit to sell when the doors opened: opening on time, the checklist score, photo compliance, docket compliance, staffing and grooming. Control measures whether the store is being run properly behind the floor: ticket ageing, ticket closure, cash variance, stock discrepancy, training currency and the audit gap. Readiness is read every morning; control is read every morning too, but moves more slowly.
The twelve KPIs
Targets are working ranges drawn from brand operations manuals and networks the author has worked with, not a benchmark; set yours after four weeks of your own data.
| KPI | Formula | Source | Working target | Owner |
|---|---|---|---|---|
| 1. On-time opening rate | Stores whose opening routine was completed inside its window / stores due to open | Checklist timestamps | 95 to 100% | Store manager; area manager |
| 2. Opening checklist score | Sum of weights of items answered yes / total weight, per store, averaged for the region | Checklist app | 85 to 95 | Store manager |
| 3. Photo compliance rate | Items completed with a live photo / items requiring a photo | Checklist app | 98 to 100% | Store manager |
| 4. Docket compliance | Windows and hero fixtures passing the docket check / windows and hero fixtures | VM AI verdict or VM team review of the opening photos | 90 to 100% in launch weeks; 85% or above otherwise | VM lead; store manager |
| 5. Staffing against roster | Staff present at opening / staff rostered | Attendance or roster in the app or HRMS | 90 to 100% | Store manager; HR |
| 6. Grooming and uniform compliance | Team members passing the grooming check / team members present | Opening team photo | 95 to 100% | Store manager |
| 7. Open ticket ageing | Tickets open beyond their SLA / tickets open | Ticket module | Under 10%; zero fatal tickets past SLA | Ticket owners; area manager |
| 8. Ticket closure within SLA | Tickets closed inside their SLA / tickets closed, trailing seven days | Ticket module | 80 to 90% | Ticket owners |
| 9. Cash variance | Absolute difference between POS day-end and banked total / day's sales; and count of unexplained variances | POS and the closing checklist | Under 0.1% of sales; zero unexplained | Cashier; store manager |
| 10. Stock discrepancy rate | Variance units in the latest cycle count / units counted | Weekly stock count in the app, shown daily as the last count | Under 1 to 2% | Store manager |
| 11. Training currency | Staff current on mandatory modules / staff on roll | Training module | 90 to 100%, and 100% before a launch | Trainer; store manager |
| 12. Audit score and re-audit gap | Latest area manager audit score; and that score minus the store's own average on the same items | Audit module | Audit 85 or above; gap under 10 points | Area manager |
The operations score
The twelve roll into one operations score out of 100 so that stores can be ranked and the scorecard can carry one number beside the selling score. A working weighting gives readiness 60 points and control 40: on-time opening 10, checklist score 15, photo compliance 5, docket compliance 15, staffing 10, grooming 5; ticket ageing 10, ticket closure 5, cash variance 10, stock discrepancy 5, training currency 5, audit gap 5. Each KPI is scored against its target range and contributes its share of its weight.
Two items are fatal at the score level as they are at the item level: an unexplained cash variance on the day, or a safety ticket open past its SLA, caps the day's operations score at 69 whatever the rest reads. Rank the stores, but read the distribution rather than the average. A region at 88 with two stores at 61 has two problems; a region at 88 with every store between 84 and 92 has none. A store at 100 every day is a store to re-audit, for the reasons at /learn/how-to-stop-backdated-store-photos-and-fake-checklists/.
The operations score beside the selling score
Kept in separate reports read by separate teams, the two scores blame each other. The sales meeting says the store was not ready; the operations meeting says the store was ready and the advisors did not sell. On one scorecard, per store, the two numbers read as one of four situations, and each has a first action.
| Operations score | Selling score | What it usually means | First action |
|---|---|---|---|
| High | High | The model store: ready every morning and converting | Send other store managers to see it; protect its roster |
| High | Low | Ready but not converting: greeting, demonstration, objections or the close | Coaching from the store's own conversations; the conversation score says which step |
| Low | High | Selling in spite of the store, usually on one strong advisor | Fix operations before that advisor leaves; the result is fragile |
| Low | Low | A leadership problem at the store | Area manager visit this week; roster and store manager review |
Reading the twelve in ten minutes
- 09:45 to 10:15: on-time opening and photo compliance across the region. Call the stores that have not opened or have opened without photos before anything else.
- Fatal flags next: any unexplained cash variance from last night, any safety ticket past SLA. These two are read before the score.
- Docket compliance during launch and festive weeks: the failing windows, photo by photo, with the VM team copied.
- Ticket ageing: who is sitting on what, by owner rather than by store, since the same facility vendor is usually behind several stores' overdue tickets.
- Staffing: which stores are short today, and whether a floater can move before the afternoon.
- Mondays add the slow movers: stock discrepancy, training currency and the audit gap, and from the bottom five stores the visit plan for the week using the format at /learn/store-visit-report-app-for-area-managers/.
Targets are ranges, not laws
The target column is a starting point. Mall stores open to the mall's clock and rarely miss; high street stores depend on the first staff member's commute and miss more. A dealership's docket compliance is about display cars and price boards; an apparel outlet's is about windows and mannequins. Set each store format's ranges after four weeks of data, publish them, and revisit them each quarter.
Resist tying incentives to the daily operations score alone. The moment it pays, it reads 100, and the tells described in the fake-checklist guide appear within a fortnight. Pay on the area manager's audit score and on the selling score, and use the daily operations score for what it is: the morning's early warning. The selling side of the same scorecard, the numbers a store manager reads on walk-ins, conversion and average bill, is at /learn/frontline-sales-kpis-store-manager/, and the wider method for measuring execution across a network at /learn/how-to-measure-in-store-execution/.
How BorentisOps shows the twelve
BorentisOps, the store operations platform at /solutions/products/borentisops/, produces the twelve from the routines it runs: checklists with a photo and a question per item give the opening, checklist, photo and grooming numbers; Drishti, its visual merchandising AI, gives docket compliance from the opening window photos in seconds; tickets with SLA escalation give ageing and closure; the closing checklist with the POS feed gives cash variance; the stock count, training module and audit module give the rest. The role dashboard shows the region as the table above and each store as a card, and the 19:30 digest email carries the day's numbers with the photos behind them.
The operations score sits on the store scorecard beside the sales conversation score from Borentis Floor, which is where the four-square reading above comes from. BorentisOps is priced per store, works offline first and runs in Hindi, English and Hinglish. Camera-based footfall and visit signals are on the roadmap rather than in the product today, so walk-ins are entered by the store or read from the POS. POS, HRMS and warehouse feeds for the cash, roster and stock KPIs are described at /solutions/products/borentisops/integrations/.
Frequently asked questions
What is a good store operations score?
With the weighting in this guide, 85 and above is green, 70 to 84 amber and under 70 red, with an unexplained cash variance or an overdue safety ticket capping the day at 69. These are working bands, not a benchmark. Read the spread across stores rather than the region's average, and treat a store that scores 100 every day as one to re-audit rather than one to celebrate.
Should store operations KPIs be tied to incentives?
Tie the area manager's audit score and the selling score to incentives, not the daily self-reported operations score. Once the daily score pays, it reads 100 within a fortnight and stops measuring anything. Use the daily score as the morning's early warning, share it openly with store teams, and recognise honest scores that vary day to day over suspiciously perfect ones.
How are store operations KPIs different from retail sales KPIs?
Operations KPIs measure whether the store was ready to sell: opened on time, dressed to the docket, staffed, groomed, cash and stock in order, tickets closed. Sales KPIs measure whether it sold: walk-ins, conversion, average bill, attachment. A store can score high on one and low on the other, which is why the two belong on one scorecard, where high operations and low selling reads as a coaching problem and the reverse reads as a fragile store.
How many stores can one area manager read daily with these KPIs?
With the twelve on a dashboard and the photos behind them, an area manager reads twelve to fifteen stores in about ten minutes each morning and spends the rest of the day on the three or four that need a call or a visit. Without the dashboard, the same read from WhatsApp groups and spreadsheets takes most of the morning and misses stores. The territory sizes common in Indian brand networks, eight to fifteen stores, fit the ten-minute read.
Related reading
- BorentisOps, the store operations platform
- Frontline sales KPIs for the store manager
- How to measure in-store execution
- Store visit report app for area managers
Where Borentis applies this
- Execution Scorecards: See the floor before the P&L does.
- Coaching from Best Conversations: Your best advisor, teaching everyone.
- Playbook Adherence: Your playbook, finally observed.
Borentis is the Agentic Operating System for Customer Interactions, built for Indian retail floors: consented one-tap capture on the advisor's phone, every conversation scored against your playbook with the evidence behind every number, leads created when a number is heard, and coaching from your own best conversations.