Mobile App Workflows
Use Zesty mobile for staff operations, Easy and Standard interfaces, billing, POS, Shift Desk, and tablet-friendly workflows.
The Zesty mobile app lets staff run the restaurant from phones and tablets. It mirrors the main web modules—orders, kitchen, billing, POS, Shift Desk, menu, inventory—while adapting layout for touch and smaller screens.
Customers do not use this app. Guests order from QR links in the phone browser. No install required for them.
Who should use mobile
| Role | Typical mobile use |
|---|---|
| Counter / cashier | Easy POS, Easy billing, Shift Desk |
| Waiter / runner | Operations workspace, orders, table context |
| Kitchen | KDS on tablet |
| Manager | Dashboard, Shift Desk, reports, alerts |
| Owner | Dashboard signals; heavy config still on web |
Easy vs Standard (interface preference)
Each staff member picks Easy or Standard as a personal setting. Two people at the same outlet can use different modes.
This is separate from the organization's sales workflow mode (Orders only, POS only, Combined).
| Mode | Best for |
|---|---|
| Easy | Large buttons, task-first flows, /easy/* routes |
| Standard | Web-like density, full dashboard and module list |
Full guide: Easy and Standard
Operations workspace
The Operations workspace is one surface for the full service path:
Order → Prepare → Serve → Collect
- Easy emphasizes the next task (what to do now)
- Standard shows more queue context on tablets
Hand off to full Orders, KDS, or Billing when you need detail on one ticket.
Solo Run vs Shared Crew
At the organization level you choose:
- Solo Run — one operator owns an order end-to-end
- Shared Crew — staff claim, assist, and hand off orders with notes
This affects how the Operations workspace behaves—not which modules you see.
Full guide: Solo Run and Shared Crew
Modules on mobile (by permission)
Depending on plan, feature catalog, sales workflow mode, and role, staff may access:
| Module | Easy | Standard |
|---|---|---|
| Home / dashboard | Easy hub | Full dashboard + widgets |
| Operations | Yes | Yes |
| Orders | Yes | Yes |
| KDS | Yes | Yes |
| Billing | Yes | Yes |
| POS | Easy POS | Full POS |
| Shift Desk | Yes | Yes |
| Shift control (header) | Yes | Yes |
| Menu | Yes | Yes |
| Inventory | Yes | Yes |
| Customers | If permitted | If permitted |
| Reports / analytics | Limited | If permitted |
| Alerts | If permitted | If permitted |
| Settings | Account + prefs | Broader settings |
If a module is missing, check plan, features, permissions, and workflow mode—not just mobile mode.
Operational shift on mobile
Most protected actions need an open operational shift. The header shift control shows status on web and mobile.
Staff should confirm shift is open at the start of every shift—same rule as web.
Auth and shared devices
- Sign in with the staff member's own account
- Sign out on shared tablets at shift change
- Admins should remove access for departed staff immediately
- Do not share one login across multiple people—audit trails depend on individual accounts
Offline behavior
Selected data caches offline with encrypted storage. Some lifecycle actions queue when there is no network and replay when connectivity returns.
Rules match web:
- shift must still be valid when replay happens
- stale actions may be rejected (order already closed)
- managers may need to resolve conflicts after reconnect
Train staff to reconnect before close-out when possible.
Tablet best practices
Tablets work well for:
- KDS in the kitchen
- POS at the counter
- Billing at pickup
- Easy home hub
- Shift Desk at day end
Before going live on a tablet:
- test brightness and mounting
- confirm Wi-Fi stability
- run a full test order through Operations
- check session timeout on long shifts
When to use web instead
Prefer the web app for:
- organization and branch setup
- feature catalog changes
- large menu imports and bulk edits
- complex reports and exports
- branch governance across many outlets
- billing plan and subscription management
Mobile is for operating the shift; web is often better for configuring the restaurant.
Common questions
Customer says QR does not work
QR is browser-based, not the staff app. Check table QR, menu availability, shift open.
Easy vs Standard—which should we pick?
Counters and new staff: Easy. Managers who want web parity: Standard. Mixed teams are normal.
App looks different from training PDF
Confirm interface preference and workflow mode in screenshots.