Knowledgebase

Event and Ticketing Applications Print

  • otherapplicationsscripts, other, email, cron, billing, cdn, refund, guide
  • 0

Selling tickets or managing bookings.

WHAT IT REQUIRES

Event listings with dates and capacity Ticket sales, with payment Capacity management, preventing overselling Confirmation and reminder emails Check-in, at the event

THE CRITICAL PART

Capacity. Two people buying the last ticket simultaneously must not both succeed. Check how the application handles this before relying on it.

PAYMENT

Confirm your gateway is supported. Test a real purchase and refund before selling to anyone.

EMAIL

Confirmations must arrive, and must contain whatever the attendee needs. Test to Gmail and elsewhere.

Reminders depend on cron. Configure the real cron job.

TRAFFIC SPIKES

Ticket sales for a popular event produce a sharp spike. A shared plan may struggle at the moment sales open.

Tell us in advance if you expect this, and consider a CDN.

AFTER THE EVENT

Attendee data is personal data. Do not keep it indefinitely without reason.

TESTING

Buy a ticket yourself, receive the confirmation, and check in. The full cycle, before selling one.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot