Skip to main content
A recurring event creates occurrences: individual dated instances that customers book onto. Recurrence is set when you create the event, and can be Daily, Weekly or Monthly. See Create. Recurring events give you fine control over each occurrence.

​
The series and its dates

Almost everything about a recurring event belongs to a date rather than to the series: attendees, activity, the waitlist, notes and tickets sold are all per-date. The events list reflects this by showing a recurring event as one row per date, so most of the time you’re working on a date. The series page itself is about the run as a whole:
  • An Occurrences tab listing every date, with the upcoming dates alongside it
  • From and Until covering the whole run, the days of the week it lands on, and how many dates are scheduled
  • Total tickets sold, revenue and outstanding across every date
  • Available reads per date, for example 100 per date
To open the series from a date, use View parent event in the date’s Actions menu, or View all beside the recurrence line.
A recurring event is only finished once its last date has passed, not its first.
Your storefront and the API both read the dates Marzipan has generated, so they never show a date in a gap between ranges. Treat those dates as authoritative rather than working them out from the recurrence type and a start date.

​
Date ranges

A recurring event can run in separate date ranges while keeping one weekday pattern and one set of times. A venue that only opens during school holidays sets a range per holiday, rather than creating a separate event for each one and splitting its ticketing, waitlist and reporting across events that are really one product. Ranges are set under Dates on the event form. The first row is the event’s own first and last date, so it reads as one list with the rest. Use Add date range for each additional window, and Remove date range to take one out.
  • The end of a range must be on or after its start
  • Ranges can’t overlap
  • You can add up to 24 ranges
Once a second range exists, the first has to be closed with an end date. Leaving it open means it never finishes, so nothing after it could ever be reached. A single range with a blank end still means the event runs on indefinitely.
A range masks the pattern rather than restarting it. A monthly event keeps its day of the month across a gap, and a weekly event still lands on the weekdays you picked inside each window. The dates simply stop in the gaps and pick up again.
Removing a range reconciles like any other change to the pattern: dates in it that haven’t sold are removed, and dates that have sold tickets are kept and stay in your reporting.

​
Occurrence status

Each date carries its own status, using the same vocabulary as the event itself:
  • Active
  • Out of stock
  • Unavailable
  • Cancelled
Dates marked out of stock or unavailable stay listed on your storefront but can’t be bought, so a waitlist still works on them. Cancelled removes the date, and is refused once tickets have been sold.
Use out of stock rather than cancelled for a date you’ve filled by other means, since customers can still join the waitlist for it.

​
Editing one occurrence

Edit one occurrence to change a single date without affecting the others. You can change its:
  • Date
  • Time
  • Location override
  • Max tickets
Customised occurrence times are preserved. Editing one occurrence does not affect the rest of the series.

​
Editing all occurrences

Edit all occurrences to apply changes across the whole series.
Occurrences you have already customised keep their times, so a series-wide edit will not overwrite the individual changes you have made.

​
Generating more occurrences

Generate more occurrences to extend the series with additional dates.

​
Cancelling a single occurrence

Cancel a single occurrence to call off one date while leaving the rest of the series in place.