Reports That Actually Tell You Something in Meztezz

Most restaurant owners have a Reports tab they don’t open. Forty links, two hundred columns, three colour-coded charts per page — and somewhere in there, the answers to questions like “is Wednesday genuinely my worst day, or does it just feel that way?”, “which dish is my second-highest margin?”, “why is my paneer cost up 11 % this month?”. The reports almost always have the answer; the problem is that nobody told the owner which report to open, when, or what to look for. A report you read on a schedule is a useful tool; a report you might open someday is decoration. This post is the owner’s reading schedule.

This guide walks through every report in Meztezz from an owner’s perspective — what to read daily (it’s two reports, five minutes), what to read weekly, what to read monthly, and what to leave for quarterly reviews — plus the four places where the terminal and the cloud dashboard show different numbers on purpose, and why. It picks up after Customers, Credit Balance & Loyalty — the Customers and Credit tabs both surface in the cloud’s Reports area too — and pulls together threads from every prior post in the series.

💡 Where these live in the app. The terminal’s reports are under Reports (the home-screen tile). The cloud dashboard’s reports are at app.meztezz.com → Reports in the side nav, organised into eight category groups (Day End, Sales, Purchases, Suppliers, Stock, Liquor, Aggregator, More). The two places share most reports but not all — the differences are in Part 12.

The Walkthrough at a Glance

Part	What you’ll learn
1. The Mental Model — A Report Is a Cadence, Not a Tab	Read on a schedule, in service of a question.
2. Terminal vs Cloud — Which One to Open When	Two devices, two reasons, easy decision rule.
3. The Owner’s Reading Calendar — In One Table	Daily / Weekly / Monthly / Quarterly, mapped to reports.
4. Daily — Day End & Settle (Five Minutes Each Night)	The two reads that should never be skipped.
5. Weekly — The Sales Briefing: Summary, Items, Tables	The Monday-morning fifteen-minute read.
6. Weekly — Discounts, Cancels & Refunds: The Cleanliness Numbers	The three reports that tell you whether the floor is honest.
7. Monthly — Tax / GST: The Report Your CA Actually Wants	What’s on it, what’s not, how to hand it over.
8. Monthly — Purchases: Summary → POs → GRNs → Debit Notes	A four-step path that reconciles to your supplier statements.
9. Monthly — Stock: Current, Summary, Movements, Food Cost, Consumption	Five tabs, three questions: what do I have, how much did I use, what did it cost?
10. Monthly — Suppliers, Liquor, Bar Sync	The smaller-but-mattering monthly reads.
11. Quarterly — Staff, Aggregator, Customers, Reservations, Credit	The owner-strategic reads that change how you run the place.
12. The Four Intentional Terminal-vs-Cloud Divergences	Where the two devices show different numbers on purpose, and why.
13. PDF & Excel Exports — When You Need Them	The “send to the CA” and “give to the supplier” workflows.
14. Honest List of What These Reports Don’t Yet Show	Limits to know before you build a process around them.
15. Habits That Save You Later	Five small disciplines that turn the Reports tab into a briefing.

Part 1 — The Mental Model — A Report Is a Cadence, Not a Tab

Three sentences, then we move on.

A report is only useful if you read it on a cadence — daily, weekly, or monthly — because numbers only mean something against the last time you looked at them. A report is only useful if you open it with a question — “did anything weird happen yesterday?”, “is my food cost drifting?” — because a report you open with no question becomes a wall of numbers. And a report is only useful if reading it leads to a decision — to do something differently, or to consciously decide not to — because a report that doesn’t change behaviour is recreational reading. The rest of this post is structured around those three tests.

Part 2 — Terminal vs Cloud — Which One to Open When

Meztezz’s reports live in two places. The decision rule is simpler than it looks.

Question you’re asking	Open this
”What happened in this one outlet, on this one day, right now?”	Terminal (`Reports` on the home screen of that outlet).
”What happened across all my outlets, last week, last month, last year?”	Cloud dashboard (`app.meztezz.com → Reports`).
”What happened in this one outlet, but I’m at home and can’t drive over?”	Cloud dashboard — filter by that one outlet.
”I need to print or PDF a report for my CA / supplier / auditor.”	Cloud dashboard — exports are the same numbers and the same layout, and the cloud always knows the outlet header (GSTIN, address) to print on the document.

The principle: the terminal is the single-outlet, single-day, in-the-moment view. The cloud is the multi-outlet, multi-day, anywhere-anytime view. The numbers are the same; the convenience is different.

The one place this rule has a wrinkle is the four intentional divergences (Part 12). For those four reports, the cloud and the terminal don’t just present the same numbers differently — they’re computed differently on purpose, because the right answer for a single-outlet operator is different from the right answer for a multi-outlet owner.

Part 3 — The Owner’s Reading Calendar — In One Table

The whole post in one table. The rest of the post is just the detail behind each row.

Cadence	Report	Where	Time	The question it answers
Daily (every night, before you leave)	Day End / Z-Report	Terminal	3 min	”Did the books match the till?”
Daily	Settle	Cloud	2 min	”Were any closes flagged tonight?”
Weekly (Monday morning)	Sales → Summary	Cloud	5 min	”How did last week compare to the week before?”
Weekly	Sales → Items Sale	Cloud	3 min	”What sold, what didn’t?”
Weekly	Sales → Tables	Cloud	2 min	”Which tables earned, which sat empty?”
Weekly	More → Discounts	Cloud	2 min	”Did anyone discount unusually?”
Weekly	More → Cancels & More → Refunds	Cloud	3 min	”Anything pulled back, and why?”
Weekly	Stock → Wastage	Cloud	2 min	”Did the kitchen waste anything unusual?”
Monthly (first week of the new month)	More → Tax/GST	Cloud	5 min	”What does my CA need?”
Monthly	Purchases (all four sub-tabs)	Cloud	10 min	”Did everything I paid for arrive?”
Monthly	Stock → Current / Summary / Movements / Food Cost / Consumption	Cloud	15 min	”Is my food cost where it should be?”
Monthly	Suppliers	Cloud	3 min	”Who am I most exposed to?”
Monthly	More → Cash	Cloud	3 min	”How much cash flowed through the till?”
Monthly	Liquor (if applicable)	Cloud	5 min	”Is my bar shrinking?”
Quarterly	More → Staff	Cloud	10 min	”Who’s pulling weight?”
Quarterly	Aggregator	Cloud	10 min	”Are Zomato / Swiggy paying their share?”
Quarterly	Customers + Credit	Cloud	10 min	”Who are my regulars, who owes me money?”
Quarterly	Reservations	Cloud	5 min	”Is the reservation funnel actually feeding the dining room?”

Total time per week: about fifteen minutes daily + thirty minutes weekly + sixty minutes monthly + ninety minutes quarterly. That is, on average, less than four hours a month for a complete picture of the business. The owners with the cleanest operations are the ones who actually spend it.

Part 4 — Daily — Day End & Settle (Five Minutes Each Night)

The non-negotiable daily reads. Two reports, five minutes total, every operating day.

4.1 Day End / Z-Report — Terminal — `Reports → Day End`

The closing ritual was covered in detail in End-of-Day: Day Close, Z-Report & Cash Reconciliation. The Day End tab is the top-level entry; the Z-Report History section on it is where you reopen a closed day’s Z-Report. The owner’s read of the closed Z-Report is shorter than the cashier’s: scan the numbers on the page, focus on three lines.

Line	What you’re checking
Net Sales	Is it in your usual band for that day of the week, or wildly off?
Variance (Excess / Shortage)	Zero is ideal; ±₹50 is fine; anything bigger needs a conversation tomorrow.
Refunds / Voids	A spike is a signal to read the Cancels & Refunds tab tomorrow morning (Part 6).

That’s it. The Z-Report has many more lines, but three is the owner’s daily read. The detail is for when one of the three flags something.

4.2 Settle Tab — Cloud — `Reports → More → Settle`

The Settle tab summarises every Z-Report closure across your outlets, with a column for flagged closes — closes where the cashier saved through one or more warnings (cash variance over threshold, fee deviation, late close, etc.). The cloud rolls these into a flaggedCount KPI.

The owner’s daily read: scan today’s row. If flaggedCount is zero, you’re done. If it’s non-zero, the bottom of the tab lists which closes had flags and which outlet they were at — and you know to ask the manager of that outlet what happened, before you forget.

