I'm trying to create what is basically a buy more save more rule for our evening concerts and am having trouble getting it to work.
Initially we thought it might be because I hadn't set up an appeal or source for it - I just wanted the rule to be applied to ANY orders with six or more seats sold to evening concerts.
I've since added an appeal and source code (though I'm hoping there is a work around on this), and still no luck.
I've made sure my Pricing Rule Set is correct and attached to the MOS I'm using. I've tried setting it up so that it can be applied to any concerts (not just evening) and any price zone (not just level 1 as I initially had it). I've tried creating a whole new rule thinking that maybe if I started over from scratch it would work - but still no luck.
I then tried creating a Product Volume rule - just to see if I could get ANY pricing rule to work - and had success.
Has anyone else been able to create a Seat Volume rule?
Also - does there have to be an appeal and source? It kind of defeats the purpose of my ticket staff not having to think about this discount, and also how can I track other marketing sources if I'm forced to use the one specific to this rule?
Thanks
Hi Toni,
You do not have to select an appeal and source for pricing rules to work.
Seat volume rules require that all seats are purchased for the same performance. When you say “six or more seats sold to evening concerts” are you intending (and then testing) that they are all reserved for the same concert?
In your rule criteria, what have you set the “Purchase X to Y seats” range to? And what have you set “to a maximum of z seats” to?
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Hi Kevin,
So my objective is to reward patrons who purchase 6 or more tickets to any of our evening performances. Ideally this would be an automated process – both for online orders and orders placed through my ticket office. Perhaps pricing rules isn’t the way to go. Would a flexpass work better for this?
Toni
Direct: 505-982-1890
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Kevin Sheehan Sent: Thursday, January 12, 2017 7:12 AM To: Toni Pittman Subject: RE: [Tessitura Ticketing Forum] Seat Volume Pricing Rule
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
It sounds like what you want is a Product Volume rule rather than a Seat Volume rule. But let’s talk through some examples just to be sure.
Let’s say we have Perf A, Perf B, Perf C, Perf D, Perf E, and Perf F.
A Product Volume rule would be purchase at least 1 ticket for all 6 performances and receive a discount. To trigger this rule you would have to purchase at least 1 ticket to Perf A, B, C, D, E, and F. This is essentially what a flex package is as well (groups of performances you set up where you set a minimum and maximum number of performances that must be selected).
A Seat Volume rule would be purchase 6 or more tickets to the same performance, like 6 tickets to Perf A, and receive a discount on those tickets. Buying 2 tickets to Perf A and 4 tickets to Perf B would not trigger this kind of rule.
What’s not possible is to set up a pricing rule where you a customer could buy 1 ticket for Perf A, 3 for Perf B, and 2 for Perf F in order to reach a total of at least 6 tickets and then receive a discount for all 6 tickets.
To sum up, you can set up a rule that counts the number of tickets for a single performance (Seat Volume), or the number different performances in the order (Product Volume).
Does that help clarify?
Kevin Sheehan said:What’s not possible is to set up a pricing rule where you a customer could buy 1 ticket for Perf A, 3 for Perf B, and 2 for Perf F in order to reach a total of at least 6 tickets and then receive a discount for all 6 tickets.
Hey Kevin Sheehan, is this still not possible?
That's correct. It is still not possible.
well damn, thanks for your quick response.
Kevin Sheehan Eric Oliphant Darn - I came here looking for a similar solution to my pricing rule woes. Any idea if applying a volume based rule to a production season is in the works?
Joel, I was looking for this thread to send a link to one of our users and saw your comment. I missed it the first time. I think the ability to do volume rule to perfs inside a package is included in v16: "A new checkbox, Apply to performances within a package, has been added to pricing rule criteria. When checked, component performances in a package can qualify for the rule. This can be useful when you want the performances chosen as part of a flex package to qualify for a rule."
Hi Eric,
I saw that too and am excited for that feature! But it would also be awesome to be able to apply a product volume rule on the entire *production season* for volume discounts that aren't per performance but across the entire prod season. The Flex pass fixes it, but still requires exchanging, instead of natively applying the discount.
And here is my shamless plug for this idea on the ideas board: https://community.tessituranetwork.com/ideas/i/ideas/pricing-rules-evaluate-at-the-production-season-or-order-level
Totally agree! Just upvoted your idea.
Thanks!
Upvoted!