The Cloud Dashboard Tour in Meztezz

The terminal is where the restaurant runs. The cloud is where the owner thinks about the restaurant. A cashier doesn’t open app.meztezz.com mid-service; an owner doesn’t take cash at the till. The whole point of the cloud dashboard is to put a single, anywhere-anytime view of every outlet in front of the person who’s making decisions about them — at home on a Sunday, in a meeting with a vendor, in an airport between flights. This post is the guided tour.

This guide walks through the main screens at app.meztezz.com from an owner’s perspective — the home cockpit, the outlet selector and date picker that drive everything, the direct order/refund/credit views, the inventory/menu/audit-log reads, the masters pages, the outlets switchboard, the subscription and payment-history pages, and the settings screen. It picks up after Reports That Actually Tell You Something — that post covered the Reports tab in depth, and this one covers the rest of the dashboard.

💡 Where this lives. The cloud dashboard is at https://app.meztezz.com. You log in with the owner email and password you set up during Install & Activation. The dashboard is part of every paid plan; the trial plan also has full dashboard access (read-only of synced data). Your phone, your laptop, an iPad — anywhere with a modern browser and an internet connection works.

The Walkthrough at a Glance

Part	What you’ll learn
1. The Mental Model — Cockpit, Not a Backup	What the cloud is for, and what it deliberately isn’t.
2. Logging In & The Controls in the Header	The outlet selector and date picker that drive every page.
3. The Home Dashboard — Your Six-KPI Cockpit	What the home page shows the moment you log in.
4. The Charts on the Home Page	Sales Comparison, Top Items, Hourly Sales, Revenue Trend, Payment Pie.
5. Active Alerts & Outstanding Credit on the Home Page	The two panels that turn the cockpit into a triage screen.
6. Order History — Every Bill, Filterable	The single most-opened page after the home.
7. Refunds — The Direct View	A focused alternative to the Refunds tab in Reports.
8. Credit / Khata — Outstanding & Top Debtors	The page that drives the Friday-afternoon collections call.
9. Inventory, Menu & Audit Logs	Three read-only pages: the stock snapshot, the menu catalog, and the who-did-what trail.
10. Masters from the Cloud — Customers, Items, Raw Materials, Suppliers, Locations	Read-only windows onto the terminal’s master data.
11. Outlets — The Multi-Outlet Switchboard	How the cloud handles two outlets, ten outlets, or fifty.
12. Subscriptions & Payment History — The Billing Side of Meztezz	Plan, renewal, invoices, GSTIN.
13. Settings — Restaurant Profile & Owner Identity	The one screen that fixes “my PDF header says GSTIN: not set”.
14. What’s NOT on the Cloud Dashboard Yet	Honest list — user management, alerting, mobile app, more.
15. Mobile, Bookmarks & The Practical Workflow	How to make the dashboard a habit, not a chore.
16. Habits That Save You Later	Five disciplines that turn the cockpit from “looks impressive” into “I actually use it”.

Part 1 — The Mental Model — Cockpit, Not a Backup

The cloud isn’t a backup of the terminal. That’s worth saying first, because every owner getting started thinks of it that way and it leads them to the wrong workflow.

The terminal is the system of record. Orders, payments, KOTs, stock movements, settlements — all of them originate on the terminal and stay authoritative there. The cloud is the read-replica plus an owner UI. It can show you everything; it can’t change operational or master data. The few things you can edit on the cloud are cloud-native: your organisation and billing profile (Part 13) and an outlet’s basic contact details (Part 11). The principle, stated bluntly:

Cashiers and managers use the terminal. That’s where service happens, the cash drawer lives, and offline operation is guaranteed.
Owners use the cloud. That’s where the multi-outlet view, the cross-day analytics, and the printable exports live.

The two systems are designed to do different jobs for different people. The cloud doesn’t try to be a “remote terminal” because that would mean serving traffic across the internet for an operation that has to keep working when the internet doesn’t. If you find yourself wanting to operate the restaurant from the cloud — take an order, void a bill, count cash — go to the terminal. If you find yourself wanting to understand the restaurant — what happened, how does it compare, who owes me money — stay on the cloud.

Part 2 — Logging In & The Controls in the Header

Open app.meztezz.com and sign in with your owner email and password. You land on the Dashboard home page (Part 3). Before reading anything on it, look at the two filters in the header — the outlet selector and the date picker — because they govern what every page in the dashboard shows.

2.1 The Outlet Selector

