PatronManager Help

How to Set Up a Choose Your Own Subscription

Updated on

Use this link to share with your colleagues:

How to Set Up a Choose Your Own Subscription: https://help.pm.leapevent.tech/a/870767

This article will walk you through the basics of building a Choose Your Own subscription. As is suggested by the name, this type of subscription gives your patrons the option to choose a pre-determined number of events from a pre-defined list of performances.

We'll show you how to:

  1. Map out your season and packages
  2. Build out your season
  3. Build your subscription framework
  4. Build the subscription packages

Ready? Let's go!

First, define your packages and pricing

We can't build anything until we know exactly what it will entail, right down to the nitty-gritty details. You may want to start this process on paper, or in a spreadsheet; whatever makes sense to you.

Let's get started!

1. Map out your season and your packages

We're diving deep into box office management in this article; go here if you need to brush up on your options when it comes to Ticketable Events and Event Instances. An understanding of how those two objects work is key to building subscription packages.

You can't build your subscription packages unless you know what you're selling. So start by gathering the following:

  • The productions in your upcoming season, with their performance dates and times
  • What subscription options you'll be selling- i.e. a Pick 3, a Pick 5, etc.
  • The price points for your subscription packages
  • The price points for your single tickets

In this article, we're specifically looking at choose your own subscriptions, meaning that patrons choose a predetermined number of shows from a list you provide- i.e. a Pick 3 or a Pick 5 package. These choices have to be made at the time of the subscription purchase- the key difference between this package and a pick later package.

If you're looking to create a fixed subscription, click here.

If you're looking to create a pick later (i.e. flex pass or voucher subscription), read here.

Unsure what we mean when we refer to these three different subscription models, and what type you need to set up? Read here.

2. And Now For Some Math

In PatronManager, the total cost of the subscription is the sum of all of the price levels in the subscription. 

This means that you should divide the total cost of your subscription by the number of events in that subscription, and the resulting number should be the cost of your subscription price levels. Sometimes the numbers won't divide evenly, in which case you can make the individual event price levels slightly different from one another. For Choose Your Own packages, it is best if your subscription cost divides evenly.

In this example, we want the subscription to cost $150 for a Pick 3 package. The customer can choose three events with this package. 3 divides evenly into 150, so the price will always be $50 per show.

What if the total cost doesn't divide evenly?

For Fixed subscriptions, you can slightly vary the price of tickets across the different Events that make up the package, in order to arrive at the correct total cost. For Choose Your Own packages, this method is not recommended, since you can't control which specific Events the patron will choose (that being the whole point of the "Choose Your Own" aspect). Instead, it's best if the cost of your Choose Your Own subscription is evenly divisible by the number of selections the patron will make.

If the price of tickets the patron might choose to complete their Choose Your Own package vary, the total cost of the package will appear as a range on the Public Ticketing Site, with the lowest amount being the cost if they chose all the lowest-priced tickets, and the highest amount being the cost if they chose all the highest-priced tickets.

Now build out your retail Events

Before we can build a subscription package, we need to build all the pieces that will make it up. You can think of your subscription Event as a nice fancy envelope, and the retail Events as the tickets you'll put into that envelope.

It's time to build out your season Events and Instances, along with the subscription Price Levels you'll need for each one - you can think of this step like assembling all the tickets you want to sell in these packages.

Sounds good, let's build out the season

If you've already built the shows of your season in PatronManager, skip ahead to create your subscription Price Levels as described in step 3.2 below. 

1. Create your first Ticketable Event and Instance

It's time to set up a single Event that will be the first show in your season and subscription package.

Set up one Ticketable Event, and one Event Instance within that Event, for the first show in your upcoming season that will be part of your Choose Your Own subscription package.

Do you need to brush up on building events? Here you go:

How to Create a New General Admission or Reserved Seating Event

Be sure to build *new* or *newly cloned* Events each season, rather than re-using last season's Events. If you don't start with new Events, you may encounter problems with exchanges and reporting later on.

2. Double check the Allocations on the Event Instance

When you set the Venue on the Event Instance, it automatically has a set of allocations that are created for your Event. Rename them and/or reallocate them if they aren't correct - here's where you can read up on that process.

3. Create your single ticket and subscription Price Levels

