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 an intended plan and review the feature catalog. The 14-day trial unlocks optional modules so you can try everything. 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.
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.
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.
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.
Settings
Organization profile, tax, payments, printers, staff, billing plan, features, branches, white-label, and launch guide.
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. Writes to the same reports as orders. Can run as the only sales path in POS only mode.
Inventory
Raw materials, recipes, stock movements, counts, transfers, suppliers, and purchase orders. Optional link from menu items to ingredients.
Customers
Customer directory by phone, visit history, loyalty points, and notes. Identity is scoped per restaurant organization.
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.
Alerts
Operational notifications such as low stock or data mismatches. Configure who receives them.
Growth modules
Analytics
Cross-functional reports: sales, payments, inventory, and operations. Requires accurate daily data entry.
Sales
Focused sales reporting: items, categories, channels, and time periods. Requires Analytics.
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.
Advanced modules
Premium menu
Extra menu controls for larger or multi-branch menus. Requires Standard menu.
Marketplace integrations
Connect delivery platforms: menu mapping, order inbox, stock sync. Requires Orders and menu.
Branches (Franchise)
Govern multiple outlets: branch profiles, feature overrides, and per-branch workspaces.
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:
| Module | Needs |
|---|---|
| Billing, KDS, Tables | Orders |
| Sales, AI Assistant | Analytics |
| Campaigns | Customers |
| Marketplace | Orders + menu |
| Premium menu | Standard menu |
| Branches, White label, Access logs | Settings |
Disabling Orders also removes Billing, KDS, Tables, and Marketplace for that scope. See Sales workflow modes.
Who sees what
Three layers control visibility:
- Plan — what your subscription allows
- Feature catalog — what the owner enabled in Settings → Features
- 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.