A dropdown in the header (the top bar of every page) labelled with your current outlet. If you only have one outlet, it shows that one and there’s nothing more to set. If you have multiple, the dropdown lets you switch between them — it’s single-select, so you’re always looking at exactly one outlet’s data at a time.

The selector’s choice persists across pages within the session, so if you pick Indiranagar on the home page, the Reports page and the Order History page both show Indiranagar data when you navigate there.

2.2 The Date Range Picker

In the header on most pages. Pick a window — Today, 7 Days, 30 Days, This Month, or a custom range you click out on the calendar. Every KPI, chart, and report on the page is computed for that window.

The picker’s choice also persists across pages within the session. If you set Last 7 Days on the home page and navigate to Refunds, you see Last 7 Days of refunds.

2.3 The Theme Toggle & Logging Out

The third thing in the header is a light/dark theme toggle — purely cosmetic, it changes what you see on screen and nothing else. There’s no avatar or user menu in the header. Logging out lives at the bottom of the sidebar, under your name, alongside the sidebar’s collapse control. There isn’t yet a multi-user management screen — owner identity is currently single-user-per-organisation. Part 14 has the honest list of what isn’t shipped yet.

Part 3 — The Home Dashboard — Your Six-KPI Cockpit

The home page is the cockpit. The moment the page loads, you should be able to read it in under fifteen seconds. The structure: a row of six KPI cards across the top, then three pairs of side-by-side panels and a final full-width panel below.

3.1 The Six KPIs Across the Top

For the date window and outlet scope you’ve picked in Part 2:

Tile	What it shows	What to read it for
Total Orders	Count of orders in the window. Sub-line: how many completed (i.e. fully settled).	Volume read. The gap between total and completed is your in-flight count.
Net Sales	Gross sales minus discounts and refunds. Sub-line: gross sales for the same window.	The headline “money kept” number.
Avg Order Value	Net Sales ÷ Orders.	Whether revenue is moving on volume or on basket size.
Items Sold	Sum of every line quantity in the window.	A second volume signal that catches drops in items-per-order (a quieter spend signal).
Active Orders	Orders currently in flight — pending KOT, in the kitchen, served-but-not-paid.	Live read — if you’re checking mid-service, this is the “what’s happening right now” number.
Pending KOTs	KOTs that the kitchen hasn’t marked ready.	The “is the kitchen behind?” number. Spikes mid-service mean a station is choked.

The six are deliberately mixed: three are post-mortem numbers (Orders, Net Sales, AOV — about what happened) and three are live numbers (Items Sold, Active Orders, Pending KOTs — about what’s happening). The home page is both a historical read and a real-time read in the same six cards, and which two you focus on changes depending on whether you’re checking at 11 PM (read the post-mortem trio) or at 8 PM mid-service (read the live trio).

3.2 What’s Missing From the KPI Row

Two numbers the home page deliberately does not surface as KPI tiles:

Total Tax. It’s on the Tax/GST report. The home page is for the headline; the detail is one click away.
Discount %. It’s on the Discounts report and the Sales Summary. Same reason.

If a number isn’t on the home page, the rule isn’t that it doesn’t exist — the rule is that it’s one click away on its dedicated report. The home is a triage page, not a kitchen sink.

Part 4 — The Charts on the Home Page

Below the KPI row, three pairs of panels sit two-up on a desktop screen, with a seventh full-width panel — Outstanding Credit — running across the bottom. Seven panels in all. They’re meant to be glanced at, not studied. If a glance raises a question, the question is what drives you into the matching Report tab.

4.1 Sales Comparison (Top Left)

A compact three-row panel comparing recent baselines — vs Yesterday, vs Last Week, and vs Last Month — each row showing the prior period’s figure and the change percentage (green up, red down). Reads in two seconds: “we’re up”, “we’re down”, or “we’re flat”.

4.2 Top Items (Top Right)

A horizontal bar list of the highest-revenue menu items in the window. The five-ten items that matter most for your top line. If the order has shifted dramatically from your last look — a previously top item missing, a new one risen — that’s the question to follow into Reports → Sales → Items Sale.

4.3 Hourly Sales (Second Left)

A line chart of sales by hour of day, summed across the window. Shows your peaks (lunch rush at 13:00, dinner peak at 21:00) and your dead hours (3 PM onwards on a weekday). Useful for staffing decisions and for spotting hours where you’re under-utilised.

4.4 Active Alerts (Second Right)

Covered in Part 5 below — this is the panel most owners spend the most time on, so it gets its own section.

