I have a couple questions about the basic Web API functionality. Your answers could potentially save me a lot of time in testing these scenarios:
Thanks,Bryan
1.Since promo codes basically are source_nos and an order can only have one of those at a time, I don't think you can have multiple promocodes applied at once. But I'm not positive about that.
3. A promocode does not have to change the mos. We have many offers that work in the default web mos tied to promocodes.
5. Pretty sure it does.
Thanks, Ms. Freeman! I have a followup question.
Re: #1 The document, Tessitura and the Web, states on p. 24, "It is possible to code a website to change the source code several times, which some organizations use to unlock multiple discounts, but only one source code can be recorded for the order. The last source used is recorded for the order." I'm not sure if this implicitly conflicts with your answer, because the document's language is ambiguous on the matter.
Basically, I would like to use a source code to unlock handicapped seats, and then use a second source code to unlock a discount. Or I'd like a constituent to be able to purchase tickets for two different shows, using a different promo code for each, all in the same cart and session. If the Web API doesn't keep track of formerly-entered source codes, then is such an arrangement impossible?
Thanks again,Bryan
I'm speaking off the top of my head here just thinking about past experience but I believe you can use multiple promo codes as long as you are in the same MOS because the ticket is reserved in the cart/order with the appropriate price type / source at the time of reservation. Then, you can enter another promo code (although it is a hassle) and perform a different reservation. Does that make sense?Also - just wondering if there is a particular reason behind using a promo code to unlock handicap seating? Should you not just be using ReserveTickets with Special Requests?Finally, you can change the price type (for discounting purposes) without using a promo code. I believe that method is the aptly named UpdatePriceType.
Yes, I believe that as long as you maintain the same MOS - TransferCart will maintain everything because the reservation has already been made.
Good luck!
Thank you, Nathan. It seems you are right. If I call GetPerformanceDetailWithDiscountingEx() on a performance after entering a relevant promo code's source number with UpdateSourceCode(), an extra "PriceType" section appears in the results. If I enter a different source by again calling UpdateSourceCode(), the former extra "PriceType" section disappears, but the PriceType unlocked by the new source code appears on its relevant show's details.
Regardless, it seems that ReserveTicketsEx(), which requires a price type among its parameters, does not care if that price type is currently locked or unlocked. And like you said, the tickets already in the cart don't change price types just because a different source was entered.
I guess what this boils down to is that it's simpler to have users enter a single promo code before purchasing tickets. However, if users fail to enter a promo code before adding tickets to their cart, and they want to enter a promo code during checkout, then the site will have to review the price types of each "line item" compared to available price types, and replace the "line item" price types with the promo alternative if it exists. Is this correct? Is there any way to automate that process?
I think, generally speaking, you want to use Offers to control _access_ to price types, but if you want to allow people to lower prices _after_ reserving seats, then you might want to look into Discounts. I can't add much more, since we haven't gotten to the point of using Discounts here, but that's my understanding of the different systems.