What's New

The old Graph page counted a different set of orders on almost every card: it ran on the calendar day so every Today card showed 0 after midnight, credit orders were left out, instalments counted twice and the 23:00 hour was lost.

📊 This Month: Nine cards on the Live Dashboard, each on its own Load button or all at once: the month so far, sales by day, how customers paid, by order type, by category, sales by hour against the average day, top 10 items, the last 12 months and purchases by day • A month picker for this month and the eleven before it; payments, order types, categories and top items switch between Today and Month • The figures are the Owner App's own, on the business day, so they agree with Today, Compare and the phone • Admins always see the tab; a role sees it once given the Live Dashboard Month permission, and only where the Owner App is ticked

📱 Owner app: The phone shows the same nine cards, for this month or any of the twelve before

🗑️ Removed: The Graph page and its menu links; its old address opens the dashboard

Result: The month's graphs count the same orders as everything else.

Tomorrow’s sales were a guess, and the prep list with them. A new report under Reports → Business Intelligence says what sales to expect over the next days, worked out from the same weekday in past weeks (newer weeks count more), and shows how right it has been.

🔍 Filters: Branch, order type (dine-in, take-away, delivery, each delivery app), days ahead (7, 14, 30), learn from (4, 8, 12 weeks) and part of the day (morning to late night); every figure follows them

📈 On the page: One sentence and six tiles: the next days, month end, today, the biggest day, the busiest part of the day, and how often it lands within 10% • Tabs: Overview, Day by day, By hour with a weekday × hour heat map, Order types, Items to prepare (a prep list per item and category for a chosen day), This month, How right it was, Suggestions and Special days • Suggestions: deals, items to push and offer times; Done or Not for us hides one for 30 days • Special days: mark a holiday or an event so the forecast allows for it • Admins see it; a role sees it once its label is ticked under Reports, behind the BI module tick like the other BI reports

Result: The kitchen knows tomorrow's day before it starts.

Owners receiving a Business Intelligence report kept asking what a card means, which orders it counts and what the arrow is compared with. Each of the eleven reports now answers that itself.

❔ On every report: A How to read this report button in the header opens a guide: what the report answers, which orders count, the business day, and what green and red mean, then every card, tab, graph and column, with a search box • Each comparison carries a "Compared with:" line, such as "the same number of days just before your window, not last year" • A small "?" appears beside a card, tab, column heading or graph title on hover; pressing it opens the guide on that entry without switching the tab or sorting the column • Nothing moved on the pages, and an Excel or PDF export carries no "?"

Result: Every number on a BI report explains itself.

Alerts were held in a batch window, an owner with several businesses on one phone could not tell whose order a push was about, and there was no way to read yesterday without opening the app.

🌅 Morning summary: At 09:00 every business with the app gets one push with yesterday: sales, orders, cancelled, discounts, the rating where reviews run and today’s bookings where a branch books; a tap opens yesterday’s board • On by default; Alert rules switches it off

🔔 Alerts: Every push starts with the business name • Three new rules: Unhappy review (2 ★ or less, sent the moment the review lands, a tap opens the bill), Booking lost with an advance held (no-show, cancelled or denied while the advance is still held), and Big booking (15 or more, a whole hall or an event; off until switched on) • Batching is gone: every alert is its own notification and push, at once

Result: Every alert arrives on its own, named, and the day starts with yesterday in one line.

Beyond sales, an owner wanted the cost of the stock in hand, to feel an ingredient price rise early, and to know who gave the discounts and voids, not only what was lost.

📦 Stock in hand: Stock value now by branch and by department, valued the way the web values it, with its trend a day, a week and a month back • Days of cover, this month's movement at cost (purchases, transfers, production, recipe use, sales, wastage, adjustments, returns), wastage by reason • Items running low, the ten items worth most, and what is owed to suppliers with the oldest bill

🥬 Ingredient prices: Every ingredient received in the period against the period before: the change and what the move cost in rupees on the units bought ("Chicken +11.1%, Rs 2,500 extra on the 50 kg bought") • Biggest rises, biggest falls and biggest spend, with a summary of the extra and the saved

👤 Money lost, by staff: One row per person, the biggest total first: discounts given, free orders, voided items and cancelled orders, with each person's share of the whole • The rows add up to the Money-lost logs, since they read the same records

Result: The owner sees what the stock is worth, what got dearer, and who let the money go.

The Today screen showed the day's money but not the guests, and there was no single reading of what came in against what went out this month.

🙋 Guests today: Rating today: how many rated, the average, happy and unhappy, comments, and the newest unhappy visits with the bill and the customer’s words • Bookings today: how many and how many guests, still to come, seated, completed, no-shows, cancelled, big parties, and the next to arrive • Each half shows only where its module runs