4.5 Revenue Trend (Third Left)

A line chart of daily revenue over the window. The shape of the line tells you what the KPI row can’t — a steady drift down vs a single bad day vs an explosive week.

4.6 Payment Breakdown (Third Right)

A pie of payment methods used in the window — cash, UPI, card, wallet, credit (Khata), loyalty. Useful for the shift in tender mix over time (UPI quietly eating into card; cash quietly shrinking; aggregator-driven wallet share growing).

4.7 Outstanding Credit (Full Width, Bottom)

A summary panel of total outstanding Khata balances across your customers — the single number “how much is on tab right now”, plus your top debtors. Covered in detail in Part 8 below; on the home page, it’s the prompt that tells you whether the Credit page is worth opening this week.

Part 5 — Active Alerts & Outstanding Credit on the Home Page

The two home-page panels that turn the cockpit into a triage screen.

5.1 Active Alerts

A small panel listing low-stock alerts across the selected outlet right now — items where the stock has fallen below the configured minimum (the cloud aggregation — see Stock & Inventory → Part 11). Each row carries a severity tag. The list is a read-only summary — it shows you what’s running low at a glance; it isn’t clickable, so to act on a low-stock item you go to the Inventory page or the matching Stock report yourself.

What the panel deliberately doesn’t do today: send you a push notification or email when an alert fires. The data is here when you open the dashboard; nothing pings you. If you want active push-style alerting, Part 14 lists it as a not-yet-shipped feature.

5.2 Outstanding Credit

A headline number and a short list:

Total outstanding — the sum of every positive Khata balance across the selected outlet. The single “how much is on tab right now” figure.
Top debtors — the handful of customers with the largest outstanding balances, each with their name and amount. For the fuller picture, open the dedicated Credit page (Part 8).

If you only look at one thing on the home page weekly, look at the top-debtors list. It’s the single fastest path to a polite collection call before a tab becomes awkward.

Part 6 — Order History — Every Bill, Filterable

Sidebar → Order History. Every order across the selected outlet and date window, listed in a paginated table. The columns are: Order #, Type, Status (a colour-coded pill), Customer (if one was attached), Total, and Date.

6.1 What It’s For

The home page tells you the aggregate. Order History is where you go for the individual. Practical uses:

“A customer is on the phone disputing yesterday’s bill — set the date to yesterday and scan for it.”
“I see refunds are up; let me filter to cancelled orders and read each one.”
“How much takeaway did we do last Saturday?” (Set the date, filter Order Type to takeaway.)
“What did dine-in look like this week versus delivery?” (Switch the Order Type filter.)

6.2 The Filters

Date range (from the header).
Outlet (from the header).
Order type — dine-in / takeaway / delivery.
Status — pending / completed / cancelled.

Click a row to open that order’s own full page — items, tenders used, taxes, discount lines, and refund lines (if any). It’s a separate page, not a pop-up panel; the back button returns you to the list with your filters intact. (For the history of who changed what and when — the state-transition trail — that lives on the separate Audit Logs page, Part 9.3.)

6.3 What Order History Is Not

It’s a view. You can’t edit a settled order from here, can’t re-print a bill from here (the terminal does that), can’t re-open a closed order from here. The cloud’s job is to show you the truth; it’s not a remote control for the terminal. If you genuinely need to act on an order, the action happens on the terminal that owns it.

Part 7 — Refunds — The Direct View

Sidebar → Refunds. A focused read of refund activity across the selected outlet and window, built around three KPI cards and a credit-notes table.

The three cards at the top:

Cancelled Orders — the count of cancelled orders, with their total value on the sub-line.
Credit Notes — the count of credit notes raised in the window.
Refund Total — the total amount refunded in the window.

Below the cards is a Credit Notes table — one row per credit note, with columns: Credit Note #, Order # (the original order it relates to), Reason, Amount, and Date.

When to use which:

Asking “did anything get refunded recently, and why?” → use Refunds (the page). The three cards give you the totals, the table gives you each credit note and its reason.
Asking “what’s our overall refund pattern this month — by reason, by who authorised it?” → use Reports → More → Refunds (the tab), which carries the deeper breakdowns.

Note what the page doesn’t show: there’s no per-row click-to-open, no refund method or authoriser column, no link back to the original order, and no per-row PDF download. It’s a read of the numbers and the credit-note list, not a transaction drill-down.

Part 8 — Credit / Khata — Outstanding & Top Debtors

