What's the maximum number of outlets LOOP supports?

There is no hard cap. The largest LOOP chain runs 90+ outlets across 3 countries on the Business tier.

Can different outlets have different menus?

Yes. One master menu with per-outlet visibility toggles and pricing zones. Outlets can also have local-only items that don't show on the master.

How fast does the roll-up dashboard refresh?

Every minute for revenue and cover counts; every 5 minutes for inventory and labour percentages.

What happens if HQ internet goes down?

Outlets keep running normally on their local offline cache. Once HQ comes back online, all transactions sync and the dashboard catches up automatically.

Does LOOP support franchise vs. owned outlets differently?

Yes. Franchisees see only their outlet's data; HQ sees everything. Royalty calculations can run automatically on a defined % of revenue.

How is per-outlet pricing handled at month-end?

Each outlet's pricing zone flows into its P&L automatically. The consolidated report shows blended ASP per region.

F&B segment

Going from 1 outlet to 5 is not a 5x scale — it's a different business. LOOP gives chains the four things that decide profitability: central recipe control, daily P&L per outlet, real-time consolidation, and AI forecasting per location.

POS for F&B Chains — Real-Time Multi-Outlet Visibility

Last updated: May 21, 2026

What we hear from operators

Recipe drift: outlet B uses 15g cheese, outlet C uses 22g — and neither HQ nor cost knows.
Daily numbers from outlets arrive 24–48 hours late in spreadsheets that don't reconcile.
Central kitchen transfers vanish between 'sent' and 'received', with no audit trail.
Aggregator menus drift per outlet — same dish, three prices, two photos, one missing modifier.

Why LOOP fits this segment

Central recipe authority — change a recipe at HQ, every outlet uses the new version on next shift, with audit trail.
Real-time roll-up dashboard: revenue, cover count, food cost % per outlet, refreshing every minute.
Central kitchen module with signed transfer receipts and variance reports on arrival.
Aggregator menu sync: edit once, push to GrabFood / ShopeeFood / Be across all outlets in one action.

What you get

Role-based access: HQ, regional manager, outlet manager, shift lead, cashier.
Per-outlet pricing zones (mall vs. street vs. delivery) with one master menu.
AI demand forecast per outlet, per SKU, per hour.
Cross-outlet inventory transfers with one-tap approval.
Consolidated VAT / HĐĐT report for the chain's accounting team.

In-depth analysis

The chain economics most POS vendors won't show you

A 6-outlet F&B chain in Vietnam typically runs 14–22 devices: tablets, KDS screens, label printers, kitchen printers. On per-device pricing (iPOS, some KiotViet F&B plans), the monthly bill grows linearly with device count, not outlet count. At 18 devices × ~₫350K/device/month, that's ~₫6.3M/month — before modules. LOOP charges ₫999K/outlet/month on Business (unlimited devices). Six outlets = ₫5.99M flat, AI forecasting included, central-kitchen module included. The crossover isn't subtle: per-device beats per-outlet only when devices per outlet stay under 1.5, which essentially never happens in chains running KDS + label printing.

Central kitchen, commissary, and the inter-outlet transfer problem

Chains crossing 4 outlets usually centralise prep — a commissary that produces sauces, marinades, par-cooked proteins, dessert bases — and ships to outlets daily. The accounting question is: when 8 kg of marinated chicken leaves the commissary for Outlet 3, who owns the COGS until it sells? Most VN POS systems either ignore inter-outlet transfers (KiotViet) or model them as outbound invoices that double-count for tax (some iPOS configurations). LOOP treats the commissary as a virtual outlet with its own recipe tree: commissary output is parent SKUs, outlet sales deduct against the parent. Variance is visible per leg — production loss at the commissary, transit shrinkage, outlet-level prep loss. Chains doing ₫50M/day discover ~₫1–2M/day of previously invisible loss in the first month.

Why chain HQs end up running two reports — and how to stop

Operations directors at chains running 5+ outlets almost always maintain a parallel Excel layer. The POS produces a sales report; the director rebuilds it because the POS report lacks daypart breakdown, weather-adjusted comps, or staff-cost overlay. This parallel layer eats 6–10 hours of finance team time per week. LOOP's reporting layer is designed around the questions ops directors actually ask: 'what's the YoY same-store comp, weather-adjusted, excluding outlet 7 which moved?' is a single query. The reason isn't engineering brilliance — it's that we shipped the schema with these queries as first-class, not as an afterthought.

When LOOP is the wrong fit for your chain

