Events and ticketing

Catalogue → Events is for one-off rides, race days and parties customers book at your `/events` page. An event sells tickets by tier, per occurrence, and every ticket carries its own QR code. Events is marked beta in the admin.

Create an event

1. 1Open Catalogue → Events and press New event. Give it a Name and a Short blurb.
2. 2Pick a Ticket type. Named tickets: every ticket carries an attendee's name. General admission: tickets are anonymous, under the purchaser.
3. 3Set Capacity per occurrence and Max tickets per booking.
4. 4Fill in Location. Dropping a pin with Location on the map puts an "Open in Google Maps" link on confirmations and tickets.
5. 5Save, then add at least one occurrence and one tier before anyone can book.

• Hidden takes the event off your booking page; Accepting bookings pauses sales while leaving it visible
• The Waiver box takes wording for this event only. Empty, your shop-wide event waiver from Policies is used. Each attendee ticks their own box and the wording they accepted is recorded

Occurrences

• An occurrence is one running of the event on one date
• On the Occurrences tab, Add occurrence takes a date, a start time, an optional end time and a capacity, plus Repeat weekly for *n* more weeks for a series
• Capacity starts from the event default and is editable per occurrence
• Rows show how each is filling, as 12/40 sold · 28 left
• Cancel one occurrence and record the reason if the weather turns

Tiers, prices and sale windows

• A tier has a Name, an optional Description, and a Price per ticket in whole dollars. Price 0 is free, so customers skip checkout.
• Tier Capacity is optional. Blank limits the tier only by the occurrence capacity, which is how you cap an early-bird release without capping the event.
• Sale window takes On sale from and Off sale from times, in your shop's timezone. Leave either blank and the tier is on sale at that end.
• Which occurrences points a tier at every date or at one.
• A tier that has sold tickets cannot be deleted. Tick Hidden instead: new sales stop, sold tickets stay valid.

Whether money changes hands at booking is shop-wide: the Events chip under Require payment at booking decides it, and events charge the full ticket total rather than a deposit. See taking payments at booking.

Check-in on the day

• Ticket QR codes are emailed to the purchaser, with a plain link as a fallback for mail clients that strip images
• On the day, open Bookings, filter the type to Events, and press Scan tickets on the session you are running
• The scanner answers Checked in, Already checked in, Wrong day, Not valid for entry or Ticket not found
• Scanning belongs to the session, so a marshal on the door never opens anyone's order