💡 The cloud knows the count, not the codes. The terminal records which specific warnings were acked (e.g. FEE_DEVIATION, DIFF_LARGE); the cloud only stores the boolean “this close had at least one acked warning”. So the cloud answers “did this close fly through warnings?” (yes/no), but for “which warnings?” you have to open the Z-Report History on the terminal at that outlet. This is one of the four intentional divergences in Part 12.

Part 5 — Weekly — The Sales Briefing: Summary, Items, Tables

The Monday-morning fifteen-minute read. Three tabs under Reports → Sales on the cloud, in this order.

5.1 Sales → Summary — `Reports → Sales → Summary`

The headline report — KPIs and trend charts for any window you pick. The KPI tiles, in order, mirror what the terminal shows:

Tile	What it is	What you’re looking for
Net Sales	Gross minus discounts and refunds.	The “money you actually kept” number.
Tax Collected	Total GST (CGST + SGST) and VAT (liquor) collected.	Sanity check against the Tax tab in Part 7.
Gross Sales	Total billed amount before tax. Sub-chips break out items / SC / packaging / tax / round-off.	Comparison to the prior period — is the headline number up, flat, down?
Discounts	Total trade discount given (manual + offers — two buckets).	Spike check — see Part 6.
Total Orders	Count of settled orders in the window.	Volume trend; pairs with AOV to explain Gross Sales movement.
Avg Order Value	Net Sales ÷ Total Orders.	Whether revenue is moving on volume or on basket size.

Below the KPIs the sections run, in order: Sales Trend (a daily line chart over the window — only visible when the date range is multi-day), Payment Methods, GST Summary, Order Types (dine-in / takeaway / delivery split), Hourly Sales Distribution, Day × Hour Heatmap (when service peaks, multi-day only), Staff Sales (per-cashier), Sales by Category, and Top Items.

The owner’s weekly read isn’t the absolute numbers — it’s the comparison. The cloud’s home page carries a Sales Comparison card that does this at a glance — today vs Yesterday, vs Last Week and vs Last Month, each with its change percentage. For an arbitrary window, set the Sales Summary date range to last week and read it against the week before. If anything is up or down more than 10 %, that’s the question to follow.

5.2 Sales → Items Sale — `Reports → Sales → Items Sale`

Every menu item with its category, sold quantity, revenue, and average price — sortable by quantity, revenue or price.

The owner’s weekly read:

Top 5 by revenue — these dishes carry the restaurant. Make sure they’re never out of stock, never get a stealth price drop, and the kitchen treats them as priority.
Bottom 10 by quantity — these dishes are taking menu space without earning it. Three months at the bottom is the trigger for a menu-engineering conversation.
Sudden drops — an item that was selling 40/week and dropped to 8 has a reason. Either the recipe changed, the price changed, or the kitchen has been running out. One of those is fixable now.

5.3 Sales → Tables — `Reports → Sales → Tables`

Per-table revenue, order count, average order value, average dwell time, and turnover days. Useful for two questions: which tables earn? (the ones to protect from being demoted into “waiting area” overflow) and which tables sit empty? (the ones to repurpose, move, or absorb).

This is the report most owners ignore for the first six months and then can’t believe they ignored.

Part 6 — Weekly — Discounts, Cancels & Refunds: The Cleanliness Numbers

Three short reports, all under Reports → More on the cloud, that together tell you whether the floor is running cleanly.

6.1 More → Discounts — `Reports → More → Discounts`

Covered in detail in Discounts, Offers, Coupons & Happy Hours → Part 14. The owner’s weekly read:

Total discount as a percentage of gross sales. A drift from your usual baseline (say, 2 % → 4 % over four weeks) is a signal, even if no single bill looks unusual.
Discount by reason. Look for changes in the mix — Customer complaint spiking is operational, Manager comp spiking is one specific manager’s habit, Promotion spiking is the offer doing its job.
Manual vs offer split. The two buckets, side by side — a rising manual share is staff giving discounts at their own discretion; a rising offer share is your promotions doing the work. For a per-cashier view of who’s discounting, open the Staff report (Part 11), not this tab.

