Dining areas and tables
Organize service areas, seats, guests, occupancy, and active sale state for dine-in or service locations.
Restaurant
Coordinate tables, waiter orders, kitchen preparation, recipes, and counter payments in one flow.
Separate food-court, bar, wine-court, kitchen, and warehouse stock while sharing authorized users and management reporting. Confirmed orders move from service staff to kitchen tickets and then into POS settlement.
What the Restaurant module covers
The workspace is organized around complete operational responsibilities, not a collection of disconnected menu labels.
Waiter ordering
Give service staff a focused order-entry workflow and route confirmed items to the correct preparation team.
Kitchen operations
Move tickets through accepted, preparing, ready, served, priority, and cancellation states on a dedicated display.
Recipes, stock, and settlement
Calculate product composition cost, consume ingredients from the correct division, and settle completed service through POS.
Records kept by the workspace
These are the principal operational records staff create, update, review, or hand to another connected module.
- Dining areas, tables, seats, and occupancy
- Waiter orders and active sales
- Kitchen tickets and preparation status
- Recipes, ingredients, yields, and composition cost
- Settlements and food, beverage, or kitchen stock movements
What the connected workflow is designed to improve
The module combines records, permissions, location scope, and shared services to support these practical operating results.
Coordinated service
Waiters, kitchen teams, cashiers, and managers work from connected order states without sharing every menu or administrative permission.
Separated operating stock
Food court, bar, wine court, central kitchen, and warehouse quantities can remain in their own branches or inventory divisions while authorized users cross approved workspaces.
Cost-aware menu decisions
Recipes, ingredient usage, yield, composition cost, sales, and payment outcomes give managers a clearer view of what each menu item contributes.
Included functionality
The module connects the following working capabilities through one tenant and branch model.
- Dining areas, tables, seats, guests, occupancy, and active-sale state
- Waiter-focused ordering with controlled confirmation into kitchen operations
- Kitchen tickets with accepted, preparing, ready, served, priority, and cancellation states
- Recipes, ingredient consumption, yields, and product composition costing
- Separate inventory divisions and branch stock for food, beverages, and central kitchens
How work moves through the module
A typical operating sequence; permissions and branch configuration determine who performs each step.
- 1
Seat guests or start a waiter order for the correct dining area
- 2
Confirm items and route preparation work to the kitchen display
- 3
Move tickets through preparation, ready, and served states
- 4
Settle through POS while recipes and branch inventory record ingredient consumption
Deployment, data ownership, and management oversight
The workspace is connected to the wider platform without removing tenant, location, department, or permission boundaries.
Deployment model
Restaurant teams can use dedicated hosted workspaces while branch checkout and supported inventory continue through the local application when required. Food, beverage, and warehouse divisions remain separate.
Access and data scope
Restaurant access can be separated for waiters, kitchen staff, cashiers, stock teams, and managers. Food, bar, wine-court, and central-store quantities can remain in distinct divisions.
Management visibility
Review active service, kitchen progress, sales, recipe cost, ingredient consumption, stock by division, waiter activity, discounts, and payment outcomes.
Assign the workspace by responsibility
Module enablement makes the workspace available to the organization. User assignments and permissions still control its menus and actions.
Waiter or serverKitchen teamCashierRestaurant or stock manager
Administrators can combine module access with branch, store, campus, facility, department, menu, and action permissions. A shared user may work across approved workspaces without receiving access to unrelated records.
Start with Restaurant, then assign the right locations and people.
Hosted onboarding records the organization, first branch, business type, module selection, and owner account. Additional branches, roles, and permissions can be configured from administration.