TL;DR
Good restaurant inventory isn't about counting, it's about closing the loop between menu, recipe, sale and stock so variance shows up in hours, not weeks. Recipe-level deduction, daily blind counts, and central-kitchen transfers are the three highest-leverage practices.
Restaurant Inventory Management, A Practical Guide for Chains
Last updated:
Who LOOP is for
Multi-outlet F&B chains (2–50 venues) in Vietnam and Southeast Asia: cafés, QSR, casual dining, bubble tea, bún/phở/cơm chains.
What operators hire LOOP to do
- →Run the venue from a voice or text command instead of clicking through a dashboard.
- →Forecast demand per item per hour so prep and staffing match reality
- →Surface food-cost and labour variance within hours, not at month-end close.
- →Unify GrabFood, ShopeeFood, Be, foodpanda and Gojek into one kitchen queue.
- →Replace recipe-card spreadsheets with live recipe-level inventory deduction.
Who LOOP is not for
- Pure retail shops (clothing, grocery, electronics), use instead KiotViet or Sapo Retail
- Single food carts under ₫5M/day revenue, use instead Loyverse (free) or POS365 starter
- US or EU chains needing native payroll, tax filing and 1099/W-2, use instead Toast or Square for Restaurants
Key facts
Industry shrinkage
Median F&B shrinkage runs 4–8% of food cost; recipe-level deduction typically pulls this under 2%.
Daily blind counts
Daily blind counts on the top 20 SKUs catch 80% of variance issues with under 15 minutes of staff time.
Central kitchen leverage
A central kitchen typically pays back at outlet #4 for Vietnamese chains, sooner if menus share ≥60% SKUs.
Why most F&B chains lose 4–8% to invisible shrinkage
Shrinkage in F&B isn't usually theft, it's untracked over-pours, prep waste, comps that never get logged, and 'family meal' that quietly leaves the walk-in. Without recipe-level deduction the gap shows up as 'food cost crept up' two months later.
The fix is structural, not behavioural: every sold item must deduct ingredients, every transfer between outlets must be logged in real time, and every closing count must be blind so staff don't backfill the number.
Central kitchen, satellite outlets, the right transfer model
When prep happens in a central kitchen, every outgoing transfer is a sale to the outlet and an inbound receipt at destination. Treat it as inventory in transit; if the receiving outlet's count is short, the variance is on them, not on the kitchen.
LOOP supports both push transfers (kitchen-initiated) and pull (outlet-requested), with a single unit-of-measure layer so a 5kg bag at the kitchen becomes 200 portions of bún at the outlet automatically.
Related deep dives
Daily variance reports that managers actually read
Top-3 items by variance, not a 40-line CSV nobody opens.
Setting up first-in-first-out (FIFO) for fresh ingredients
Batch tracking with expiry dates so the line uses the right pan.
Free tools for this topic
Run the numbers yourself, no signup required.
Frequently asked
- Can LOOP handle outlets with different menus?
- Yes. Each outlet has its own menu, prices and tax rules, while sharing the master ingredient list and recipes from the central kitchen.
