Five numbers a restaurant owner should read every morning

1. Where did yesterday's orders come from?

Count completed orders by source before looking at the total. Keep cancelled orders separate, and use the same branch and trading period each morning. A shift towards marketplace orders can change what you keep from sales even when the kitchen handles the same volume.

Here, Talabat and Careem account for half the completed orders. That is a channel mix, not a profit calculation. Their commissions still apply to orders they bring. Nexara charges no commission on your own website, app and call-center orders; payment and delivery costs are separate.

Where it lives in Nexara: start with the Channels and Orders tabs in Charts & Reports, then investigate individual records in Order History. Live Orders brings these channels into one queue per branch. Orders outside Nexara still need to be included in your restaurant-wide check.

Compare with the same weekday, rather than treating a quiet Sunday as a failed Thursday. Investigate a missing channel before spending money on a promotion.

2. How much was the average completed order worth?

Average ticket = sales value for the selected orders ÷ completed order count. Write down your sales definition. Decide how discounts, refunds, tax and delivery charges are treated, then keep that definition unchanged. Dividing one report's gross total by another report's net order count produces a misleading number.

For the example, 1,400 JOD in sales after discounts and refunds, excluding tax and delivery charges, divided by 200 completed orders gives an average ticket of 7 JOD. That is sales per order, not profit per order.

Read average ticket by channel as well as for the branch. A larger share of small pickup orders can pull the overall average down without any change in what a typical pickup customer buys. Check the mix before asking staff to push extras.

Where it lives in Nexara: the Orders and Financial report tabs are the starting points for reviewing orders and money. Products helps investigate what sold. Bloub can answer sales-summary and channel-breakdown questions with citations to the company's data. Keep the underlying records in view when checking the calculation.

3. Did kitchen tickets print when they were needed?

Printed-on-time rate = eligible tickets printed within your target ÷ eligible tickets due × 100. Set the target locally. Measure from when a ticket should reach the kitchen, which matters for scheduled orders. Printing time is not preparation time or delivery time.

Suppose your target is 60 seconds and 190 of 200 eligible kitchen tickets meet it. The rate is 95%, leaving 10 tickets to investigate. Count kitchen tickets consistently, not customer receipts or manual reprints. Category routing can create more than one ticket for an order.

Where it lives in Nexara: Printing provides the operational starting point, including the visible queue. Bloub can retrieve printer status. A ready-made historical printed-on-time percentage is not a verified feature, so treat this calculation as a manual audit unless the team demonstrates the required timing records.

Nexara queues tickets during connection loss and catches up after reconnection. Backup printer routing is available where configured. Those mechanisms reduce lost work, but a ticket printed later still missed your target. Separate connection problems from printer faults before assigning the fix.

4. How many orders produced a complaint?

Start with the number of orders that received a complaint, then read the cases. For the example, 4 affected orders out of 200 completed orders gives a complaint rate of 2%. Multiple calls about one order should not become multiple affected orders in that calculation.

Keep two views separate: complaints received yesterday, and complaints attached to yesterday's completed orders. A customer may report a problem the following morning. Mixing those periods makes the rate hard to interpret.

Where it lives in Nexara: use the Complaints report tab and Cases. Cases support routing, SLA clocks, photos and workflow-task sync, with open, breached, escalated and resolved states. Feedback Calls builds follow-up tasks from delivered orders; it is another source of issues that customers may not report themselves.

A low complaint count does not prove every customer was happy. Read unresolved cases and check whether the same item or handoff appears repeatedly. Assign an owner to each unresolved problem. Treat a food-safety concern according to your safety procedure regardless of the day's complaint percentage.

5. Does counted stock match expected stock?

Stock variance = physical count minus expected stock. Calculate expected stock from opening stock plus receipts and net transfers, minus recipe usage and recorded waste. Use the same unit throughout. A case count cannot be compared directly with a recipe measured in kilograms.

In the example, chicken starts at 20 kg. The branch receives 10 kg, uses 18 kg according to recipes and records 1 kg of waste, with no transfers. Expected closing stock is 11 kg. A physical count of 9 kg leaves a variance of -2 kg.

That gap is a reason to investigate, not proof of theft. Recount first. Then check receiving records and whether prep yield or recipe portions reflect what the kitchen actually does. Record waste when it happens rather than relying on memory at close.

Where it lives in Nexara: Inventory and Stock Counting support ingredients, recipes and branch counts. Recipe costing, prep yield and waste analytics help investigate differences. These are the records behind the check; this guide does not promise a single automatic variance tile. NexaraFlow includes a Morning Inventory template, and workflows require Pro.

How do you turn the five numbers into a morning routine?

Use one short review sheet with a row for each measure. Include the comparison period and a named person responsible for any follow-up. A percentage without a denominator is difficult to audit; a problem without an owner usually returns tomorrow.

1. Fix the scope: one branch, one trading period and documented rules for completed orders and refunds.
2. Read channel counts and average ticket together. Check unusual changes against the underlying orders.
3. Review late printing and unresolved complaints. Record the operational cause where it is known.
4. Recount unexpected stock gaps before adjusting stock records.
5. Assign each follow-up a person and a deadline, then check yesterday's unfinished actions.

Nexara also has End of Day and Cashier Reconciliation report tabs. These five daily KPIs do not replace cash reconciliation. Nexara is the order and operations layer beside the till, not the till itself.

For the wider reporting framework, see restaurant reports that matter. The Bloub assistant guide explains asking questions about your own numbers. Bloub provides a morning brief and cited answers; that does not mean scheduled email reports are available.

Message Nexara, the team behind nexaratech.io, to walk through this morning review and confirm which checks are native reports and which need a manual calculation.