A weekly class, a six-week course and a prepaid visit pack can all appear on the same calendar, but they promise different things. A drop-in purchase reserves one date. Course enrollment may include every date. A visit pack lets the customer choose eligible sessions later, subject to availability. The software needs to preserve the promise you sold.
For a yoga studio or workshop business, Gomry combines scheduled Experiences with prepaid Bundles and separate Event tickets. A customer can use Bundle credit for an eligible weekly session and buy a separate ticket for a public workshop. The Bundle does not cover one-off Event admission, and buying credit does not automatically reserve every date in a course.
Before comparing platforms, decide which of those offers your customers need. For a fixed course, check the course-registration requirements, including whether one purchase secures all sessions. For flexible attendance, examine eligible sessions, capacity, credit expiry and what happens after a cancellation. If recurring billing is required, evaluate it separately from the rules that grant access.
The comparison below starts with those buying and attendance rules. You can also compare the wider selection of class and workshop platforms. Once the offer is clear, test a changed date and a canceled booking so staff can explain the customer's remaining place, credit or payment.
Compare recurring-event platforms and their integration boundaries
Ticket Tailor documents repeated occurrences and exposes event-series and occurrence tools through MCP. Bookwhen combines schedules with passes and memberships; its published public API is read-only. Eventbrite combines ticketing with a discovery marketplace. Gomry separates scheduled Experiences from ticketed Events and offers authenticated organizer tools alongside a consumer-event commerce interface.
| Your priority | A useful comparison |
|---|---|
| Repeated ticketed dates | Ticket Tailor’s occurrences against the intended Event or Experience model in Gomry |
| Existing class packs | Bookwhen pass rules against eligible Gomry Experience Bundles |
| Marketplace discovery | Eventbrite’s actual booking contribution against proposed additional channels |
| Agent-operated workflows | The exact MCP or API actions, permissions and resulting booking records |
Keep the offer clear: Gomry Subscriptions combine recurring billing with Experience access, while Membership Levels assign an organization-wide member status. Both are available; neither should be confused with a reservation for every date on the calendar.
First, decide what “recurring” means for your offer
| Offer | What the customer buys | The system model to validate |
|---|---|---|
| Weekly drop-in | One place on one date | Separate occurrence, its capacity, and its change rules |
| Rolling time slots | Access to a chosen time | Inventory and availability across many slots |
| Multi-week course | One commitment covering several sessions | One enrollment plus attendance or completion across dates |
| Monthly membership | Ongoing eligibility or credits | Membership state plus booking and cancellation rules |
| Seasonal program | A defined set of dates with occasional exceptions | Shared setup with controlled overrides |
How the purchase determines the schedule
Repeated dates are not automatically one course
Ticket Tailor's recurring occurrences share core event details and ticket setup. An occurrence can be available or unavailable, visible or hidden. Its documentation separately advises using a single event when one ticket includes several weekly course dates.
That distinction matters to the buyer: choosing one occurrence buys admission to that date, while course enrollment promises the included sequence. In Gomry, a Bundle gives credit for eligible Experiences. The customer still chooses an available session and reserves a place; buying the credit does not reserve every date in a course.
Prepaid credit and recurring access remain separate purchases
Gomry Bundles hold a finite prepaid balance for one Experience or a selected pool. Subscriptions combine weekly, monthly or yearly billing with unlimited Experience access or a visit allowance per cycle. Membership Levels provide organization-wide member status independently of those class purchases.
Use a Bundle when customers prepay and decide on eligible dates later. Use a Subscription when the offer renews with defined access each billing cycle. Neither purchase should be described as automatic enrollment in every future session.
A change of attendee is not a change of date
For eligible Gomry Event tickets, guests can start a transfer to another person. A change of ticket holder is separate from moving to another date or transferring prepaid Experience credit.
A canceled booking and a refunded payment are also separate records. The customer's policy must distinguish a released place, remaining visit credit and money returned. No single “canceled” label tells the customer which of those outcomes applies.
Full sessions and waiting lists
A waitlist entry is not a confirmed booking. A customer still needs a reserved place before attending.
A class business relying on automatic waitlist promotion needs that workflow included in its booking setup. Punchpass and Momence describe their own waiting-list processes; the timing of an invitation and the allocation of a place are separate parts of that process.
Capacity still belongs to the booked date. A customer's unused credit or member status is not a reserved place in a full session.
At the entrance and in the customer record
After a date or attendee change, staff need the current admission record, not only the original confirmation. Gomry's online scanner reads the current attendee record; the check-in guide explains roles and exceptions. Contacts provides customer context, while refunds remain in payment records. Keep those records distinct when resolving a changed booking.
Give customers a clear date, time, location and purchase entitlement in the event or activity information. A series page should not imply that a ticket, credit balance and membership all grant the same access.
Integration boundaries
Gomry's API introduction documents organization-scoped API keys and resources including events, attendees and ticket classes. Use these resources for the documented Event operations. Experience bookings, memberships and accounting need their own supported interface; they are not interchangeable with Event-ticket operations.
Bookwhen's published public API is read-only and directs booking through its booking page. Ticket Tailor publishes organizer MCP tools for event series and occurrences. An interface that retrieves a schedule and one that changes an occurrence therefore support different work.
A website displaying a read-only schedule still sends customers to the booking page to reserve. Tools that can change an occurrence instead let authorized staff update the date itself. These are different integration tasks.
A controlled launch plan
Launch a single series first. Keep the policy set small: one cancellation rule, one membership rule if needed, one waitlist rule, and named people for support and finance. Run staff through test purchases and changes before opening sales. At the end of the first cycle, reconcile the records and list every manual intervention.
Expand after the team has resolved the exceptions found in the first series.
Frequently asked questions
Can recurring events have different prices?
They can, but the important detail is scope: does the price change apply to the whole series, selected future dates, or one occurrence? Test it before publishing a promotion.
Should every date have its own URL?
Not necessarily. A stable series page can be clearer for a repeating offer. Create distinct pages only when dates genuinely have distinct intent and content; otherwise avoid thin, duplicative pages.
Do I need memberships for repeat customers?
Use memberships when repeat access changes price, booking rights, limits, or cancellation treatment. A straightforward bundle or multi-date ticket can be sufficient for a simpler offer.
How should a recurring-event refund policy work?
Define notice period, refund or credit treatment, waitlist actions, staff ownership, and customer communication before setting the automation. Local consumer rules may affect the policy, so obtain appropriate advice.
What data should be portable?
Future occurrences, event settings, customers and consent, orders, attendees, attendance or check-in data, payments, refunds, and membership balances where applicable. Check whether relationships survive the export.
Configure a short series, change one date and cancel one booking. Ask staff to identify the current information and remaining entitlement before opening the rest of the calendar.
Choose Gomry for repeat attendance with clear booking products
Set up the next short series in Gomry Experiences. Check a date change against an existing booking, then confirm the credit or payment outcome of a cancellation before opening the full schedule.