You'll create both your single ticket Price Levels and the set of subscription Price Levels that you'll use a bit later to build your subscription packages. Here are specifics on creating those subscription Price Levels:

3.1. Set the Visibility for the subscription Price Levels to "Subscription"

3.2. Create a subscription Price Level for each package you offer

If you offer multiple subscription prices/packages for the same Allocation (such as Adult vs Student, or Fixed vs Choose Your Own), create as many subscription Price Levels as you need to make up each subscription pricing option.

3.3. Create subscription Price Levels in every Allocation you sell as a subscription package

By this, we mean that you sell a subscription package at one price point in the premium orchestra, and another price point in the orchestra. You would create subscription Price Levels on both the premium orchestra and regular orchestra Allocations.

4. Clone the completed Event Instance as needed

Once you have your first Event Instance set up to your liking with both single ticket and subscription Price Levels and correct Allocations, clone the Event Instance until you have as many Instances (i.e. performances) as you need for that particular Ticketable Event.

5. Clone the Ticketable Event along with Instances to build out the rest of your season

Got your first full Ticketable Event set up? Great! Now, clone it and edit the details (and delete or add Event Instances, as well as adjusting names and dates for each) to build the rest of the shows in your upcoming season.

Nice job! Now it's time to build the framework for your subscription packages

Once your single ticket Event Instances are set up with the Price Levels that will make up your subscription packages, you can build the packages themselves. Think of this like printing the envelopes which will hold all those subscription tickets.

I'm ready, let's build the subscription package framework!

1. Go to the Event Inventory tab and click "New Ticketable Event"

2. Name your subscription, change the Type to "Subscription" and click "Save"

This is the top-level grouping for the set of subscription packages you'll sell within this Event.

Q: How should we organize subscription packages?

A: This is a great question, and there are several things to consider in making this decision, from reporting to display on the Public Ticketing Site. For a complete overview and demo, check out this recorded webinar on Subscription Package Best Practices.

We typically recommend a single subscription Ticketable Event if you have a limited number of subscription packages, each with similar marketing and perks. In that case, your subscription Event would be called something like "2022 Subscriptions."

If you have a wide variety of packages and/or if the marketing and perks vary between them, it can be easier to communicate the differences to patrons by grouping them into separate subscription Ticketable Events. In that case, your subscription Events might have names like "2022 Fixed Subscriptions" and "2022 Choose Your Own Subscriptions."

We recommend you set up your Subscription Event Inventory as follows:

  • Ticketable Event: the year of your subscriptions, or a subset of the type of subscription for that year
    • e.g. "2025 Subscriptions" or "2025 Choose Your Own Subscriptions"
  • Event Instance: each subscription package you plan to sell
    • e.g. "Pick 3", "Pick 4" etc.
  • Allocations: create Allocations to mirror the sections in your single ticket Event Instances (the Event Instances that make up your season)
    • e.g. "Premium Balcony", "Mezzanine", etc. or "Tier 1", "Tier 2", etc
  • Price Level: if you're selling different price points for subscription packages in the same Allocation, detail those
    • e.g. "Adult Subscription", "Senior/Student Subscription", etc.

Want patrons who buy this subscription to automatically receive a subscriber badge? Set the "Subscriber Badge" picklist to "Current"!

You can change this value at any point, and badges for your patrons will automatically update the following day.

3. Scroll down to the bottom section and click "New"

4. Name the Event Instance for your first subscription package

The Instances are going to be the individual subscription packages, so name your Event Instance after the package you're offering. Set the Instance Date to be the last possible date someone could buy the package - i.e. if it is a Pick 3, pick the date of your third to last eligible performance.

5. Set the Subscription Type and Number of Selections

Select "Choose Your Own" from the "Subscription Type" field, then fill in the number of shows the patron will need to pick in the "Number of Subscriber Selections" field.

Make sure that you pick the correct Subscription Type! After associating Price Levels with this subscription, you won't be able to change the Subscription Type anymore.

6. Choose a Venue if applicable

Only set a Venue here if all subscription performances take place in that same venue. If your retail Events take place in multiple Venues, leave this blank.

7. Click "Save"

8. Turn on PYOS subscriptions (optional)

If you'd like to give your patrons the ability to choose their own seats online when they purchase this subscription, you can turn on Pick Your Own Seat (PYOS) subscriptions.

