Reports & insights

Reports, in the left-hand bar under 'Know your numbers'. It holds four cards: Monthly statements, Message history, Sent email and Tracked links — all read-only; opening them changes nothing. Your day-to-day numbers live one group up, on the Dashboard.

Revenue and orders for today, the last 7 and 30 days; average order value; revenue and orders-per-day charts; a best-sellers table; a repeat-customer table; coupon usage; and review-link clicks. With a loyalty programme running there is also a tile for cards with stamps and rewards earned in the last 30 days.

The 'Best sellers' panel on your dashboard ranks your most-ordered items — how many sold and what they brought in — over the 7, 14 or 30 days the range switch selects. Revenue is the amount actually charged, so bundle prices and offers are already reflected, and cancelled orders are excluded. Items are ranked by name, so a dish keeps its history even after a bulk menu re-import.

Things that need a decision now: orders waiting to be confirmed, orders out for delivery, items with no stock, and messages that failed in the last 24 hours. Each links to the page that fixes it, and the strip disappears entirely when every count is zero.

No — every revenue figure on the dashboard and in statements counts non-cancelled orders only. Order COUNTS include everything, which is why the two can move differently on a night with cancellations.

Yours. Every daily figure is bucketed in your restaurant's own timezone (printed under the page title), so a late evening does not roll into tomorrow at some foreign midnight.

For each window — 3, 5, 7, 14 and 30 days — how many distinct customers ordered, how many ordered more than once inside it, and the repeat rate. Cancelled orders excluded. Judge yourself on the 30-day row; the short windows swing wildly.

Not on the dashboard — it shows counts only, with no name, phone or address anywhere on the page, deliberately. Customer-level detail lives on the orders board, where you are looking at a specific order for a reason.

One document per month covering orders, revenue, discounts and a day-by-day breakdown — as a PDF for filing and an XLSX for your own book-keeping, both built from one set of figures so they cannot disagree with each other or with your dashboard.

Two sheets. Summary: orders (placed, delivered, cancelled), money (revenue, of-which-delivered, items subtotal, delivery fees, discounts), how orders arrived (delivery vs dine-in), how customers paid (cash vs card machine), and every coupon redeemed that month. Daily: a row per day plus a Total row.

Yes — the numbers are real numbers with the currency in the cell format, not text like AED 39.00, so your formulas work. The Total row is a stored value, not a formula, so nothing silently recomputes a figure the system never claimed.

It reports what was actually charged at the time, not a recalculation — editing a price today or renaming an item has no effect on a month that has closed.

It is the month in progress — every order placed today lands in it, and its row says 'This month so far' for exactly that reason. Download again after month end for the settled figure.

The most recent 24 months, from your first order. Trading longer? A note at the bottom says older months exist — ask the platform operator for those.

Only with a TRN saved under Settings → Ordering rules. With one, statements and invoices show the VAT included in your totals and invoices are titled 'Tax Invoice'; without one they are titled 'Invoice' with no VAT line at all.

Yes — a statement is a whole month of your trading in one file, so every download writes a change-log entry with the month, the format and who took it. That record protects you if a figure is ever disputed.

Every WhatsApp message this system sent or tried to send on your behalf — confirmations, kitchen and delivery tickets, review requests, campaigns — each with time, type, recipient and a status: sent, failed, paused, held, no channel, queued or discarded.

The reason is printed under the row in plain English, translated from what WhatsApp told us — most commonly that the number is not on WhatsApp. Raw provider output is never shown, deliberately.

Sending was switched off when that message came due, so it was recorded and NOT sent — the row says so explicitly. That is different from 'failed', and worth knowing before apologising to a customer for the wrong thing.

The second tab on the message history page: marketing our safety rules held back — a customer who would be reached twice in one week, or a type that always needs approval — waits there for you to approve or discard. It carries a number badge when something is waiting. The Marketing hub's 'Review queue & weekly cap' card opens this same tab, so you can reach it from either side.

Review requests and map pins go out as short links so the system can tell you which were actually tapped. The report shows sent, tapped-at-least-once, click-through rate, and a row per link with the order and customer. Kinds: Review, Location, Referral, Group order.

Deliberately conservative: WhatsApp's preview fetch is filtered out, and the same person tapping repeatedly within an hour counts once. The number can understate interest; it never inflates it.

Not from your panel. What you export yourself is your ORDERS as a spreadsheet (the 'Export these orders' panel on the Orders board), monthly statements, and per-order invoices. A customer LIST export exists only as an operator action, recorded in the change log because it is personal data leaving the system; ask support if you genuinely need it.

It carries the same fields, arranged by order rather than by person, and we would rather say so than pretend otherwise. Two things make it different in practice: it covers a period you choose rather than everyone you have ever served, and it is the same information already on your own orders board. It is treated as personal data leaving the system all the same — owner-only, and every download written to your change log with the dates and who took it.

On the dashboard, not in the message history. History proves a campaign was SENT; the 'Coupons & promos' panel shows how many ORDERS carried a code and what discount you gave — the number that matters. Judge a promotion by orders, not sends.

Reports → Sent email. Every email this system sent, or tried to send, about your restaurant — billing notices, security alerts such as a password change, the QR print pack when you email it to yourself — with the time, the type, who it went to, the subject, and a clear sent or failed on each. Filter by status or type, and press 'Show message' on a row to read the exact text that went out. Times are in your restaurant's own timezone.

Reports → Sent email, and set Status to failed. A failed email appears there the moment it fails, marked 'This email could not be delivered', so you can tell the difference between 'we never sent it' and 'it was sent and your inbox ate it'. If the row says sent, check the spam folder of the address it names — that address is shown on the row. Email is deliberately a separate screen from Message history: WhatsApp and email are different channels with different failure reasons, and mixing them would make both harder to read.

No — it is never plan-gated, on purpose. What lands there is platform-to-restaurant mail: what you are being charged, and warnings about your own account's security. A restaurant must always be able to see what it was told, whatever plan it is on.