Membership versioning
Membership versioning controls how changes to a membership's benefits are handled. When versioning is enabled, editing benefits creates a new version rather than modifying the existing configuration. Existing enrolled members remain on their original version; new sales use the latest version.
Audience: Membership administrators who manage membership configurations and pricing.
On this page
- Before you begin
- How versioning works
- Changing prices for existing members
- Upgrade and downgrade with versions
- Diagnosing unexpected benefit loads
- Monitoring version usage
- Tips
- Troubleshooting
Before you begin
Permission: Edit (under Memberships) β Required to modify existing membership configurations.
- The Membership Versions organization setting controls whether versioning is enabled. Contact Zenoti Support if you are unsure whether this setting is active for your organization.
- Versioning applies to benefit edits. Pricing changes also create a new version when versioning is enabled β see Changing prices for existing members.
- Upgrade and downgrade actions do not migrate existing members to a new version. See Upgrade and downgrade with versions.
How versioning works
When versioning is disabled (non-versioned model)
When the Membership Versions setting is disabled:
- You cannot edit benefits on an existing membership, even if you have the Edit permission (under Memberships).
- To modify benefits, you must create a new membership using Add new from Master data > Memberships.
- All enrolled members remain on the single configuration of the membership.
When versioning is enabled
When the Membership Versions setting is enabled:
- Editing benefits creates a new version of the membership automatically.
- Existing enrolled members remain on their original version and continue receiving the benefits from when they enrolled.
- New sales use the latest version.
- Each version maintains its own independent benefit configuration.
Note: A version is also created when you change a membership's price. Guests already enrolled stay on the version they purchased β so new sales bill at the new price while existing members' recurring collections continue at the price their version carries β indefinitely. See Changing prices for existing members.
Changing prices for existing members
Editing a membership's price when versioning is enabled creates a new version. The new price applies only to new sales from that point forward. Guests already enrolled remain on the version they purchased, and their recurring collections continue at the price that version carries β indefinitely.
Moving enrolled members onto the latest version (and its price) is not a center-level action. If you need to migrate existing members to the new version, raise the request with Zenoti Support.
Upgrade and downgrade with versions
Upgrade and downgrade actions do not migrate existing members to a new version of the same membership. If you need to move existing members to a new version, a backend migration operation is required β raise this with Zenoti Support.
Diagnosing unexpected benefit loads
When a sale executes against an older, inactive version of a membership, the system loads the benefit or session count that version carries rather than the currently advertised configuration. This can result in a guest receiving more or fewer credits than expected.
To diagnose the cause:
- Compare what loaded at the time of sale against what was sold.
- Identify which version the sale used β the version, not the guest's profile, determines the benefit configuration.
- Review the configured benefit count on that version to confirm it matches what loaded.
If the version's configuration explains the discrepancy, the behavior is expected. If you need to correct the guest's balance, manage credits from the guest's membership details page.
Monitoring version usage
The existing membership reports do not track version-specific enrollment trends, version revenue, or per-version member counts.
Tips
- Before editing benefits on a high-enrollment membership, communicate the change to affected staff so they understand that existing members will not automatically receive the new benefits.
- When you need to change pricing, create the new version and verify the new price appears correctly on a test sale before communicating the change to guests.
- If you need to move a large number of enrolled members to a new version, plan the migration with Zenoti Support in advance β backend migrations require coordination and may have lead time.
Troubleshooting
Guests are receiving benefits from an older version after a benefit update. This is expected behavior when versioning is enabled. Existing enrolled members remain on the version they purchased. Only new sales use the latest version. If you need to move existing members to the new version, contact Zenoti Support.
I cannot edit benefits on an existing membership. If the Membership Versions setting is disabled, benefit editing is blocked on existing memberships regardless of your role permissions. To modify benefits, create a new membership using Add new from Master data > Memberships.
A sale loaded the wrong benefit count. Identify which version the sale used and review the benefit count configured on that version. A sale against an older inactive version loads that version's benefit configuration, not the current advertised one. See Diagnosing unexpected benefit loads for the full diagnostic steps.