Sidebar → Credit / Khata. The dedicated view for everything credit-balance-related, covered conceptually in Customers, Credit Balance & Loyalty. The page is structured around the questions an owner actually asks weekly.

8.1 The KPIs

Four cards across the top:

Total Outstanding — the sum of positive balances. This is “money on tab” across the restaurant.
Credits Issued in the window — the value of bills charged to credit (money put onto customer tabs).
Credits Redeemed in the window — credit spent back down by customers.
Unique Customers — how many distinct customers had credit activity in the window.

8.2 The Outstanding Accounts Table

Below the cards, a list of customers carrying a balance — your top debtors. Each row shows the customer name, their phone, and the outstanding amount. That’s the full row; there’s no sort control, no ageing columns, and no last-activity date on this page today.

8.3 The Weekly Read

The owner’s Friday-afternoon discipline: open Credit, glance at the Total Outstanding card, then run down the top-debtors list and call the largest few. Five minutes. Most weeks, two of the three say “oh yes, I forgot” and pay in days; the third becomes a conversation worth having early.

Three read-only pages that round out the operational picture.

9.1 Inventory — Stock Snapshot Without the Reports Detour

Sidebar → Inventory. A direct view of what’s on the shelves right now, across the selected outlets — without going via Reports → Stock.

Useful when:

The kitchen manager texts you “we’re low on cooking oil” and you want to sanity-check across outlets in ten seconds.
A supplier is on a call asking what’s running short.
You’re considering a stock transfer between outlets and want to see who has surplus.

The page shows a searchable, filterable list of every stock item with the current quantity, the location (if you use multi-location), the cost, and the colour-coded low-stock flag. It’s the cloud-side equivalent of the terminal’s Inventory tab, scoped to whichever outlets you’ve selected in the header.

The deep operational actions — recording a transfer, drafting a PO, doing a physical count — happen on the terminal, not here. Inventory on the cloud is for seeing, not for doing.

Sidebar → Menu. A view of your menu as it currently stands, with two tabs — Categories and Menu Items. Browse the catalog, search it, and click an item to open a read-only detail view. It’s a way to confirm “what’s on the menu right now” from anywhere; like the rest of the cloud, it doesn’t let you add, rename, or re-price items — that’s terminal work.

9.3 Audit Logs — Who Changed What

Sidebar → Audit Logs. The page that answers “who did that, and when?”. Three tabs:

System Audit — the trail of significant operational events, including order state transitions (the change history that an individual order page doesn’t carry).
Table Operations — table moves, merges, and splits during service.
Reservations — the booking trail.

This is where you go when a number on another page raises a “but who authorised that?” question. It’s a read of history — nothing here is editable.

Part 10 — Masters from the Cloud — Customers, Items, Raw Materials, Suppliers, Locations

Sidebar → Masters. A small group of pages that mirror parts of the terminal’s masters setup (Setting Up Masters After Installation) but from the cloud. These pages are read-only — they’re a window onto the master data the terminal owns, not a place to change it. Five sub-pages:

Sub-page	What it shows
Customers	The customer master across all outlets. Searchable by name, phone, or email. Each card shows the customer’s totals — orders, spend, credit, loyalty — inline.
Items	The item catalog. Columns are Name, SKU, HSN, Unit, (for liquor) Bottle Size and Default Peg, Min Stock, Track Batch, Active, and whether stock alerts are on.
Raw Materials	The raw-material catalog. View units, current global stock, low-stock flags.
Suppliers	The supplier directory. View PO history per supplier, contact info.
Locations	The storage-location list per outlet (name, description, active status).

10.1 Read-Only By Design

None of these masters can be edited from the cloud. Every one of them — customers, items, raw materials, suppliers, locations — is a view, with no save button. That’s deliberate: master data is owned by the terminal, which is the operational source of truth, and the cloud doesn’t push master changes back down to it. If a customer’s phone number is wrong or an item needs re-pricing, that edit happens on the terminal. (The cloud does let you edit a handful of cloud-native things — your organisation and billing profile in Settings, and an outlet’s name/address/phone/GSTIN in the Outlets section — but those aren’t terminal master data.)

10.2 Why Cloud-Side Masters Matter

The single biggest reason to open these pages is the cross-outlet read. The Customers page shows you the same regular’s behaviour across outlets — useful for chains where a Whitefield regular sometimes eats in Indiranagar. The Items page gives you one place to confirm what’s in the catalog and which items have stock alerts switched on, without logging into each terminal in turn.

Part 11 — Outlets — The Multi-Outlet Switchboard

