The orders page is the money view. Most of it is self-explanatory; three parts are not.
Leads versus paid
Leads are not failures to chase away — they are the most useful list on the page. Everyone in it gave you an email address and wanted a ticket, and both CSV exports at the bottom of the panel are there so you can do something about it.
Two warning tiles appear only when they apply: Awaiting UPI verification, and Paid but no ticket issued — the second is rare and worth opening immediately.
The filters are the URL
Search, status, ticket-email state and event are all query parameters, so a filtered view is a link you can bookmark or send to a colleague.
Search covers the order reference, the buyer's name and their email.
Filtering and paging both happen in the database
Search runs over every order you have, not just the ones on screen, so a buyer on page 9 is found by typing their name on page 1. The line above the table says which rows you are looking at — "showing 101–150 of 587 orders" — because a list that stays silent about where it stops implies it is showing everything.
Paging
The page number and the rows-per-page choice are query parameters too, so page 3 of a filtered view is a link like any other.
Changing a filter takes you back to page 1
Searching from page 7 cannot keep you on page 7 — a different filter is a different set of orders, and page 7 of it may not exist. Rows per page (20, 50, 100 or 200) behaves the same way, since page 3 of 50 is not page 3 of 200.
A page number past the end of the results shows the last page rather than an empty table, so an old bookmark still lands somewhere useful.
A delivery filter implies Paid, since an unpaid order has no ticket email. Where an order has both a failure and a success, "failed" wins — matching what the table shows.
The ticket email column
Per row, this cell is both a state and an action: Failed, a delivered timestamp, or Never sent, with Resend, WhatsApp and Forward myself buttons beside it. You can work a delivery backlog from this page without opening a single order.
Detail: Sending and resending tickets about sending and resending tickets.
A row awaiting UPI verification gets a different button
A row still waiting on you for a direct-UPI claim has no ticket to send, so this cell shows Tell them we got it instead — a WhatsApp message to the buyer saying their claim has arrived and is being checked against the bank statement. It carries no link; there is nothing to send them to before the claim is verified. Detail: Verifying a UPI payment about verifying a upi payment.
Exports
Two CSVs at the bottom of the stats panel: leads and paid orders. Both render from the form as it was at the time of the order, not from your current settings — so an export of a six-month-old event still shows the questions that event actually asked.