6.2 More → Cancels — `Reports → More → Cancels`

Every cancelled order in the window, with the reason, the cashier, the manager (if PIN was used), the time. Two reads:

Volume, against the same window last month. A spike of cancels is rarely random — it’s usually a kitchen issue (the dish keeps coming back), a staffing issue (a captain who confuses orders), or a guest experience issue (long wait times leading to walk-outs).
Reason mix. If “kitchen error” is up, talk to the kitchen. If “guest walked out” is up, talk to the host. The report tells you which conversation to have.

6.3 More → Refunds — `Reports → More → Refunds`

Every refund in the window — different-day refunds become credit notes, captured here with full tax-reversal detail (CGST / SGST / VAT). Three reads:

Total refund value as a percentage of gross sales. A weekly baseline number for you.
By Reason — the breakdown of why money came back. The cloud lists every distinct reason your team has used; the terminal trims this to the top 10 because a single outlet rarely needs more. (This is the second intentional divergence — see Part 12.)
By Authoriser — which manager approved the refunds. Useful for the same per-person trend-watching as Discounts → By Cashier.

Part 7 — Monthly — Tax / GST: The Report Your CA Actually Wants

The single most important monthly report, in compliance terms. Reports → More → Tax/GST on the cloud.

7.1 What’s on It

Total taxable sales for the month (the goods value tax was computed on).
CGST collected and SGST collected — broken down by tax slab (5 %, 12 %, 18 %, 28 %).
VAT collected (liquor) — broken down by VAT rate.
Credit-note adjustment — tax reversed via credit notes for refunds processed that month (the net-of-CN tax figure).
HSN-wise summary — quantities, taxable value, and tax per HSN code. This is the section your accountant wants verbatim for GSTR-1.

7.2 The Workflow

First week of the month, open the previous month’s report, hit Export PDF. The PDF carries your outlet header (name, GSTIN, address, phone) — already formatted for handing to your CA. The Excel export carries the raw numbers if your accountant wants to recompute or roll up across outlets.

If you have multiple outlets, the cloud lets you select all of them and export a consolidated view, or export per-outlet (per-outlet is what you want for GST filing, since each outlet is a separate GSTIN).

7.3 What the Tax Report Won’t Tell You

It won’t tell you whether you’ve filed. That’s between you, your CA, and the GSTN portal.
It won’t tell you about input GST on purchases. The Purchases reports (Part 8) carry that — your CA pulls input credit from there.
It won’t compute your monthly liability after input credit. That’s still a CA calculation; this report is the input to it.
It won’t separate aggregator §9(5) tax. The Tax/GST tab is your own-supply tax; for the platform-collected-and-remitted (Section 9(5)) split, the Aggregator report — and the terminal’s Z-Report “9(5) Exempt” line — is where that breakdown lives.

Part 8 — Monthly — Purchases: Summary → POs → GRNs → Debit Notes

The four-tab sequence under Reports → Purchases on the cloud, read in order.

Tab	What it shows	The question it answers
Summary	Total purchase value, supplier count, tax breakdown for the month.	”How much did I spend on stock this month?”
POs	Every Purchase Order — drafted, ordered, received status, value.	”What’s still in the pipeline?”
GRNs	Every receipt — what arrived, when, from whom, at what cost.	”Did everything I paid for actually arrive?”
Debit Notes	Returns to vendor / shortage adjustments.	”What did I push back?”

The owner’s reconciliation read: total purchase value in Summary should match the sum of invoices your supplier sent for the month. If they don’t, the GRNs tab is where you find the gap — usually a partial receipt that wasn’t completed, or a receipt logged on the wrong date.

For your accountant: the Tax Summary on the Summary tab is the input-GST number for the month — the credit your CA will set against your output tax in Part 7.

Part 9 — Monthly — Stock: Current, Summary, Movements, Food Cost, Consumption

The Reports → Stock group is the densest on the dashboard — ten sub-tabs. The five that matter for the monthly read, in this order.

9.1 Stock → Current Stock

A snapshot — every item, current quantity on hand, value at most recent cost. The end-of-month read: scan for surprises. Items you didn’t know you had. Items you thought you had more of. Negative values that crept in (covered in Stock & Inventory in Practice → Part 13).