Two cases: (1) Chains where the franchisor-mandated POS is non-negotiable — even when LOOP would save you money, you usually can't unilaterally switch. (2) Chains that have already invested in deep custom integrations (ERP, fiscal printer middleware) on an existing platform within the last 18 months — the sunk-cost math sometimes doesn't favour migration even when LOOP is the better steady-state fit. We tell prospects this directly during sales calls.

Operator economics (2026)

Devices per outlet (median, chains)	2.4–3.7	Tablets + KDS + label printer + kitchen printer in typical F&B chain configs.
Per-device pricing crossover	Outlet 2 or device 3	Beyond either threshold, per-outlet flat (LOOP) beats per-device decisively.
Invisible commissary loss discovered (median)	2–4% of food cost	First 30 days on LOOP for chains migrating from per-SKU systems. As-of 2026-05.
Finance-team hours saved/week	6–10 hrs	From killing the parallel Excel layer; based on 24 chain customers surveyed Q1 2026.

Migration playbook

01
Pilot one outlet for 14 days
Pick the outlet with the most experienced manager, not the highest revenue. We want the cleanest signal on operational fit, not the largest financial blast radius.
02
Wire central kitchen / commissary
If you have one. We model it as a virtual outlet with its own recipe tree. Daily transfer schedule is loaded as recurring picks. Tax treatment is configured with your accountant in the loop.
03
Roll out outlet-by-outlet
One outlet per week is the default cadence. Each outlet gets 2 hours of on-site training plus 7 days of remote office-hours from our onboarding team. Faster than that, training quality degrades.
04
Migrate historical data
We import 24 months of historical sales for YoY comp continuity. Inventory history transfers as opening balances, not item-level movements — there's no schema that makes that mapping clean across vendors.
05
Decommission legacy stack
Day 60–90, depending on chain size. Legacy stack stays read-only for 12 months for audit. We do not recommend a hard cutover before parallel reconciliation is clean.

Which plan, by persona

3–6 outlet chain, no central kitchen yet
LOOP Growth. The savings vs per-device pricing alone justify the switch; the AI forecasting and aggregator normalisation are gravy.
7+ outlets with commissary or central kitchen
LOOP Business. The commissary-as-virtual-outlet model is the deciding factor; nothing else in the VN market handles inter-outlet transfers with this clarity.
Master franchisee with brand-mandated POS
Don't fight the brand. If the mandated POS is failing you, escalate to the franchisor with documented operational data, not a unilateral switch.

Deeper questions

Can LOOP roll out to all my outlets in one weekend?: Technically yes; operationally we strongly advise against it. One outlet per week is the cadence that produces clean training and zero post-migration support tickets. Big-bang migrations look fast on paper and cost 3× more in remediation.
How does LOOP handle franchise royalty calculations?: Royalty rules are configurable per outlet (flat %, tiered by revenue band, or per-transaction). Reports export in formats accepted by major Vietnamese F&B franchisors. Custom rules can be added by our onboarding team.
Does LOOP integrate with our existing accounting software (MISA, Bravo, Fast)?: Yes for MISA (native), CSV/Excel export for Bravo and Fast tuned to their import templates. Direct API integrations are on the roadmap for Q3 2026.

Pricing built for chains

Flat per-outlet pricing, unlimited devices per outlet. Free for a single outlet. Growth and Business tiers add multi-outlet sync, AI forecasting and central-kitchen control.

See pricing

Evaluating alternatives? See LOOP vs POS365 or all comparisons.

Frequently asked

What's the maximum number of outlets LOOP supports?: There is no hard cap. The largest LOOP chain runs 90+ outlets across 3 countries on the Business tier.
Can different outlets have different menus?: Yes. One master menu with per-outlet visibility toggles and pricing zones. Outlets can also have local-only items that don't show on the master.
How fast does the roll-up dashboard refresh?: Every minute for revenue and cover counts; every 5 minutes for inventory and labour percentages.
What happens if HQ internet goes down?: Outlets keep running normally on their local offline cache. Once HQ comes back online, all transactions sync and the dashboard catches up automatically.
Does LOOP support franchise vs. owned outlets differently?: Yes. Franchisees see only their outlet's data; HQ sees everything. Royalty calculations can run automatically on a defined % of revenue.
How is per-outlet pricing handled at month-end?: Each outlet's pricing zone flows into its P&L automatically. The consolidated report shows blended ASP per region.

Book a 20-minute walkthrough

We'll map your current stack to LOOP, show you the AI forecast for a real outlet, and answer pricing and migration questions on the call.