Greetings!
We are looking to switch to TNEW, but that will require us to start putting our Facility Fee (which is included in the advertised price) in a price layer instead of using a custom call on the web. What considerations do I need to keep in mind while I implement this transition? We've used layers before but I was so frustrated with reporting and not being able to see the fee in ticket processing that I vowed never to do it like that again, but here we are! How will this switch to using layers impact our ticket sellers and processing exchanges/returns? What are your favorite reports that break out price layers? How can I structure this to make reporting easy? This is a big deal for us, and I need to make sure I think this through before jumping in!
Looking for any insight as I solve this problem!
Thanks!
Erin Korthals
Database Administrator, Orchestra Iowa
*cross-posted in Admin/IT
Erin,
We've been doing it this way since being on Tessitura, in fact, we even layer our season ticket handling fees like this....I LOVE it. Price layers follow the order, so as long as you don't turn off a layer, you shouldn't see any changes to how to you exchange tickets.
A few things to be wary of:
Please feel free to reach out if you have more questions, happy to help.
Good luck,
Kimberly Darlington / SVP Ticketing, TPAC
There is also support for price layers in Analytics (I think for version 15.1+)... and 100% what Kimberly said
To continue with Kimberly's advice, here are some standard reports that include a Price Category parameter, which lets you filter out facility fee layers:
-Michael