Hello,
We are upgrading our website and are looking to see if anyone has come up with a creative way to sell an online flex subscription package that doesn't use the API technology even in v10.0? I am being told that the user experience will be very "messy" if its done the way that the API provides for.
My biggest concern is that if we just call it a bunch of single tickets in an order even if a special price type is used, its never going to look like a "package" in Tess. I fear for the integrity of the data to report on later , if its set up as a bunch of single ticket order lines instead of one package line.
Has anyone tackled this problem? What did you do? Help!
Thanks!
Hi Amy,I don't think the user experience is messy - I'd be interested to hear why. I think you could easily make it messy but it doesn't have to be. There's a number of contributing factors, including seat selection.Our subscription package is basically just a flex package and the seating is completed later by an operator, not on the website.You can take a look: bellshakespeare.com.au/packages