AI menu design: predicting your next best-seller before you launch it

2026 benchmark: Median food cost across SEA QSR chains: 30–34% in 2026.

The 60% failure rate nobody talks about

Most Vietnamese F&B chains launch 6–12 new menu items per year. Industry benchmarks (and quiet internal data from chains we've worked with) suggest 60–70% of them fail — defined as not reaching 3% of category revenue within 90 days and being delisted within 12 months.

The usual failure pattern:

1. The chef or owner has an idea
2. It tastes great in R&D
3. It goes on the menu with photos and a Zalo OA blast
4. Week 1 sales spike from curiosity
5. Week 4 sales drop 70%
6. Quietly removed at the next menu refresh

The waste isn't just R&D cost. It's opportunity cost — every failed launch took the slot of a potential winner.

The 3 signals that actually predict winners

AI menu design isn't about generating recipes (don't let a model invent your food). It's about scoring R&D candidates before launch using 3 signals:

1. Cross-sell pattern fit

For each candidate dish, look at its proposed category (e.g., "iced milk-based drink, ₫45–55k") and pull the historical basket data:

• What do customers who buy that category usually buy alongside?
• Does your existing menu have the right pair partners?
• A new dessert that pairs naturally with your top 3 drinks has 2–3x higher launch ceiling than one that doesn't.

2. Ingredient overlap with existing winners

Ingredients your kitchen already uses at high volume = better margin, faster prep, lower stockout risk. A model scores each candidate on:

• % of ingredients already in your top-20 SKUs
• Marginal SKU adds required
• Estimated COGS at current supplier prices

Winners usually overlap ≥70% with existing inventory. Below 50% overlap predicts both higher COGS and higher waste.

3. Search-trend lift (local)

Google Trends + Shopee Food / GrabFood search data, filtered to Vietnam and ideally your city, tell you whether the category is rising, flat, or falling. Launching a "matcha latte" in 2024 vs 2026 are very different decisions. The model weights candidates by 90-day trend slope.

The scoring rubric

For each of N candidates, compute a 0–100 score:

score = 0.35 × cross_sell_fit
      + 0.30 × ingredient_overlap
      + 0.25 × trend_lift
      + 0.10 × margin_index

Then rank. In practice, the top 1–2 candidates out of 8 are usually clear winners; positions 3–5 are coin flips; 6–8 should be killed before they cost you photo-shoot money.

Real case: bánh mì + drinks chain, 6 outlets

A bánh mì + bottled-drink chain (6 outlets, ₫4.2B/month combined) ran 5 R&D rounds of 8 candidates each in 2024–2025 using gut feel + chef preference. Hit rate: 6 winners out of 40 launches (15%).

In 2026 they rebuilt R&D selection around the 3-signal scorer (built into their POS analytics layer):

Round 6, May 2026

• 8 candidates → top 5 launched (scores 71, 68, 65, 58, 54)
• Killed 3 below 50 (one was the founder's favorite — hardest meeting of the quarter)

60 days later

• 4 of 5 hit ≥5% of category revenue (true winners)
• 1 missed at 2.8% (delisted at month 4)
• Hit rate: 80% (vs 15% historical)
• Combined incremental revenue from 4 winners: +₫340M/month within 90 days

What this approach can't replace

• Tasting. The model can't tell you if it's delicious.
• Local cultural context. A model trained on national data missed that one outlet (in a Korean-heavy neighborhood) needed a kimchi variant.
• Brand fit. If a high-scoring candidate doesn't feel like your brand, kill it. Scores are inputs, not orders.

How to start without a data team

1. Export 6 months of basket data from your POS. You need order-line resolution, not just daily totals.
2. List your top 20 ingredients by purchase volume in ₫.
3. Pull Google Trends (free) for the category names of your 8 candidates — Vietnam, last 12 months.
4. Score manually in a spreadsheet using the rubric above. The math is simple; the discipline of scoring before the launch decision is what matters.
5. Track outcomes for 4 quarters and tune the weights to your business. By year 2 your hit rate should be 2–3x the industry baseline.

The goal isn't to remove the chef. It's to give the chef better odds than a coin flip.

Related reading

• AI A/B Menu Pricing: Test Prices Per Outlet Without Spreadsheets
• AI A/B testing menu prices by branch — no Excel needed
• AI demand forecasting for Tet and peak season in F&B

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.

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 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

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, 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.

Related guides

• LOOP blog — AI POS guides for SEA
• LOOP POS
• Peko Rewards loyalty
• VeLoop delivery aggregator unification
• LOOP pricing
• Compare LOOP vs other POS

FAQ

How fast can a SEA F&B chain switch to LOOP?

Typical cutover for 2–10 outlets is 5–10 business days: CSV import of menu, recipes, customers, loyalty and 24 months of sales, parallel run over a weekend, then cut over Monday open. Larger chains (20+ outlets) usually phase by region over 4–6 weeks.

Does LOOP work without stable internet?

Yes — LOOP runs offline-first with a 90-second resync window. Orders, payments and KDS keep firing during ISP drops; the cloud reconciles automatically on reconnect. Aggregator orders queue locally and dispatch when the link returns.

What does LOOP cost?

Per-outlet monthly pricing with no per-device upcharge. Peko loyalty customers get 50% lifetime discount on LOOP — see /pricing for the current band.

Does LOOP support VAT e-invoice (TT78)?

Yes — LOOP integrates with MISA, Viettel and VNPT as e-invoice providers. Issuance is automatic at order close and reconciles end-of-day.

Which payment rails does LOOP support?

Native: VietQR, MoMo, ZaloPay, VNPay for Vietnam; PromptPay (TH), QRIS (ID), DuitNow (MY), PayNow (SG), QR Ph (PH). Card acquirers are wired through local PSPs per country.