Food & Beverage
ERP software built for restaurants with kot.
A full-service, dine-in-first restaurant: guests are seated at tables, a waiter takes the order, the order is routed to one or more kitchen stations as Kitchen Order Tickets (KOTs), food is prepared and served at the table, the bill is sett…
How it works
The business model
Revenue is per-order, per-table, largely same-day cash/card settlement (occasional house-account tabs for corporate/regular guests). Cost structure centers on food cost % (ingredient consumption per recipe) and labour (waitstaff, kitchen staff, chefs) — food cost % is the single most tracked KPI. Table turnover (seatings per table per shift) directly drives revenue capacity — a full-service restaurant is capacity-constrained by tables + kitchen throughput, not just by demand.
What you get
Modules included
Everything a restaurants with kot business needs, in one subscription.
Visibility
Reports and dashboards
See how the business is doing without waiting on anyone.
Reports
- Daily Revenue · KOT Performance (avg time queued→ready per station) · Kitchen Performance (per-station throughput, delay rate) · Food Cost % · Recipe Cost (per dish) · Table Turnover (seatings/table/shift) · Best-Selling Items · Waste (recipe-implied vs physical count) · Void/Discount Analysis · Shift Closing (cash reconciliation) · Sales by Waiter · Sales by Order Type (dine-in/takeaway/delivery mix)
Dashboard widgets
- restaurant.open_orders
- restaurant.kot_pending (tickets queued/preparing, flagged if over SLA)
- restaurant.tables_status (live floor heat-map)
- restaurant.top_items
- plus platform widgets: today's revenue
- food cost % trend
- low-stock ingredient alerts
Built for reality
What Muhasib handles
The situations that break generic software are designed in from day one.
86'd items mid-service: an ingredient runs out mid-shift — item must be marked unavailable on the Order Taking screen immediately (blocks new orders for that product) without touching KOTs already sent for it.
Kitchen delays: a ticket sits preparing past SLA — triggers manager alert (§13); does not auto-cancel, but flags on Kitchen Performance report.
Wrong order sent to kitchen: void the specific order item (requires reason + ingredient stock is NOT reversed unless the item was never actually prepared — manager judgment call, configurable "void before send" vs "void…
Comps/void reasons: every void/comp requires a reason code (customer complaint, kitchen error, manager comp, quality issue) for accurate Void/Discount Analysis reporting.
Table transfer mid-KOT: transferring a table does not resend or duplicate KOTs — only the table association changes.
Split bill with shared items: an item shared across the whole table must be split proportionally or assigned to one payer — Split Bill Wizard must support partial-line splitting, not just whole-line assignment.
Related in Food & Beverage
Built for your business. Ready in under an hour.
Subscribe today and get your restaurants with kot business fully set up on Muhasib — all modules, no hidden fees.