Class Registration Software: Choose the Right Booking Model

Class registration software should make three things clear: what the customer bought, which dates are reserved and what the instructor needs to know about each participant. The right system depends on whether you sell flexible visits, enrollment in a complete course or programs with family and student records.

A five-visit drawing pack lets the buyer choose eligible dates later; a five-week course promises a place in a defined sequence. This guide compares those registration models. Gomry fits recurring adult classes, prepaid visits and separately ticketed workshops. Bookwhen belongs on a course-and-session shortlist; Jumbula and CourseStorm address family or education registration; Arlo focuses on training providers.

Compare the registration models

Bookwhen's feature list distinguishes course tickets from passes for future bookings. That matters when you sell both a complete beginner course and flexible attendance: customers should not need to guess which dates their purchase reserves.

Jumbula is relevant when registration centers on families and multiple classes. CourseStorm's arts offering connects family registration with instructor rosters and automated payment plans. These are different requirements from simply collecting an adult's name and payment for one session.

Arlo addresses training administration, including registration and invoicing. If completion certificates or formal assessments determine your choice, establish their exact requirements separately; a paid registration does not prove completion.

For children's programs and materials, the art class registration guide develops the family and instructor requirements in more detail.

How classes and prepaid visits work in Gomry

Use Experiences for scheduled sessions with a host and a capacity per slot. Add Bundles when customers should buy several visits now and choose eligible dates later. They sign in, select an available session and apply credit. A pack can cover one Experience or a selected pool, with an optional expiry.

For example, a drawing studio could include its Tuesday and Saturday sessions in the same pack. A customer buys five visits, books Tuesday and retains credit for later eligible bookings. Buying the pack does not reserve every Tuesday or guarantee a place in a full session.

A visiting artist's separately ticketed workshop uses Events. Bundle credits do not pay for that ticket. Keep the distinction beside the offer, so the customer knows which purchase to make before checkout.

For eligible Event tickets, guests can transfer a ticket from the ticket page or app. The recipient signs in to accept before the attendee list, exports and scanner update. Transfers are on by default and can be disabled per ticket class. This is a change of ticket holder, not a transfer of class credit or a move to another date.

For students returning regularly, Gomry Subscriptions combine recurring billing with unlimited access or a per-cycle allowance for Experiences. Membership Levels assign an organization-wide member status; Bundles provide prepaid visits. These products are available, but they do not create family accounts or enroll a student in a fixed sequence of dates. If guardian administration, automatic tuition installments or formal training records drive the purchase, prioritize those requirements in the shortlist above.

Keep scheduling, registration and payment connected

Class scheduling software records when a session runs, who teaches it and its capacity. Registration identifies the people expected there. Payment records what has been paid, remains due or has been returned.

Consider a drawing class with 12 workstations. A second instructor does not create a thirteenth workstation. If another activity uses the same room, separate capacity limits on the two booking pages do not establish shared-resource protection. The studio needs either a supported shared-resource rule or a timetable that allocates those workstations without overlap.

A cancellation also has more than one consequence. The place may become available again, while the customer's payment or credit follows the cancellation policy. A submitted form is not proof of payment, and a refund is not proof that a reservation was removed. Before opening sales, run one cancellation and inspect all three records together.

Online class registration and payment should finish with a confirmation that identifies the session, participant, price and purchase status. For a course, include all reserved dates. For a pack, explain that the customer still needs to book sessions.

Give the instructor a usable participant list

The payer and participant can be different people. If one person registers three attendees, the instructor needs three identifiable participants and their relevant information, not just the buyer's name.

The same applies to preparation. A materials choice belongs with the person using that kit. The creative-workshop guide follows these choices into the staff handoff. Limit instructor access to the information needed to run the session rather than exposing unrelated financial or personal data.

For a class scheduling app, the useful mobile test is specific: a customer can understand and book the offer, and an instructor can find the current roster after a change. A native app badge alone answers neither question.

Compare the cost of your actual program

Use the same sales volume and requirements for each quote: platform charges, payment processing, staff access, paid add-ons and migration. Include family or training administration if it is essential; a cheaper booking-only setup is not equivalent if it leaves those jobs elsewhere.

Gomry's pricing page sets out current service fees and payment processing. Tap to Pay is available in the US for contactless phone payments, subject to device eligibility. It supports reception payments; it does not turn a sequence of charges into an installment plan.

The Bookwhen comparison expands on the choice between subscription and transaction-based costs.

When a form is enough, and when to move

A small, free session with stable attendance may work with a form and a clearly owned participant list. Someone still needs to close registration and communicate changes. A booking platform becomes useful when payments, limited places, repeated dates or customer changes make that manual process unreliable.

When moving, carry over the commitments, not just customer names: future reservations, unused visits, unpaid balances and recurring payment arrangements. Reconcile them before changing the public booking link. Assign one system to own availability for each session so both systems cannot sell the same remaining place.

For a recurring workshop, see the workshop booking guide. For class levels and social admission, use the dance studio guide.

Optional: working through an AI assistant

Teams that want to use compatible assistants can use Gomry MCP for documented event, attendee, contact and reporting operations under their account permissions. This is an additional way to work with records, not a replacement for the registration model above.

Consumer commerce is separate: connected applications can use supported event listings and an enabled checkout integration or a link into Gomry checkout. Listing coverage and direct checkout access depend on the application. A search result is not a confirmed registration. The agent-readiness article contains the dated September 17, 2026 assessments and their scope.

For adult classes with flexible return visits, start with one session in Gomry Experiences. Make its capacity, purchase and cancellation terms clear before adding a pack or expanding the timetable.

See how Experiences work →