Sidebar → Outlets. The page that’s nearly empty if you have one outlet and increasingly important as you grow into more. Lists every outlet your organisation owns as a card, each showing:

Name and address.
Phone and GSTIN.
Terminal Setup Code — the code you use to link a new terminal to this outlet, with copy and regenerate buttons.

Each card has an Edit button that opens a small dialog to change the outlet’s name, address, phone, and GSTIN — these are the cloud-editable, outlet-specific details (your Mumbai outlet’s Maharashtra GSTIN differs from your Pune outlet’s). Click the card itself to open the outlet’s detail page (Part 11.1).

11.1 The Outlet Detail Page

Clicking a card opens a read-only detail page for that outlet — its name, address, phone, and GSTIN at the top, and below them a Terminal card. The Terminal card shows the device’s status (online/offline), when it was last seen, and its app version, with two actions: Rotate Key (issue a fresh API key to the connected terminal) and Replace Terminal Device (deactivate the current device and register a new one). That’s the scope of the detail page — there’s no editing of GST regime, bill template, or currency symbol here; those are terminal-side display settings, and the editable contact fields are changed via the Edit dialog on the outlets list, not here.

11.2 Adding an Outlet

When you open a second outlet, you add it here first (cloud-side), then install the terminal at the new location and link it to the new outlet via the activation flow (covered in Installing & Activating Meztezz). The cloud is the registry; the terminals are the runtime instances.

11.3 What Outlets Don’t Do Yet

A few owner-strategic things this page doesn’t yet do — but Part 14 has the full list. The headline limit: you can’t manage cross-outlet stock movement from this page (inter-outlet transfers aren’t a shipped feature yet, as the Stock post covered). Outlets here are an administrative switchboard, not an operational one.

Part 12 — Subscriptions & Payment History — The Billing Side of Meztezz

The two pages that govern your relationship with Meztezz the product (as opposed to your relationship with your guests).

12.1 Subscriptions — `Sidebar → Subscriptions`

The current plan, the next renewal date, and an upgrade / downgrade path. Plans are priced per organisation, each with its own limits — a maximum number of outlets, terminals, and captain devices — shown on every plan card. There’s no per-outlet pricing; you buy one plan for the business and it covers up to its outlet limit. If your plan grants specific features (advanced analytics, multi-outlet, premium support), they’re listed here too.

Practical uses:

Check renewal date — so you can budget for the renewal hit.
Upgrade — when you’ve outgrown your current tier (e.g. opening a second outlet on a single-outlet plan).
Downgrade — rarely, but it’s available.
See which features your plan includes vs locks — useful when the dashboard shows a feature gated behind an “Upgrade” prompt.

12.2 Payment History — `Sidebar → Payment History`

Every subscription payment you’ve made, in a table with these columns: Date, Description (what the charge was for), Amount, Status (paid, etc.), and an Invoice download button on each paid row. The invoice number, GSTIN, and full tax breakdown live inside the downloadable PDF rather than as on-screen columns — and that PDF is exactly the kind of invoice your CA needs to claim input GST on the Meztezz subscription itself.

The single most common use is end-of-quarter — your CA asks for all your software subscription invoices for input-GST purposes, you open Payment History, download the quarter’s PDFs, send. Two minutes.

Part 13 — Settings — Restaurant Profile & Owner Identity

Sidebar → Settings. The smallest page in the dashboard, and the most important to set up correctly on day one.

13.1 Organisation Profile

Organisation name — the legal name of your restaurant business.
Owner name & phone — the person Meztezz contacts about your account.
GSTIN — the GST number that prints on every cloud PDF report header.

13.2 Billing Address

Address, city, state, pincode — where your organisation is billed for the subscription. This is also the GSTIN-registered address.

13.3 Why This Page Matters

Two reasons. First, every PDF you export from the cloud uses this profile in its header — outlet name, GSTIN, address, phone. A PDF that says “GSTIN: not set” handed to your CA is the start of an awkward conversation. Set this up on day one. Set it once, never again.

Second, the dashboard uses this profile to contact you about account-relevant events — subscription renewal reminders, payment failures, plan changes. The phone number here is the one Meztezz uses if support needs to call you. Keep it current.

Note that organisation profile is for the organisation. Each outlet has its own profile (GSTIN, address, phone) at Outlets → tap an outlet. Both must be set; both show up in different exports.

Part 14 — What’s NOT on the Cloud Dashboard Yet

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

