Walking, not serving
Every order means a trip to the counter and back. On a full evening that is most of the shift spent crossing the floor.
Fixed. The order, the bill and the payment all happen at the table.
Live on Google Play
Your floor staff stop walking back to the counter
RPOS Captain puts table service on one phone. Waiters take the order at the table, raise the bill, and confirm payment where the guest is sitting — not at a terminal across the room.
- Free to install
- No ads, no tracking
- Android 7.0 and up
10Ordering languages
60 secTo undo an order
7Table statuses tracked
Table 1 running3 orders · 3 done
Payment verifiedUPI · ₹1,250
Table 3 seatedMenu opened
Order sent to kitchenEven offline
HTTPS onlyPlain HTTP is blocked
Keystore tokensNever backed up
Zero trackingNo ads, no analytics
Role permissionsSet in the web app
The floor, honestly
Four things that slow a busy restaurant down
None of them are the staff's fault. They are what happens when the only place to enter an order is a machine at the counter.
The wrong dish, already cooking
One mis-tapped item and somebody is in the kitchen apologising to the chef while the guest waits.
Fixed. Sixty seconds to pull the order back and edit it before the kitchen sees it.
Orders that quietly vanish
The Wi-Fi drops for a second, the phone locks, the shift ends — and an order nobody remembers taking never reaches the kitchen.
Fixed. A confirmed order still reaches the kitchen through all four of those.
Closing totals that do not tally
A guest says cash, pays by UPI, and nobody corrects it. The day's figures drift and the difference is found a week later.
Fixed. Reception verifies every payment and can correct the method before the table closes.
Everything on the floor
Built for the person holding the phone
Sixteen things your staff can do without leaving the guest's table. Search to find one.
Live table view
Every floor and area at a glance. Tables read free, occupied, ready to serve, awaiting payment, cleaning or blocked — so staff know where to go next without asking anyone.
Orders in ten languages
Browse the live menu by category with current prices. The screen reads in English, हिंदी, ગુજરાતી, मराठी, தமிழ், తెలుగు, ಕನ್ನಡ, മലയാളം, বাংলা and ਪੰਜਾਬੀ.
A 60-second undo
Confirmed the wrong item or quantity? Pull the order back and edit it within a minute, before it reaches the kitchen. Nobody has to chase the chef.
Orders that do not get lost
Phone locked, app in the background, shift ended in a sign-out, Wi-Fi dropped — a confirmed order still reaches the kitchen. A guest never waits on an order that vanished.
Running tabs
Guests keep ordering after the bill is raised. Everything stays on one growing tab and is paid once at the end, with every line item, quantity and total on screen.
Cash and UPI at the table
Show the restaurant's UPI QR code where the guest is sitting, or take cash. No walk to the counter to settle a bill.
Verified payments
Reception confirms each payment before the table closes, and can correct the method if a guest said cash but paid by UPI — so daily closing totals stay accurate.
Reservations
Check the day's table reservations, with guests still expected listed ahead of those who have already left.
Seat a guest in seconds
Assign the guest to a table and the session opens right away, so you can order for them immediately. Company name and GSTIN are there when the bill needs them.
Move a party, move everything
Shift guests to another table and their whole session goes with them — orders, bill and payments. Nothing is re-entered.
Table housekeeping
Mark a table for cleaning, block it while a leg is being fixed, or clear its status — all from the floor plan.
Permissions that match the web app
Each staff member sees only what Access Control granted them. Owners get everything; a waiter can be limited to taking orders without touching payment verification.
Menu preview
Open the live menu without starting an order, when a guest asks what is available today and at what price.
Repeat an order
A table asks for the same round again. One tap sends it, instead of rebuilding the order item by item.
One database with the web app
Sign in with your restaurant's tenant code and every table, order and payment stays in step with what the management team sees on the web.
Finish a table cleanly
Close the session once the bill is settled, and the table returns to the floor plan ready for the next party.
Nothing matched that. Try table, bill, UPI or language.
No English requirement
Your staff order in their own language
The ordering screen reads in ten. Nobody has to learn a menu in a second language before their first shift.
English
हिंदी
ગુજરાતી
मराठी
தமிழ்
తెలుగు
ಕನ್ನಡ
മലയാളം
বাংলা
ਪੰਜਾਬੀ
From install to first order
Five steps, one evening
1
Install on the staff phone
Free from Google Play, on any Android 7.0 or newer device. No extra hardware to buy.
2
Sign in with the tenant code
Your restaurant administrator gives each person their tenant code and staff login. That is what ties the phone to your restaurant.
3
The floor plan loads
Every floor, area and table appears with its live status. Nothing to set up in the app — it reads what the web platform already knows.
4
Seat a guest and take the order
Register the guest, the session opens, the menu opens with it. Confirm the order and it goes to the kitchen.
5
Raise the bill and settle
Show the UPI QR or take cash at the table. Reception verifies it, and the table closes clean.
Real screens
What your staff actually see
Screenshots from the shipped app, not mock-ups.
Manage tables, quick orders and live billing from one screen. Statuses tell staff where to go next.
Built for a busy floor
Guest bills do not travel in the clear
A restaurant's Wi-Fi is a shared network. Everything below is in the shipped app, not on a roadmap.
HTTPS, or nothing
Every request runs over HTTPS. Plain HTTP is blocked outright, so staff logins and guest bills are never sent in the clear.
Tokens in the Android Keystore
Your sign-in token is held by the operating system, never backed up to the cloud and never transferred to another device.
No ads, no analytics
No third-party tracking of any kind. Nothing about your restaurant is sold, shared or profiled.
Only what the role allows
Permissions come from Access Control in the web app. A waiter cannot reach payment verification unless you grant it.
Before you install
Straight answers
Do I need an RPOS account to use this app?
Yes. RPOS Captain is the staff companion to the RPOS restaurant platform. Ask your restaurant administrator for your tenant code and staff login. It is a tool for restaurant staff — not a table-booking app for diners.
Can a waiter fix an order after confirming it?
Yes — there is a 60-second window to pull the order back and edit it before it reaches the kitchen. After that the kitchen has it, and a correction goes through the usual channel.
What happens if the Wi-Fi drops mid-order?
A confirmed order still reaches the kitchen. The same holds if the phone is locked, the app is sent to the background, or the shift ends in a sign-out. A guest never waits on an order that quietly vanished.
Can I stop a waiter from verifying payments?
Yes. Each staff member sees only what Access Control granted them in the RPOS web app. A waiter can be limited to taking orders while reception handles verification. Change it on the web and the app follows.
Where do inventory and reports live?
In the RPOS web app, not in this one. RPOS Captain is deliberately a floor tool: tables, orders, bills and payments. Your management team keeps stock and reporting on the web.
Does it work without an internet connection?
An internet connection is required. What the app protects against is a connection that drops for a moment — a confirmed order survives that and still reaches the kitchen.
Put the counter in your waiter's pocket
Free to install. Ask your restaurant administrator for the tenant code, and your floor can be running on it tonight.