Everything to move your programmes, payments and bookings into Zooza — with a direct link into the app and to help at every step. Set your region once and every app link points to the right place.
Almost every class-based business does. First find the pricing shape that matches how you actually collect money — this decides most of your setup.
One session on one day — a workshop, open day or lecture. No repeating schedule.
Clients sign up for the activity, then pick individual sessions — drop-in yoga or pilates. Credits/passes count down.
A fixed charge on a regular cycle (e.g. monthly) for as long as the class has sessions — no target total, it keeps billing while the group runs.
You have a final amount to collect for a term and want to split it — e.g. into monthly payments across a billing period.
Membership vs. term fee — don’t mix them up. A membership keeps billing a recurring amount for as long as the class has sessions — there’s no target total. Term fee is one known total for a term, split into instalments that stop when the term ends. Most schools splitting a course price monthly want term fee. See payment templates →
Parents see the payment options you allow (monthly / quarterly / yearly) at registration, choose one, and Zooza handles the rest.
Start from a worked example that matches you — each is a full setup walkthrough on help.
The whole lifecycle, end to end — this is what every setting below is in service of.
A parent finds a class on your site and books in a few taps.
A trial session or two to experience the class before committing.
An auto invite turns the trial into a full enrolment for the term.
Invoiced automatically; paid online or by bank transfer — matched for you.
You mark who came each session; make-up credits handle absences.
At term end, families roll into the next term automatically.
Three layers for what you offer, plus how people and orders sit against them. Full explanation →
Editing sessions (skip a holiday, move a date) never drops the enrolled families — everyone in the class comes along.
A client is the person you hold consents for (usually a parent linked to a child). A booking is their registration into a class. One client → many bookings.
Bookings are for services (classes). Orders are for products — merch, entry passes, digital content and videos — a separate flow from a class booking.
Open each step. Every one links straight into Zooza (region-aware) and to its help article.
Your account arrives as an invite — log in to the app with your email and set a password.
Add every venue where classes take place. Locations are shared across all your programmes.
Billing periods are the term blocks used for reporting and grouping — e.g. one season. The date range is optional: leave it out and it simply frames the term; add it and Zooza uses the range to help you generate sessions within it.
Add your own closures on top of public holidays so sessions skip them automatically.
Add other instructors if there will be any besides you, and set their access and pay rates.
Configure the consents you collect (photo/video, health, GDPR). Consent texts use HTML tags — see the help article for formatting.
Create your programme once, then set pricing. Offer parents several payment options (monthly / quarterly / yearly) — they pick at registration. Payment templates are reusable; make as many as you like.
Each class has its own capacity, trainer and venue. Sessions are generated as you build the class — skip holidays, move or edit dates; enrolled families follow automatically.
Tailor the messages parents receive. Each opens straight in the editor:
Order for an ongoing programme: Confirm (they verify email & contact) → Enrolment welcome. Trial emails send only if trials are switched on. These are the ongoing-class templates — one-off events and pay-as-you-go have their own sets.
Two ways — combine them if you like. Payment gateway only (e.g. Stripe): you're done — Zooza reads payments straight from the gateway, no bank to connect. Bank transfers: automate matching with the email parser (forward your bank's payment emails → matched by variable symbol) or connect GoCardless for direct debit.
Link Zooza to Claude or ChatGPT — it can advise you and increasingly do the work for you.
Tick these off — they decide how the whole offer behaves. Your progress is saved on this device.
Setup done. Now put it in front of parents. Embed exactly the piece you need on your own website — one widget per page — or let Zooza host the whole thing. You configure every widget in one place.
Each product/class page gets its own booking form, scoped to one programme, class or venue.
docs →📅CalendarA live calendar of sessions — filter by venue, course or trainer; click through to booking.
docs →📍MapParents search by address, pick a location, see its classes and book.
docs →🛍️Order formSell videos, e-books, passes and coupons — before, during or outside a booking.
docs →🎬VideoSecure playback for enrolled, logged-in families — your parent-zone content.
docs →👨👩👧Parent zoneHistory, outstanding payments, cancellations, make-ups and purchased content.
docs →Share the ready booking page for any programme — or, with no site at all, get a full hosted mini-site at zooza.site/youraccountname. Set it all up under Widgets.
Your embed points at the API host for your region — set automatically:
Full styling is website-side (your CSS); scoping and options are set per programme in the app.
The Calendar runs your current week — attendance, cancellations, day-to-day. But changes to a class (dates, times, trainer, venue) are made in the class schedules list, not the calendar.
Layer these on once the basics run. Each opens in Zooza.
We watch the in-app chat and reply fast — or book a call whenever you need one. Best way to work with us: describe what you’re trying to solve → ask the Zooza AI Assistant or ChatGPT → if it’s still not solved, send it over. There may already be an answer, or we’ll build one. ✨
Book a meeting →