The price rules tool at the top of the price calculations page functions like a calculator.
From here, I've selected "create new" next to "select a price rule." Make sure to give any price rule a unique name so it can easily be identified when applying it later.
There are a few options here for what kind of price rule can be created, and for whom:
% increase: This would be used if the upcoming agreement's price can be based on pricing from last year. For example, a 5% increase from last year.
Uniform price: This would be used if a group of member have the same price.
Price per: This would be used if users want to set up pricing per a specific field. The group types are either FTE or subscribers, and the sub-group can be determined by the information the consortium adds to the member profile. For example, population served could be added as a sub-group for public library members. The table can be built out based on how many lines of pricing are needed. There is also an option to include a minimum and maximum price for the table.
Price per range: if the pricing should be determined within a specific range, users can select the "price per range" option, which looks similar to the "per subscriber" option.
For all of these options, users can opt to apply this to all members or get specific about which kinds of members in the "toggle advanced options" section.
All of this information about the member can be found on the member profile. If pricing is dependent upon a specific piece of information (FTE, membership type, etc.), it is important to make sure that information is fully entered before applying pricing rules to agreements.
Member types would include things like library type (K-12, academic, etc.) whereas membership types distinguish the kind of member the library is in the consortium (core, affiliate, non-member, etc.). Those types and the FTE groups can be found, created, and edited in the system settings.