9.2 Stock → Stock Summary

The month’s in-out roll-up per item: opening stock, in (purchases + transfers in), out (sales / consumption + transfers out), wastage, adjustments, closing stock. Each row should reconcile: opening + in − out − wastage ± adjustment = closing. If a row doesn’t reconcile, something is recording incorrectly — the Movements tab is where you trace it.

9.3 Stock → Movements

The transaction log — every stock-moving event in the window, with the type (stock_in / stock_out / wastage / adjustment / transfer), the reason, the user, and the reference (PO ID, KOT ID, count ID). When you want to know why a number is what it is, this is where you go.

💡 The row limit is different on terminal vs cloud. The terminal caps the list at 1000 rows because it’s a single-outlet report. The cloud scales the cap to (1000 × outlets, max 5000) so a multi-outlet org sees enough. KPIs (totals, summary) are always unbounded on both, so the headline numbers stay correct regardless. This is the third intentional divergence — Part 12.

9.4 Stock → Food Cost

The percentage that explains whether your menu is priced right. Computed as (cost of goods used in recipes) / (revenue from those sales) × 100. Industry baselines: most Indian full-service restaurants run between 28–35 %; bars run lower; pure dessert / coffee shops run lower still.

The monthly read: is it where it should be? Drift up means either recipes are off (the kitchen is plating more than the recipe says — fix the recipe or the plating), prices are too low (raise the menu price), or waste is up (read the Wastage tab next).

9.5 Stock → Consumption

The flip side of Items Sale: which raw materials were consumed, and how much. Useful for spotting the ingredient that’s quietly draining — we used 47 kg of paneer this month? when we only sold 200 paneer dishes at 80 g each, that should be 16 kg — that 31 kg gap is your conversation with the kitchen.

Part 10 — Monthly — Suppliers, Liquor, Bar Sync

The smaller-but-mattering monthly reads.

10.1 Suppliers — `Reports → Suppliers`

The Suppliers tab is the accounts-payable view — how much you owe and to whom. It has four sub-tabs: Aging (what’s outstanding, bucketed by how overdue), Statement (a per-supplier ledger of bills, payments, and debit notes), Top Creditors (who you owe the most), and Payment History (what you’ve paid out). The owner’s read: which supplier are you most exposed to (concentration risk), whose balance is creeping into the older aging buckets, who has the highest debit-note rate (quality risk)? One of those usually drives a payables conversation.

For delivery timeliness — is this supplier actually showing up on time? — open the Stock → Supplier Performance tab in the Stock group instead. It ranks suppliers by an Avg On-Time % from the operations side, where the Suppliers tab is the finance side (rupees you owe). Read both if you’re considering switching a major supplier.

10.2 Liquor — `Reports → Liquor`

If you serve alcohol, this tab is the monthly bar reconciliation: opening stock (in bottles and in volume), purchases received, sales, wastage, closing stock. Liquor is the single most stolen category in most restaurants; if you have a bar, this report is the lever for keeping that honest.

10.3 Liquor → Bar Sync

If you use an external bar inventory system that syncs into Meztezz, this tab shows the sync history — what synced, when, with what counts. Useful for confirming the integration is healthy. If you don’t use bar sync, ignore this tab.

10.4 More → Cash — `Reports → More → Cash`

Net cash flow through the till for the month — opening floats, sales-in-cash, refunds-out-in-cash, cash-in slips, cash-out slips, closing cash. Useful for the simple “how much physical cash moved through this restaurant this month” picture. Pairs with Tax (for the accountancy view) and Day End (for the per-day view).

Part 11 — Quarterly — Staff, Aggregator, Customers, Reservations, Credit

The owner-strategic reads — the ones that change how you run the restaurant, not what you do tomorrow morning.

