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
Hi Adriana
ACO does CYO packages on the web in the same MOS.
But that's a bit of special coding from Lynch, and some local table work - there's effectively a whole module in there for dealing with CYO (aka NFS) packages neatly. We like it.
If you have a look at LTR_ACO_PRICETYPE_RULES, you'll see that we use a local table which controls which pricetypes can be used in various contexts, including "NFS Pkg" - so our "PAK3" pricetypes are only available in that context, and not in the "Single Tix" context, and other pricetypes are not available in the NFS context. That sort of thing is a fairly straightforward way of getting around the limitation, but obviously, the rest of the site has to be made context-aware if you take that route, so it might involve a moderate amount of webdev work, depending on how the rest of the purchase path works.
K