Paid event operations tend to get messy fast. Pricing rules live in one place, discount logic in another, and inventory problems usually show up at the worst possible moment.
This update makes paid ticketing more usable for organizers, clearer for attendees, and safer during checkout.
If you are selling tickets, the important part is not just taking payment. It is keeping pricing, availability, and registration behavior aligned.
Why it matters
For many organizers, paid registration is not just “set one price and hope for the best.” You may need early and standard tiers, promo codes for specific groups, comp access for partners or speakers, and a way to see what actually sold afterward.
This changelog adds more control on the organizer side, while making the attendee checkout flow more predictable.
What changed
Organizer: More control over paid ticket setup
- Ticket tiers: organizers can now create ticket tiers with pricing, sales windows, caps, statuses, and archiving.
- Discount codes: organizers can create fixed-amount or percentage discounts, set usage limits, and target specific tiers.
- Comp tickets: organizers can manually grant complimentary tickets, including tier assignment and issuer details, with reporting visibility.
- Sales reporting: ticket sales reporting now breaks out activity by tier, discounts, and comps, with CSV export available.
Attendee: Clearer ticket buying during registration
- Tier selection: attendees can choose a ticket tier during registration.
- Discount entry: attendees can enter a discount code and see the server-calculated total before checkout.
- Group quantities: attendees can buy multiple tickets in one purchase, then assign attendees after payment.
Payments and reliability: Safer checkout behavior
- Reserved inventory during checkout: ticket inventory is reserved while Stripe Checkout is open.
- Inventory release on failed checkout: reserved inventory is released if checkout is cancelled, expires, or fails.
- Idempotent payment confirmation: payment confirmation now avoids double-confirming registrations or inventory if webhook events are replayed.
Good checkout behavior is quiet. People should not have to think about inventory races or duplicate confirmations.
What this helps with in practice
These changes are useful for organizers running paid events with more than one audience or offer. A few examples:
- selling early, regular, or VIP access as separate tiers
- offering promo codes to sponsors, partners, or member groups
- granting comp access without losing reporting visibility
- letting one buyer purchase for a group, then assign attendees afterward
- reducing oversell risk while payment is in progress
In other words, less ticketing guesswork, and less cleanup after the fact.
Availability
These updates were recorded in the Bewitt product changelog on 2026-07-05.
If you want to see how Bewitt handles paid registration, ticket setup, and reporting, you can Book a Demo or start an event.
