Place
Canonical location identity used by multiple domain records.
Key fields: id, name, formatted_address, lat, lng
Links to: Kitchen, Company
About Misebox
Operating System for Kitchen Teams
We run kitchen operations and hiring from one platform, with one consistent flow from prep to service and staffing.
We run menus, recipes, dishes, prep tasks, team coordination, and hiring in one operating flow so service teams can move faster with less friction.
What this page covers
- How the core Misebox modules fit together
- The key entities and how they connect
- Small realistic sample objects for context
- Quick links to public and console routes
Misebox - Key Concepts (Priority Order)
- 1. Ecosystem
An ecosystem of apps for kitchen operations and recruitment. - 2. Kitchen Operations
The systems kitchens use to organise menus, prep, service, and team. - 3. Kitchens
Each kitchen has its own workspace to run operations and organise its team. - 4. Professionals
Hospitality professionals create profiles that showcase experience instead of CVs. - 5. Jobs
Kitchens publish roles and connect directly with professionals. - 6. Menus & Dishes
Menus, dishes, and recipes live in one structured system. - 7. Prep & Service
Prep tasks and service coordination keep the kitchen organised. - 8. Team
Kitchens organise and manage the people running service. - 9. Suppliers
Suppliers connect kitchens with the ingredients and products they need. - 10. Apps
Specialised apps extend the Misebox ecosystem over time.
Modules
How we organize the app
Each module owns a clear part of operations, and together they power one kitchen workflow.
Entities
The records we work with every day
Kitchen
Operational kitchen identity and runtime context.
Key fields: id, name, short_address, image_url, is_test_kitchen
Links to: Menu, Dish, Ingredient, KitchenRecipe, KitchenMiseTask, KitchenTeamMember, Order, Job
Menu
Kitchen-owned menu identity. Sections and items live in child collections.
Key fields: id, kitchen_id, name, description, source_language, status
Links to: Dish
Dish
Individual food item with recipe and ingredient links.
Key fields: id, kitchen_id, name, ingredient_ids, recipe_ids
Links to: Ingredient, KitchenRecipe
Ingredient
Stock and costing ingredient identity for dishes and purchasing.
Key fields: id, name, default_unit, allergens, active
Links to: Dish, KitchenRecipe, Supplier
KitchenRecipe
Standardized prep/cook instructions for consistent output.
Key fields: id, name, yield_qty, ingredient_lines, steps
Links to: Dish, Ingredient
KitchenMiseTask
Prep and service task tracking for kitchen operations.
Key fields: id, kitchen_id, title, station, status
Links to: KitchenTeamMember, Menu, KitchenRecipe
KitchenTeamMember
Team assignment record for stations, roles, and capability tags.
Key fields: id, kitchen_id, name, role, station
Links to: KitchenMiseTask
Order
Customer/service order with scope, lines, totals, and status.
Key fields: id, scope_type, scope_id, status, totals
Links to: Kitchen, Menu
Job
Open role advertised to professionals in the ecosystem.
Key fields: id, title, status, type, place_id
Links to: Kitchen, Professional, Agent
Chef
Chef profile overlay used in Misebox workflow.
Key fields: id, title, summary, positions, user.id
Links to: User, Kitchen, Job
Professional
Cross-role profile with experience and contact surfaces.
Key fields: id, title, summary, positions, user.id
Links to: Job, Agent
Agent
Recruiting/operator profile for staffing and outreach.
Key fields: id, title, summary, user.id, coverage
Links to: Professional, Job
Supplier
Supplier profile and sourcing identity for kitchens.
Key fields: id, name, email, phone, place_id
Links to: Company, Ingredient, Kitchen
Company
Business identity tied to places and supplier/client structures.
Key fields: id, name, place_id, short_name
Links to: Place, Supplier
Structure
Relationship map
Place
-> Kitchen
-> Menu -> Dish -> Ingredient
-> KitchenRecipe
-> KitchenMiseTask -> KitchenTeamMember
-> Order
-> Job -> Professional
-> Agent
Company
-> Supplier
-> Ingredient
Examples