# One scan, every stall, one bill.

> A food court only works if the guest journey feels like one place, not twenty separate queues. Papaya lets a table order from every vendor on a single QR, settle one combined bill, and pays each stall out automatically — so guests eat sooner and operators stop running cash between counters.

`One QR across stalls` · `One combined bill` · `Auto split payouts`

## At a glance

- **One QR, every stall** — Guests browse all vendors in one menu
- **Split payouts** — Each stall paid its own share, daily
- **One combined bill** — PromptPay or card, pay once for the table
- **Per-stall tickets** — Each stall sees only its own orders

## Three frictions every food court lives with — solved.

A hungry table shouldn’t have to queue at four counters, juggle four receipts, and wait for four cooks who can’t see each other. Papaya stitches independent vendors into one journey while keeping every stall’s money straight.

- **A queue at every stall** — A group of four wants noodles, rice, salad and drinks — that’s four separate lines and four people guarding a table. Half the visit is spent standing, not eating.
  - Fix — **Order every stall from the table**: One QR opens a menu spanning all vendors. The table builds a single order across stalls and never leaves their seats.
- **Four stalls, four bills** — Settling means visiting each counter, paying separately, and hoping the maths adds up before the table turns over.
  - Fix — **One combined bill, settled once**: Everything the table ordered lands on a single bill. They pay once by PromptPay or card, and the court reconciles the rest.
- **Cash chased between counters** — With independent vendors under one roof, working out who earned what — and paying each fairly — is a nightly spreadsheet headache.
  - Fix — **Centralised settlement, automatic payouts**: Takings are collected centrally and split to each vendor by what they actually sold, with a clear statement per stall.

## The parts of Papaya a food court leans on.

- **One menu across every vendor.**: A single QR at the table opens a menu that spans every stall in the court. The guest orders noodles, rice and drinks in one basket; each vendor receives only its own items.
  - Browse and order from all stalls in one basket
  - Items route to the right vendor’s screen automatically
  - Sell-outs grey out the moment a stall runs low
- **One bill the whole table pays once.**: No counter-hopping to settle. The table pays a single combined bill by PromptPay or card, and Papaya splits the money to each vendor behind the scenes.
  - One combined bill across every stall ordered from
  - PromptPay and card, paid from the table
  - Automatic split payouts with a statement per vendor
- **A till per stall, a view for the court.**: Each vendor runs its own counter, menu and ticket queue, while the operator sees the whole court live — open tables, ticket times and takings across every stall.
  - Independent till and menu for each vendor
  - Per-stall ticket queue shows only its own orders
  - Court-wide dashboard of orders, prep times and sales

## More baskets, fewer queues.

- **+22%** — average basket once a table can order across every stall
- **3 stalls** — the typical number a single table orders from in one sitting
- **~50s** — to settle a multi-stall table on one combined bill
- **T+1** — vendor payouts split and settled by the next day

_Aggregate figures from Papaya food court and food hall venues; results vary by venue._

> "Guests used to queue at three counters and pay three times — most never made it back for dessert. Now one table scans once, orders from every stall, and pays a single bill. At close, each vendor’s payout is already worked out for them."
> — Operations manager, Food hall · Bangkok

## Good to know

The things every food court operator asks before signing up vendors.

**How does the money reach each vendor?**

Takings are collected centrally on the combined bill, then split to each vendor by exactly what they sold. Payouts and a per-stall statement go out on your settlement schedule — typically next day. You set the cycle and any commission the court takes.

**Do vendors keep their own menus and prices?**

Yes. Each stall runs its own menu, prices and stock independently from its own till, and edits flow straight through to the shared guest menu. The court layer sits on top — it doesn’t flatten vendors into one kitchen.

**What if a vendor already uses their own POS or cash?**

They can still join the shared QR menu and combined bill, with their items routed to a printed ticket or a screen. You lose the live court dashboard for that stall until they move onto Papaya POS, but onboarding is gradual — you don’t need every vendor on day one.

**Can guests still order from just one stall if they want?**

Of course. The single QR is the default for a shared table, but a guest can order from one vendor and pay only for that. Combined billing is an option the table opts into, not something forced on every order.

**What happens when one stall sells out or closes early?**

That vendor’s items grey out across the shared menu the moment stock hits zero or the stall closes for the day, so guests never order something that can’t be made. The rest of the court keeps trading normally.

## One court, one journey.

Bring every vendor under a single QR, one combined bill and automatic payouts. Start with the stalls you have, add the rest as they’re ready.

---

Source: https://www.papaya.co.th/solutions/food-courts