Part 1: What they actually bought
Tickets, seats and add-ons, line by line, with what each cost. The answer to "what did I pay for" takes one look.
Aftercare
Most of the work happens after the sale, and it is the part most tools leave to a spreadsheet.
Every Verimly order carries its items, its payment, its history and its notes in one place. Refunds — full or partial — are issued from the order and sync back automatically, disputes and fraud warnings are recorded against the order they belong to, and every buyer has a customer record with their whole history. Door sales and online sales are the same kind of order.
The numbers on the screen above mark the parts that do the work. Here is what each one is.
Tickets, seats and add-ons, line by line, with what each cost. The answer to "what did I pay for" takes one look.
Refund one ticket out of four, or the whole order. The figures recompute rather than being typed in, and the money goes back the way it came.
Created, paid, emailed, refunded, disputed — in order, with times. When something is contested, the record already exists.
Internal notes stay on the order. The colleague who picks up the phone tomorrow sees what was agreed today.
Every buyer has a record with their orders and their tickets, so a regular is recognisable and a question about last season is answerable.
Refunding one ticket out of four should not require a calculator and a note to self. Issue the refund from the order, and the totals, the payout figure and the reporting all recompute from what actually happened. Partial refunds, full refunds and repeated partials all end up consistent.
When a buyer disputes a charge, the case is recorded against the order it came from, with its current status. You are not reconciling an email from a payment provider against a row in a spreadsheet at the end of the month — the two are already the same thing.
Buyers are recorded as customers, with every order and every ticket they have ever held. A regular is visible as a regular, a complaint has context, and a question about a purchase from last season is answered without a search through email.
Cancel the event from its dashboard and work through the orders it produced. Cancellation and refund emails go out in your branding, the tickets stop being valid, and the reporting reflects the cancellation rather than pretending the sales are still real.
What you actually do, in order, the first time.
From the orders list, the event, or the customer record — whichever you have to hand.
Items, payment, history and notes are on one screen, not four.
Refund in part or in full, resend the tickets, or leave a note for whoever picks it up next.
Payouts, reporting and the customer record update from the same action.
| Orders | Online and door sales in one list, with the same detail |
|---|---|
| Refunds | Full or partial, issued from the order and synced back automatically |
| Disputes | Recorded against the order, with their status kept current |
| Fraud warnings | Surfaced on the order they relate to |
| History | Every state change kept with its timestamp |
| Notes | Internal, per order, for the person who picks it up next |
| Customers | A record per buyer with their whole order history |
| Abandoned carts | Kept with what was in them |
| Cancellation | Cancel an event and refund from the orders it produced |
Yes. Refund a single ticket, several, or the whole order. The totals recompute from what was actually refunded rather than being entered by hand.
The refund returns the buyer's money through the same payment method. Your payout is recomputed to reflect it, so your reporting stays consistent with the money that moved.
It stops being valid, and a scan at the door fails. The seat, if the event is seated, returns to availability.
The dispute is recorded against the order with its current status, so you have the order, its history and its emails in one place when you respond.
Yes. Ticket access can be sent again from the order, without reissuing anything.
Yes. Customer records belong to your workspace, and exporting them is not something you have to ask permission for.
Get started
No subscription, no setup fee, nothing to cancel. Build the whole thing, and decide at the end whether to publish it.