All Collections
ARMS Camps
Creating a Waitlist
Creating a Waitlist
Reid Merritt avatar
Written by Reid Merritt
Updated over a week ago

Creating a waitlist for an event that is full, or rapidly filling up, can save time for both you and the registrant by collecting registration information on the front end and accepting payment at a later date.

To set up a waitlist, you must first clone the existing camp that is full

  1. Go to Storefront,select Events

  2. Click on the camp you would like to create a waitlist for

  3. In the top right corner of the page, select “Clone”. This will take you to the Clone Product window

  4. Change the name of your event to “‘WAITLIST -’ Event Name”, keep the same dates of your event, and add some minor details in the description to reiterate that this registration is for a waitlist. Once your details have been edited, click “Save and Configure”.

  5. First, you will need to change your SKU or SKUs to be $0. Edit each SKU name to “Waitlist”, then their price by clicking the pencil icon next to the SKU, then select “3. Price” and enter “0”. Once entered, save the SKU, and repeat for each price.

  6. If your event has any add-ons, make sure to detach them. You do not need to include add-ons, as the registrant can pay for them later if transferred into the event.

  7. Scroll down to “Follow-up email” and change the follow up email to read “You have successfully registered for the waitlist. We will reach out to you with further details if someone can no longer attend”. Save

  8. All other facets in your product configuration page can remain the same. Once you have reviewed the waitlist, push your waitlist live on the website!

If your event is full, it may be good practice to Unpublish it from your website, and leave the waitlist live in its place. That way, as you mark registrants for your full event as “not attending”, more registration spots will not open up on your website. This will also allow you to seamlessly transfer registrations without adjusting your overall capacity.

Did this answer your question?