Dynamic Pricing Rules have conditions which can be TRUE or FALSE. Based on the result of the condition, a function can be used to alter the price of the item. The first part of the function specifies what to do if the condition is TRUE; the second part of the function specifies what to do if the condition is FALSE. If there is no FALSE specification in the function, then nothing is done to alter the price of an item when a condition leads to a FALSE result. Functions may also be used without conditions.

 

Note: There is no limit to how many lines you can have in a Dynamic Pricing Rule.

 

 

Note: Conditions can use AND/OR/NOT.

 

 

Note: Rules can be referenced in other rules using SUB()

 

 

This option would allocate $50 to the LESSONS profit center per Lesson modifier attached with the remaining (up to $5000) going to TICKETS.

The HASMOD condition can take up to four parameters. The first is Department, Category, Item, and then the number of times the mod is present. This example specifies the category name LESSON with incrementing numbers of times that an item in the LESSON category is used as a mod.

 

 

This would allocate a one day's worth of revenue to LESSONS per lesson modifier with the remaining going to TICKETS. It is much more complicated because the percentages vary based on the # of days on the ticket. The provided samples are up to 6 days and 6 lesson mods. You would need to do the full 14 or whatever max you have for ticket duration.