Differentiation between ‘stand alone’ and ‘add on’.

Hi Cyber peeps,

Need some thinking outside the square here so I am hoping someone out there can help.

We are starting to do add ons, one will be the car park.

We have decided that a ‘stand alone’ car park will not incur the transaction fee but will incur a $3 internal charge between departments.

When the car park is sold with a ticket then the $3 internal charge will not be processed at there is a $7.15 transaction fee.

My question is differentiating between the ‘stand alone’ item and the ‘add on item’ in Tess. (can seem to find a practical way to define these…)

Also we have EBMS interfaced with Tessitura so I was thinking about how or if from a financial side of things this could be done?

Any ideas would really be appreciated!

Parents
  • Former Member
    Former Member $organization
    Look into using an embedded fee for the box office's $3 share of the stand alone parking pass (if I am following the transaction correctly).  That should work well.  We use an embedded fee to service a bank loan ($3 off the top of every ticket). Be aware  Tess discounts won't work correctly with embedded fees (probably not an issue here--setup special staff and VIP price types if needed) and counting "sales" may require you to refer to the transaction table instead of t_order, etc.  

    On Feb 28, 2010, at 5:51 PM, "Ranie Daw" <bounce-raniedaw3224@tessituranetwork.com> wrote:

    Hi Cyber peeps,

    Need some thinking outside the square here so I am hoping someone out there can help.

    We are starting to do add ons, one will be the car park.

    We have decided that a ‘stand alone’ car park will not incur the transaction fee but will incur a $3 internal charge between departments.

    When the car park is sold with a ticket then the $3 internal charge will not be processed at there is a $7.15 transaction fee.

    My question is differentiating between the ‘stand alone’ item and the ‘add on item’ in Tess. (can seem to find a practical way to define these…)

    Also we have EBMS interfaced with Tessitura so I was thinking about how or if from a financial side of things this could be done?

    Any ideas would really be appreciated!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Reply
  • Former Member
    Former Member $organization
    Look into using an embedded fee for the box office's $3 share of the stand alone parking pass (if I am following the transaction correctly).  That should work well.  We use an embedded fee to service a bank loan ($3 off the top of every ticket). Be aware  Tess discounts won't work correctly with embedded fees (probably not an issue here--setup special staff and VIP price types if needed) and counting "sales" may require you to refer to the transaction table instead of t_order, etc.  

    On Feb 28, 2010, at 5:51 PM, "Ranie Daw" <bounce-raniedaw3224@tessituranetwork.com> wrote:

    Hi Cyber peeps,

    Need some thinking outside the square here so I am hoping someone out there can help.

    We are starting to do add ons, one will be the car park.

    We have decided that a ‘stand alone’ car park will not incur the transaction fee but will incur a $3 internal charge between departments.

    When the car park is sold with a ticket then the $3 internal charge will not be processed at there is a $7.15 transaction fee.

    My question is differentiating between the ‘stand alone’ item and the ‘add on item’ in Tess. (can seem to find a practical way to define these…)

    Also we have EBMS interfaced with Tessitura so I was thinking about how or if from a financial side of things this could be done?

    Any ideas would really be appreciated!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Children
No Data