Packages & memberships

A package is a reusable prepaid option: the client pays once, then “spends” it at booking. A 10-visit card, a monthly subscription, a gift card, a bundle of several services. For you it means predictable income and a client who comes back.

Packages live in Catalog → Packages. That’s where you build the definitions — what you sell. The concrete instances a client owns show on their client card, Packages tab.

1. Two levels: definition and client package

This distinction explains 90% of package questions.

	Definition (Package)	Client package
What it is	the template you sell — “10-yoga pack, €100, valid 90 days”	the concrete instance owned by a concrete client
Where it lives	Catalog → Packages	the client card → Packages
How many	one definition	one per purchase
What it carries	type, price, validity, scope, locations	remaining balance, expiry date, status, history

Editing the definition does not touch already-sold instances — they keep the numbers they had at purchase.

2. Packages are a paid feature

Packages appear from the Growth plan upwards.

Plan	Packages
Start	no
Growth	yes
Pro	yes
Custom	yes

When the feature is missing:

• the new-package button in Catalog → Packages carries a padlock; pressing it shows “Packages is available on a higher plan. Upgrade to unlock it.” with an Upgrade plan link;
• packages you already created disappear from the public page — clients cannot buy them;
• client packages already sold stay in the database and remain visible on the client card;
• nothing is lost — the feature returns with the plan.

3. The “Catalog → Packages” page

The title is the entity’s name (“Packages”) and the subtitle explains the thing: “Reusable purchase options clients can apply at booking — prepaid credits, unlimited subscriptions, or fixed-schedule courses.”

Each row shows:

• an icon for the type (coins, infinity, calendar, box, gift);
• the name;
• a type badge — Credits / Subscription / Bundle / Gift card / Course;
• for credits — ”×{count}”;
• the scope — “All services”, the names of 1–2 offerings, or “{N} services”;
• the validity — “{N} days” or No expiry;
• the price (for a gift card — “from {lowest denomination}”);
• a publish switch — on = for sale on the public page;
• a three-dot menu: Edit, Archive (or Restore).

Rows are reordered by dragging (Drag to reorder) — the order carries over to the public page.

An empty list shows “No active packages” with the nudge “Define a credits pack, monthly subscription, or course so clients can prepay at booking.”

Archived packages sit in a separate block below — Archived: “Hidden from the public booking page. Restore to put them back on sale.”

4. Publish switch, archive and delete

Three different actions that get confused:

Action	What it does	Reversible
switching publish off	the package leaves the public page but stays in the admin and can still be issued by hand	yes, instantly
Archive	the package leaves the active list and the public page; already-sold instances are untouched	yes, via Restore
Delete	”Existing client packages tied to this definition will be marked refunded. Consider archiving instead.”	no

Delete is the only action that touches sold instances. If you just want to stop selling — switch publish off, or archive.

5. How a package reaches a client

There are two paths, and they behave differently where money is concerned:

5.1 The client buys it on the public page

The page has a packages section. The client picks one, fills in their details and confirms.

Important: today’s public checkout takes no card for a package. The purchase is recorded as a real sale that hasn’t been paid yet — the client pays at the venue. Until someone records that the money arrived:

• on the client card the package carries an Unpaid badge, explained as “Bought online without payment — the money hasn’t been collected yet.”;
• in the statement the line type is Package not paid yet and carries amount 0;
• in the money report the package does not count as revenue.

5.2 You issue the package from the client card

Open the client → Grant package → pick a board and a package (and, for a gift card, an amount) → Grant.

Important: the form has no payment-method field. So every package issued here counts as a gift — compensation, a bonus, a gesture — and never enters revenue. In the statement such a line is of type Package given away with amount 0, and the warning reads “{N} given-away package is not counted in the sums.”

If you actually took the money at the desk, record it as a payment the usual way: Recording cash and card.

6. The money rule in one sentence

A package sale becomes revenue at the moment the money is recorded as collected — not at the moment of purchase. A gifted package never becomes revenue.

Here is how that looks in the statement:

Line	When it appears	Amount	Counted in the totals
Package sold	the package was paid	the price	yes
Package not paid yet	sold online, money not in yet	0	no
Package given away	issued from the client card with no money	0	no
Package refunded	the package was refunded	minus the price	yes

Revenue is booked in the period the money arrived, not the period of purchase. A package bought in July and paid in August lands in August — which is exactly what keeps a closed July from moving.

7. What packages do NOT do

• They don’t charge a card automatically. There is no monthly auto-renew for a subscription. “Subscription” here means “unlimited access for a period”, not a recurring charge.
• They don’t apply themselves to past bookings. The deduction happens at booking time.
• They don’t combine within one booking. One visit is paid with one package.
• They don’t email anyone at issue time. The only package-related email is the gift-card activation link.
• They aren’t deducted by an offering that doesn’t accept them. The offering’s Accepts package payment switch is required (except in Package only mode).

8. Troubleshooting

The client doesn’t see any packages on the site. Check: is the publish switch on; is the package archived; does the workspace have the Packages feature.

A package isn’t offered when booking a specific service. The package’s scope doesn’t cover that offering, or the offering doesn’t accept package payment.

I sold packages and the report shows zero. See §6. Most likely they were all “given away” (issued from the client card) or “not paid yet” (bought online and not yet collected).

I deleted a package and its client instances vanished. Delete marks existing client packages as refunded. That’s why the dialog suggests archiving.

What’s next

• Package types — which type when.
• Sell a credit card — the most common package, step by step.
• Redeeming & balances — deduction, expiry, refunds.
• The client card — where the balance shows.