Hi everyone,
It’s the age-old ‘reporting on subscriptions’ question… I am not concerned so much about the financials (finance is happy with gl reporting), but I need to get an accurate count of how many packages have been sold/we are selling. It doesn’t matter to me if a show has been exchanged/returned/donated as long as that doesn’t affect the package sales number (they’re still a subscriber if they ditch one of their shows). Likewise, I *do* need the number of subs sold to reflect if a package is returned in its entirety.
If I do a simple TStats report of ‘package name x number of package seats, filter-sliced by season’, that seems to match the Package Sales Report. And at first glance it seems to be exactly what I want. But…. it isn’t close to the Package column in the Performance Sales Summary by PT Category report, which is what has historically been used at my org.
Previously, subscriptions have been reported by using the Performance Sales Summary by PT Category report and picking, say, production #2. In theory, this should work because all of our subscription price types have the subscription category on them (and it’s not on anything else) and we’re only working with full-packages to start with. But it looks like this report is affected by partially paid orders, not to mention it gets very messy when we get into cyo and peel-off packages.
In your opinions, which out-of-the-box method is the most accurate way of reporting on package numbers (I don’t think customization is an option at the moment)? My thought is that TStats and the Package Sales report would be best, if it’s a true and accurate representation of the number of whole packages, but I worry about the difference between that and the Performance Sales Summary by PT Category report. Any advice/musings gratefully appreciated, and I’d be happy to help you out with something in trade J
Cheers, Kathleen
Thank you, Shelley and Nicole! It’s kind of what I’m thinking, and I know the team here will appreciate the outside voices.
Cheers,
Kathleen
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nicole Keating Sent: Wednesday, April 08, 2015 5:43 PM To: Kathleen Smith Subject: RE: [Tessitura Ticketing Forum] accuracy of subscription reports
The discrepancies I usually see in T-Stats are eliminated when I pull in SubLineitem Status.
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Shelley Osburn Sent: Wednesday, April 08, 2015 5:32 PM To: Nicole Keating Subject: RE: [Tessitura Ticketing Forum] accuracy of subscription reports Importance: High
T-Stats works for me. We only use Flex packages so the canned sub reports don’t count those.
Shelley Osburn
Systems Services Manager
I have no idea if this will be helpful, but in reckoning with this issue in the past I was referred to this link:http://www.tessituranetwork.com/Community/groups/tstats/wiki/matching-package-sales-report-to-t-stats.aspx Our company sells Reserved & Flex subscriptions, had been reporting on them using a TSTATS workspace I inherited from the past individual in my position. Higher-ups noticed a lot of inconsistency in package reporting, specifically the flex packs, so I built the TSTATS workspace linked to above in an attempt to figure out where the discrepancies are occurring. The short answer is that I'm still unsure but the workspace I built matches the Package Sales Report very closely when "mixed" sub line items are included.From my conversation with a JCA (the developers of TSTATS) tech, she mentioned a couple things that might be pertinent as well: "Remember that T-Stats is not live data it’s a nightly refresh and that there may be small variances between T-Stats and Tessitura due to activity that has taken place since the load completed. Something else that you could ask your IT staff to do is to check your T-Stats SQL Job Load parameters for the exclusion of certain package price categories, resold seats or unfulfilled rollover orders."