Documentation
Getting startedFeature Catalog

Feature Catalog

A complete list of Zesty modules, what each one does, and how plans and permissions affect visibility.

Zesty is built from modules. During onboarding you pick a plan and review the feature catalog. The 14-day trial unlocks the modules of the plan you chose, so what you try during the trial is what you keep. After trial, you keep modules that your plan includes and that you left enabled in the catalog.

Core modules stay available on all plans: Dashboard, Standard menu, and Settings. Orders and Billing are central to most restaurants but depend on your sales workflow mode.

1Set upProfilebranchestables2Publish menuCategoriesitemsQR3Run serviceOrdersKDSbilling4Review dayShift Desksalesstaff

Core modules (always important)

Dashboard

Your home screen with live signals: open orders, payments, stock pressure, and attention items. Customize which widgets you see. Fixed shortcuts to New Order, Billing, KDS, and POS.

Dashboard guide

Orders

Create and manage dine-in, takeaway, and online orders. Includes order history, lifecycle actions, and links to kitchen and billing. Required for table service and QR flows.

Orders guide

Billing

Generate bills, apply tax and discounts, collect cash or UPI, handle split payments, print or share receipts, and process refunds. Requires Orders in the catalog.

Standard menu

Categories, items, prices, descriptions, food type labels, images, and availability. Powers staff screens, QR menus, KDS, and POS.

Menu guide

Settings

Organization profile, tax, payments, printers, staff, billing plan, features, branches, white-label, and launch guide.

Organization Settings is the guided administration surface for organization profile, locations, permissions, billing, privacy, and operational defaults. Owners and admins should confirm these settings before inviting staff or opening a production shift.

Restaurant setup

Operations modules

Kitchen Display (KDS)

Kitchen screen with columns for incoming, cooking, and ready orders. Staff move tickets forward so front of house knows when food is ready. Requires Orders.

Tables

Table records, QR code per table, and dine-in session context. Required for table-based QR ordering. Requires Orders.

POS

Counter register for paid sales without going through the full service-order path. Payment can be taken immediately, or the order left unpaid and settled later. Writes to the same reports as orders. Can run as the only sales path in POS only mode.

POS register · POS and imports

Inventory

Raw materials, recipes, stock movements, counts, transfers, suppliers, and purchase orders. Optional link from menu items to ingredients.

Inventory guide

Customers

Customer directory by phone, visit history, loyalty points, and notes. Identity is scoped per restaurant organization.

Customers guide

Expenses

Record operating expenses: vendor, amount, category, date, payment method, and approval status.

Staff

Invite team members, assign roles, and manage permissions. Works with access logs and shift activity.

Staff guide

Alerts

Operational notifications such as low stock or data mismatches. Configure who receives them.

Administration

Administration covers platform governance, organization settings, access logs, capabilities, and audited support controls. Platform administration is a Standard-only surface.

Organizations

Organizations and locations are tenant-scoped. Organization Settings, branch assignments, and permissions are checked before a mutation is accepted.

Profit Advisor

Profit Advisor summarizes sales, margin coverage, payment exceptions, and recovery opportunities, and proposes changes through a preview → approve → execute → verify pipeline. Owner and admin only. See Owner Brief, Menu Profit, and Insight Canvas.

Growth modules

Analytics

Cross-functional reports: sales, payments, inventory, and operations. Requires accurate daily data entry.

Analytics guide

Sales

Focused sales reporting through Insight Canvas: curated views for items, categories, channels, and time periods, with saved views. Requires Analytics.

Owner Brief

A saved snapshot of yesterday, delivered each morning in your Location's local time, with push to owners and readable history. Owner and admin. Requires Analytics.

Contribution value, current purchase cost, cost coverage, and confidence for each menu item, with discounts allocated proportionally. Requires Inventory and recipes.

Owner Brief, Menu Profit, and Insight Canvas

Campaigns

Customer offers and WhatsApp campaigns. Requires Customers module and proper consent.

AI Assistant (Zesty Assistant)

Ask questions about your operating data and product help. Treat answers as guidance—verify against live reports. Requires Analytics.

Zesty AI (paid add-on)

A paid tier add-on, currently coming soon. Its purchase controls stay hidden until it is available. See Plans and billing.

Advanced modules

Premium menu

Extra menu controls for larger or multi-branch menus. Requires Standard menu.

Branches (Franchise)

Govern multiple outlets: branch profiles, feature overrides, and per-branch workspaces.

Branches guide

Staff PINs

Four-digit PINs so staff can identify themselves on a shared counter device without signing in and out. Set in People & Access. See POS register.

Per-Location control of the web nav bar order, what hides behind More, and the mobile dock default. See Navigation layouts.

Printers and devices

Bluetooth thermal printer pairing on Android, a Location print agent, and saved printers per device. See Printers and devices.

White label

Custom brand colors, logos, and assets on web, mobile, and public ordering (eligible plans).

Access logs

Audited history of sensitive organization and staff actions.

Priority support

Faster support routing on eligible plans.

How modules depend on each other

Some modules need others to work:

ModuleNeeds
Billing, KDS, TablesOrders
Sales, AI AssistantAnalytics
CampaignsCustomers
Premium menuStandard menu
Branches, White label, Access logsSettings

Disabling Orders also removes Billing, KDS, and Tables for that scope. See Sales workflow modes.

Who sees what

Three layers control visibility:

  1. Plan — what your subscription allows (see Plans and billing)
  2. Feature catalog — what the owner enabled in Settings → Features
  3. Permissions — what each staff role can open

A staff member may have a module on the plan but still not see it if their role lacks permission.

Changing modules after onboarding

Owners and admins open Settings → Features, adjust toggles, and save. Saving replaces the full feature snapshot and requires password or email verification. Disabling a module may hide dependent modules—review the impact before saving.