Sell a class, a tour or a run of shows from a single page. Set the pattern once and the dates build themselves, with timed-entry windows, a cap per window, and a waitlist when one fills up.
Almost every hard question about a repeating event turns out to be the wrong shape rather than a missing feature. These three are not interchangeable, and the one you choose decides what the buyer sees and how much work you inherit.
A single event page that sells across a schedule. The buyer picks their date on the page and the ticket carries it. Timed-entry windows live here too, set on the schedule and applied to every date.
Skip this if every date has a different lineup, price or room. Those are separate events, and forcing them into one series makes them impossible to describe on the page.
Sub-events. One event split into sections, each with its own page, description and set of tickets.
Skip this if the sections are on different days. Dates belong to a schedule, not to a section, and using sub-events as a calendar is how one page ends up describing six unrelated nights.
A collection. Separate events, each complete on its own, grouped behind one shareable page.
Skip this if the events really are the same event on different dates. A collection groups things that stand alone, and using it for a weekly class gives you a hub of fifty near-identical pages to maintain.
Nothing is saved and nothing is sent. It walks the same decisions you would work through above, and it applies the two rules you cannot undo before you build anything.
Does the same event happen on more than one date?
The same event means the same description and the same tickets. Only the date changes.
This picker needs JavaScript. The three shapes above cover the same ground, and the section below spells out the two rules it applies.
Everything below ships today. The schedule builds the dates, the dates carry the orders, and timed-entry windows decide how many people arrive at once.
Describe how the event repeats and the dates are built for you, in the event's own time zone, up to the day you say it stops.
Repeat every day, every week or every month, or build a custom pattern from an interval and the specific weekdays it lands on. Every two weeks on Tuesday and Thursday is a pattern you can describe.
The series runs until the date you set and stops there. Nothing keeps generating quietly in the background after the run is over.
Dates are generated in the event's own time zone, so a seven o'clock class is seven o'clock where the class is, whatever the server thinks the time is.
The pattern is stored as an RRULE, the same repeat format calendar applications use, so the schedule stays readable outside this platform instead of being a private format.
Occurrences are generated about ninety days ahead and extended as time passes, up to the end date. A two-year series does not create seven hundred pages on the day you save it.
Only dates that do not already exist get created, so extending the window is safe to run again and cannot double anything up.
Set who runs the series once, then swap in a substitute for a single date without touching the rest of the run. That date remembers the substitute; every other one keeps the default.
Your event has one address, one description and one set of tickets. The date is a choice the buyer makes on the page, and it follows their order all the way to the door.
Every upcoming date is listed and labeled the way a person reads it, like Wed, Mar 5 at 7:00 PM, with the time zone spelled out.
Each date has its own address, so an email about Saturday can send people to Saturday instead of to a picker they have to read.
The chosen date shows in the cart, on the ticket and in the order, so no one is left holding a ticket that does not say which night it is for.
The add-to-calendar link is built for the occurrence they bought, not for the series, so it lands on the right night.
Recurring events appear in search and browse with their upcoming dates, rather than sitting behind a single stale start time.
Each occurrence has its own attendee list, so the door on Tuesday is not looking at everyone who ever bought a ticket.
Slots are how you stagger arrivals. Each window has a cap counted separately from your ticket types, which is what lets you sell three hundred tickets into a room that holds sixty at a time. Windows are set on a recurring event's schedule and apply to its dates, so timed entry starts by making the event recurring.
Windows belong to the schedule, not to a single date, so an event needs to be recurring before it can have them. A daily tour is a daily recurring event with windows on it.
Add entry windows with a start and end time and a limit on how many people can book each one. The cap is on the window, counted independently of which ticket they hold.
Give a start time, an end time and an interval and the windows are generated for you, down to five-minute spacing.
Limit a window to particular ticket types, or leave it open to all of them. A members-only early window is a list of ticket types, not a separate event.
Close a window a set number of hours before it starts, so no one books the 9 AM tour at 8:55.
The series carries the usual windows and any single date can have its own set instead. Clear the override and that date goes back to the series.
Ask for four places in a window with two left and the quantity is reduced to two, with a notice saying so, rather than the order going through and the problem surfacing at the door.
If your window capacities add up to less than your ticket capacity, you are told the moment you save, because otherwise buyers get blocked from booking a window after the tickets are gone.
When a window fills, people can join a waitlist for it. If a booking is canceled or refunded, the first person waiting is emailed a link straight back to that date and that window.
Everyone holding a window gets an email the day before, naming the window they booked.
Download the summary of who booked which window, for the people running the door.
Both of these are enforced on the server, and both are usually discovered after an event has been built. They are here rather than in a support article because they are decisions, and the moment to make them is before anything exists.
An event created as a one-time event cannot be turned into a recurring one later, and a recurring event that has already generated dates cannot be turned back into a single one. Both are blocked on the server rather than being discouraged in the interface.
What to do: If you are unsure, ask whether the same event repeats on a pattern. If it does, create it as recurring from the start. If it does not, a collection groups separate events later without needing anything decided now.
A seat map belongs to one date. Assigned seats and a repeating schedule are mutually exclusive here, and choosing Reserved Seating turns the recurring option off in the create-event screen rather than letting you build something that cannot work.
What to do: For assigned seats across several nights, create an event per night and group them in a collection. Each night gets its own map, its own holds and its own manifest, which is what a seated run needs anyway.
A weekly class sold from one page, with each week its own date, its own roster and its own door list.
Timed entry through the day, with a cap per window, a booking cutoff, and a waitlist when a window fills.
A run of the same show across several nights, promoted as one page, with a link that goes straight to a chosen night.
Sessions that repeat on a pattern, each with a limit on how many people can be in the room at once.
A recurring market where each date sells its own stalls and its own entry.
Independent nights, each complete on its own, grouped behind one collection page you can share.
A program split into sub-events, each part with its own page, description and tickets.
Appointments, fittings, consultations and inspections, booked against windows with a cutoff.
A recurring event is still an event. Everything you use to promote it, staff it and run the door works the same way, one date at a time.
Collections, QR codes, discount codes and the rest of the promotion around a series.
See marketing toolsSeat maps and assigned seating, for the single-date events a seated run is built from.
See reserved seatingSet the pattern, add your entry windows, and sell every date from one page. Free to start, with no monthly fee, and every date's money deposits into your own account as it clears.