F&B inventory management 2026: Par levels, counts & shrinkage
By LOOP Research
Last updated:
F&B inventory management 2026: Par levels, counts & shrinkage
Inventory is where margin is silently won or lost. A disciplined inventory system returns 2–4pp of margin and reclaims 6–10 manager-hours/week. Here is the operator playbook.
TL;DR
- Three SKU classes (A/B/C) drive count cadence and par strategy.
- Par level = avg daily usage × lead-time days × (1 + safety buffer).
- Count cadence: A weekly, B bi-weekly, C monthly.
- Shrinkage benchmarks: dry 1–2%, produce 3–5%, bar 4–6%, dairy 2–4%.
- Consolidate to 3 primary suppliers + 1 backup per category — anything more is admin debt.
1. SKU class system
| Class | % of SKUs | % of COGS | Examples | Cadence |
|---|---|---|---|---|
| A | 15–20% | 70–80% | Coffee, milk, key proteins, top toppings | Weekly count, daily eyeball |
| B | 25–35% | 15–20% | Secondary ingredients, packaging | Bi-weekly count |
| C | 45–60% | 5–10% | Garnish, sauces, smallware | Monthly count |
Most operators count everything weekly (waste of 4 hours) or nothing (waste of 4 pp of margin). Class-based is the middle path.
2. Par level math
Par level = (avg daily usage × lead-time days) × (1 + safety buffer %)
Example — espresso beans at a Specialty café:
- Avg daily usage: 4.2 kg
- Lead time: 3 days
- Safety buffer: 20% (volatile aggregator demand)
- Par = 4.2 × 3 × 1.2 = 15.1 kg
Reorder point = par × 0.6. When stock hits 9 kg, place order.
Recalculate par quarterly or when avg daily usage moves ±15%.
3. Count workflow that works at 11pm
- One staff + one tablet, not paper
- Count by storage location (walk-in → freezer → dry → bar), not by menu
- Photo capture for variance >10%
- Submit; system computes variance vs theoretical; flag investigations
Total time at a Specialty: 35–50 minutes weekly for class A; 60–80 min bi-weekly for B; 90–110 min monthly for C.
4. Shrinkage benchmarks (Vietnam 2026)
| Category | Healthy | Investigate |
|---|---|---|
| Dry goods (rice, sugar, flour) | 1–2% | >3% |
| Produce | 3–5% | >7% |
| Dairy | 2–4% | >5% |
| Proteins (chilled) | 2–4% | >6% |
| Bar (spirits) | 4–6% | >8% |
| Bar (beer, kegs) | 3–5% | >7% |
| Packaging | 1–2% | >4% |
Above the investigate threshold, audit one of: portioning, receiving accuracy, theft, or recipe spec.
5. Receiving discipline (the 3-touch rule)
Every delivery passes three checks:
- Count vs PO (units, weight, case size)
- Quality (temperature, dates, freshness)
- Match invoice → receiving note → PO
Skip any one and shrinkage jumps 2–3pp within 60 days. The most expensive shortcut in F&B.
6. Supplier consolidation
Most independents have 9–14 suppliers. Target: 3 primary + 1 backup per category (dry, fresh, beverage, packaging) = 8–12 total relationships, but 4–5 doing 80% of volume.
Benefits at consolidation:
- 2–5% better pricing on volume commitments
- Fewer deliveries (lower receiving labor)
- One invoice per week per supplier, not three
- Stronger leverage when issues arise
Quarterly bid the top-20 SKUs to keep pricing honest.
7. The single dashboard
Replace 4 spreadsheets with one view:
- Current stock (units + days of cover)
- Reorder triggers (red, amber, green)
- Variance vs theoretical (last 7 days)
- Top 10 shrinkage items
- Supplier price changes (last 30 days)
If your POS does recipe-deduct, this dashboard builds itself. If not, build it in Sheets — but the manual maintenance is 3–5 hours/week.
8. Common mistakes
- Counting everything weekly ("being thorough" = burning labor)
- Par levels frozen for 12 months while demand shifted
- Skipping receiving counts on "trusted" suppliers
- Treating modifier ingredients as free
- No backup supplier — one outage = one weekend lost
FAQ
How often should I count inventory? By class: A weekly, B bi-weekly, C monthly.
What's a healthy shrinkage %? Depends on category; see §4. Bar is highest tolerance (4–6%), packaging lowest (1–2%).
Do I need software? For >100 SKUs, yes — manual is 5+ hours/week of admin debt.
How many suppliers should I have? 8–12 total, with 4–5 doing 80% of volume.
What's the fastest pp recovery? Receiving discipline (3-touch rule) and bar shrinkage audit — typically 1.5–2.5pp in 30 days.
When do I recalculate par? Quarterly, or when avg daily usage moves ±15%.
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.
The SEA F&B operator landscape in 2026 also looks materially different from 2023. Aggregator commissions in Vietnam have settled in the 22–28% band; Thailand and the Philippines run higher, Singapore lower. Labour minimums have moved twice in eighteen months in Vietnam. E-invoice (TT78) is now non-negotiable and enforced. Loyalty has shifted from punch cards to messaging-native (Zalo OA, LINE, WhatsApp, Messenger) — and the chains that ride that shift are seeing repeat visits double inside ninety days. None of that lands as an upgrade on a legacy POS; it lands as a different operating model.
SEA benchmarks (2026)
- Median food cost across SEA QSR chains: 30–34% in 2026.
- Median labour cost across SEA F&B chains: 22–28% in 2026.
- Repeat-visit rate for loyalty-enabled cafés: 38–46% in 2026.
- Average ticket time for SEA QSR in peak: 6.8–9.2 minutes in 2026.
- Aggregator commission band in VN: 22–28% per order in 2026.
- AI demand forecast MAPE on LOOP cohorts: 14–22% per outlet in 2026.
- VAT e-invoice (TT78) compliance among LOOP outlets: 100% by 2026.
- Average POS uptime LOOP cohorts: 99.92% rolling-90-day in 2026.
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, foodpanda, Gojek). Configure e-invoice provider (MISA / Viettel / VNPT). Confirm payment rails (VietQR for VN; PromptPay / QRIS / DuitNow / PayNow / QR Ph for the rest of SEA). 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 within MAPE 18% and stays there.
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 (MAPE 14–22% on LOOP cohorts), 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, foodpanda and Gojek into one queue, supports VietQR / PromptPay / QRIS / DuitNow / PayNow / QR Ph, and ships VAT e-invoice (TT78) via MISA, Viettel and VNPT. Pairs with Peko loyalty (50% lifetime discount on LOOP for Peko customers).
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.