Can each vendor have its own tax code on receipts?

Yes. Each vendor's HĐĐT is issued under their own MST. The centre operator's commission is a separate invoice from operator to vendor.

What if a vendor wants their own POS too?

They can run their own LOOP outlet account and link it to the food court. Settlement still flows through the central till.

How are refunds handled across vendors?

A refund at the till deducts from the next day's settlement to the relevant vendor. The operator sees a unified refund log.

Do customers pay each vendor or pay once?

Once, at the central till — for cash, card, QR or Momo. Splitting to vendors happens entirely server-side.

Can we run a food court loyalty programme?

Yes. Points are earned and redeemed across all vendors. The centre operator funds the discount and recovers it via vendor billing.

What hardware do food courts typically need?

One central till tablet + thermal printer, one tablet per vendor station (for KDS), and a buzzer system if customer wait > 5 min.

F&B segment

Food courts have one queue and many kitchens. LOOP gives the centre operator a single till that routes to each vendor's kitchen, then settles by transfer at end of day — minus the operator's commission, transparent to every vendor.

POS for Food Courts — Multi-Vendor Settlement on One System

Last updated: May 21, 2026

What we hear from operators

Five vendors, five tablets, five payment slips at the customer's table.
Daily settlement is a manual reconciliation across cash, card, QR and Momo per vendor.
Commission disputes when the operator's number doesn't match the vendor's count.
Loyalty doesn't work across vendors — each runs a different programme.

Why LOOP fits this segment

Central till orders for all vendors in one transaction, splits to per-vendor KDS in the background.
Single payment from the customer; LOOP allocates revenue per vendor and queues settlement.
Per-vendor commission rules (flat or %) applied automatically with daily statement PDF.
Food court-wide loyalty — points earned at any vendor, redeemable at any vendor.

What you get

Buzzer / pager integration so customers leave the till and get notified per dish.
Per-vendor performance dashboard (revenue, items, prep time).
Operator's commission report with auto-generated bank transfer file.
Shared loyalty membership QR working in Zalo Mini App.
Per-vendor HĐĐT issued under each vendor's tax code, not the operator's.

In-depth analysis

Central cashier vs per-stall POS — the structural choice

VN food courts split into two operating models: central cashier (Vincom, AEON style — customer orders at counter, pays once, food comes from multiple stalls) and per-stall POS (older market food courts). LOOP supports both natively. Central cashier mode: each stall is a virtual outlet, KDS at the stall fires only its lines, central cashier sees a consolidated check. Per-stall mode: each tenant gets a separate LOOP instance with court-level revenue-share reporting for the landlord. Most VN POS vendors force one model or the other; we ship both.

Landlord revenue share — the trust problem

Food court tenants pay landlords either flat rent or revenue-share (typically 8–15%). Revenue-share creates a perennial trust gap: tenants under-report cash sales, landlords distrust totals, monthly reconciliation eats hours. LOOP's landlord portal gives the mall operator read-only access to summary numbers per tenant per day — no individual transaction PII, just totals — eliminating the dispute. Tenants accept it because the alternative is daily cash audits.

When LOOP isn't right for your food court

Wet-market style food courts where most tenants are cash-only with no inventory tracking — LOOP's depth is wasted; basic per-stall solutions are sufficient.

Operator economics (2026)

Reconciliation hours/month (revenue-share)	12–20 hrs → 1–2 hrs	Landlord finance team, mid-size court (12–20 tenants).
Central-cashier wait time	3–5 min → 45–90s	Multi-stall consolidated check vs serial per-stall payment.

Migration playbook

01
Choose operating model + onboard tenants
Central cashier or per-stall. Tenant onboarding cadence: 2 stalls/week.
02
Configure revenue-share rules
Per-tenant % + landlord portal access scope.
03
Deploy KDS at stalls + central display
Order number callback display for central-cashier mode. One KDS per stall.

Which plan, by persona

Mall food court operator (landlord)
LOOP Business with landlord portal. The reconciliation savings + tenant retention from trust improvements justify it 5×.
Individual stall tenant in food court
LOOP Free or Growth depending on volume. The court's KDS infrastructure makes onboarding faster than a standalone outlet.

Deeper questions

Does the landlord portal expose tenant transaction details?: No. Landlords see daily totals per tenant for revenue-share calculation. Individual transactions, customer PII, and item-level mix stay with the tenant.

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

Can each vendor have its own tax code on receipts?: Yes. Each vendor's HĐĐT is issued under their own MST. The centre operator's commission is a separate invoice from operator to vendor.
What if a vendor wants their own POS too?: They can run their own LOOP outlet account and link it to the food court. Settlement still flows through the central till.
How are refunds handled across vendors?: A refund at the till deducts from the next day's settlement to the relevant vendor. The operator sees a unified refund log.
Do customers pay each vendor or pay once?: Once, at the central till — for cash, card, QR or Momo. Splitting to vendors happens entirely server-side.
Can we run a food court loyalty programme?: Yes. Points are earned and redeemed across all vendors. The centre operator funds the discount and recovers it via vendor billing.
What hardware do food courts typically need?: One central till tablet + thermal printer, one tablet per vendor station (for KDS), and a buzzer system if customer wait > 5 min.

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.