Report	Where	What you’re looking for
Staff	`Reports → More → Staff`	Per-cashier and per-server performance — sales handled, average ticket size, refunds approved, hours worked (if attendance is being captured). Read for who to promote, who to coach, who’s quietly carrying the team.
Aggregator	`Reports → Aggregator`	Per-platform (Zomato / Swiggy / etc.) revenue, commission, net revenue, cancelled. Read to decide whether each platform is paying its share or quietly costing you margin.
Customers	The Customers page on the dashboard (not in the Reports group)	Tier distribution (how many Gold customers do you actually have?), top spenders, dormant Gold customers. Covered in Customers, Credit Balance & Loyalty.
Credit	The dedicated Credit page, and also `Reports → More → Credit`	Outstanding balances, ageing, top debtors. Lives in two places — the standalone Credit page and a sub-tab under Reports → More. Quarterly read because monthly is too frequent for an honest collections conversation.
Reservations	`Reports → More → Reservations`	Reservations made, confirmed, walked-in, no-show rate per source (phone, walk-in-the-door, web). Read to decide whether the reservation flow is feeding the dining room or just generating no-shows.

These reports won’t tell you what to do tonight. They’ll tell you what to do next quarter. Both kinds of read matter; the operational dailies are the ones most owners get right, and the quarterly strategics are the ones most owners skip.

Part 12 — The Four Intentional Terminal-vs-Cloud Divergences

This is the part that’s easy to mistake for a bug. Four reports compute differently on the terminal and the cloud, on purpose. Knowing which is which saves you from a confusing afternoon.

12.1 Low Stock Alerts — Per-Location vs Aggregate (Per-Brand Card Only)

Terminal: lists every item where any one storage location is below its minimum stock.
Cloud: lists every item where the total stock across all locations is below its minimum.

Same item can appear on one and not the other. The terminal answers “the tandoor’s working tray is empty — top it up”. The cloud answers “the outlet is about to run out entirely — order more”. Both are correct for who’s reading them.

This divergence is only on the per-brand card. Both the terminal and the cloud also show a Low Stock by Raw Material card on the same Alerts tab that sums each ingredient across all its linked brands; that card uses identical math on both sides — no divergence. Covered in detail in Stock & Inventory in Practice → Part 11.

12.2 Refunds → By Reason — Top 10 vs All

Terminal: shows the top 10 reasons by value.
Cloud: shows all reasons, no cap.

The terminal serves a single outlet, which rarely has more than 10 reasons in active use, so the trim keeps the report tight. The cloud serves multi-outlet orgs where the union of reasons can be larger, and the row totals are expected to sum to the headline Total refunds KPI — capping silently would break that sum. The summary numbers (totals, percentages) match on both; only the reason breakdown table is different.

12.3 Refunds — Always India-GST Layout on Cloud

Terminal: branches the Refunds register on tax regime. India-GST tenants see CGST / SGST / VAT columns; non-India tenants see a single Tax column with a separate component breakdown.
Cloud: always renders the India-GST layout (CGST / SGST / VAT columns hardcoded), with the VAT column hidden when there’s no VAT in the window.

The reason is product-scope: the cloud is India-only today, so an India-GST layout is correct for every tenant who can actually log in. If you ever see a “this column doesn’t apply to me” thought on the cloud refunds tab, that’s why.

12.4 Stock Movements — Row Cap

Terminal: caps the rows at 1000 (single outlet, plenty of headroom).
Cloud: scales the cap as (1000 × number of selected outlets, max 5000) so a multi-outlet org isn’t capped at single-outlet budgets.

The KPIs (total in, total out, total wastage value) are computed over the full window with no cap on either side, so the headline numbers stay correct regardless. Only the transaction-list grid is windowed. If you need every single movement row for a huge window, export to Excel — exports use the same scaled cap.

12.5 The Settle Acked-Codes Limitation

A fifth, smaller wrinkle that’s worth flagging here even though it’s a cloud limitation more than a divergence. The cloud knows whether a Z-Report close had any acked warnings (the boolean flagged flag is mirrored), but it doesn’t know which codes were acked. The terminal stores the JSON-encoded list of codes (FEE_DEVIATION, DIFF_LARGE, etc.); the cloud rolls them into a single boolean. So “this close was flagged” is a question the cloud can answer; “which warnings were overridden?” is a question only the terminal can answer.

Part 13 — PDF & Excel Exports — When You Need Them

Every report on the cloud dashboard has a PDF and an Excel export button in the top-right of the toolbar. Two simple rules.

13.1 PDF for People; Excel for Machines

