Cloud kitchen Vietnam 2026: Unit economics & operator playbook
By LOOP Editorial
Last updated:
Cloud kitchen Vietnam 2026: Unit economics & operator playbook
Cloud kitchens were oversold in 2022 and undersold in 2026. The model works — but only with brutal unit economics discipline and the right host/format choice. Here is the operator's honest playbook.
TL;DR
- 3 viable formats 2026: shared-hub kitchen (GrabKitchen, CloudEats), host-restaurant kitchen, own dark kitchen.
- Capex: 80–350M VND depending on format; opex 60–180M VND/month.
- Sustainable aggregator commission effective: <22% (else margin caps at 8%).
- Break-even: 80–140 orders/day per virtual brand at AOV ~135K.
- 60% close because of: low AOV, single-brand single-kitchen, weak packaging, no own-channel acquisition.
1. Three viable formats
| Format | Capex | Monthly rent | Best for |
|---|---|---|---|
| Shared hub (GrabKitchen, CloudEats) | 80–160M | 12–28M | Testing 1 virtual brand |
| Host kitchen (sub-lease in existing restaurant) | 100–220M | 18–35M | 1–2 brands, low risk |
| Own dark kitchen | 180–350M | 25–55M | 3+ virtual brands, scale |
The hub is the lowest commitment, but stack-fees are punishing above 600 orders/month. Own dark kitchen wins only with 3+ brands sharing the same prep line.
2. Capex breakdown (own dark kitchen 60m²)
| Item | Cost (M VND) |
|---|---|
| Deposit (3 months) | 45 |
| First month rent | 15 |
| Build-out + cool storage | 85 |
| Cooking equipment | 95 |
| Packaging machinery | 18 |
| POS + KDS + tablets (3-channel) | 22 |
| Initial inventory (2 weeks) | 28 |
| Aggregator setup + photography | 18 |
| Permits + signage + electronic invoice | 12 |
| Pre-open labor + training | 12 |
| Total | 350 |
3. Monthly opex (steady state, 3 brands)
| Item | Cost (M VND) |
|---|---|
| Rent | 35 |
| Labor (1 head + 3 line + 1 dispatch) | 58 |
| COGS (32% of 240M revenue) | 77 |
| Packaging (4.5% of revenue) | 11 |
| Aggregator commission effective (22%) | 53 |
| Utilities | 9 |
| Marketing (mostly aggregator + KOC) | 14 |
| POS + software | 4 |
| Maintenance | 3 |
| Total opex | 264 |
| Revenue (240M × 3 brands × 0.85 mature) | 612M |
| EBITDA | ~88M (14%) |
A 3-brand dark kitchen at maturity returns 14% EBITDA. A single-brand kitchen returns 4–7% if at all — which is why most close.
4. Aggregator economics (the gravity)
Effective commission on GrabFood/ShopeeFood/Be 2026 ranges 18–28% depending on:
- Base commission tier (18–22%)
- Featured/ad fee (3–6%)
- Promo co-funding (1–4%)
Above 22% effective, margin caps at 8% no matter what you do on COGS. Mitigations:
- Own-channel mix >25% (Zalo Mini App ordering, web)
- Bundle for AOV >150K (commission % bites less in absolute)
- Negotiate tier down at >2,000 orders/month
5. The virtual brand math
Running 1 brand: AOV 125K, 90 orders/day, 22% commission. Net per order: ~38K margin. Daily contribution: 3.4M VND. After rent + labor + utilities (3M/day at this volume), unit nets ~400K/day. Below sustainable.
Running 3 brands sharing kitchen: same prep line drives 240 orders/day across 3 menus. Marginal cost of brand #2 and #3 is ~15% of standalone. Unit nets 2.5–3.5M/day. Sustainable.
The lesson: single-brand cloud kitchens almost always fail. Plan for 3 brands or don't start.
6. The 4 failure modes (account for 60% of closures)
- AOV under 100K — commission eats everything
- Single brand single kitchen — fixed cost not amortized
- Weak packaging — leak/cold/messy = 1-star reviews = ranking collapse
- 100% aggregator dependence — algorithm change = revenue cliff
If you're building today, design against all 4 from week 1.
7. The packaging spec that prevents 1-star reviews
- Leak-proof rated to 95°C for 45 min
- Vented for crispy items (separate compartment for sauce)
- Branded sticker seal (visible tamper evidence raises trust)
- Insulated bag tested at peak commute time (60 min @ 33°C)
Budget: 4.5–6.5% of revenue. Below 4%, you're cutting reviews.
8. Own-channel acquisition (the survival lever)
Aggregator-only is structurally unprofitable above 22% effective commission. Build own-channel:
- Zalo OA + Mini App with own delivery (Ahamove/Grab Express direct)
- QR on packaging linking to Mini App with 15% incentive vs aggregator
- Loyalty cohort seeded from delivery customers
- Catering for offices (highest AOV, lowest CAC)
Target 25–40% own-channel mix at year 2. Below 15%, you're a hostage.
FAQ
Is cloud kitchen worth it Vietnam 2026? Yes if you can run 3+ virtual brands from one kitchen with >25% own-channel mix. No otherwise.
Best format to start? Shared hub for 60-day market test. Move to host or own dark kitchen only when one brand proves >100 orders/day.
Sustainable aggregator commission? Effective <22%. Above, build own-channel aggressively or close.
How many brands per kitchen? 3 is the sweet spot. 4 starts to hurt prep speed. 2 doesn't amortize fixed cost.
Capex realistic? 80–160M for hub start, 180–350M for own dark kitchen with 3 brands.
Payback? 14–24 months at 3-brand maturity. 30+ months single-brand (and usually closes first).
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.