04Proposal section
Product Modules
The customer-facing, staff-facing, and admin-facing product scope.
Visual direction
Modules should match restaurant roles
Customer, staff, kitchen, manager, finance, and admin modules should be designed around what each role needs to see and act on quickly.
Guest appKitchenDashboardFinance
Customer Ordering
- QR menu
- Search and categories
- Item modifiers and add-ons
- Cart and checkout
- Dine-in, takeaway, pickup, delivery
- Order status
- Digital receipts
Restaurant Operations
- Menu management
- Availability and sold-out control
- Tables and sessions
- Kitchen order queue
- Waiter requests
- Staff roles
- Reservations
Growth & Finance
- Payment adapters
- Refunds
- Coupons and offers
- Loyalty and CRM
- Customer feedback
- Reports and exports
- Multi-branch analytics
Module design principle
Each module should be owned by a clear user role and backed by explicit permissions. Customer screens need speed and trust, staff screens need fast state changes, and management screens need control, reporting, and auditability.