Restaurant Mode

Restaurant mode is designed for restaurants, cafes, takeaway outlets, food courts, and dine-in operations.

Core operating model

Restaurant mode is a hybrid inventory and service workflow with two common stock paths.

Path A: Raw materials to production to sale

purchase raw materials -> stock ingredients -> recipe/production -> sell dish

Path B: Direct purchase to sale

purchase finished item -> stock -> sale

This dual-path design is important for real restaurant work because some items are prepared while others are sold directly.

Recommended setup sequence

Before live billing begins:

1. create the business in restaurant mode
2. create branches
3. create users for service staff
4. add waiter and kitchen staff users
5. create restaurant tables
6. create menu categories
7. create menu items
8. create resale items such as soft drinks
9. create raw materials
10. create recipes or production definitions when ingredient deduction is used

Restaurant users and tables

Restaurant orders usually involve staff such as:

• waiter
• kitchen staff
• chef
• captain
• cashier

Tables should be configured as records, not only free text, because they support dine-in assignment, table status, and service coordination.

The manual table or token field should still stay available as a fallback.

Product Create in restaurant

Restaurant products usually include:

• menu dishes
• beverages
• direct-sale packaged items
• raw materials when enabled

Restaurant products normally work better with modifiers than with large numbers of retail-style variants.

Billing Page in restaurant

Restaurant billing behaves like order capture.

Main fields include:

• order type
• dining table
• table or token
• order staff
• kitchen status

Recommended daily flow:

1. select branch
2. select customer or walk-in
3. select order type
4. if dine-in, select dining table
5. select order staff
6. add menu items
7. add notes or modifiers
8. save order
9. kitchen receives pending items
10. kitchen status is updated
11. payment is completed when appropriate

Sale Create and Sale Edit

Sale Create is the structured order entry screen and should expose the same core restaurant fields as Billing Page.

Sale Edit is very important because restaurant orders change often. Staff may:

• add dishes
• remove items
• change modifiers
• move table
• assign a different waiter
• update kitchen status
• change payment state

Purchases, raw materials, and production

Restaurant purchases usually include two classes:

• raw materials used in recipes
• finished goods sold directly without preparation

When raw materials and production are enabled, restaurant mode supports recipe-driven consumption and more realistic ingredient control.

Best fit

Restaurant mode is best when the business needs:

• order flow instead of invoice-only flow
• table management
• waiter assignment
• kitchen status tracking
• raw material and recipe support
• modifier-based menu customization