Restaurant Setup
Configure organization details, branches, tables, payments, white-label settings, and launch readiness.
Restaurant setup is everything you configure before and during go-live. It defines what customers see on QR menus, what appears on bills, which modules staff can open, and how payments and taxes are calculated.
Complete setup in a calm window—not during your first Friday rush.
Setup order (recommended)
- Organization profile and tax
- Sales workflow mode and feature catalog
- Branches (even for single outlet)
- Payment modes and providers
- Printers (if used)
- Menu categories and items
- Tables and QR codes
- Staff invites and permissions
- Test order end-to-end
- Launch guide checklist in app
Organization profile
The profile is reused everywhere:
- staff workspaces and receipts
- customer QR ordering screens
- support tickets and exports
- tax lines on bills
Fields to get right
| Field | Why it matters |
|---|---|
| Display name | Customer-facing brand |
| Phone and address | Receipts, support, delivery context |
| GST / FSSAI (if applicable) | Compliance on bills |
| Tax rates | Every bill and report |
| Operating hours | Customer expectations (where shown) |
| Currency and locale | Formatting on screens and exports |
Wrong profile data forces staff to fix the same mistake on every order.
Sales workflow and features
Sales workflow mode
Choose how this organization sells:
- Orders only — table/QR/staff orders; no POS-first path
- POS only — counter register; service queues hidden
- Combined — both counter and table service
Detail: Sales workflow modes
Feature catalog
During trial, optional modules unlock for 14 days. Pick your intended plan and which modules you plan to keep.
After trial, disabled modules disappear unless you upgrade. Owners save the catalog in Settings → Features with password or email verification.
Detail: Feature catalog
Branches
Even a single-outlet restaurant should have one main branch. Branches separate:
- tables and QR codes
- staff scope
- inventory and stock
- reports and expenses
- feature overrides (for groups)
Branch managers must work inside their branch context so data does not mix.
Multi-outlet groups: decide whether menu and rules are central or per branch.
Detail: Branches and outlet controls
Tables and QR codes
Rules
- One physical table = one table record
- One unique QR code per table
- Never reuse one QR on many tables
Pre-go-live test (customer phone)
- Scan QR from a real customer device (not staff preview)
- Confirm correct table number and outlet name
- Confirm menu loads and sold-out items are hidden
- Place a test order
- Confirm staff see it on Orders or KDS
- Run bill and payment flow your outlet uses
Mixed table sessions break kitchen routing and billing.
Payments
Configure before live service:
| Mode | When to use |
|---|---|
| Cash | Physical drawer tracking |
| Manual UPI | Staff confirms UPI on their phone |
| Razorpay / provider | Integrated online collection |
| Split tender | Part cash, part UPI on one bill |
Train staff on:
- which modes are allowed
- how to record manual UPI
- how to read provider status vs Zesty status
- when manager approval is needed for discounts or refunds
Printers
Configure when you need:
- kitchen tickets (KOT)
- counter receipts
- billing handoff without screen-only workflow
Test print from each station before opening. Wrong printer mapping delays service.
White-label (plan permitting)
Eligible plans can set:
- brand colors
- logos on web, mobile, and public ordering
- approved assets for customer touchpoints
Uploaded assets apply at runtime. Packaged mobile app icons may still show Zesty unless you ship a custom build through your rollout process.
Launch guide (in-app)
After basic setup, open Settings → Launch guide. It tracks:
- profile completeness
- menu and tables
- staff access
- test order
- first live shift and Shift Desk familiarity
Use it as the shared checklist between owner and manager.
Launch readiness checklist
Access
- Owner can reach billing, staff, features, support
- Staff see only modules they need
- Departed staff removed
Customer-facing
- QR menus correct per table
- Food type labels (Veg / Non-veg) set where required
- Prices and tax reviewed
Operations
- Operational shift opens cleanly
- One full internal order: scan or staff → KDS → bill → payment → receipt
- Manager trained on Shift Desk
Money
- Payment modes match how you collect
- Provider credentials tested (if used)
Common mistakes
- Skipping branch setup on single outlet (reports lack context)
- One QR for all tables
- Going live before payment modes are tested
- Inviting all staff before permissions are planned