The Night, and the Money After It

Revenue used to sit in a 14-day settlement hold counted from the ORDER, so a ticket bought three days before doors held your money for another eleven days after the night had already happened. That hold exists to cover a cancellation or a postponement and the refunds either would trigger — once the event has run, it is measuring nothing. Settlement now happens on whichever comes first: fourteen days after the order, or the day after the event. A finished event is payable in full. On live data at the time we shipped it, this released $4,155 being held for a night that had already been danced. The event reserve follows the same rule and is released on the same day.

When Rameelo closes out one of your events you now receive a statement rather than a number. It is a single ladder you can read top to bottom: gross ticket face value, less discounts, less refunded tickets, less disputes, then the refund fees you absorbed, then any marketing cut from ticket revenue, then any adjustments, ending at the net settlement due. It is ticket FACE VALUE throughout — the platform fee and the card fee the buyer paid on top are stripped out entirely, because they were never yours and listing them would only invite subtraction. Alongside the ladder is your organization-wide payout position: paid to date, approved and awaiting payment, still under review, and available now. A statement is frozen when it is sent, so a refund issued next week cannot quietly rewrite the copy already in your inbox.

Refunds no longer require emailing us. From any order in your portal — the org-wide Tickets list or an event’s Orders tab — you can refund at face value, in two steps that end in typing the word REFUND. Face value is deliberately the only refund an organizer can issue: it is the one whose cost comes entirely out of ticket revenue you already control, so you can never accidentally bill yourself fees or hand back part of a card fee Rameelo already paid. The screen states plainly what leaves your revenue, what the buyer does NOT get back, and that $0.00 is billed to you. Three emails go out automatically — to the buyer, to your whole team, and to us — all built from one place, so nobody is reading a different account of the same refund. A refunded order then says so on its own page: the amount returned, the date, and the fact that it has left every sold and revenue figure.

Open any order and you can see its whole history — every email it generated and every change anyone made to it, in one timeline: repriced, refunded, moved to another event, cancelled, details corrected, with who did it and when. It is written by the database itself rather than by whichever tool made the change, so nothing can happen to an order without leaving a trace. Crucially, you and the Rameelo admin looking into the same order are reading the exact same list — the question “what happened to this order” now has one answer.

The most important number on your dashboard was wrong, in the direction that matters. It counted platform ticket sales and nothing else, so comps and manually issued tickets were invisible and a multi-night pass counted on one night only. One live event reported 37 tickets when 91 people were entitled to walk in; another showed 7 sold on a night 26 pass holders could attend. The headline is now the TOTAL of every settled order, with sold tickets, comps and manual entries each keeping their own labelled line so you can always see why the total is larger than what Rameelo collected. A four-night pass is counted as one sale and four admissions — separate figures, never added together, because a pass is one payment and four people through a door on four different nights. Money is still booked once, on the night the pass was bought, and the page says so out loud.

The scanner was rebuilt around what actually happens at a garba door. There is now exactly ONE way to scan, and it is full screen — the page used to carry a second, smaller viewfinder halfway down itself, and volunteers worked the queue in the small one, where the verdict was the width of a paragraph. The viewfinder is magnified and fills the phone; the only thing inside it is the whole event’s check-in count, small and tight to the top edge. Every verdict floods the bar under the camera with colour, because a chime is useless next to a dhol: GREEN for admitted, RED for every refusal. Amber is gone entirely — an already-scanned ticket used to arrive in amber, which at arm’s length reads as “hmm, maybe”, and guests were being waved through on the strength of it.

The most serious fix in this release, and worth stating plainly. Admission used to be a counter: scanning a ticket set a number, so the same QR code scanned four times admitted four people, and nothing on the door screen looked wrong. One forwarded screenshot could walk a whole group in. Admission is now recorded per individual ticket, and a duplicate is impossible at the database rather than merely discouraged — the second scan of the same seat is a refusal, with the time it first went through and who let them in printed on the bar. Related: every transferred ticket now carries its own QR code. Previously every recipient of one order was shown the same code, so on one live order with seven accepted transfers, the first person through the door was admitted and the other six were rejected as already scanned.

