GaiabyO2
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.
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.
| Item | Complaints | Orders | Restaurants | Units sold | Rate |
|---|
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.
| Customer ID | Orders | Items | Complaints | Restaurants |
|---|
| Date | Order ID | Restaurant | Items | Qty | Rating | Complaints |
|---|
| Item | Qty | Orders | Rating | Complaints |
|---|
| Date | Txn ID | Type | Restaurant | Bill | Comm % | Commission | Tax | Net | Status | Settled |
|---|
| Item | Units | Orders |
|---|
| Swiggy ID | Name | Orders |
|---|
| Restaurant | Orders | Units | Revenue | Avg rating |
|---|
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.
| Brand-Location | Month | Status | Portal | Orders | Net AOV | Items Total(A) | Discount(B) | PC(C) | Tax(D) | Net Rev(E) | Gross Rev(F) | Disc% |
|---|
Operations view — data freshness and report usage across all users. Not visible to viewers.
| User | Role | Total opens | Top report | Reports used | Last active |
|---|
| User | Requests (30d) | DB rows read (30d) | DB rows written (30d) | Est. cost (30d) | Est. cost (all time) | Last active |
|---|
| Dataset | Pushes | Rows added (total) | Last update |
|---|
| When | Type | By | Details | Added |
|---|
Add users and control which firms and restaurants each one can see (access = the union of both).
| Username | Role | Firms | Restaurants | Reports | Status | Actions |
|---|
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.
| 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.
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 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.
Order ID, header row and one row per order, with item columns of the form name_reward_quantity_price+variants+addons.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.
Restaurant ID, Restaurant name, Subzone, City, Order ID, Order Placed At, Order Status, Distance, Items in order, Bill subtotal, Total, Rating, Customer complaint tag, …
| When | Type | By | Details | Added | Dup |
|---|