We are preparing for a large annual sales weekend for local residents, and this year we are trying to format our discount options a little differently. I'm posting this with hopes someone can give some advice and/or tell me something I'm trying to do is not possible.
Goal: To encourage buyers to purchase tickets to more than one performance.
Deal: Have one price that buyer pays if they purchase ONE performance. Have a different price (lower price) that buyer pays if they purchase 2+ performances. Discounts only apply to certain seats (price zones).
Example:
On "locals weekend", I purchase a Swan Lake ticket for the discounted price $40 (full price $70). BUT, if I purchase another performance with my Swan Lake ticket, the price drops to $35 for Swan Lake.
Here's my current plan for setup (we used TNEW):
1.) Create a MOS just for this sale entitled "Locals Weekend"
2.) Use promo code for MOS switch from Web to Locals Weekend
promo code is LOCAL*18
3.) Create 1 price type called "Locals Single", and 2nd price type called "Locals Multi". Locals Single is used if customer only wants to buy one performance. Locals Multi is used if they buy 2+ performance.
4.) Add these 2 price types to all performances that we want to discount, set discounted prices, and un-enable any price zones we want to exclude from deal
5.) Add Locals Weekend MOS to discounted performances- add Offer to that MOS on all discounted performances- I want the promo code to only show Locals Single when entered.
6.) Create Pricing Rule- Product Volume, that triggers a price type change to Locals Multi if 2+ discounted performances are added to the cart (Locals Multi price type is NOT seen until 2+ performances are added)
I know I'm skimming over some steps above but that's my outline so far. Basically, no one without the promo code LOCAL*18 should be able to select a Locals Single or Locals Multi price (to keep the sale hidden to everyone except local residents or anyone with the promo code). And no one purchasing just one performance should be able to select or have the Locals Multi price applied to their performance (because they would receive a deeper discount than intended).
Hopefully that makes sense to some of you. Would love to hear if you've done this kind of thing before.
We have a similar set-up for the buy-more, save-more discounts for one of our clients (3-show, 4-show, and 5-show discounts). They also have rolling on-sale dates (high level donors, medium level donors, then public), so donors are given promo codes that unlock their respective MOS. Since the MOS start dates manage the on-sale access dates, the pricing rules can be active as of the first date and work for all three MOS. I strongly recommend applying this rule internally for your staff, rather than just online - it saved us tons of training and human error.
We actually had to dive even deeper into it last year because one show had a pre-sale months earlier, so anyone who already bought that show needed the buy-more, save-more discount to trigger one show earlier for them. For those people, we had three separate pricing rules that were associated with constituent criteria (tied to a list of those ticket buyers) and were built to trigger one show sooner for each discount level. Then we ranked the rules so these special rules were ranked above those for new buyers.
If you have any trouble as you build I'd be happy to send you more info about our set-up :)
We have done similar things for Black Friday/Cyber Monday deals as well. Agreeing with Anna; with pricing rules, it is easiest if you just have the turned on to your Phone/Window MOSes, too, so as to minimize what your staff needs to remember. It has worked well for us.
I am also happy to assist if you have questions on the set-up, but it sounds like you are fully on the right track!
John