What's New

The menu engineering report did not cut the previous period on the shop day's clock, a dash typed as a variant name was read as a variant, and an item alone in its category was judged against the category's bar.

📊 Now: The previous period starts and ends on the shop day, so it lines up with the period you are looking at • A dash typed as a variant name is no longer treated as a variant • An item alone in its category is judged on its own numbers

Result: Menu engineering compares like with like.

Menu Engineering left out orders still due on account, counted a deal once for each of its parts, and listed add-ons as dishes of their own.

📊 Numbers you can trust: • Sales count paid orders and unpaid dues, net of returns, at the price before tax • A deal counts once, at its own price • An add-on folds into the dish or deal it was sold with • The cost follows the recipe for each order type and each third-party company

🧭 The report: • Each category is placed on its own, with the Kasavana and Smith thresholds for stars, plowhorses, puzzles and dogs • KPI cards, a category panel and margin charts • A previous-period comparison beside the current one

Result: Each category shows its real stars and its dogs.

With the single device login switch on, a phone that was lost or replaced could keep its owner out, and a rider signing in on a second phone was simply refused.

📱 Now, under Business Settings → single device login: • The new phone takes the slot when someone signs in on it, and the old phone stops • A lost phone never locks its owner out • A rider signed in on one phone is refused on a second one until the first signs out • A manager signing a phone out lets the other one in • Signing in again on the same phone keeps its notifications

Result: One device per user, and the owner can always get back in.

A password changed in the waiter app could leave the old password working at the POS, because the two places it is kept did not move together.

🔐 Password: • A change now writes both places in the right order • The new password works at sign-in and at the POS straight away

📜 Order History: • Off until the restaurant turns it on under the tablet settings in Business Settings • While it is off the tab is hidden in the waiter app, and the server refuses the request too

Result: Waiters see past orders only where the restaurant has chosen to open them.

One very large bill could make a quiet hour look like the busiest of the day, because busy hours followed the money.

⏰ Now: • The bars count orders, so the busiest stretch is the one with the most work • The verdict on the day runs on the same order count • The money stays beside each bar, for reference

Result: The busiest hour is the one with the most work, not the biggest bill.

The Money dashboard showed what had been billed, but not what was still on the floor or where the day was heading.

📈 Now: • Placed and not billed yet: what is ordered on the floor and still open • Expected by close: the total the day is on course to reach

Result: The owner sees where the day will land while it is still open.

On the Owner App, a cashier's or a branch's cash variance was worked out against the wrong figure, so the number did not show how the drawer really stood.

💵 Now: • Variance is counted cash minus expected cash, for each cashier and for the branch as a whole • A short drawer shows as short

Result: The variance tells you the truth about the drawer.

The Net Report and the ingredients list worked out costs on every load, whether or not anyone needed them.

📑 Net Report: • COGS by recipe is off by default; the select starts at No • Turn it on and the figure is costed from the same costing sheet in one pass • The older report tabs keep their costs through the same sheet

🥫 Ingredients list: • Prices show as N/A by default • Turn on prices to see them, and they come from purchases and batches over the costing window • Pick a location to price at that location, or All for the whole business

Result: The costs are there when you ask for them, and the screens stay quick when you do not.

Recipe costs were fixed figures that drifted away from the prices the restaurant was actually paying for ingredients.

🧾 Costing from purchases: • Every recipe screen prices from received purchases and from the batches of items the kitchen produces • Costs are per base unit, so a recipe written in grams is costed in grams • A sub-recipe is costed with its yield and its production cost • An item the kitchen makes is costed from its own batches • Costs look back over 90 days by default, and the window can be changed on the report

📊 Food Cost page, under Inventory: • Shows what every item and variant costs right now by its recipe, beside its base price • The order type drops lines that are not sold for it • Filters narrow the rows without changing the costs

📄 Recipe Excel exports: • The food sheet follows the cost choice on the report • The ingredient sheet has an Export with Costing button

Result: Margins on every plate are worked out from real purchase prices.

The Owner App's Right Now tile said 18 riders out while the Riders card said 27. Registers the shift change had opened for every cashier counted as open, and Reports called a day closed while a second shift was still trading.

🛵 Riders out: • One rule counts a rider out: a paid delivery order still on the road keeps him out • The tile, the Pulse and the Riders card now give the same number

🧾 Registers and closes: • A drawer counts as open only once a sale or cash has landed on it • Unused drawers are counted apart, not as open • Reports lists every close of the day by its shift, plus the shift still trading after the last close • A branch counts as closed only while no order has followed its last close

⏱️ Quiet reliability fixes: • Pages load faster on the phone, with large answers compressed • An order's last-seen time takes the later of its two clocks, and a branch with a register open but no orders says so

Result: Every number in the Owner App matches the screen behind it.

Changing many delivery areas meant opening each area or sub area and editing it on its own.

🗺️ Now, under Options → Areas and Sub Areas: • Tick several rows and set one value on all of them in one step • Edit all in a grid, the way a spreadsheet works • Filter the list, with Select all for what the filter shows • Distance bands, with a preview before you save • Delete several at once, with each bulk run written to the activity log

Result: A whole city of areas is maintained on one screen.

On the dark theme the dispatcher board painted whole delivery rows in strong stage colours, which was hard to read through a long shift.

🌙 Now, on the dark theme only: • Each delivery row takes a faint tint of its stage colour • The token number keeps the full stage colour as a block, so the stage is still clear • The light theme, the badges and the legend are unchanged

Result: The board reads calmly in the dark and the stage is still easy to see.