Your floor plan with every table's live state, reservations with notes and conflict checks, staff POS and customer QR ordering into the same tab, a kitchen display grouped by table — and bills that add service charge and GST as your restaurant sets them.
A concept — nothing is running at a restaurant yet, and we say so. The ordering, kitchen-ticket and payment-confirmation patterns underneath run daily at our own F&B stall. The demo is fully simulated.
Booking by phone or your own link, with pax and notes — "birthday, cake at 9". Conflict checks stop double-booking a table or overfilling a slot; a full slot offers the waitlist.
SIMULATEDThe floor plan shows every table's state — free, reserved, seated, ordering, served, billing. Seat the booking, slot walk-ins into true gaps, and never guess what's open.
SIMULATEDStaff key the order on a tablet at the table — zi char modifiers and all. Customers can also scan the table QR and add dishes themselves; both channels land on the same tab.
SIMULATEDThe kitchen display groups tickets by table in firing order — never a payment screen, never a mixed-up chit. Mark dishes served and the floor plan knows.
SIMULATEDOne bill per table with service charge and GST added as your restaurant sets them. PayNow goes straight to the restaurant's own bank — simulated in the demo, direct in real life. Close the table and the floor resets for the next guests.
SIMULATEDEnglish and Chinese on the same menu — staff screen, customer QR and reservations alike. The demo runs a fictional zi char kitchen, Lilian's Kitchen 莉莲餐厅.
Less oil 少油, no spring onion 不要葱, extra rice 加饭 — plain-word modifiers that reach the kitchen exactly as spoken, priced as you set them.
Payments go straight into the restaurant's own bank account. We never hold your money and take no commission — on covers, orders or regulars.
One bill per table with service charge and GST added as your restaurant sets them — labelled exactly that way in the demo. No commission on top, ever.
Any Android phone or tablet you already own — floor plan on one, staff POS on another, kitchen display on a third. No terminals to rent, no lock-in.
Your booking link is yours, your customers stay yours, your floor stays yours. We're the system behind the counter — not a channel in front of it.
The ordering, kitchen-ticket and payment-confirmation patterns underneath run at our own 4 MEE F&B stall daily since Sep 2026 — a second trilingual menu (Thai kitchen, pre-opening) runs the same engine. Real orders, real days, real closing numbers.
The restaurant layer — floor plan with live table states, conflict-checked reservations, staff POS + QR ordering on one tab, kitchen display, service-charge bills — is fully clickable in the demo with dummy data, and deployed nowhere yet. We build it with our first restaurant partners.
Planned, not promised: reservation deposits and no-show fees, WhatsApp confirmation reminders, delivery-platform sync, printed chits. We label them exactly that way in the demo too.
A small number of founding restaurants and bistros. We map your real floor — tables, rooms, second storey — build your bilingual menu with the zi char modifiers you actually use, configure bills to your service charge and GST, and stand with you on day one. Real weeks decide: covers served, booking conflicts caught, closing numbers trusted.
Pricing is discussed, not published — the first conversation sizes it honestly for your restaurant, with no surprises.
Not on day one. Reservations and QR ordering can run first alongside what works for you; the full suite replaces a system only when it has earned it. We shape this around your floor, not a checklist.
Honestly: planned, not built. Deposits at booking and no-show fees are labelled "planned" in the demo — today it shows conflict-checked bookings without deposits, and we won't promise more until it exists.
Yes — the floor plan is drawn around your real floor, rooms included. The demo shows one floor of twelve tables as the concept; your installation would use your actual layout.
Any cheap Android phone or tablet you already own. Floor plan, staff POS and kitchen display are just screens on the same system — no terminals to rent, no special hardware.
Bills add them the way your restaurant sets them — configurable and labelled "as set by the restaurant" in the demo. Try changing them yourself in the bill view.
Honestly: no. The engine underneath runs daily at our own F&B stall; the restaurant suite is the interactive concept we'd build first. That's why everything here links to a labelled simulation.
StallPOS by Madam Chin Kitchen Pte Ltd · UEN 202637886D · 5058 Coffee Shop, Singapore — this page describes a concept; every restaurant screen shown is a labelled simulation.