Tap the verdict bar on a refusal and you get one flat panel — no expander inside an expander — led by the number the person on the door actually needs: how much of this guest’s party is already in (“23 of 50 tickets checked in · 27 still to come”), counted across every order they placed for tonight rather than only the one they scanned. Then why it was refused, then when it already went through and who admitted them, then the plain facts. Nothing on the scan screen has to be dismissed before the next guest can be read: the popup that used to stop the queue for an acknowledgement is gone.

Check-in reaches every event you run, current or past, for every member of your team — owner, admin, member and scanner alike, plus the event’s own owner. Two things were wrong before: an event carrying no organization locked out the very person who created it, and the event picker was date-bounded, so a night that ran late could not be reconciled the next morning. Both are fixed, and the picker now lists every event holding at least one admissible ticket, tonight and ahead first, then history.

Beyond the totals and the per-scanner tallies, Door Progress shows what just happened and who did it, across your whole organization, in a history that pages back through the entire night. It refreshes by merging new scans in at the top rather than replacing the list, so someone reading back through an hour ago is not yanked to the top every twenty seconds. There is also a missed check-in report: who did not scan, and how much of their order did.

Walk-ups are real: people buy at the gate an hour into a garba night. Sales now close at the end of the event in the event’s own city rather than at doors-open, and one single instant decides both “has this ended” and “is this still selling”, so a page can never tell a buyer the event is over while it is still taking money. A multi-night run stays live mid-run. And when the times on an event row are simply wrong, there is now a manual override that keeps it selling regardless of the clock — a deliberate human decision that does not expire, and every surface reading it says out loud that it is on.

A flash sale is a ticket tier with a start and end INSTANT rather than a date, because a Labor Day special sold on a countdown needs an hour, not a day. While the window is live, that tier is the only single-event ticket on sale: every other tier on the event is paused no matter what its own dates say, which is what makes the price on screen the price. Paused is its own state and says so — nothing sold out, and nothing closed on its own schedule. Multi-night passes are never paused, since a pass spans nights that may have no flash sale at all, and no promo code stacks on a flash price. The saving a buyer is shown is worked out live against the cheapest tier the flash is blocking, so it can never advertise a discount that stopped being true when a tier was re-priced. Ask us and we will set one up on your event.

For the case that keeps happening: early bird is re-opened after someone already paid the regular rate. Rameelo can now re-assign an order to a different tier on the same event and restate what each ticket was worth, without touching the card transaction — the difference is settled with the buyer directly, and the correction flows through every revenue figure you read, because it is the ticket face value that moves. How the difference actually settled is recorded too, not just ticked off: Zelle, Venmo, cash, check or card, with the amount, so it can be reconciled against a bank statement six weeks later.

A comp now carries a kind: your own giveaway, or a seat the platform took. They are reported on separate lines everywhere, because folding them together overstates what you gave away, and neither is ever revenue. An organizer cannot move their own giveaway onto Rameelo’s line, and a Rameelo team ticket is never emailed to anyone.

Not every marketing service is bought through the portal — sometimes it is agreed on a call. Anything Rameelo charged you now appears on your payouts page with how it settles, and only the charges actually being cut from ticket revenue reduce your balance; anything paid by card or Zelle is listed for the record and deducted from nothing. A balance smaller than you expected must always have a line beside it explaining why.

An artist change after tickets are sold is now the one event field with a full change trail, and the people who already paid are told what it means for them: their existing tickets still work with the same QR codes, and the price they paid is honoured, early bird included. Multi-night pass holders are included and are shown which night of their pass changed — “the artist changed” is unusable to a four-night pass holder who does not know which night. Your event page also names the previous artist, because someone half-remembering a different name needs the page to confirm it.

