Two Pricing Rules under One Source Code

I am building out a new source code with pricing rules that change the admission price of all our adult ticket types to $10 and then our youth ticket type to $5. Do I need to create two pricing rules and then apply them to the same source code? I do not see how I can achieve this in one pricing rule setup. This is my first time creating a source code/pricing rule with different prices for multiple ticket types. Thank you!

  • Assuming you are NOT on V16, off the top of my head would be a price type change rule assigned to the source code.

    You create 2 new price types, add them to your performances at the $10/$5 prices, make sure the new price types are NOT assigned to the Web User group, the price type change rule can map the price type changes and overcome the lack of assignment to the Web User group. The new $10/$5 price types would also not appear online since they are not assigned to the Web User group. The new price types would also need to be associated with your various online MOS's.

    I'd suggest you first attempt this in your Test/Dev environment.

    Here is an example:









    We only have the 50% off price types assigned to the System Admin User Group so that staff are not tempted to use it. They would have to apply the source code to access them.


    Does that all make sense?

  • Thank you, Neil! This did make sense and I was able to set up the new source code using this information. Appreciate your help.