• Replies 4 replies
  • Subscribers 416 subscribers
  • Views 105 views
  • Users 0 members are here
Related

Advanced vs Day-of Pricing, for every performance

Nathanael Pearson
$organization

Hi all,

We're looking into having a pre-sale price and day-of price for one of our exhibits. We'll have ~250 performances for the whole year (starting May-ish). We want tickets purchased day-of to be one price ($X), and tickets purchased in advance to be a lesser price ($Y). I see three ways of doing this:

  1. work with Digonex (our dynamic pricing partner) to automate the price events each day
  2. set uponea pricing event for the standard price type, for each performance
  3. Have a 'pre-sales' price type, and a 'day-of' price type, with the different prices. 'Day-of' would only be available on the Performance Date, 'Pre-Sales' would only be available before the Performance Date

I dislike having multiple Price Types when one would suffice, but I also dislike having ~250 Price Events, each one performance-specific. What are your thoughts? Are there time-efficient ways to do this?

Parents
  • $organization

    Nathanael,

    Zero help for you right now, but I do love the notion of a relative date option for updating/creating pricing events in Season Maintenance.  That seems like a highly useful notion as I think many places could potentially benefit from that.  Because given the above, I do think that 2 would be the best solution with the massive exception that that would be a giant pain to set up in the first place.

    I do feel like there is probably a SQL way to to achieve what you want there, though that Digonex or maybe someone on staff would be able to do that could potentially save someone some headaches.  I have done some dynamic inserting of pricing events through the database, so it is definitely possible.

    Best of luck.

    John A. Moskal II

Reply
  • $organization

    Nathanael,

    Zero help for you right now, but I do love the notion of a relative date option for updating/creating pricing events in Season Maintenance.  That seems like a highly useful notion as I think many places could potentially benefit from that.  Because given the above, I do think that 2 would be the best solution with the massive exception that that would be a giant pain to set up in the first place.

    I do feel like there is probably a SQL way to to achieve what you want there, though that Digonex or maybe someone on staff would be able to do that could potentially save someone some headaches.  I have done some dynamic inserting of pricing events through the database, so it is definitely possible.

    Best of luck.

    John A. Moskal II

Children
No Data