Remove Perf from Sale after Purchase?

Hello all,

This is related to my quest to allow simultanoius on-demand events being setup in advance in Tessitura and sold online, then removing the alternative performances. 

Can anyone envisage a LP that works with the web that allow the following flow:

  1. Customer sees Perf1 on date n and Perf2 on the same date via the calendar or event list.
  2. Customer adds Perf1 to shopping  cart, completes purchase.
  3. Tessitura removes remaining seats for Perf1 from sale.
  4. Tessitura removes Perf2 from sale.

I hope that scenario makes sence.

Even if this sounds foriegn, I would still be very interested to know if anyone has implemented any specific rules that are triggerd by purchasing performancs that could automatically other performances.

Cheers,

Nicholas



[edited by: Nicholas Hudson-Ellis at 7:40 (GMT -6) on 11 Dec 2011]
Parents
  • Former Member
    Former Member $organization

    For a somewhat similar scenario - SOH Tourism sets up a set of performances (one per day per tour-type), with a zone representing each possible timeslot. They put holds on all the seats in all the zones except the basic "every-day"  times, and then they can take the holds off whenever they need to add additional public tours, or to book a private tour into a slot. That's done manually, of course, either using Season Manager or individually.

    Given that the API can modify Holds, could you do something similar from the web by adding and removing holds as needed? You might need some tricky code to get back the list of seat id's to apply the Holds to, but it should be possible to make it work from web code, rather than trying to trigger something automatically in Tess.

    (From the API doc::
    UpdateHoldCode Method

    Overview 

    UpdateHoldCode is used to apply hold codes to seats. Details about hold codes can be obtained using the GetHoldCodes method.  A Tessitura user account ID and password (not a constituent account) are required.)

Reply
  • Former Member
    Former Member $organization

    For a somewhat similar scenario - SOH Tourism sets up a set of performances (one per day per tour-type), with a zone representing each possible timeslot. They put holds on all the seats in all the zones except the basic "every-day"  times, and then they can take the holds off whenever they need to add additional public tours, or to book a private tour into a slot. That's done manually, of course, either using Season Manager or individually.

    Given that the API can modify Holds, could you do something similar from the web by adding and removing holds as needed? You might need some tricky code to get back the list of seat id's to apply the Holds to, but it should be possible to make it work from web code, rather than trying to trigger something automatically in Tess.

    (From the API doc::
    UpdateHoldCode Method

    Overview 

    UpdateHoldCode is used to apply hold codes to seats. Details about hold codes can be obtained using the GetHoldCodes method.  A Tessitura user account ID and password (not a constituent account) are required.)

Children
No Data