These settings control how the ePOS waiter app behaves for a specific branch: what orders staff can see, which payment methods appear at checkout, how orders are assigned, and what managers can approve on their own. Role-based permissions live separately in Role Settings — this page covers operational behavior, not who can do what.
You must have the Manage Settings permission to change these settings. Settings are branch-specific — select the correct branch at the top of the page before saving.
Opening the settings
Go to Settings
In the web admin, open Settings from the main navigation and choose Waiter App Settings.
Select your branch
Use the branch selector at the top of the page to choose the branch you want to configure. Changes apply only to the selected branch.
Adjust settings and save
Update the options described below, then save your changes.
Order visibility
| Setting | What it does |
|---|
| Waiter show all orders | When on, every waiter on the app sees all open orders for the branch. When off, each waiter only sees orders assigned to them. |
Turn this off if your floor team works individual sections and you want waiters focused on their own tables only.
Payment methods
Choose which payment methods appear as options when a waiter closes a bill. Enable only the methods your branch accepts.
Available options: Cash, Card, UPI, Bank transfer, Other, Talabat, TM Done, Khedmah.
Order assignment
| Setting | What it does |
|---|
| Auto-assign waiter to orders | Automatically assigns the waiter who creates an order to that order. |
| Max concurrent orders per waiter | Limits how many open orders one waiter can hold at once. Leave blank for no limit. |
UX and confirmation options
| Setting | What it does |
|---|
| Require table confirmation | Before sending a new order to the kitchen, the app prompts the waiter to confirm the table. Helps prevent orders going to the wrong table. |
| Require attendance before order | Staff must clock in before they can create a new order. Useful when you track attendance alongside shift operations. |
| Enable order timeline | Shows a live activity timeline inside each order, so staff can see when items were added, bumped, or paid. |
| Show item tax breakdown | Displays a per-item tax detail line on the order screen. |
Shift management
| Setting | What it does |
|---|
| Shift management enabled | Enables shift open/close workflow on the device. When on, waiters must open a shift before taking orders and close it at end of service. |
| Post-shift-close behavior | Controls what happens to orders after a shift is closed: Lock waiter (waiter’s orders are locked to them), Lock all (all orders on the branch lock), or No change (orders remain accessible as normal). |
If shift management is disabled, the shift open/close controls do not appear on the ePOS app for this branch.
Invoice sending
| Setting | What it does |
|---|
| Invoice send enabled | When on, waiters can send a digital invoice to the customer (for example, by email or link) directly from the order screen. |
History windows
History windows control how far back each role can scroll when viewing past orders on the ePOS app.
| Role | Options |
|---|
| Waiter history window | Current shift, Today, Last 7 days, Last 30 days, All |
| Manager history window | Current shift, Today, Last 7 days, Last 30 days, All |
| Admin history window | Current shift, Today, Last 7 days, Last 30 days, All |
Set tighter windows for waiters to keep their view focused on current service, and broader windows for managers who need to investigate past orders.
Active orders scope
Controls which orders appear in the Active Orders panel on the ePOS home screen.
| Option | What it shows |
|---|
| Current shift | Only orders created during the currently open shift. |
| Today | All orders created today regardless of shift. |
| All | All open orders with no time restriction. |
Manager override settings
These settings govern when a manager PIN is required for sensitive actions and whether managers and admins can approve their own actions.
| Setting | What it does |
|---|
| Manager self-approve | When on, managers and branch heads can approve their own sensitive actions without a separate PIN from another manager. |
| Waiter override actions | Select which actions waiters can request a manager override for (for example: void items, cancel orders, apply discounts). Actions not listed here always require a manager PIN. |
Enabling Manager self-approve means a manager can perform sensitive operations — such as applying large discounts or voiding items — without a second approval. Review this carefully for high-trust branches.
The override PIN flow, thresholds, and how managers generate override tokens are covered in Manager Override PINs.
Permissions note
All settings on this page require the Manage Settings permission. To control what individual roles can do inside the app (void orders, process refunds, apply discounts, etc.), go to Role Settings.