No user / team management. Today, the dashboard is single-user-per-organisation. There’s no “invite my accountant”, “give my manager view-only access”, or “create a role”.
No push / email alerts. The home-page Active Alerts panel surfaces conditions when you open the dashboard. Nothing pings your phone when an alert fires.
No mobile app. The dashboard is a responsive web app — it works on a phone browser well enough, but there’s no dedicated iOS / Android app. (Most of the dashboard is genuinely usable on a phone; some heavier tables work better on a tablet or laptop.)
No remote actions. You can’t void a bill, re-print a KOT, or open a session from the cloud. Operational actions belong to the terminal.
No scheduled / emailed reports. You can’t tell the cloud “email me Monday’s sales summary at 7 AM”. Discipline of opening it is yours.
No saved report views or named bookmarks. Bookmark the URL (it carries the filters) — that’s the practical workaround.
No KPI thresholds / anomaly alerting. You can’t say “ping me if food cost crosses 35 %”. Today, the read is yours to do.
No cross-outlet stock transfer. The Outlets page is an administrative switchboard, not an operational one. Stock transfer between outlets isn’t shipped yet.
No inline support chat. Support is via email (Part 15).
No light/dark theme toggle for the dashboard PDFs. PDFs use a fixed monochrome layout (so they print well); the on-screen theme toggle only affects what you see in the browser.
No native mobile push for sync issues. When a terminal stops syncing, the outlet detail page shows it as offline with a stale Last Seen time — but you have to open the page and look. We don’t yet push a notification when sync goes silent.

Part 15 — Mobile, Bookmarks & The Practical Workflow

Two practical notes that make the dashboard a habit instead of a chore.

15.1 On a Phone

The dashboard is mobile-responsive. The home page, the Order History, the Refunds and Credit pages all read well on a phone — the six-KPI row stacks into a column, the side-by-side panels stack vertically, the tables horizontally scroll. Reports with wide tables (Items Sale, Stock Movements, Tax/GST) are usable on a phone but easier on a tablet or laptop. The PDF export buttons work on a phone (the PDF downloads or opens in a new tab).

For the two-minute daily Settle check (from Reports → Daily reading), the phone is genuinely fine. For the Monday-morning sales briefing, a laptop is more comfortable.

15.2 Bookmarks

Every filter is in the URL. The date range, the outlet, the active tab, the sort column — all encoded as query parameters. This means you can bookmark a specific configuration of any report and the bookmark takes you back to exactly that view.

Practical bookmarks an owner might keep:

“My weekly sales briefing” — Sales Summary, last-7-days range (read it against the home page’s Sales Comparison card).
“My monthly tax dump” — Tax/GST, last-month range, all-outlets selected.
“My credit collections call” — the Credit page, all outlets.
“My daily settle check” — More → Settle, today.

Bookmark them in your browser, give them clear names, open them on a schedule. That’s the practical workflow.

Part 16 — Habits That Save You Later

Five disciplines that turn the dashboard from “looks impressive in a demo” into “I actually use it weekly”.

Set Restaurant Profile and every Outlet profile on day one, then forget them. Once they’re filled in, every PDF you ever export carries the right header. Half an hour, paid back forever.
Make the home page your start-of-week page. Monday morning, coffee, the home page first. Read the six KPIs against the prior week. Spend ten more minutes on whichever panel pulled your eye. That’s the briefing.
Open Credit on Friday afternoon and call your top three debtors. Five minutes. The hardest call is the one you’ve delayed for six months; the early ones are easy.
Bookmark your four most-used views in the browser. Don’t navigate from scratch each time — let your browser remember the configuration.
When the dashboard shows you something surprising, follow it the same session. “AOV is down 8 %” deserves the ten minutes of Items Sale and Discounts that explains it, now, while the question is fresh. A note-to-self for “later this week” is a note that never gets read.

If any of this didn’t behave the way the guide describes — a KPI card that’s stuck loading, an outlet selector that won’t change scope, a report that doesn’t match what the terminal shows you, a PDF whose header is blank, or a Khata balance that’s different from the customer record on the terminal — drop us a line at bazimat@gmail.com or contact us. Tell us which page you were on and what you were seeing; we’ll usually have you sorted in a single back-and-forth.

Once you’re navigating the cloud like a cockpit, the next chapter is the one most ambitious owners reach for at exactly the wrong time: Running Multiple Outlets — chain and franchise setup, shared masters vs per-outlet overrides, central reporting, what changes when you go from one outlet to many. We’ll publish that one next. 🎉