A restaurant is not a shop with chairs. Orders change mid-flight, the kitchen and counter must speak the same language, recipes decide whether a dish makes money, and dinner rush punishes any slow screen. MrPOS RMS is built around that reality, this tour walks the product the way a service walks a Saturday night: from the door, to the waiter, to the kitchen, to the bill, to the owner's report.

The counter: three service modes, one screen
Every order starts by choosing Dine-In, Takeaway or Delivery. The screen adapts: tables for dine-in, rider/customer fields for delivery, token numbers for takeaway. Nothing to switch, nothing to reinstall at lunch versus dinner. Bills print per mode with the fields each one needs (table number, token, address).
Tables, waiters and the floor plan
The floor plan shows every table's state at a glance: free, occupied, billed, merged. Waiters log in with their own PIN, so every order carries a name and per-waiter sales are reportable. Merge and split tables take two taps, and the running bill is always visible before the guest asks for it.
KDS: the kitchen stops reading paper
When the waiter confirms an order, it appears instantly on the kitchen display screen: itemized, timed, color-coded by waiting age. No handwritten chits, no "kitchen never got table 7's order". The kitchen marks items ready and the counter sees it live. Rush-hour visibility alone typically removes the most common service complaint: the lost or delayed ticket.
Recipes: the difference between sales and profit
The silent killer of restaurant margins is the dish that sells fast and loses money. RMS links every menu item to its ingredient recipe, one plate of chicken karahi deducts the real grams of chicken, oil, masala and packaging from stock. Now dish-level cost is a report, not an estimate, portioning drift shows up as rising food cost percentage, and procurement becomes math instead of memory. This is the feature that pays for the software; our RMS product page shows recipe support as a core requirement for exactly this reason.
Modifiers without friction
"Less spicy", "no onion", "extra raita +PKR 50": modifiers live on the item, required ones force a choice, priced ones add automatically. The kitchen sees them on KDS; the bill prices them without a manual edit. Modifier mistakes are the #1 cause of returned plates in manual systems, this is where that stops.
Split, merge and settle, the end-of-meal moments
| Moment | What RMS does | What breaks without it |
|---|---|---|
| Group wants separate bills | Split by item or equal parts in two taps | Manual math while the table waits |
| Two tables together | Merge bills, one payment or split at settle | Two receipts, one angry reconciliation |
| Half card, half cash | Mixed payment on one bill | Manual notes, end-day mismatches |
| Guest pays part now, rest later | Partial settlement tracked on the bill | Memory-based balances that argue |
Delivery orders without a second system
Phone and WhatsApp orders land in the same queue with rider and address fields; if you list on delivery platforms, order slips are entered by counter staff and reportable side-by-side with dine-in. One kitchen queue, one revenue report, no app-jumping at rush hour.
The reports a restaurant actually opens
- Hourly sales load: when to schedule staff and prep, from your own data not folklore.
- Dish-level profit: selling price minus real recipe cost, per item, per period.
- Per-waiter and per-shift performance: sales, voids, discounts by name.
- Wastage and food-cost drift: the recipe engine flags items whose cost share is climbing.
- Slow movers: the menu items that occupy your kitchen but not your cash.
What runs behind it
RMS shares the platform with MrPOS Retail and MrPOS ERP: same offline billing, same stock engine, same credit ledger for regulars, same WhatsApp marketing for offers and events, and the same PKR 5,000/month plan (or PKR 30,000 lifetime). If you run a bakery corner or retail shelf alongside the restaurant, it is one system, not three.
Frequently asked questions
What hardware does a restaurant need for RMS?
Counter PC or tablet + thermal printer; a KDS screen (or an old TV with a stick) for the kitchen; optional waiter handhelds. A single-counter café can start without KDS and add it later.
Does RMS work during internet outages?
Yes: billing and kitchen flow continue offline and sync when the network returns. Rush hour never waits for the router.
Can I track food cost per dish?
Yes: recipes link ingredients to menu items, so every sale deducts real quantities and dish-level cost and margin are reportable, including portion-drift detection.
Can waiters take orders on their own phones?
RMS supports handheld/tablet ordering with waiter PINs. Personal phones are not recommended for hygiene and accountability reasons: dedicated inexpensive tablets work best.
How is RMS priced vs the retail edition?
Same platform pricing: PKR 5,000/month or PKR 30,000 lifetime (~$108). Restaurant features (tables, KDS, recipes, modifiers) are included, not add-ons.
Next step: see it on your own data
MrPOS offers a free live demo (no card required): setup typically completes in one day, including data import. WhatsApp us at 0316 6132742 or message us for a free demo.
Explore the products: MrPOS ERP · MrPOS Retail · MrPOS RMS, or use the Your Number calculator to estimate how much your current setup is leaking.