Restaurant POS Vietnam 2026: Buyer's guide for operators
By LOOP Research
Last updated:
Restaurant POS Vietnam 2026: Buyer's guide for operators
Picking a restaurant POS in Vietnam in 2026 is no longer about screens and printers. It is about three things: e-invoice compliance, aggregator unification, and recipe-level inventory. Everything else is table stakes.
TL;DR
- E-invoice (HĐĐT) issuance from POS is mandatory for F&B above the VND 1B revenue threshold; most serious operators are already there.
- Aggregator sync (GrabFood, ShopeeFood, Be) must be menu + stock + price + 86-list, not just order import.
- Recipe-deduct (one sold drink decrements 9 ingredients) is the only way to control food cost ±2pp.
- Hardware capex: 8–55M VND per outlet depending on tier.
- Total monthly software: 500K–3.5M VND; the difference is features used, not advertised.
1. The 2026 non-negotiables
Any POS shortlist must clear these five gates:
- HĐĐT issuance through a licensed provider (VNPT, Viettel, Misa, EasyInvoice) — direct from POS, not a separate flow.
- Aggregator unification — one menu source of truth pushing to GrabFood/ShopeeFood/Be; orders pull back into the same KDS.
- Recipe-level deduction — sell a phin sữa đá, deduct 18g coffee + 25ml condensed milk + ice + cup + lid.
- Modifier + variant matrix — size, sugar, ice, toppings, add-ons must each carry their own COGS and price.
- Offline-first — drops to 4G or no internet cannot freeze ordering.
If a POS misses any of the above, it is a 2023 product re-branded.
2. Hardware tiers
| Tier | Use case | Stack | Capex (VND) |
|---|---|---|---|
| Kiosk | Takeaway / 1 station | Android tablet + cash drawer + thermal printer + scanner | 8–14M |
| Compact | 1 cashier + 1 KDS | + KDS screen + label printer | 18–28M |
| Specialty | 2 cashiers + bar KDS + kitchen KDS | + 2nd printer + handheld order pads | 28–42M |
| Flagship | 3+ stations + bar + 2 kitchens + QR table | + QR ordering kiosks + 3rd KDS | 42–60M |
Buying refurbished commercial-grade tablets (not consumer iPads) and Star/Epson printers cuts 20–30% with no operational hit.
3. Vendor matrix (operator lens, not marketing lens)
| Vendor | HĐĐT | Aggregator sync | Recipe-deduct | Multi-outlet | Monthly | Best fit |
|---|---|---|---|---|---|---|
| iPOS | Strong | Strong | Adequate | Strong | 1.2–2.8M | Mid + chains |
| KiotViet | Strong | Adequate | Weak | Strong | 0.5–1.4M | Retail-leaning F&B |
| Sapo FnB | Strong | Adequate | Adequate | Strong | 0.7–1.8M | SMB chains |
| Misa CukCuk | Strong | Adequate | Adequate | Strong | 0.8–1.6M | Full-service |
| LOOP | Strong | Strong (unified) | Strong (ingredient-level) | Strong | 0.9–2.4M | Operators chasing margin |
| GoSell / Haravan | Adequate | Weak | Weak | Adequate | 0.4–1.2M | Bakery / retail-F&B hybrid |
"Adequate" means it works; "Strong" means it survives an audit.
4. The hidden cost: total cost of ownership
Sticker price misleads. Real TCO includes:
- Implementation (recipe load, menu setup, hardware install): 4–18M one-off
- Training (cashier, manager, kitchen): 2–6M one-off
- Add-ons (KDS, table QR, loyalty, accounting bridge): 0.3–1.2M/mo each
- HĐĐT pages (per-invoice fee with provider): 200–600 VND/invoice; ~80–280K/mo
- Payment gateway fees (QR, card): 0.8–2.2% of revenue
- Support SLA upgrades (priority response): 0.4–1.5M/mo
A "500K/mo POS" with three add-ons + HĐĐT + premium support is 2.4M/mo.
5. Recipe-deduct: why it is the single feature that matters
Without recipe-deduct, food cost is reconciled monthly by physical count, with variance commonly 5–9pp. With recipe-deduct, the system shows expected vs actual nightly; variance stays in ±2pp. On a 480M VND/mo specialty café, that is 14–34M VND/mo preserved. That is the entire monthly POS cost, paid for by one feature.
6. Aggregator unification: the silent killer
Three tabs (Grab Merchant, Shopee Partner, Be Merchant) + WhatsApp from runners is how 60% of independents still operate. The cost is not visible: it is the 86-list desync, the menu-price drift, the 4 missing orders/day, the 1.5–2.5 hours/day of admin. Unified ordering is a 6–14 hour/week labor recovery + 2–4% revenue recapture.
7. The 30-day evaluation playbook
Week 1: Demo top 3 vendors with your real menu loaded (force them to handle modifiers + Vietnamese names). Week 2: Pilot at 1 outlet, both peak and off-peak. Measure: order-to-kitchen time, KDS desync rate, aggregator order miss rate. Week 3: Recipe-load 80% of menu. Run a 7-day variance report. Week 4: Tally TCO including hidden adds. Decide.
Avoid: signing annual contracts before week-3 results. Most vendors will accept month-to-month for 6 months.
8. Common buyer mistakes
- Picking by UI screenshots, not by ops audit
- Skipping aggregator depth ("we'll sync later")
- Ignoring offline-first (one outage = one shift lost)
- Not testing on slow Wi-Fi
- Loading top SKUs only and never finishing recipe load
FAQ
Best POS for Vietnam F&B 2026? Depends on stage. Single-outlet kiosks: KiotViet or Sapo. Multi-outlet chains chasing margin: LOOP, iPOS, or Misa CukCuk. Hybrid bakery/retail: GoSell.
Is HĐĐT really mandatory from POS? For F&B above the revenue threshold, yes — and the audit risk grew sharply in 2025–26.
Recipe-deduct vs. periodic stock count? Both. Recipe-deduct gives daily signal; weekly physical count corrects drift.
Cheapest viable POS 2026? ~500K/mo software + 8M hardware for kiosk. Below that, you lose HĐĐT or aggregator depth.
Can I migrate POS mid-year? Yes, but only if recipes export cleanly. Test the export before signing.
Do I need KDS? Above ~150 covers/day or 2+ stations, yes. Below, ticket printers are fine.
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.