To do this, first click "Edit"

Click Edit

Then check "Enable Online Seat Selection" and save.

Check Enable Online Seat Selection

9. Create a new Ticket Allocation

A quick note about subscription Allocations and Price Levels: when you're finished, each subscription Price Level should map to exactly one retail Price Level on any given Event Instance. That means there should also be a one-to-one correlation between subscription Allocations and Allocations on your retail Event Instances.

Said differently, if you sell Adult and Student subscriptions and your venue has three Allocations, you'd have three subscription package Allocations, each with an Adult and a Student subscription Price Level, for a total of six different package options.

Set the Sale Status to "Public" if you want to sell subscriptions online (remember they'll only be available to purchase online after the "Sale Start Date" on this subscription Event Instance), or "Private" if you only want to sell the package internally.

Each subscription Allocation should correspond to single Allocation on each of your retail Events, like "Orchestra". If the Allocations on your retail Events have varying names due to multiple Venues, you can name your subscription Allocations something like "Tier 1" and "Tier 2" instead.

10. Add the number of packages available in this Allocation to the Original Quantity field, then click "Save and Create Level"

11. Add as many subscription Price Levels as you want to offer for this Allocation

For example, "Adult" and "Student".

You'll notice the Price column is blank. Don't worry! We'll take care of that later.

12. Enter fees as applicable for each subscription Price Level

Subscription package item fees are set here, for the package as a whole. Any fees you set on the subscription Price Levels you built on your retail Event Instances won't be applied, since the tickets are being sold as a group via this subscription Event Instance.

13. Clone the Event Instance to create other subscription packages

Once all your Allocations and Price Levels are set up, click "Clone" to make more package options (e.g. a "Pick 4" and a "Pick 5"). Clone for as many packages as you want to offer, adjusting the dates and Number of Subscriber Selections as needed for each one.

When building multiple packages, the Instance Date controls the order in which the packages are listed. Make each package's Instance Date an hour later than the previous package for easy sorting.

Great work! Now we can connect everything together to create the actual subscriptions

In this final step, we'll link the retail subscription Price Levels to the subscription package framework you built in the last step.

To complete our metaphor, you've got all your season "tickets" built out, you've printed your "envelopes" - now it's time to assemble the whole thing - stuff the "envelopes" with "tickets" so you can start selling!

Sounds good, let's hook it up!

A quick note about what we're doing: since these are Choose Your Own subscriptions, each package will be mapped to all the valid "tickets" that a patron could choose between for that package.

Here's an example

Let's say you have a five-show Shakespeare season, in a venue with two Allocations - Orchestra and Balcony. Each Event (i.e. Hamlet) has three performances, on Friday, Saturday, and Sunday. Because you have five Events, each with three Instances, you'd have a total of 15 retail Event Instances.

You sell Adult and Student subscriptions, and you're building a "Pick 3" Choose Your Own subscription, where the patron can choose three of the fifteen total Event Instances.

Retail Event Instance example

Each retail Event/Instance would be structured like this example (though probably with more single ticket Price Levels):

  • Ticketable Event: Hamlet
    • Event Instance: Friday Feb 3 at 8:00 PM
      • Allocation: Orchestra
        • Price Level: Regular (single ticket)
        • Price Level: Adult Subscriber (subscription)
        • Price Level: Student Subscriber (subscription)
      • Allocation: Balcony
        • Price Level: Regular (single ticket)
        • Price Level: Adult Subscriber (subscription)
        • Price Level: Student Subscriber (subscription)

Subscription Event Instance example

Then your Pick 3 subscription Event/Instance (aka subscription package) would have this framework, with a total of four subscription Price Levels split between two Allocations:

  • Ticketable Event: 2025 Subscriptions
    • Event Instance: Pick 3
      • Allocation: Orchestra
        • Price Level: Adult Subscription
        • Price Level: Student Subscription
      • Allocation: Balcony
        • Price Level: Adult Subscription
        • Price Level: Student Subscription

Subscription Price Level mapping example

And each of those four subscription Price Levels would be mapped to a corresponding set of fifteen retail Price Levels - one for each of the 15 retail Event Instances (remember, the patron will choose 3 from among these options).

The "Adult Subscription" Price Level in the "Orchestra" Allocation on the subscription Event Instance maps to the following 15 retail Price Levels:

  1. Hamlet, Friday Feb 3 at 8:00 PM, Orchestra, Adult Subscriber
  2. Hamlet, Saturday Feb 4 at 8:00 PM, Orchestra, Adult Subscriber
  3. Hamlet, Sunday Feb 5 at 8:00 PM, Orchestra, Adult Subscriber
  4. Othello, Friday Mar 3 at 8:00 PM, Orchestra, Adult Subscriber
  5. Othello, Saturday Mar 4 at 8:00 PM, Orchestra, Adult Subscriber
  6. Othello, Sunday Mar 5 at 8:00 PM, Orchestra, Adult Subscriber
  7. Macbeth, Friday Apr 3 at 8:00 PM, Orchestra, Adult Subscriber
  8. Macbeth, Saturday Apr 4 at 8:00 PM, Orchestra, Adult Subscriber
  9. Macbeth, Sunday Apr 5 at 8:00 PM, Orchestra, Adult Subscriber
  10. The Tempest, Friday May 3 at 8:00 PM, Orchestra, Adult Subscriber
  11. The Tempest, Saturday May 4 at 8:00 PM, Orchestra, Adult Subscriber
  12. The Tempest, Sunday May 5 at 8:00 PM, Orchestra, Adult Subscriber
  13. King Lear, Friday Jun 3 at 8:00 PM, Orchestra, Adult Subscriber
  14. King Lear, Saturday Jun 4 at 8:00 PM, Orchestra, Adult Subscriber
  15. King Lear, Sunday Jun 5 at 8:00 PM, Orchestra, Adult Subscriber

1. Head to your first subscription Event Instance

2. Click "View/Edit Price Levels" next to the first Price Level in the package

Click "Expand All" to open up the Allocations if the Price Levels are hidden - and note that there's a default setting you can adjust in PatronTicket Settings to have them expanded automatically, which is handy while building subscriptions!

3. Use the filters to get the retail subscription price levels you created for this package on one screen

Set the "Visibility" filter to "Subscription," and use the Price Level and Allocation filters as well. You can filter by Ticketable Event," and use the "|" character to search for multiple events at once. In this example, we've entered five of the Events in this series by typing a "Zorba | Chicago | Kiss of the Spider Woman | The Scottsboro Boys"

Not seeing any Price Levels?  Make sure the Ticketable Events and the Event Instances that you're filtering for are set to "Active".

You can also use asterisks to narrow your results, in addition to the | character

Here are some tips on using them:

  • If you only type the * after the text in the field, it will only find matches for any Ticketable Event (or Event Instance, or Allocation, or Price Level) that has different characters after the asterisk. For example, if you typed S* in the Event Instance, it would find any Event Instance that started with an S, like "Saturday", or "Sunday". It wouldn't return "Thursday", even though Thursday contains an S, because Thursday doesn't begin with an s.
  • If you put an asterisk before and after the text in the field,like this- *S*- it will find any match that contains that character or string. It would find "Sunday", "Saturday", and "Thursday" (as well as "Tuesday" and "Wednesday" for that matter).

4. Associate the correct Price Levels for this subscription package

If you've been able to isolate only the specific Price Levels you're adding to this subscription Price Level, you can click the "Associate All Price Levels" button - otherwise you can use the checkboxes on the left and then click "Associate Selected Price Levels".

The associated price levels will move to the top. You can adjust filters and repeat this process if you need to add more Price Levels for this subscription package.

5. Once you've associated all the right Price Levels, click "Done"

6. Review the number of mapped levels and the resulting price

Back on the subscription Event Instance, you'll now see the number of retail Price Levels associated with the subscription Price Level, as well as the resulting price of the package.

Because this is Choose Your Own package, you'll see more price levels than the patron will be able to select (yay, options!).

The package in this example has a price range from the lowest to the highest possible package price. This is because our total cost didn't divide evenly - if you want a single total cost, each retail Price Level the patron could select must have the same amount.

7. Repeat this process for each subscription Price Level to finish building your packages

That's it - you've built your Choose Your Own subscriptions! Nice job!

Previous Article How to Set Up a Fixed Subscription
Next Article How to Set Up a Pick Later (Flex Pass) Subscription
Still Need Help? Continue to the Client Community