Choose a report below. Once inside a report, open the O2 toggle (top-left) to set Firm / Brand / Zone / date filters — your selection carries across reports.
Pick a restaurant to begin
Use the filters above. The quadrant plots every menu item by units sold and average rating.
Dashed lines mark the median units sold and median rating for this selection. X-axis is log-scaled so low-volume items stay readable. Only items with at least one rating appear here.
All rated items
Click a column to sort. Click an item name to see its rating timeline.
Item
Units
Avg rating
Ratings
Quadrant
Item rating timeline
Average rating over time. Defaults to the blended trend across all items; pick an item to isolate it. Points are labelled with the rating value.
Sold but unrated
Item
Units
Zomato Complaint
Orders & complaints over time
Daily orders (left axis) and complaints (right axis) for the current selection.
Complaints by category
Breakdown of complaint types in this selection.
Items by complaints
Which items draw the most complaints. Rate = complaints ÷ units sold.
Item
Complaints
Orders
Restaurants
Units sold
Rate
Zomato Customer
Customers split by how they're identified — phone number or Customer ID — ranked by order volume. Click a row to see its order timeline and items.
Customers by Customer ID
Customer ID
Orders
Items
Complaints
Restaurants
Order timeline
Every order this customer placed, most recent first — with the items in each order.
Date
Order ID
Restaurant
Items
Qty
Rating
Complaints
Items ordered (totals)
Across all of this customer's orders.
Item
Qty
Orders
Rating
Complaints
Zomato Dine In Finance
Bill, commission & net receivable over time
Daily settlement totals for the current selection (bill & net on the left axis, commission on the right).
By settlement status
Settlement transactions
Most recent first (up to 500).
Date
Txn ID
Type
Restaurant
Bill
Comm %
Commission
Tax
Net
Status
Settled
Swiggy Revenue
Orders & items sold over time
Daily Swiggy order count and units sold for the current selection (orders on the left axis, units on the right).
Top items
By units sold (up to 300).
Item
Units
Orders
Unmapped Swiggy restaurants
These Swiggy outlets aren't linked to a RID-sheet restaurant yet, so their data is excluded above. Set their Swiggy ID in Data update → Restaurant data to connect them.
Swiggy ID
Name
Orders
Zomato Revenue
Orders & revenue over time
Daily order count and GMV (Total) for the current selection (orders on the left axis, ₹ revenue on the right).
Orders by hour of day
When orders come in (0–23h), with revenue per hour.
By order status
Top restaurants
By revenue (up to 200).
Restaurant
Orders
Units
Revenue
Avg rating
Order Search
Paste a Zomato or Swiggy order ID — both datasets are searched. Firm / brand / zone / restaurant slicers apply; the date range is ignored for an exact-ID lookup.
Items in this order
Order details
Settlement / payout (Zomato finance)
Revenue Details
Revenue by restaurant · month · status · portal
A = items total · B = discounts · C = packaging · D = GST (Swiggy only — Zomato order data carries no tax) · E = A−B+C · F = A+C+D. Small ▲/▼ = change vs the same day numbers of the previous month.
Brand-Location
Month
Status
Portal
Orders
Net AOV
Items Total(A)
Discount(B)
PC(C)
Tax(D)
Net Rev(E)
Gross Rev(F)
Disc%
Orders by date
Net revenue by date
Net AOV by date
Discount % by date
Comparative Trend
Previous
→
Orders by date
Net revenue by date
Discount % by date
Net AOV by date
Current
→
Orders by date
Net revenue by date
Discount % by date
Net AOV by date
Mealtime & Hourwise
Orders by meal period
Net revenue by meal period
Orders by day
Net revenue by day
Net AOV by day
Discount % by day
Orders & net revenue by hour
Net AOV & discount % by hour
Payout Recon
Outlets
Payout & orders per outlet for the selected window — Swiggy and Zomato side by side, linked by the RID sheet.
Outlet
Zone
Swiggy payout
Sw orders
Sw reports
Zomato payout
Zo orders
Zo reports
Total payout
Not in RID sheet
These platform ids have annexure data but no RID-sheet outlet — map Swiggy IDs in Data update → Restaurant data.
Platform
Rest ID
Name
Payout
Orders
Orders
Order ID
Date
Outlet
Status
Category
Item total
Discount
GST
Fees
Net payout
Settlement
Additions & deductions (non-order level)
Swiggy adjustments & ads investments · Zomato ADS, Hyperpure, other deductions and additions.
Outlet
Week
Section
Type
Ref / Invoice
Applies to
Status
Total
Adjusted
Outstanding
Admin Panel
ADMIN · MANAGER
Operations view — data freshness and report usage across all users. Not visible to viewers.
Report opens (all time)
Activity — opens per day (30d)
Usage by user
Every user's report opens — sorted by activity. "Top report" = the report they use the most.
User
Role
Total opens
Top report
Reports used
Last active
Cloud usage & billing — per user
Consumption counters behind the Cloudflare bill: every API request a user makes, and the database rows their queries read/write. Cost estimated at paid-plan marginal rates — Workers $0.30/M requests · D1 $0.001/M rows read · $1.00/M rows written. Plans include free quotas, so the actual invoice can be lower.
User
Requests (30d)
DB rows read (30d)
DB rows written (30d)
Est. cost (30d)
Est. cost (all time)
Last active
Data updated — dataset freshness
Dataset
Pushes
Rows added (total)
Time taken
Last update
Dataset health — missing dates & anomalies
For each dataset: calendar gaps inside its date range, days whose volume is far off the median (<35% = drop, >250% = spike), and data-quality issues. Red = needs attention, amber = worth a look.
Loading…
Recent data pushes
When
Type
By
Details
Added
User management
Add users and control which firms and restaurants each one can see (access = the union of both).
Add user
Firms
Restaurants
Reports
Users
Username
Role
Firms
Restaurants
Reports
Status
Last login
Active time
Actions
Edit access —
Firms
Restaurants
Reports
Data update
Edit brand / firm / zone / city / state / link for any restaurant. Rows still labelled “RID …” have no metadata yet — fix those first (use the Zomato link to identify them). Firm controls who can see a restaurant's data.
Bulk fill from CSV
RID-sheet format (Restaurant ID, Brand-Location, Brand, Firm, Zone, City, State, Zomato Link). Only missing fields are filled and new RIDs added — existing data is never overwritten and RIDs are never duplicated.
RID
Rows
Name (brand-loc)
Brand
Firm
Zone
City
State
Zomato link
Swiggy ID
Upload one or more settlements CSVs (the pipeline's finance_transactions.csv, or a Zomato "Transactions summary" exported to CSV) — you can select multiple at once. Rows with a duplicate Transaction ID are skipped. Firm / brand / slicers are pulled from the RID sheet via Res ID.
Expected columns
Header must include at least these (aliases accepted):
Transaction ID, Res ID, Date and time, Transaction Type, Bill Amount, Commission %, Commission Amount, Tax on commission, Net receivable, Settlement status, Settlement date, UTR
Upload CSV
Upload raw Swiggy "Order History" / past-orders CSV exports — one file per restaurant, and you can select many at once. The Restaurant Id is read from each file's header block; each order's item columns are exploded into one row per item. Duplicate orders (same Order ID & item position) are skipped. The outlet is linked to a RID-sheet restaurant via its Swiggy ID — set that in the Restaurant data tab so the data shows in the Swiggy report.
Expected format
A standard Swiggy order report: a metadata block (Restaurant Name, Restaurant Id, Duration…) followed by the Order ID, header row and one row per order, with item columns of the form name_reward_quantity_price+variants+addons.
Upload CSV
Upload raw Zomato order_history_*.csv exports (one row per order) — select one or more at once. Restaurant ID is the Zomato rid and links to the RID sheet automatically; any new outlet is added to the RID sheet (set its Firm afterwards). Duplicate Order IDs are skipped. Large files are uploaded in chunks.
Expected columns
Header must include (others ignored):
Restaurant ID, Restaurant name, Subzone, City, Order ID, Order Placed At, Order Status, Distance, Items in order, Bill subtotal, Total, Rating, Customer complaint tag, …
Upload CSV
Upload Zomato Enterprise Order Level *.csv exports (the Z Ent data dataset) — one row per order; select one or more files at once. res_id is the Zomato rid and links to the RID sheet automatically. Duplicate Order IDs are skipped, so re-uploading an overlapping export is safe. Large files are uploaded in chunks.
Upload Swiggy payout annexures (invoice_Annexure_<RID>_<DDMMYYYY>_….xlsx) and/or Zomato settlement reports (Zomato_Settlement_Report_<RID>_<start>_<end>.xlsx) — select many at once; the platform is detected from each filename. Files are parsed in your browser and only the extracted rows are uploaded. A file already ingested (same name, or same outlet + payout period) is skipped, so re-uploading a week is safe. This feeds the Payout Recon report.
Expected files
The original .xlsx files exactly as downloaded from the Swiggy and Zomato partner portals — Summary, Payout Breakup, Order Level, additions/deductions and Glossary tabs are read automatically (both the old and new Swiggy formats, incl. Toing orders, and both Zomato generations).
Upload annexures (.xlsx)
Refresh log
Every data push to the live dataset — item, restaurant, settlement & Swiggy uploads — across all users, newest first.