Price card groups are useful for more complex situations, and can help reduce the number of price cards you need to edit to implement pricing changes.

For example: If two time periods have the same fundamental ticket pricing, but different availability of tickets, two Standalone price cards are needed.

To implement a pricing change, both price cards must be edited to ensure that ticket types included in both price cards retain the same fundamental pricing.

This can become an undesirable situation where significant extra work is required, and there is the risk of forgetting to update one of the price cards, leaving it with the old pricing.

Using a price card group reduces the maintenance overhead. All ticket types are included in the Base price card, and two associated Derived price cards determine the two subsets of available ticket types.

To implement a pricing change, only the base price card has to be edited, and the prices will automatically be inherited to the derived price cards.

Example

A base price card will include all your ticket types and set their prices:

A derived price card for Weekday sessions may include all tickets and inherit the prices from the base price card:

A derived price card for Weekend sessions may inherit the same prices for the Adult and Child tickets, but the discounted Student and Staff tickets may not be available:

To implement a pricing change in all of these ticket types, you only need to edit the base price card.

See also:

Examples of price card groups