incorrect capacity in performance summary

Interesting problem: for 3 events in the same venue the capacity $$ as reported in the Performance Summary bears no relation to the actual capacity $$ (the number of seats is correct).  The reported capacity is more than double what it should be.  What the three events have in common is that they have the same price scale and the prices were increased in a new price layer (all old prices have been expired).  The inflated capacity $$ is exactly the same for all 3, HOWEVER:  the reported subs, singles, discount and total sales are all correct.  The Lost to Discount and Total Unsold are also wildly inflated.  There is no problem with the other events in the same venue, none of which had their prices increased.  All the events in the venue use the same Price Zone.  Suggestions?

Parents
  • Hi Ellen,

    I think the capacity is calculated on the base price.  If two price layers are both marked as base price then the capacity calculation will probably add them together even if the old one is expired.

    If this is the case you then need to choose which layer you want to use as base price.

    Jared

  • I think I've come across this issue once before where we had the wrong price set up on an event and it was realised after we'd sold some tickets.  We added a new price and removed the old one but the result was that Tessitura added both the old base price and the new base price together which increased a lot of things in season overview such as the potential sales and the loss to discounts.

     

    You can view what has happened in Performance Sales Analysis report, you will see your price bands at the top with their base price - you'll probably see that the base price being calculated is the 2 prices added together.  

    Underneath each price band column you'll be able to see how many tickets were sold at each price type and that none of them will be the inflated amount and will be the actual amounts that people paid, but as far as Tessitura is concerned the base price is that of the column heading and calculates accordingly.

    Since our experience we've never changed the base price of events after selling tickets.

Reply
  • I think I've come across this issue once before where we had the wrong price set up on an event and it was realised after we'd sold some tickets.  We added a new price and removed the old one but the result was that Tessitura added both the old base price and the new base price together which increased a lot of things in season overview such as the potential sales and the loss to discounts.

     

    You can view what has happened in Performance Sales Analysis report, you will see your price bands at the top with their base price - you'll probably see that the base price being calculated is the 2 prices added together.  

    Underneath each price band column you'll be able to see how many tickets were sold at each price type and that none of them will be the inflated amount and will be the actual amounts that people paid, but as far as Tessitura is concerned the base price is that of the column heading and calculates accordingly.

    Since our experience we've never changed the base price of events after selling tickets.

Children