We're looking at offering CYO/packages on the web. As a venue, we don't really do traditional subscription-style packaging. Rollovers and seat renewal are not requirements.
The advice that we've received is that in order for package price types to not also be available in the price selection within the single ticket purchase path, packages need to be made available in a separate mode of sale.
We want packages to remain in the same MOS as single tickets so that customers can purchase both in one online transaction and so we're currently investigating solutions. I ask of you:
Thanks,
AdrianaSydney Opera House
Adriana,
We use a separate mode of sale for packages (we only sell NFS packages, same as you), but we do allow people to add single tickets (at a discount, we call them "sub add-ons"). The "Web Subscriptions Order" MOS allows price types for fixed show packages, CYO packages, a child package price type and sub add-ons. But the latter means that to get things to work I have to manually manage which pricetypes can be shown for our SYOS app. Ultimately this leaves me with the question of whether I shouldn't have just done all this explicit pricetype management outside of Tessitura. It would certainly require more time and planning in terms of web development, but would also have potentially allowed more flexibility in our offerings.
--Gawain
Thanks all for your responses. There's a lot to think about.I don't think that switching MOS is an option at all for us. Dale, you're right - there's no need to change pricing for subscribers as we won't have any.We were hoping to filter by price type name or category but are now looking into creating a local table to manage this (McSwain, we need to talk).Thanks again,Adriana