• Replies 10 replies
  • Subscribers 414 subscribers
  • Views 109 views
  • Users 0 members are here
Related

How to Handle Specialty Discounts? (Ex. 1 Free Adult with Child Ticket Purchase)

Chelsea Marti
$organization

Connecticut offers a CT Summer Free at the Museum program where museums get grant money to cover the cost of adult tickets that get purchased with children's tickets. The exact discount is "1 Free Adult (or Senior) with purchase of Child ticket." 

Last year we set this up as a source code that was attached to a pricing rule. That works great for our online sales (and we plan on doing it that way for TNEW this year), however for in person sales it was difficult for our VSA staff to constantly switch between Source Codes. They would forget to switch back in between sales and our data coming out of last year is a little skewed because of it. 

To make their lives easy, I just want to set up a discount. The problem is it looks like there is no way (as far as I understand) to only put the discount on X number for each ticket type. It'll let me give a 100% discount on the adult ticket type, but it will not limit it to only 1 ticket. 

For example, if a VS Associate sells 2 adults and 2 children, we only want the discount pulling off of one of those adult tickets, not both. 

Is it possible to do this via discounts, or are we stuck using the Source Code attached to the pricing rule like last year (which wasn't useful and was difficult)? 

Parents
  • $organization

    Hi Chelsea,

    You can accomplish this with a Multiple Price Type rule, which is triggered based on a combination price types purchased together, such as a mix of Adult and Child tickets.

    1. Set the Action for the rule to (map price types)
    2. Set the range of qualifying Adult tickets to 1 to 999 and the range of qualifying Child tickets to 1 to 999. This controls when the rule is triggered, but not how many tickets can get discounted. You set a large range because you don't want the rule to not trigger at all if people are buying more than 1 Adult and 1 childe.
    3. Click the Price Type Mapping button to open the mapping window and then map the Adult price type to whatever comp adult price type you are using. Map the Child price type to the Child price type (the net result of which will be that the Child price type doesn't get changed)
    4. Set the maximum on the Adult price type (listed as the first set of price types) to 1. This means no more than 1 Adult ticket will get changed to comp.
    5. Set the maximum on the Child price type (listed as the second set of price types) to 1. This number doesn't really matter since we aren't actually changing the Child price types, but might as well limit the fake change to just 1 ticket.
    6. If you are including Senior tickets in this as well, you just add the Senior price type to the first set of price types with the Adult price type and map that price type to a comp price type when you do the price type mapping part.

    This should get you a rule that is automatic with no source codes required. I did a quick test in my system just now and it worked pretty well.

Reply
  • $organization

    Hi Chelsea,

    You can accomplish this with a Multiple Price Type rule, which is triggered based on a combination price types purchased together, such as a mix of Adult and Child tickets.

    1. Set the Action for the rule to (map price types)
    2. Set the range of qualifying Adult tickets to 1 to 999 and the range of qualifying Child tickets to 1 to 999. This controls when the rule is triggered, but not how many tickets can get discounted. You set a large range because you don't want the rule to not trigger at all if people are buying more than 1 Adult and 1 childe.
    3. Click the Price Type Mapping button to open the mapping window and then map the Adult price type to whatever comp adult price type you are using. Map the Child price type to the Child price type (the net result of which will be that the Child price type doesn't get changed)
    4. Set the maximum on the Adult price type (listed as the first set of price types) to 1. This means no more than 1 Adult ticket will get changed to comp.
    5. Set the maximum on the Child price type (listed as the second set of price types) to 1. This number doesn't really matter since we aren't actually changing the Child price types, but might as well limit the fake change to just 1 ticket.
    6. If you are including Senior tickets in this as well, you just add the Senior price type to the first set of price types with the Adult price type and map that price type to a comp price type when you do the price type mapping part.

    This should get you a rule that is automatic with no source codes required. I did a quick test in my system just now and it worked pretty well.

Children
  • $organization in reply to Kevin Sheehan

    Normally I would love this, but it is for CT residents only. We do get patrons that would fit this description from out of CT (who wouldn't be eligible for this pricing rule).

  • $organization in reply to Chelsea Marti

    I see. You could set up CT resident price types to use during the time period when this offer is active, and then only have those price types trigger the rule. It would increase your setup somewhat, and require a bit of extra training for your operators, but the advantage to going that route over the source code route is that it's not sticky. The choices they make in one order wouldn't affect the next order. And if they make the wrong choice (choose the resident price types when they shouldn't or don't select them when they should) it would become apparent fairly quickly based on the application or non-application of the rule. You could even use pricing rule messages to make it clear what they are selecting (the message displaying with the rule is applied as well as a rule that just triggers a message when a non-resident price type is selected to ask the operator if that is what they meant to do).