TL;DR
F&B KPIs Vietnam 2026: the 12 daily/weekly/monthly numbers that matter, target ranges by format, dashboard hierarchy, and the review cadence that prevents 80% of operator mistakes.
F&B KPIs & dashboards 2026: The 12 numbers that actually run the business
F&B KPIs & dashboards 2026: The 12 numbers that actually run the business
Most F&B operators track 40+ metrics and run by none of them. The brands that scale track 12 (daily, weekly, monthly) and review them on a fixed cadence. Here is that list.
TL;DR
- 12 KPIs total: 5 daily, 4 weekly, 3 monthly.
- Each has a target band by format and a trigger threshold.
- Three dashboards: shift, weekly P&L, monthly strategic.
- Review cadence: shift handoff (5 min), weekly Wed (45 min), monthly first-week (2 hours).
- The 80/20: 4 KPIs explain 80% of margin variance, food cost %, labor %, repeat rate, AOV.
1. The 5 daily KPIs (shift dashboard)
| KPI | Target | Trigger |
|---|---|---|
| Revenue vs forecast | ±8% | >12% miss |
| Average order value (AOV) | Brand-specific | -5% vs 30-day avg |
| Cover count / cups sold | Brand-specific | -10% vs same-day-last-week |
| Food cost variance (theoretical vs actual) | ±2pp | >3pp |
| Aggregator order acceptance rate | >97% | <94% |
Reviewed at shift handoff. 5 minutes. Variance >trigger → flag for next-day investigation.
2. The 4 weekly KPIs (operations dashboard)
| KPI | Target | Trigger |
|---|---|---|
| Labor % of revenue | Brand-specific (22–30) | +3pp |
| Repeat rate 14-day | 24–34% | <22% |
| Aggregator effective commission | <22% | >24% |
| Stock-out incidents | <3/week | >6/week |
Reviewed Wednesday for prior week (Mon-Sun). 45 minutes with the team.
3. The 3 monthly KPIs (strategic dashboard)
| KPI | Target | Trigger |
|---|---|---|
| EBITDA % | Format-specific (10–18%) | <8% |
| Customer cohort retention (30-day) | 38–48% | <34% |
| Marketing CAC by channel | Channel-specific | +25% vs 90-day avg |
Reviewed first week of month, 2 hours. Decisions on price, menu, marketing reallocation.
4. Target ranges by format
| KPI | Kiosk | Café | Full-service | Bar | QSR |
|---|---|---|---|---|---|
| Food cost % | 28–32 | 24–30 | 30–36 | 18–24 | 28–32 |
| Labor % | 18–24 | 22–28 | 26–32 | 18–24 | 24–30 |
| Aggregator effective % | <20 | <22 | <22 | <18 | <24 |
| AOV (K VND) | 35–55 | 55–95 | 220–450 | 180–380 | 75–135 |
| EBITDA % | 12–18 | 10–16 | 8–14 | 14–22 | 10–16 |
Outside ±2pp of these bands, investigate, don't adjust gut-feel.
5. The 80/20 rule of margin variance
Across 80+ audited operators, four KPIs explain ~80% of EBITDA variance:
- Food cost % (highest leverage)
- Labor %
- Repeat rate 14-day (drives revenue stability)
- AOV
Fix these four and EBITDA settles into target band. Chasing the other 8 first is procrastination.
6. The dashboard hierarchy
Shift dashboard (5 min)
↓ rolls up to
Weekly P&L dashboard (45 min Wed review)
↓ rolls up to
Monthly strategic dashboard (2 hr first-week review)
Each layer pulls from the same POS source of truth. No copy-paste from email. No PDF screenshots.
7. Review cadence rules
- Same time every cycle: shift handoff at clock-out, Wednesday 14:00 weekly, first Tuesday monthly
- Same attendees: shift lead, ops manager, owner
- Same template: preserves comparability week-over-week
- Decisions logged: what changed, expected impact, review date
Skip cadence twice = data integrity degrades, accountability erodes.
8. Common operator mistakes
- Tracking 40 KPIs (cognitive overload)
- Monthly review only (signal too late to act)
- Targets without trigger thresholds (knows the number, doesn't know when to act)
- Different dashboards from different tools (data fragmentation)
- Reviewing alone (no accountability)
FAQ
How many KPIs is too many? Above 15 is cognitive overload. 12 is the operational sweet spot.
Daily, weekly, or monthly? All three. Daily = course-correct, weekly = adjust, monthly = strategic.
Best dashboard tool 2026? POS-native is fastest (LOOP, iPOS, Misa). Standalone (Metabase, Looker) for chains 5+ outlets with custom needs.
What's the single most important KPI? Food cost %, highest leverage, worst when ignored.
How long until KPI discipline pays off? 60–90 days. The first month often shows worse numbers because measurement reveals hidden issues; payoff lands month 2–3.
Manual or automated? Automated for >100 covers/day. Below, spreadsheets work but consume 4–6 hours/week.
Related
Why this matters in 2026
Multi-outlet F&B operators across Vietnam and Southeast Asia are running into the same wall in 2026: aggregator commissions compress margins, food-cost drift compounds across outlets, labour cost climbs faster than ticket size, and a traditional POS only surfaces the damage at month-end when the only response left is firefighting. Operators who win in 2026 close the loop in hours, not weeks, variance flags before the next shift, demand forecasts before purchasing, daypart promos drafted automatically for slow slots, and a single morning brief instead of five dashboards. That is the bar this guide is written against, and the reason LOOP exists. The cost of a missed signal is no longer a single bad week, it is the difference between a chain that compounds outlet-level profitability and a chain that opens new outlets to mask the leaks at the old ones.
Operator playbook, first 30 days on LOOP
Week 1: Foundations. Import menu, recipes, modifiers, customers, loyalty balances and 24 months of sales via CSV. Connect aggregators (GrabFood, ShopeeFood, Be). Configure e-invoice provider (MISA / Viettel / VNPT). Confirm payment rails (VietQR for VN; DuitNow, PayNow and QR Ph are on roadmap). Train two staff per outlet on voice and text commands; the rest pick it up by observation in days 4–7.
Week 2: Variance and forecast online. Switch demand forecasting on at daypart level. Set variance alert thresholds (default: food-cost ±3pp, labour ±2pp, void rate ±0.5pp). Let the system run a full week without intervention so the baseline calibrates. Review the morning brief each day; ignore the urge to override, by day 10 the forecast typically holds steady.
Week 3: Promo and loyalty loop. Turn on daypart promo drafting for the two slowest hours per outlet. Connect Zalo OA / LINE / WhatsApp for delivery; start with a single segment (e.g. lapsed-30-day) and a single offer. Measure incremental visits, not coupon redemptions.
Week 4: Compound. Roll the same flow to a second outlet, then a third. The operating model is the same at outlet 2 as outlet 20, that is the point of LOOP.
KPI table, what to watch
| KPI | Target band 2026 | LOOP signal |
|---|---|---|
| Food cost % | 30–34% (QSR), 27–32% (café) | Variance alert within 6 hours of shift close |
| Labour cost % | 22–28% | Daypart staffing recommendation in morning brief |
| Repeat-visit rate (90d) | 38–46% (café), 28–36% (QSR) | Loyalty segment drafted weekly |
| Aggregator share of revenue | 18–32% | One queue across 5 aggregators; per-aggregator margin in dashboard |
| AI forecast MAPE per outlet | 14–22% | Recalibrates weekly per outlet |
| Ticket time (peak) | 6.8–9.2 min | KDS routing recommendation when over band |
| Void rate | <0.8% | Pattern-detection on staff/outlet/daypart |
Common pitfalls SEA operators hit in 2026
Treating aggregator orders as a separate business. Operators who keep five aggregator tablets running in parallel lose roughly 4–7 minutes per peak hour to context-switching alone, and miss the per-aggregator margin picture entirely. Unifying the queue (one tablet, one KDS, one accounting line per aggregator) is usually the single highest-leverage move in the first 60 days.
Letting variance live in spreadsheets. A weekly food-cost review is a 7-day reaction time on a 24-hour problem. Variance has to live in the operating layer, flagged, attributed and routed to the responsible manager within hours, not aggregated to a Friday email.
Loyalty as a punch card. A 2026 loyalty programme is a messaging channel with attribution. If the only metric is "points issued", the programme is a cost centre. If the metric is "incremental repeat visits per segment per month", it compounds.
Forecasting at the wrong resolution. Chain-level forecasts are wallpaper. Daypart-and-outlet is the smallest unit that pays back, coarser is too vague to act on, finer is noise.
How LOOP solves this
LOOP is an AI-native restaurant operating system built for SEA F&B chains. Operators run their venues by voice or text command instead of clicking through dashboards. AI forecasts demand per outlet at daypart resolution (modelled accuracy published in our methodology), flags food-cost and labour variance within hours of the shift closing, drafts promos for slow daypart slots and pushes them to Zalo OA / LINE / WhatsApp, and delivers a three-item morning brief at 06:30 local time so the operator's first action of the day is informed. LOOP unifies GrabFood, ShopeeFood, Be into one queue, supports VietQR in Vietnam; DuitNow, PayNow and QR Ph are on roadmap, and ships VAT e-invoice (TT78) via MISA, Viettel and VNPT. Pairs with PEKO loyalty. PEKO customers get 50% off LOOP POS paid plans.
Under the hood, LOOP is offline-first with a 90-second resync window so orders, payments and KDS keep firing through ISP drops; recipe-level COGS is computed at order time so every plate's contribution margin is visible before the shift ends; and the morning brief is generated from the previous day's variance, the current day's forecast and the next 14 days of bookings, weather and local events, not a static template. The result is fewer dashboards, faster decisions, and a noticeably calmer week for the operator.
