Plans, packs and the honest answer to "how many sessions do I have left?"
Every membership system eventually has two ways to count what someone is owed, and they disagree. Ours had that and we deleted one: plans are now the only entitlement engine, so there is exactly one number and exactly one place it changes. That is a smaller feature list and a much better answer at the front desk.
One entitlement engine, not two
Plans and packs are the same mechanism with different shapes. There is no second balance kept somewhere else that has to be reconciled against the first.
- Recurring plans and finite credit packs on one engine
- One balance per customer plan — the number at the desk is the number in the system
- Plan definitions created and edited in one place
A roster you can run a business from
Who is active, who is frozen, who lapsed — as a working list rather than a report, because freezing a membership is a Tuesday activity, not a quarterly one.
- Freeze and unfreeze without deleting and re-selling the membership
- Business-wide roster across plans
- Recurring revenue visible from the same records, not a separate spreadsheet
Manual changes leave a reason behind
Sometimes you just give someone a session back. The adjustment is a first-class action on the plan and it requires a reason, so the balance can always be explained.
- Per-plan adjust, with a required reason
- The reason is stored with the change rather than remembered by whoever made it
- No side door that changes a balance without a trace
What Membership management runs on
Hold this on its own, or add the modules beside it when you want them — they share one login and one set of records. See the module library and pricing.
- Memberships
- Attendance
- Point of Sale
- CRM
- Scheduling & Classes
Questions buyers ask
What is the difference between a plan and a pack?
Shape, not mechanism. A plan recurs; a pack is a finite number of credits. They run on the same entitlement engine, which is the important part — there is one balance per customer plan rather than two systems that can disagree about what someone has left.
Can we freeze a membership?
Yes, freeze and unfreeze are on the roster, so a member who is away for a month does not have to be deleted and re-sold. That is the operation people actually perform, so it is a button rather than a workaround.
Can we manually give someone a session back?
Yes — each plan has an Adjust action, and it requires a reason. The reason is stored with the change, so a balance that looks wrong can be explained rather than argued about. There is deliberately no way to move a balance without leaving that trace.
Do we need the classes module to sell memberships?
No. Memberships is its own module. It gets better beside Attendance and Point of Sale — selling a plan at check-in, for instance — but it does not require them, and you will not see their screens if you do not hold them.
See it running
Create an account, or tell us how you work today and we'll show you what Membership management looks like on your data.