Introduction to OCTK Restaurant OS
High-level operational overview of the unified restaurant operating system and branch management model.
Unified Operating Architecture
OCTK Restaurant OS is designed as an integrated point of sale, kitchen display, inventory deduction, and table management platform for restaurants, cafes, and multi-location hospitality venues.
The operating system provides frontline staff with specialized interfaces for dining room orders, kitchen station preparation, inventory tracking, and delivery management.
All operational restaurant records—such as menu catalogs, recipes, active table occupancy, and shift hours—are partitioned strictly by branch location.
Branch-Isolated Operational Scope
Each branch operates independently with its own table floor layout, assigned staff rosters, live kitchen stations, and ingredient inventory balances.
Branch-Specific Data Model
Operational restaurant data is strictly branch-specific where applicable. Menu items, ingredient inventory, staff rosters, table floor layouts, orders, reservations, invoices, staff hours, and cash reports belong to a single branch context.
The Owner role maintains consolidated visibility and authority across all branches, whereas Branch Managers operate strictly within their assigned branch context.
Primary Operational Modules
| Module | Purpose | Primary User |
|---|---|---|
| Point of Sale (POS) | Table ordering, bill calculation, payment recording, and takeaway dispatch | Waiter, Host, Manager |
| Kitchen Display (KDS) | Station-routed order preparation, item completion, and remake coordination | Chef, Kitchen Staff |
| Recipe & Inventory | Ingredient tracking, waste logging, adding stock, and periodic audit | Owner, Manager, Inventory Staff |
| Floor Map & Tables | Live seating status, automatic waiter assignment, guest movement, and QR menus | Host, Waiter, Manager |
| Delivery Dispatch | Online order acceptance, distance-based delivery fees, and driver tracking | Manager, Host, Driver |
Related Documentation Guides
System-generated login email, temporary credentials flow, mandatory password change on first login, and contact email security.
Complete breakdown of login-enabled staff roles, operational boundaries, and managerial override privileges.
Define daily operating hours (one Start and one End time per day), overnight schedules, and weekly schedules per branch.