Documentation
Restaurant SetupRestaurant Setup

Restaurant Setup

Configure organization details, branches, tables, payments, white-label settings, and launch readiness.

Restaurant setup defines what customers see, what staff can operate, and what appears on bills and reports.

1ProfileNametaxhours2BranchesOutletsscope3TablesQR pertable4PaymentsCashUPIprovider

Organization profile

Complete the organization profile before inviting the full team. Keep the display name, phone, address, GST or FSSAI details where applicable, tax rates, operating hours, and payment settings accurate.

This profile is reused across staff workspaces, bills, QR ordering, support context, and reporting. If a field is wrong, staff may repeat the same correction in every order or support ticket.

Configure printers when your outlet needs kitchen tickets, counter receipts, or billing handoff outside the screen workflow.

Branches

Use branches when each outlet needs separate tables, staff scope, inventory, or feature controls. Branch managers should work inside their branch context so orders, stock, expenses, and reports stay separated.

For multi-location groups, confirm whether menu, features, and operational rules are managed centrally or overridden branch by branch.

Tables and QR codes

Each physical table should have its own table record and QR code. Do not reuse one QR code across many tables because it can mix table sessions, bills, customer order status, and kitchen handoff.

Before opening service, scan a sample QR from a customer device and confirm:

  • the table number is correct
  • the menu is visible
  • unavailable items are hidden
  • order submission reaches staff
  • bill request and payment flow match your outlet workflow

Payments

Set payment modes before live service. Zesty supports restaurant workflows such as cash, manual UPI review, payment-provider flows, split tender, and mixed settlement. Staff should know which modes are allowed and how provider status is reconciled.

Launch readiness

  • Owners and admins can access settings, billing, support, and staff controls.
  • Staff can access only operational modules required for their role.
  • Tables and QR codes are tested.
  • Menu items and prices are current.
  • Tax and payment settings are reviewed.
  • One internal order has moved from scan to KDS to bill to payment.