Understanding the PlayerFirst Cart and Waitlist Updates

PlayerFirst has made several updates to improve how a program waitlists registrations and the checkout process for our users. While a lot of the updates are architectural in nature, the myriad of updates we have made results in the following…

New Features

• A program level setting that waitlists registrations after a set number of registrations.
  Previously, a program could only be set to begin waitlisting registrations at a set date/time.

• A program level setting that marks a program as Sold Out and stops registrations after a set number of registrations.
  Previously, a program could not be set to automatically be marked as Sold Out after a set number of registrations.

• A division level setting that marks a program as Sold Out and stops registrations after a set number of registrations.
  Previously, a division could not be set to automatically be marked as Sold Out after a set number of registrations. Divisions had to be marked as Sold Out manually.

• Waitlist Limits at the program and division level.
  Previously, a program/division would allow an unlimited number of waitlist registrations unless the program/division was manually closed or marked as Sold Out.

• Program specific Registration Confirmation Emails.
  Previously, Registration Confirmation Emails could only be set at the brand level, forcing admin to receive Registration Confirmation Emails for every brand within a program, including the ones they weren’t in charge of.

• A timed registration queue. This timer tells the user how long the item(s) in their cart are guaranteed for before they’ll need to refresh the page. Once the registration timer hits zero, the item(s) are no longer guaranteed and the user risks returning to a cart where some of their items may be available for waitlist only or Sold Out.
  Previously, once an item was added to a user’s cart, that item stayed in the cart, regardless of the number of registrations occurring concurrently for that item. This resulted in PlayerFirst allowing a limited number of registrations past the registration limit of the program/division.

• An updated Waitlist column that indicates to admin if a program/division has space to remove a registration from the waitlist.
  Previously, admin would only see a check mark to identify if a registration was waitlisted.

• A new Waitlist # column that clearly identifies which registration is next to be removed from waitlist.
  Previously, admin had to rely on the Waitlist Date column to identify the first registration to be added to the waitlist.