PDF is for handing to a person who will read it — your CA, your bank manager, a vendor you’re disputing with, your spouse asking what the restaurant did this quarter. PDFs print formatted with your outlet header (name, GSTIN, address, phone), date range, and the same KPI / table layout you see on screen.
Excel is for handing to a machine (or a person who’ll use it as a machine) — your CA’s bookkeeping tool, your accountant’s GST utility, your own spreadsheet for cross-outlet roll-up. Excel exports use raw numbers (no currency symbols) so values are formula-ready.

13.2 The Single Watch-Out

Make sure your outlet GSTIN, address, and phone are filled in under Settings → Restaurant Profile (the masters setup post covered this) — they’re what shows on every PDF header. A PDF that says “GSTIN: not set” handed to your CA is the start of an awkward conversation.

The terminal also has PDF and Excel export, with the same numbers and the same outlet header. Use whichever is closer to hand at the moment you need to export.

Part 14 — Honest List of What These Reports Don’t Yet Show

So you don’t go hunting for something that isn’t there:

No saved report views or named bookmarks. You can’t “save this filter set as ‘My Monday Briefing’”. You re-select your filters each session, or rely on URL query params (every filter is in the URL — bookmarking the URL is the practical workaround).
No scheduled / emailed reports. Meztezz won’t email you Monday’s sales summary at 7 AM. The discipline is yours; the system delivers when you open it.
No alerting / thresholds. You can’t tell the system “ping me if food cost crosses 35 %”. Today, the read is yours to do.
No per-customer loyalty history report on the cloud. Per-customer loyalty transactions exist on the terminal’s Customer Statement; the cloud’s per-customer drill-down doesn’t yet break them out. See Customers, Credit Balance & Loyalty → Part 16.
No multi-period comparison beyond previous period. You can compare this week to last week, this month to last month — but you can’t see “this month compared to the same month last year” in a single view.
No drag-to-build custom report. The reports are a curated set, not a query builder. If you need a slice that isn’t built in, the Excel export is your bridge.
No automatic detection of anomalies. “Wednesday’s net sales were 40 % below the four-week average” isn’t surfaced as a callout — it’s something you spot by reading the Sales trend chart. (We may add this later; today the read is human.)
No native dashboards / KPI board you can pin. The cloud lands you on the Sales Summary by default; there’s no “owner home page” with a curated KPI board.

Part 15 — Habits That Save You Later

Five disciplines that turn the Reports tab into a briefing rather than a maze.

Pick a fixed time for each cadence. Daily: last thing before you leave. Weekly: Monday morning, coffee, fifteen minutes. Monthly: first week of the new month, an hour. Quarterly: first Saturday of the quarter, an hour and a half. The schedule is the discipline; the reports do the rest.
Always read with a question. “How did last week compare to the week before?” is a question. “Let me look at the reports” is not. The question makes the numbers mean something.
Compare, don’t measure. A number on its own is decoration. A number compared to last period is information. The dashboard home’s Sales Comparison card (vs Yesterday / vs Last Week / vs Last Month) gives that read in one glance; for any other window, change the report’s date range and read it against the period before.
When you spot a drift, follow it. Discount % up by 1 % this week? Open Discounts → By Reason. Food cost up by 2 %? Open Wastage and Consumption. The reports are linked by question; let the question lead you across them.
Export the monthly Tax/GST report on the first Sunday of each month and email it to your CA. No “I’ll do it later”. Make it a Sunday habit. Your CA will love you; your filings will stop being a panic on the 18th.

If any of this didn’t behave the way the guide describes — a KPI tile that doesn’t match what the terminal shows, an export that’s missing its outlet header, a stock movement that’s on one device but not the other, or a number that’s drifted in a way you can’t trace — drop us a line at bazimat@gmail.com or contact us. Tell us which report you’re on, which device, and what you’re seeing; we’ll usually have you sorted in a single back-and-forth.

Once you have a reading rhythm, the next chapter is the one that turns the cloud from “the place I export reports from” into the management cockpit it was built to be: The Cloud Dashboard Tour — what app.meztezz.com gives the owner that the terminal doesn’t, the cross-outlet view, the analytics surfaces, the subscription and users panels, the alerts. We’ll publish that one next. 🎉