Two smaller additions on the marketing side. The countdown blast is a flat-priced last-week push where the number of days is computed at the moment it sends rather than when you bought it, so the inbox is always right. And Rameelo can now send you a guide to the attendee-facing information still blank on an upcoming event — directions from the highways, drive times from nearby cities, landmarks, parking, arrival and check-in — listing only what is actually missing, with the exact place in the portal to fill each one in.

Onboarding an organizer is a conversation about dates, venues, artists and payouts, so the public front door collects the answers and a human replies, instead of handing out a self-serve account nobody could use yet. Applications land in the admin queue as a pending organization and are surfaced so they cannot be missed — an application nobody notices is an organizer we lose.

Buyers were going home with the wrong ticket. The event page used to sell multi-night passes in three places at once — a priced picker above the fold, a teaser card in the ticket column, and the combo half of a price toggle — while the single-night ticket sat quietly as a pre-selected default, so people who came for one night checked out holding a pass. The event page is now a page ABOUT the event: no tier list, no stepper and no prices, just the date, one Buy tickets button and plain-language signals (“$5 off each on 10+”, “a multi-night pass exists”). Everything priced lives in one modal, and when an event has both options the first screen is a choice with nothing pre-selected, the two options carry equal weight, and the dates are always on screen — “Just this night” names the night, the pass names every night it covers. On a phone it is a full-screen takeover whose footer restates the quantity, the ticket and the night right above the pay button.

Eight separate card islands became one continuous page, the mobile action bar stays pinned to the bottom instead of floating mid-screen, the cover is given back to the artist artwork rather than cropped into a banner, and the popups no longer interrupt someone who is reading. There is also a direct line to a human as the second action on the page — a WhatsApp message about group rates, already typed.

A bottom tab bar on mobile with everything else tucked under Profile, every ticket for one event gathered into a single card instead of scattered down the page, a much bigger QR code, and a Garba Passport stamp that lands by itself. Tickets also stay in your active list until the event actually ends, rather than disappearing on the morning of the night you are going.

The optional donation at checkout is always removable in one tap, and organizations can now choose whether it arrives pre-ticked for their events at all. The amounts, the causes and the receipt are identical either way. Donations are separate money from the beginning: never folded into a ticket price, never reaching an organizer’s payout, and the buyer’s receipt names the organization and the amount as the written acknowledgment a tax-deductible gift requires.

Members stay signed in for 30 days instead of being logged out constantly, and signing in — along with every signed-in surface behind it — now runs on one canonical rameelo.com address, so a session started in one place is not silently invisible in another.

The Add to Apple Wallet button has been taken off member tickets rather than left in place half-working. A Wallet pass is a live document that keeps showing whatever it last fetched, so getting it wrong means a refunded ticket sitting in someone’s Wallet looking valid indefinitely. Tickets live in the member portal until we are confident in it.

Public listings were judging “is this event over” against a UTC date, which rolls over at 5 PM Pacific — so a live Los Angeles event flipped to its “This event has ended” recap, taking every buy button with it, before doors had even opened. One definition now answers that question, in the event’s own city, and last night’s event stops being advertised across ten public surfaces the following morning.

Stated plainly, in the same spirit as last release’s recipient-list bug. Every headline on the Rameelo admin dashboard was counted in the browser from a query that stops at 1,000 rows with no error, so “Total Users” read 1.0k against 3,146 real profiles and had not moved in months — and the ticket and profit figures were one busy month away from silently understating in the same way. Everything is now aggregated in the database, and the tiles state exact numbers with separators rather than a rounded “1.0k”, because an abbreviation is what let a broken count pass for a tidy one.

Rameelo now ranks the events people keep asking us for tickets to but which we do not sell, counted one entry per person and mailed as a daily chart with real day-on-day movement. Every other report we have is built on orders that DID happen, which makes this demand invisible everywhere else.