Clients, memberships, packages & credits
Everything about the people who come to your space, and everything they can pre-pay toward coming back: client records, the self-service dashboard, class packs and memberships, gifting, session credits, and waivers. The thread that ties it together is simple — creating the offerings you sell can be gated to Professional, but a client’s ability to buy and use what you’ve created is always free and ungated.
Client records
The first time anyone books, enrolls, buys a package, or registers, Gather Grove creates a single client record for them — keyed to their email, with a matching WordPress user account behind it. Guests who check out without an account get a record too; the moment they later log in, that guest record is promoted to a full client in place, so no booking or payment history is ever orphaned or duplicated.
You manage clients under Booking → Clients. Each client’s detail page is organized into tabs — Overview, Bookings, Packages, Memberships, Purchases, Invoices, Documents, Profile, and Notes — and the Profile tab holds the fields you’d expect at a front desk:
- Name, email & phone — the basics, editable from the Profile tab.
- Birthday — used by the birthday-greeting automation (see Notifications & automations).
- Mailing address — address lines, city, state, ZIP, and country.
- Emergency contact — name and phone, kept on the record for in-person classes.
- Bio — a short free-text note about the client.
- Custom fields — your own studio-defined fields (allergies, referral source, shirt size — whatever you need), captured on the client record.
- Badges — assignable labels you define and pin to a client (for example “VIP” or “Founding member”).
- Internal notes & tags — private staff-only notes and comma-separated tags on the Notes tab, never shown to the client.
Email verification
Each record tracks whether the client’s email has been verified. Verification is passive and automatic: simply logging in, or completing a password reset, proves the person owns the address on file and flips them to verified — no extra step for most clients. Records that haven’t been verified yet show an Unverified badge in the Clients list, and you can re-send a verification email from the client’s detail page.
Marketing opt-in
Every client has a global marketing opt-in flag, and can also disable individual marketing-class types. When a client is opted out, every marketing-style automation skips them — but operational notifications (booking changes, package-expiry warnings, membership-renewal notices) always still send. The opt-in state lives on the Profile tab, and clients can manage it themselves from their dashboard.
Medical certificates and other documents that expire (Booking 1.272.0)
Some documents only count for a while: a medical certificate for sport is usually good for a year. Upload the client’s copy on their Documents tab as usual and fill in Expires on. Already uploaded it? Type the date in the Expires column next to the file; it saves straight away. Leave the date empty for documents that never expire.
- Reception sees it. The client’s record and their Front Desk card show “Medical certificate: valid until 12 Nov 2027”, “expires in 5 days” or “expired 3 Oct 2026”.
- The client sees it. When theirs is about to run out or has run out, their account page asks them to bring or send a new one. It never says what the document is about beyond its name.
- The newest date counts. Upload this year’s certificate with its date and last year’s warning goes away; the old file stays on the record.
- Reminder emails. Booking emails the client once when their certificate enters the warning window and once just after it expires (within two weeks; a certificate that ran out long ago gets no surprise email). Change the date and the reminders start over. Turn them off under the settings below. Edit the wording under Booking → Settings → Email (“Medical Certificate Reminder”).
- Who opened these files. The Documents tab lists every time someone opened, uploaded, re-dated or deleted one of the client’s files, with who and when (the last 50). Nobody can edit or clear this list; it goes only if you erase the client’s personal data.
- Settings (Pro). Under Booking → Settings → Booking → Medical certificates you can rename it (for example “Certificato medico”), choose how many days ahead to warn (30 by default), and decide what happens when one has expired: warn only (the default), stop the client booking online, or stop them booking online when it has expired or there is none on file. Staff can always book the client at the Front Desk.
Custom profile fields: dates (Booking 1.272.0)
Under Booking → Settings → General → Custom client fields a field can now be a Date (for example “Certificate issued on” or “Insurance renews”). It shows a date picker on the client’s Profile tab and reads the site’s way on the Front Desk card.
Deleting a client (Booking 1.252.0)
Delete a client from the Clients list, or delete their login under WordPress Users. Before anything happens, Booking tells you what deleting will end: a membership or payment plan that is still charging, studio credit left on the record. Click Delete anyway to go ahead. WordPress’s own delete screen shows the same list.
- Memberships and payment plans stop at once (Pro). Everything the person pays for is cancelled straight away, in Stripe too, including memberships they pay for their children. Nothing more is charged. You get an email and a notice saying what was cancelled. If Stripe can’t be reached, Booking tries again 15 minutes later, and tells you if you still need to cancel it in the Stripe Dashboard.
- Their history stays. Bookings, payments, invoices and waivers stay on the client record under their name and email. Deleting is not the same as erasing their personal data.
- Their email choices stay. If they had unsubscribed from marketing email or texts, the client record keeps that.
- Signing up again starts fresh. If someone later signs up with the same email, they get a new client record. The old notes, credit and household are not handed to them.
The client dashboard
The Client Dashboard Elementor widget gives your clients a self-service home — they sign in and manage their own world without emailing you. It renders one panel at a time behind tabs, and you choose which sections appear. The sections are:
- My bookings — upcoming and past classes and appointments.
- Packages — class packs they hold, with sessions remaining and expiry.
- Memberships — active subscriptions, with the option to cancel (cancellations route through the secure REST API).
- Enrollments — course enrollments; this section only renders when the client has at least one active or pending enrollment (Pro).
- Waivers — review and sign your active waivers; only renders when at least one active waiver exists.
- Waitlist — sessions they’re waiting on; only renders when they’re on at least one waitlist.
- Household — the people they book for (Pro). They can add a dependent, rename one, remove one, and edit a dependent’s details: date of birth, phone and address. The date-of-birth action shows what is on file, so you can see at a glance which members still need one.
A member’s own email is not editable from the household panel — it is the address their account and their booking mail are tied to, so changing it stays with you. Household members who have their own login manage their own profile, and the payer cannot edit them.
Two adults looking after the same children (Pro)
Plenty of families have more than one grown-up involved — a co-parent, a grandmother, a nanny — but only one of them pays. From the Household panel, the paying member can pick any adult in their household and choose “Let them manage children.” That adult can then book, cancel, sign agreements for and see the schedule of every child in the household, from their own account.
What that adult cannot do is just as deliberate:
- They see nothing about the payer’s money. No rate, payment schedule or Cancel Membership button on a membership the payer pays for — their view of it simply says who handles billing. If you run a sliding scale, a family’s rate stays between them and you.
- They gain nothing over the other adults. Management reaches the children only. Nobody can act on another grown-up’s account, and nobody but the payer can grant or remove this — so two adults can never lock each other out. This runs in both directions: the paying member does not see another adult’s classes, agreements or documents either. Their Household panel still lists everyone, so they can always remove someone or change what they can do.
- They can see who else is looking after the children — first names only, with the person who handles billing marked. Enough that nobody has to ring you to ask whether an agreement has already been signed, and not enough to see anything about that person.
- They can still pay for extras. A workshop or an extra day they book goes on the card they enter at checkout.
- A membership they start, they pay for (Booking 1.240.1). When this adult signs a child up for a membership, checkout says “Billed to your own account, not the household account holder’s.” It is billed to their own Stripe account with their own card, and the invoices, receipts, reminders, Pay ahead and Cancel Membership for it are theirs. The paying member still sees the membership on the child’s card, with “Billing is handled by Pat.”, and is never charged for it. Their card is never saved on the paying member’s account.
Memberships a co-parent started before Booking 1.240.1 were billed to the paying member’s account, and the co-parent’s card was saved there as its default card. To find them, a developer can run wp gather-grove billing cards --list. For each one it shows the card, whether it is the paying member’s default, which of their other memberships would renew on it, and whose card it looks like. wp gather-grove billing cards --tag --yes then marks each card as the co-parent’s, where that is clear, so the paying member can no longer use it. Where it isn’t clear, ask the family and name the owner: --membership=<id> --owner=<client id> --tag --yes. Tagging changes no payment: the membership keeps renewing on the same card.
Nothing changes for anybody until the payer grants it — no existing account gains access on upgrade. Removing someone from the household removes their access at the same time, and adding them back later does not bring it with them; it has to be granted again on purpose.
Booking confirmations for a child go to both responsible adults, so whoever booked and whoever pays are both in the loop.
Who gets the billing emails (Pro)
Every household member has a Billed separately checkbox — on the client’s Household tab under Booking → Clients, on the Add a dependent and Link an existing adult forms there, and in the Household panel of the paying member’s own account.
- Ticked: this person gets their own billing emails and reminders — renewal and grace-period notices, rate check-ins, tuition due and late-fee emails, failed-payment notices — and Gather Grove Pulse’s payment events are about them.
- Unticked: all of those go to the household payer instead — even for an adult, once you have saved it that way.
- It also decides who pays for new memberships (Booking 1.240.0). A membership started for this person from now on is billed to whoever the box says. A membership that is already running stays on the account it is billed to; ticking or unticking the box never moves it.
Until somebody decides, the date of birth decides, exactly as before Booking 1.238.0: 18 or over gets their own billing emails; under 18 or no birthday on file goes to the payer. That covers everyone already in a household when you update, so nobody’s billing emails move. The Household tab marks those rows From date of birth — not set yet, and the box shows what the birthday currently says. Once you (or the paying member) save the box, ticked or unticked, that choice wins — and it no longer changes on an 18th birthday. The member themselves cannot change it.
A member who has their own login sees where their billing emails go on the Household panel of their own account: “Billing emails go to you.” or “Billing emails go to Dana.”, with a note that only the payer or the studio can change it. There is nothing for them to click. (Booking 1.239.0.)
Who pays for a membership (Pro)
Each membership remembers whose Stripe account it is billed to. Usually that is the member themselves, or the household payer for a child without a login. The paying person sees the membership’s price, Pay ahead / Pay now and Change how you pay on their account page, and gets its receipts; anyone else in the household sees who handles the billing instead.
A child who got their own login after joining keeps their membership on the parent’s account, so it is the parent who sees and pays it.
Paying for a child who has their own login (Pro, Booking 1.240.0)
Some children have a login of their own, usually older students. Under Settings → Payments → Households, Bill children with their own login to the household payer is on by default. With it on:
- The parent can book for the child and sign them up. Put the child’s date of birth on file. A household member with their own login who is under 18 by that date shows on the parent’s Household panel as You book for them. At membership checkout the parent sees them under Who is this for? (see Starting a membership for someone in your household); when a membership needs approval, only once the child is approved. Without a date of birth on file the child is treated like any linked adult, who books for themselves.
- The parent pays. When the parent (or you) starts a membership for the child, checkout says “Billed to your account. Invoices come to you.” The membership is the child’s: their classes, attendance and course access. It is billed on the parent’s Stripe account with the parent’s card. The parent gets the invoices, receipts and reminders, and can Pay ahead for it alongside brothers and sisters. The child’s own page says who handles the billing.
- A child who signs up themselves pays for it. Whoever is at the keyboard pays, so nothing is charged to a parent who isn’t there to agree to it.
When a birthday is missing, everyone is told. A household member with their own login and no date of birth on file can’t be booked or paid for by the parent yet, because nothing says whether they are a child. Instead of leaving them out, Gather Grove says so:
- On the parent’s Household panel: “Add Louise’s birthday so you can book and pay for them. Ask the studio to add it.” A member with their own login owns their profile, so the parent can’t add it themselves.
- In Who is this for? when booking, and at membership checkout: they are listed greyed out, with the same line, and can’t be chosen. If the parent picks them anyway, the answer is that line, not “submit a request first”.
- On the client’s Household tab: a Birthday missing — affects billing and booking badge on their row.
- For staff who manage clients: one notice, “3 household members have no birthday on file. Billing and booking for them may not work as expected.”, with a See who link to Clients filtered to Household: birthday missing. Dismissing it hides it for you until more people are affected.
Add the date of birth on the person’s client page, or tick Billed separately if they book and pay for themselves (that clears the notice for them too).
Billed separately on a household member overrides the setting either way. Ticked, the child pays for their own memberships. Someone else can still start one for them if it is paid by invoice. A card checkout is turned away with a note saying what to do instead (the child starts it from their own account, pay by invoice, or ask the studio to bill it to the parent), so a parent’s card never ends up saved on the child’s account. Unticked, the parent pays, even for a grown-up child. Adults you link into a household, and adults who accept an invitation, are billed separately automatically when they are 18 or over or have no date of birth on file. On Link an existing adult, choose Automatic for that, or pick Billed separately / Billed to the payer yourself.
Turn the setting off and children with their own login pay for their own memberships, unless they are unticked Billed separately. A login-less child is always billed to the parent.
Memberships already running don’t move when you update or change any of this. A child with their own login who was signed up on their own account before 1.240.0 is still billed there until you move it (below).
Moving a running membership’s billing to the parent (Pro, Booking 1.241.0)
Stripe can’t hand a subscription from one person to another, so Gather Grove re-homes it: it starts the same membership on the parent’s Stripe account and quietly ends the one on the child’s. For the family, nothing else changes:
- Same membership. Same classes, bookings, attendance and course access. It is still the child’s membership.
- Same due day and price. Nothing is charged when it moves. The next invoice comes on the day it would have, for the same amount, to the parent.
- Nothing lost. A discount that applies to renewals carries over, and so does a trial. Late fees waiting for the next invoice move with it. Anything paid ahead for this membership moves to the parent’s account too.
- No goodbye email. Ending the old subscription is not a cancellation: no “membership ended” email, nothing released, no access lost.
- The child’s own cards and other credit stay with the child. Past invoices and receipts stay on the child’s account in Stripe.
For now this is done from the command line, by whoever runs WP-CLI for your site. (Buttons on the Household panel and in Settings → Payments come in a later release.)
- See who.
wp gather-grove billing rehome --listlists every household member’s membership billed away from the household payer. It changes nothing. - Preview a household.
wp gather-grove billing rehome --household=<payer's client id>prints the exact plan for each membership the default would move: from whom to whom, the price, the next invoice date, each discount and how it carries, the late fees and credit moving, what stays with the child, and anything in the way. It changes nothing. One membership:--membership=<id>. - Move it. Run the same command with
--yes. Ready memberships move at once. Running it again does nothing. - Check.
wp gather-grove billing rehome --statusshows every move and where it is.
Some memberships wait instead of moving. The preview says which and why, and --yes queues them; they then move by themselves:
- An invoice for it is open. An invoice can’t change accounts, so the move waits until it is paid, voided or marked paid (paying by cheque and marking it paid in Stripe works; the daily check notices).
- It is paid automatically and the parent has no card or bank account of their own on file. A card can’t be copied from the child’s account. Ask the parent to add one on their account page; the move runs as soon as they do. Or switch the membership to invoices first.
Some can’t move: a member ticked Billed separately (someone decided they pay for themselves; to move one anyway, name the payer with --to=<client id>, and untick the box if the payer should get the billing emails too), within 48 hours of its renewal (try again after it), one set to cancel, a payment plan (it finishes where it started), and a complimentary or cash membership with no Stripe billing.
Gifts are never moved to the household payer: a gift is the giver’s money. --membership=<id> --reason=gift moves a gift onto the giver’s own account (they need a card of their own on file for an automatic one), and then removes the giver’s card from the recipient’s account. A membership a co-parent started before 1.240.1 can move to the co-parent’s own account with --reason=coparent --to=<their client id>; if their card was tagged as theirs (wp gather-grove billing cards --tag), it is then removed from the household payer’s account once nothing there uses it.
If a move is interrupted (Stripe was unreachable, say), it is either undone completely, before the membership switched over, or finished by the daily check after it. wp gather-grove billing rehome --resume --yes finishes it straight away.
Before the first move on a live site, try it in Stripe test mode with the same kinds of membership (invoiced and automatic, a due-day package, a discount). Check that nothing is charged or emailed when it moves and that the next invoice lands on the usual day.
Drop this widget on any page and protect it behind a login. See Elementor widgets for placement and The booking flow & modal for how clients sign in.
Packages & memberships
A Package (under Booking → Packages) is a thing a client pre-pays for. There are two types:
- Class pack — a fixed number of sessions (or unlimited), valid for a set window. “10-class pass, good for 90 days.”
- Membership — a recurring subscription billed by Stripe on an interval. “Unlimited monthly.”
Each package carries a description (also surfaced by the Package Description dynamic tag), a type, a session count (0 = unlimited), a price (0 = free), and a validity window in days (0 = no expiry). You can also scope a package to specific classes and/or class categories — an empty list means it applies to everything.
With Gather Grove Courses active, the package screen also has a Course Access section: Grants Course Access (no access, specific courses, or the entire library) and, for specific courses, Place buyer in cohort — the cohort a buyer is seated in on payment, so the cohort’s drip schedule and community space apply from their first login rather than a self-paced enrollment with everything open. The cohort must belong to a ticked course. Selling a cohort seat end to end walks through the whole purchase-to-enrollment flow.
A package that grants two or more courses also has Offer on these course pages: one box per course, all ticked to start with. Every ticked course’s page offers this package. Untick a course to keep the package off that page. That’s for a bundle: say a training bundle includes Course B, and Course B also has its own cheaper package. Untick Course B on the bundle, and Course B’s Buy button goes straight to its own package, with no list of bundles. People who buy the bundle still get Course B. Keep at least one course ticked.
The Pro line, precisely. Class packs and memberships are Professional features; the free plugin from WordPress.org does not include them. If your Professional license lapses and you publish a new package, it’s saved as a draft (never lost) with a friendly notice, and existing published packages stay fully editable. Your clients can always buy and use whatever you’ve already published — purchase and consumption are never gated. See Free vs Pro.
Putting a package on sale (Booking 1.278.0)
Give a package a Sale price (under its Price in the package editor) to run a special, with optional from and until dates. While the sale is on, shoppers see the regular price crossed out next to the sale price, plus “Sale ends date” when you set an end date. Checkout charges the sale price, and a promo code takes its discount off the sale price. When the end date passes, everything goes back to the regular price by itself.
- Where it shows: the package shop, the course checkout page, and anywhere you put
(addshow_ends="yes"for the end date). With Elementor, the Package: Price tag shows the sale price, and Package: Regular price (shown during a sale) gives you the old price to style with a strike-through. It’s empty when no sale is on. - Dates are whole days in your site’s time zone: from the start of the “from” day to the end of the “until” day. Leave “from” blank to start now and “until” blank to run until you clear the sale price.
- Not for memberships or sliding-scale prices. The fields are hidden on memberships, and a sliding scale keeps its range. Payment-plan amounts don’t change.
How a package is used at booking
When a client who owns an applicable, active, non-expired package books a qualifying class, Booking deducts a session automatically instead of charging a card. When a pack’s remaining sessions reach zero it’s marked exhausted; once a validity window passes it’s expired. Both states stop further deductions, and the client simply sees the normal pay-to-book path again.
More than one pack of the same package
Clients often buy a second pack before the first runs out. Booking treats all their packs of the same package as one supply:
- One total. The booking form, the appointment booker and the client’s account page show the total left across every usable pack, for example “5 sessions remaining across 2 packs”. On the account page the packs share one card: the total first, then each pack with its purchase date, what’s left and its expiry. The Package: Sessions Remaining dynamic tag shows the same total. If any of the packs is unlimited, the total is unlimited.
- Emails follow the supply. The “pack expires soon” email gives the expiring pack’s own count, then the total across all their packs. The “you finished your package” email isn’t sent while they still have another usable pack of the same package.
- The pack that expires soonest is used first. Packs with no expiry come last; between two with the same expiry, the older purchase goes first. The client doesn’t choose.
- Group bookings can span packs. A client booking three seats with 1 left on one pack and 3 on another is not refused: the seats come from both, soonest expiry first.
- Cancels go back where they came from. When a booking is cancelled and its seats are returned, each seat goes back to the pack it was taken from.
A pack’s history (Pro)
On a client’s Packages tab under Clients, click a pack’s name to open its history, oldest first:
- the purchase;
- every booking that used a session from it: the class, the date and time, who came (with guests), the seats and the booking’s status, including “seat kept (late cancel)”;
- every seat handed back;
- every staff adjustment, with the reason and who made it;
- the balance after each line.
Bookings made before this history existed are read from the booking itself and marked “(from the booking status)”. If the history starts from fewer sessions than the pack was sold with, for example an imported balance, it says so above the list.
Comp packages
From the admin Manual Booking flow you can assign a comp package to a client — a fully usable, zero-price package that the booking flow deducts from exactly like a paid one. Useful for trades, make-goods, and staff perks.
Starting a membership for someone in your household (Pro)
A parent signed in to their account can buy a membership for their child straight from the Package Shop. When they click Buy Now on a membership that doesn’t need approval, the checkout asks Who is this for?: Myself, then each household member they can book for (the same people the booking form offers).
- The child can be added right in the checkout. Under Who is this for?, + Add a family member asks for the child’s name and date of birth, adds them to the parent’s household and selects them, and the parent carries on to payment. There’s no need to set up the household first, and it works for a parent with no household yet, who sees Myself and the add link. The date of birth is required here because a child’s membership needs one. Adults join a household by accepting an invitation, so they are added from the parent’s account, not from checkout. Only the household’s account holder sees the link: someone who is themselves a household member can’t add members. (Booking 1.264.0)
- The membership is the child’s. Their classes, attendance and course access. If the membership has Auto-enroll members in these classes ticked, it is the child who is booked into them.
- The parent pays. Checkout says “Billed to your account. Invoices come to you.” The first payment and every renewal go on the parent’s Stripe account and card, and the parent gets the invoices and receipts. A co-parent who manages the child pays from their own account instead (see above).
- Billed separately still applies. For a child ticked Billed separately, checkout warns before anyone types a card, and a card payment is turned away with what to do instead: the child starts it from their own account, the parent picks pay by invoice if the membership offers it, or you bill it to the parent.
- A missing birthday is shown, not hidden. A child with their own login and no date of birth on file is listed greyed out with the reason, and can’t be chosen until you add it.
- Only their own household. Nobody can start a membership this way for someone outside their household. The site refuses, and nothing is charged.
- “Buying for someone else?” is hidden while a household member is picked. A gift is for someone outside the household, by name and email (below).
- A parent who already has the membership sees Active Membership on the card, with two buttons: Buy for Someone Else (a gift by name and email) and Buy for a Household Member. The second asks Who is this for? with only the household members who don’t have it yet, even when there is just one, so checkout always shows whose membership it is. When the only member left needs a birthday on file, the card shows that line instead of the button. (Booking 1.262.0)
The intake questions and agreement terms on the membership, if any, are answered by the parent at checkout. Waivers are owed by the person booked: an auto-enrolled child’s bookings carry a Waiver pending note, so it is collected at their first visit, as for any member.
Memberships that need approval work the same way once the child is approved, and memberships that need an application are bought by the applicant.
On a class that requires a membership, the booking form’s Who is this for? greys out anyone in the household without it, the parent included, with a Get a membership link. See The booking flow, under Membership-restricted classes.
Gifting
Both packs and memberships can be purchased for someone else. The buyer enters the recipient’s name and email; Booking resolves or creates the recipient’s client account and assigns the package to them. (Behind the scenes this fires gather_grove_package_gifted / gather_grove_membership_gifted for any integrations you’ve wired up.)
Gifting hands someone a specific offering you’ve chosen for them. If you’d rather let the recipient pick for themselves, sell a gift card — open, stored value they redeem against anything.
Membership lifecycle
Memberships are real Stripe subscriptions, so their lifecycle mirrors Stripe’s:
| Event | What happens |
|---|---|
| Renewal | On each period rollover the subscription renews and, for allowance-style memberships, the monthly session allowance resets. The membership-renewal automation can warn the client ahead of the charge. |
| Cancel — end of period | The subscription is set to cancel at period end. The client keeps access through the time they’ve already paid for; nothing is clawed back. |
| Cancel — immediate | The subscription is cancelled now, and the membership’s future confirmed bookings are released so those seats free up. |
| Changed in the Stripe Dashboard | (Booking 1.251.0) If you set a membership to cancel at period end in Stripe, Booking shows it as cancelling too. If you undo a cancel in Stripe, Booking stops saying it’s cancelling and it renews as normal. If you pause payment collection in Stripe, the membership shows Billing paused in Stripe on the client’s page and in their account; their access doesn’t change. Booking catches up within a day even if Stripe’s message is missed. |
| Payment failure | When a renewal invoice fails at Stripe, the membership is flagged and gather_grove_membership_payment_failed fires so you (and your automations) can follow up. |
| First payment fails at checkout | (Booking 1.266.1) If the very first payment doesn’t go through (a declined card, a failed Link payment), the membership never starts: it shows as Incomplete, gives no booking access, and the person can check out again. They get an email with a link to try the payment again, and you get a note saying the signup payment failed. Stripe doesn’t retry a first payment: if it isn’t paid within about 23 hours, Stripe closes the checkout, the membership is cancelled and the person is told they weren’t charged. This isn’t treated as a late renewal, so no grace period or payment-failed automations run. |
Billing everyone on the same day (tuition)
By default a membership renews on the anniversary of the day someone joined. If your members all pay on one day of the month — a school whose fees are due on the 1st, say — set Due on day in the package’s settings (under Manual payments). Then:
- Autopay members are charged on that day.
- Invoiced members are sent their invoice on that day, due the same day. The Invoice due within setting is ignored for them.
- Someone who joins mid-month starts on the next due day. Tick Charge the first period when they sign up (Billing Schedule) if they should pay for the time until then; leave it unticked to give them that time free. Ticked, they pay today for the period their first session falls in: someone who picks a first session after the next due day pays for that later period today and is next charged when it ends. Tick Prorate it too, and they pay only for that period’s sessions from their first one (see Ongoing groups).
- Members see “Due on the 1st of each month” at checkout and on their account page.
It applies to monthly and quarterly billing, and to new members only — current members keep the billing day they already have. Leave the field blank to bill on the anniversary as before.
Ongoing groups: join any week, pay monthly (Pro, Booking 1.266.0)
Dance, theatre, martial-arts, music and language schools often run weekly groups that continue while they have students. Families join and leave at any point and pay a monthly fee. Neither a session allowance (a month can hold 3, 4 or 5 sessions) nor booking every scheduled session (months ahead) fits that, so a membership has three settings for it. Each is off by default and works on its own.
- Ask “When would you like to start?” at checkout (next to Auto-enroll, with the group’s class selected under the classes this membership covers). The Package Shop lists the group’s next sessions, and the member is booked from the one they pick. A gift membership is booked from today.
- Book through the paid period only, and extend at each renewal. Auto-enroll books the member up to their next billing date instead of every scheduled session. When the subscription moves into its next period, the member is booked into it straight away, before the payment clears. That matters for SEPA Direct Debit, which takes a few days to confirm. A member paying by SEPA Direct Debit (or another bank debit) agrees to the direct debit at checkout even when nothing is charged that day, so the first regular payment can be collected. If their bank account can’t be set up, checkout tells them and the membership isn’t started. (Booking 1.269.1.) A membership that falls behind on payment isn’t extended, and one that ends releases its future bookings as always.
- Prorate the first period (Billing Schedule, with Charge the first period when they sign up and a due day or start date). It’s measured against a whole period: someone joining with 2 of the month’s 5 sessions left pays 2/5 of the fee today, then the full fee on the due day. Someone whose first session is after the next due day pays for that period today (with fees due on the 2nd, a first session on 12 November of 5, 12, 19 and 26 November pays 3/4 of the fee) and is next charged on 2 December. Sessions are counted on the membership’s classes and the member’s own weekdays, so cancelled sessions (closures, holidays) aren’t counted. For a group that started partway through the month, the month after is used as the whole period. Under 0.50, nothing is charged today. (Booking 1.269.1.)
At checkout the member sees what they’ll pay, under the start they pick: “Today: $32.00 for 2 of the period’s 5 sessions, until Nov 1. Then $80.00 from Nov 1. Charged on the 1st of each month.” Without Prorate it it reads “Today: $80.00 for the period until Nov 1.”
Studio credit paying for the first payment covers only what is charged today: the prorated amount, or nothing when billing waits for the due day. The rest stays in the member’s credit for later, so their balance and their Stripe invoices always agree.
Paying ahead, and paying an open invoice
Members who pay by invoice see what they owe at the top of My Memberships on their account page:
- An invoice is open — “October — $800 for Arthur, due October 1”, with a Pay now button that opens the invoice.
- Nothing is open yet — “November — $800 for Arthur, due November 1”, with a Pay November now button. They can pay whenever they like; they don’t have to wait for the invoice.
- Already paid — “November is paid for Arthur — thank you.”
Paying ahead takes them to a secure Stripe payment page (card or bank account). The money is held as credit on their account, and when the invoice is issued on the due day it is paid from that credit automatically — there is nothing for you or them to do. A bank payment shows as “on its way” until it clears.
If they have a card saved on their account, they also get a one-tap button — Pay November with Visa •• 4242 — that charges it straight away. If their bank asks for extra verification, or the card is declined, they’re taken to the secure payment page instead, so the button always gets them somewhere that can finish.
If a membership ends after a month has been paid ahead — and before that month was invoiced — the payment for that month is refunded automatically to the card or bank it came from. For brothers and sisters paid together, only the share for the membership that ended is refunded.
Brothers and sisters billed on the same day are paid together in one payment. Only the person who pays sees the amounts and buttons; other adults in the household see the membership but not the money.
Money you receive by cheque or cash works the same way: record it under Offline Payments on the member’s page and it comes off their next invoice. If you refund a paid-ahead payment in Stripe, the credit is taken back automatically.
Late fees
In a membership’s settings (Billing Schedule → Late fees), tick Add a late fee when a payment is overdue and set the fee, how many days late it starts, and how often it repeats — for example $50 after 5 days late, then every 7 days. You can also set a cap; leave it blank for none. Once saved, the box shows the terms exactly as members will read them, and what the cap allows — “At most 2 fees per invoice ($100 in all)” — or a warning if the cap is smaller than one fee, which would mean no fee is ever charged.
- Fees are checked every morning. Each fee is for one membership (so two children paying late is two fees); the overdue invoice itself never changes.
- Bill each fee: on their next invoice (recommended) adds the fee to that member’s next invoice, with no extra emails from Stripe. As its own invoice invoices and emails each fee the day it is added — quicker to collect, but a family three weeks late gets three more invoices.
- Fees stop the moment the invoice is paid — including when you mark it paid in Stripe for a cheque or cash. A bank payment that is still clearing never counts as late.
- Members who pay automatically get the same fee if their payment fails, counted from the day it was due.
- Members see the terms on the plan card before they join, on their account page, and in the footer of their invoices. Their account page also shows any fees waiting on their next invoice, or invoiced and waiting to be paid.
- The person who pays gets an email the day before the first fee (Late Fee Warning: pay today and it won’t be added) and each time one is added (Late Fee Added, with the total so far and when the next would come). Brothers and sisters are in one email. Both are under Settings → Emails → Automated.
- On a member’s page (Memberships tab) you’ll see each fee, with Waive while it’s still unpaid (a fee sent as its own invoice is voided in Stripe), and Pause late fees for this member for a family with an arrangement.
- Reports list fees as Late Fees, and the Revenue tab counts the fees you collect in their own Late fees bucket rather than as recurring income. The money is counted once.
Whether you can charge a late fee is for your own agreement with your members to say.
The “payment due soon” email
For memberships paid by invoice on a set due day, Booking emails the person who pays a week before each due date (change the number of days under Automations → Membership Payment Due Soon):
Hi Ember, Arthur’s November membership is $800.00, due on November 1. You can pay it now from your account — it only takes a minute, and there will be nothing to do on the day. [Pay November now]
- Brothers and sisters due on the same day are in one email.
- It is not sent if the family has already paid ahead or you have recorded a cheque that covers it.
- It takes the place of the Membership Renewal Reminder for these memberships, so families don’t get two. Turn it off and the renewal reminder comes back. Members who pay automatically keep the renewal reminder.
- You can edit the wording under Settings → Emails.
{whose}reads “Arthur’s”, or “your” when an adult is paying for their own membership.
Reminders when tuition is still unpaid
Three more emails go to the person who pays, all on by default and all under Settings → Emails → Automated:
- Membership Payment Reminder — 2 days before the due date (change it under Automations), only if the month is still unpaid. Never on the same morning as the “payment due soon” email.
- Late Fee Warning and Late Fee Added — see Late fees above. Only on packages that charge late fees.
These, the “payment due soon” email and the late-fee emails are bills, so they are always emailed — a family can turn off the copy in their account, not the email. Like every billing email (renewal reminders, payment problems, rate check-ins), they go to the parent who pays, even when the child has a login of their own — unless that household member is ticked Billed separately (see Who gets the billing emails above), in which case they get their own.
Each one is checked again just before it goes: a family who has paid, paid ahead, or had the fee waived doesn’t get it. If you use Gather Grove Pulse, its Tuition overdue starter can take over the overdue reminders in your own words — switch it on in Pulse and Booking’s Late Fee Warning steps aside so nobody gets two.
One-time setup for the Pulse starter: it listens for “invoice issued” news from Stripe. If you connected Stripe webhooks before Booking 1.236.0, go to the Payments settings tab and click Connect Webhook Automatically once more — the existing connection is updated in place, nothing else changes.
In Reports, a paid-ahead payment appears as Paid Ahead on the day it was made, and the invoice it covers appears as a $0.00 renewal — so the money is only ever counted once.
Clients can cancel their own memberships from the dashboard; you can cancel on their behalf from the client detail page. For the payment side of all this — Stripe setup, invoices, refunds — see Payments, Stripe & commerce.
Enrollment courses (Pro)
An enrollment course is a class set to enrollment mode: instead of selling drop-in by the session, it sells as one fixed-length series. A single purchase fans out into the constituent session bookings, all linked to one enrollment record, so the client is booked into every meeting of the course at once. Enrollment courses support guest checkout just like drop-in bookings, and the course’s full set of eligibility checks (mode, status, whether enrollment is still open, whether sessions exist, already-enrolled) runs before the sale completes.
Creating and selling enrollment courses requires a Professional plan. The mechanics of building a course schedule live in Classes & scheduling.
Session credits
Session credits are a precise, per-client tally of bookable entitlements for a specific class type — distinct from a money balance. Where studio credit is a single currency amount, a session credit says “this client holds 3 Vinyasa sessions.” A booking that matches the class type consumes one credit instead of charging.
How the ledger works
- Lot-based. Each grant is its own immutable lot with a starting count and an optional expiry date. A client can hold several lots of the same class type at once.
- FIFO by expiry. When a credit is spent, Booking always draws from the soonest-expiring valid lot first, so credits never quietly expire while a longer-dated lot sits unused. Lots that never expire are drawn last.
- Auto-applied. At booking time, if the client holds a valid credit for that exact class type, it’s consumed automatically — no toggle to remember.
- Refundable to the source. If a credit-paid booking is cancelled, the credit returns to the exact lot it came from. The one exception: a lot that has expired in the meantime is gone — an expired credit is never resurrected by a cancellation.
- Class-type exact. A credit for one class type is never spent on another.
Where credits come from
Credits can be minted by a package purchase, by an enrollment, or by a manual admin grant. Today the shipped path is the manual grant: on a client’s detail page, the Session Credits card lists their current lots and lets you grant a new one — pick a class type, a count, and an optional expiry, and it’s added. This is the way to hand-give entitlements (“here are two free form-check sessions”) with a clear, auditable trail.
Granting credits is a staff action gated on the manage-bookings capability and enforced on the server. Each deliberate grant stacks as its own lot, so repeated grants add up rather than overwrite.
Waivers
A Waiver (under Booking → Waivers) is a document a client must agree to before they can book. Each waiver has a body, a version, an optional validity window in days, and an active toggle.
- Versioned. Change the version and every client is required to re-sign — the old signature no longer counts as current. Leaving the Version box blank keeps the current version, so clearing it by accident never sends everyone back to sign. If you edit the waiver text but keep the version, you’ll see a reminder that existing signatures stay valid — bump the version when the change should make everyone re-sign.
- Expiry-aware. Set “valid for N days” to require periodic re-signing (an annual liability waiver, say). Leave it blank and a signature is valid forever.
- Active gate. Only active waivers are enforced; deactivate one to retire it without deleting its signature history.
- Applies to. Choose Everyone with an account (the default) or Participants only. On a family account, “Participants only” stops asking a parent for a copy of their own when they book for their children and never attend themselves — they carry on signing on each child’s behalf. If that parent ever books a place for themselves, the waiver is asked for at checkout exactly as before. This changes who is listed, never who is let through.
How waivers gate booking
Two kinds of waiver can apply to a session: studio-wide waivers set in your general settings, which everyone must sign whatever they book, and a class-specific (or service-specific) waiver attached to that class. You can name more than one studio-wide waiver — a studio often asks for both a liability waiver and a photo-permission consent, and the second is not tied to any particular class. Before a client can complete a booking, Booking checks that they hold a valid, current-version, non-expired signature for every applicable active waiver — and if not, presents the waiver text inline in the booking form to sign on the spot. You can also record a paper waiver signed in person from the client’s Documents tab, where signatures and uploaded documents are kept together.
Signing ahead, with no booking
Put the shortcode on a page (a /waiver page, say) and share the link — in a welcome email, on a QR code at the front desk, or ahead of a first class. It shows your studio-wide waiver(s); name a specific one with , or several with id="123,456".
- Signed in: the page shows where they stand — “✓ You’re all set, signed date, valid until date” — and a signing form for anything still owed. On a family account they can sign for each household member they manage.
- Not signed in: they enter their name and email (and phone, if you require one), read the waiver, and sign. A new visitor gets a guest record, exactly as a guest checkout would create. If the email already belongs to an account, they are asked to log in first, so nobody can sign on someone else’s behalf by typing their address.
- A signature made here counts at checkout later — there is nothing left to sign when they book.
Courses ask for the waiver before payment
When someone buys an online course, the checkout page shows your studio-wide waiver(s) with an “I have read and agree to this waiver” box, and the Pay button doesn’t go through until it’s ticked. This works whether they pay by card, studio credit, a payment plan or a code that makes the course free. Someone who has already signed isn’t asked again.
- Signed in: the signature is recorded as soon as they press Pay.
- Buying without an account: their agreement is recorded on the account the purchase creates, once the payment goes through (or once they confirm their email, for a free claim). If the email they used already belongs to an account, nothing is recorded for them; they’re asked to sign the next time they log in.
- A waiver built in Gather Grove Forms: signed-in buyers get a link to fill in the form, then come back to pay. Buyers without an account are asked to log in or create one first.
- “Guests can book, and are asked when they arrive”: with this setting on, buyers without an account aren’t asked at checkout, the same as for bookings.
People who bought a course before this was asked, or through the front desk, see “Please read and sign our waiver for your course” on My Account until they sign, with a link to their Waivers tab. On Booking → Waivers, a studio-wide waiver also lists Course buyers who haven’t signed, so you can follow up.
People who booked without signing
A few routes let a booking through without a signature on purpose: bookings you make in the admin, instructor walk-ins, gifted seats, membership auto-enrolment, named guests on a group booking, and guests when “Guests can book, and are asked when they arrive” is on. A waiver you revise, or one that expires, puts earlier bookers in the same position. For all of them:
- Automatic reminders. Once a day, anyone with a confirmed booking in the next 7 days who still owes a waiver is emailed a link to sign. They get at most two reminders per waiver version, at least three days apart. Turn this off, or change how far ahead it looks, under Settings → General → Waivers. The Waivers screen shows who has been reminded and when.
- No email on file? They are skipped, and the Waivers screen marks them to collect in person or record a paper signature.
- Instructors see it too. The instructor dashboard roster and the pre-class roster email mark anyone who owes a waiver, with a reminder to collect a signature at the door.
- The note clears itself. As soon as they sign, by any route, the “⚠ Waiver pending” note comes off their upcoming bookings.
When what people agree to needs answers
A waiver on its own shows your text and takes one signature. That is right for a straightforward liability waiver, and not enough for a real agreement — one that needs initials beside each clause, consent choices, or a child’s details. For those, build the document in Gather Grove Forms and point the waiver at it: fill in Form ID in the waiver’s settings, and the waiver is signed by completing that form instead.
Everything else about the waiver keeps working exactly as before — it still shows as signed or not signed, still expires, still counts on the Waivers compliance screen, and still gates booking. What changes is how it is signed: at checkout, the form appears right in the booking, in place of the “I agree” box, and the booking carries on the moment it is submitted. See Form waivers at checkout for the whole flow.
- Form page is optional. Add the page your form is embedded on only if you want links to it — the reminder emails and the member portal’s Review & Sign use it. Checkout never needs it.
- Addressed to the right person. On a family account the portal groups waivers by person — a heading for each child with their agreements under it, and your own marked as yours — and each link (or the in-checkout form, when a parent books for a child) knows which member it is for, so a submission is tied to that child rather than to whatever name was typed in.
- Filled in for them. Because the link already knows who it is for, the form arrives with the participant’s name filled in, along with the signed-in parent’s own name, email and phone. It recognises the field names people naturally use (
child_full_name,guardian_nameand similar). Everything filled in stays editable — and which person the signed form is about is established by the link itself, not by what is typed. - No payments on a waiver form. A form that takes a payment cannot be used as a waiver at checkout (it would charge inside someone else’s booking). The waiver’s settings warn you, and checkout refuses it.
- Changing the version costs more here. Bumping a normal waiver’s version asks people to click once. Bumping a form-backed one asks them to fill in the whole form again — right when you have genuinely revised the agreement, unfair when you are fixing a typo. Leave the version alone for corrections.
Only forms you deliberately attach behave this way, and a form-backed waiver is never signed by a plain “I agree” tick anywhere in the product — including the reminder-email signing page. If the form cannot be shown (Gather Grove Forms switched off or older than 1.33.0, the form archived, or the form set up to take a payment), bookings that need it are refused with “This class needs a waiver we can’t show right now. Please contact the studio.” — and a red notice in your dashboard names the waiver and the form so you can fix it.
Where to go next
- Payments, Stripe & commerce — connecting Stripe, invoices, refunds, and account balances.
- The booking flow & modal — how packages, credits, and waivers surface to the client mid-booking.
- Notifications & automations — renewal reminders, expiry warnings, and birthday greetings.
- Free vs Pro — exactly what’s gated, and the “own your data” promise on lapse.
Applies to Gather Grove Booking v1.278.2. Last synced November 11, 2026.