AI menu engineering: how data picks your next bestseller
By LOOP Editorial
Last updated:
AI menu engineering: how data picks your next bestseller
Menu engineering used to be a quarterly meeting with a chef, a finance person, and a spreadsheet. AI did not replace that meeting — it made it ten times sharper, because the data finally fits the question.
2026 benchmark: Median food cost across SEA QSR chains: 30–34% in 2026.
What menu engineering really is
Menu engineering is the discipline of classifying every item by two axes: popularity (units sold) and contribution margin (gross profit per unit). The classic 2x2:
- Stars: high popularity, high margin. Protect and promote.
- Plowhorses: high popularity, low margin. Re-engineer the cost or reposition.
- Puzzles: low popularity, high margin. Reposition on the menu or kill.
- Dogs: low popularity, low margin. Kill.
Easy in theory. In practice, most operators do this once a year with stale COGS data and gut feel about popularity. AI fixes both inputs.
How AI sharpens the inputs
Real-time COGS
LOOP joins live supplier invoices to recipe data, so contribution margin updates the moment a beef price changes. The chef sees that her wagyu bowl dropped from a 62% margin to 51% the day the new shipment hits. No spreadsheet involved.
Popularity weighted by branch and daypart
A bowl that is a star at lunch downtown can be a dog at dinner in the suburbs. AI segments by branch × daypart × day-of-week before classifying. This is the single biggest improvement over traditional menu engineering.
Substitution awareness
If you kill a popular plowhorse, customers will substitute. AI estimates the substitution matrix from order co-occurrence — so it can tell you "if you cut the chicken rice, 38% will substitute beef rice (higher margin), 22% will leave."
Toast''s industry data shows operators using data-driven menu engineering grow same-store gross margin 4-7% in the first year. See also Square''s menu optimization guide for the operational playbook.
A real example: a 9-location pho chain
We ran LOOP''s menu analyzer on a 9-location pho chain in HCMC. The 2x2 surfaced surprises:
- Star to puzzle: their "signature beef pho" was a star in 7 branches but a dog in 2 (both near competitors with cheaper beef pho). Recommendation: localize price, not menu.
- Plowhorse: a chicken pho with a 41% margin (vs. chain average 58%). Root cause: a sauce ingredient cost had crept up 22% in 6 months without a menu price change. Fix: 8% price increase. Result: margin recovered, units dropped 4% (well within the elasticity estimate).
- Puzzle: a premium oxtail dish at 71% margin selling 6 units/day. AI suggested moving it from page 3 to page 1 of the menu. Units rose to 18/day in 30 days, no price change.
- Dog: a vegetarian pho selling 2/day at 38% margin. Killed. Substitution model predicted (correctly) that 60% of customers would switch to a different pho.
Net impact: 5.8% margin lift on the food P&L in one quarter.
What to look for in an AI menu feature
- Live COGS feed. Static recipe costs are useless.
- Branch × daypart segmentation. Aggregate menus hide everything that matters.
- Substitution matrix. Killing items without modeling substitution is dangerous.
- Price elasticity per SKU. Lets you test price changes without flying blind.
- A/B testing on the live menu. The QR menu makes this trivial — different prices to different cohorts.
How LOOP does it
LOOP refreshes the menu engineering 2x2 nightly. Operators see four lists ("kill these, raise price on these, promote these, leave alone") rather than a chart. A weekly digest highlights changes vs. last week. Chefs can override any recommendation with a one-tap "keep as is" — the model learns from the override.
FAQ
How much data do I need? 30 days minimum for the popularity model, 90 days for the substitution model.
What about seasonal items? The model excludes items with <30 days of history from the kill list, and tags seasonal items so they aren''t classified as dogs in the off-season.
Can it suggest new items? Yes, using ingredient co-occurrence + adjacent menus. Quality varies; we treat these as brainstorm inputs, not commitments.
Does it work with set menus / combos? Yes — combos are decomposed into their components for margin analysis, then reassembled.
Related reading
- AI A/B testing menu prices by branch — no Excel needed
- AI demand forecasting for Tet and peak season in F&B
- AI fraud detection at the POS: voids, refunds, ghost orders
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.