All Collections
Add Ons
Packages
Mass-Updating Packages
Mass-Updating Packages

Adjust Member Packages

Josh Willey avatar
Written by Josh Willey
Updated over a week ago

INTRODUCTION

  • Feature Summary: Add, remove, or adjust the Start Date, End Date, and Eligible Items fields on packages sold to members.

  • Use Case: Previously, members who purchased a package could not use those punches to pay for an event registration with a new event category. Now, system users can mass-update previously sold package types to adjust the eligibility for package usage.

PREREQUISITES

Mass updating is only possible if the organization has sold the package type.

SETUP REQUIREMENTS

To mass-update an active package type:

  1. Go to Settings > Billing Settings > Packages.

  2. Locate the package and click Edit.

Updating sold packages

System users can mass-update these fields:

  • Package Start Date

  • Package End Date (Dynamic Expiration and Expire on Specific Date)

  • Allow Package to be Used While Unpaid

  • Eligible Items: Court Time

  • Eligible Items: Lessons

  • Eligible Items: Event Categories

After system users update the package type, additional information and settings populate below the Eligible Items table. Below the table, red text shows the number of active packages affected if the system user checks the Update Sold Packages box and clicks Save. The red text also shows which parameters will be updated based on page edits.

If the system user checks the Update Sold Packages box and clicks Save, a confirmation message confirms the updates. It also shows the number of updated active packages.

These updates only affect sold ACTIVE packages. If a system user uses the mass-update tool to change a package type's end date to the current date, all sold packages will expire. This change cannot be undone.

The package type's audit log shows all mass-updated parameters. The log shows all changes, when they were made, and the name of the system user who made the changes. Update Sold Packages will appear at the top of the audit log action if a mass-update took place during this edit.

What's next?

Did this answer your question?