📆 Month so far: Sold this month to date, what went out (purchases received, approved expenses, refunds), and what is left or short with its share of sales • The same days of last month to the same clock, and one plain sentence • A rough reading, not the P&L: stock used from earlier purchases and anything not booked as an expense voucher are not in it, and the card says so

Result: One screen says who came today and whether the month is ahead.

The summary cards on the dashboard had flat graphs, tables that scrolled sideways, white bands under short tables and two donuts that looked the same. The figures do not change; the look does.

📊 Cards and graphs: Donuts show the total in the middle and a legend with each slice’s share; empty graphs say so instead of drawing equal slices or a bare frame • Category Wise Sale is a rose chart, so it no longer reads as a second Department donut • Bars are rounded with a soft track, lines are smooth with a shaded area, the Discount gauge is a progress arc, and axis labels read 3K or 1.2M • Cards sit in rows of two with shared edges, tables never scroll sideways on desktop, and a narrow card or a phone puts the graph above its table • The filter strip is one toolbar: business, branch and today on the left, the date window and Search on the right • Lost Business no longer breaks its graph when nothing was lost

📰 What's New: Tabs All, New features, Improvements and Fixes, each with its count • The list on the left walks through the latest notes by itself; the note on show appears on the right with its sections and Result • The note's own page is redesigned with At a glance, jump links, Older / Newer and More updates

Result: The same figures, on a dashboard that reads at a glance.

The owner app had no view of the guest side: what customers said about their visit, or what came of the bookings. There was no reservation report anywhere, even on the web.

⭐ Customer Reviews: The web page’s figures on the phone: average, reviews, happy and unhappy, comments, dish ratings, the window before, star bars, the newest unhappy visits, best dishes and dishes that need a look, by order type, branch, staff, question and day • A list of the rated visits, 50 a page, filtered to unhappy, happy, with a comment or with answers; a row opens its bill • An order's invoice in the app carries what the customer said about it

📅 Reservations: Bookings and guests against the period before; upcoming, seated, completed, no-shows, cancelled and the show-up rate • The bills the bookings led to, advances received, used, returned and still held; by status, type, branch, weekday and hour, and who booked • The next seven days with big parties, whole halls and events marked, and a bookings list filtered by status or advance still held • Both cards show only where the module is on, or where a branch has booked in the last 90 days

Result: The owner reads the guests' verdict and the bookings' outcome from the phone.

The counter had no screen for the customer, who watched nothing until the bill was printed. A second screen now faces the customer and follows the cashier’s POS, with four moments: waiting, order, paying and thank you, in a white or dark look.

🖥️ What the customer sees: Waiting: slides of the items and deals ticked Is Special, then the top deals of the last 30 days and the new deals, each with its picture, contents and price • Order: the item just punched big on the left, the order list, and subtotal, tax and total as the POS shows them; an inclusive menu says "Includes tax" • Paying: the amount, and the payment QR once the cashier picks a method that has one • Thank you: payment received, the token, "ready in about", and the review QR where the branch runs reviews

🎨 Set-up: Super Admin ticks the module for the business, then Options → Customer Display switches it on per branch with a live preview of every moment • Look, colour, slide and thank-you seconds, the line under the slides and the cashier name are set there • Options → Payment Methods takes a QR picture per method, kept byte for byte • The screen fits a standing or a lying monitor by itself; a Customer screen switch on the POS top bar opens it on the second monitor

Result: The customer watches the order build and pays from a screen of their own.

The booking wizard on the staff phone could not take an advance payment or note who referred the guest, so those bookings still had to be made at the office computer.

📅 On the phone: A booking can carry a referrer (name and mobile) and an advance, with how it was paid and a note • The advance needs a payment method the branch allows for advances • The money goes into the branch's open register with its voucher and history line; with no register open the phone says so, and a booking without an advance still saves • An advance can be increased later, never reduced, and does not change once an order has used it

💵 Also: The app can quote a guest the expected dine-in bill with the branch's service charge and tax as a bill applies them

Result: A booking with an advance is made on the floor, and the money lands in the register.

Pressing This year, an arrow or a filter while the page was still reading lit the chip but kept the old dates. And a review whose order had since been deleted said the bill was in another branch.

🖱️ Now: A choice made while the page is reading runs as soon as the read lands, so the dates change to what was pressed • The bill popup tells the two cases apart: a bill in a branch you cannot see, or a bill no longer in the system with only its review left

Result: The page does what was clicked, and says plainly why a bill cannot open.

A bill paid partly in cash at the counter, with the rest put on credit and collected a day or two later, showed the counter cash as credit still owed on the Daily Activity report. At one business the month closed with a Validation diff of −7,900 on two bills.

🧾 Now: What is still owed on such a bill is the bill less what was paid at sale less what was collected • Only the counter payments come off; a refund is not mistaken for one • The validation diff reads 0 and the credit sale figure is right

Result: A bill part-paid at the counter is counted as paid, not owed.