QAD Configurator Basics > Pricing
When you define a configuration in the questionnaire, Configurator calculates its price in real time.
In many situations, the price of a configuration is equal to the sum of the prices of its components. Now suppose that each component is only chosen if a certain option is selected as an answer (a one-to-one relationship between the options and the components). Then instead of associating a price with the component you can also associate a price with the relevant option and sum the prices of the options. Configurator uses this method.
To link a price to an option, define a pricing part for that option. Configurator uses the price and price lists (if any) of this pricing part to find the best net price and the best list price of the feature option. Any item can serve as a pricing part.
If there is a one-to-one relationship between the options and the components, all Configurator has to do is to sum the prices associated with the selected options. But sometimes, selecting a certain option leads to selecting more than one unit of some component. In this case, you can include the number of the component in the price of the configuration.
For numeric features, you can use the value of this feature as the number of units of the component; select Qty Based check box in Variable Maintenance or Feature Maintenance. If you do not select Qty Based, the quantity is one.
For other types of features, the Quantity Based check box is not available. In these cases, you can set the pricing quantity (pricing_qty) attribute of a feature.
The pricing functionality offers many more possibilities for defining the price of a configuration:
The pricing part of an option does not have to be the component that is selected if you choose that option. In other words, you can associate with an option any price you want, by specifying a dummy item and using that item as a pricing part for the option.
If a pricing part is not the component that is selected when you choose an option, then the number of units is not the number of units of the actual component, but the number of units of the item that serves as the pricing part. The pricing quantity only helps you find a price in a price list and does not even have to refer to a number of units that is selected in the variant product structure. This means that you can force the price of a configuration to go up when a certain option is selected, even if you do not want the choice to result in the selection of a component.
If some components are always selected (independent of the answers given), you can define a separate price list containing the total price of this collection of items. Then you link the price list to a dummy item. Later this dummy item can be used as a pricing part. Its price can always be included in the configuration price, for instance by having a rule that makes sure that the relevant option of this dummy feature is always selected.
If more than one different component is selected, you can create price lists containing the prices of the relevant collection of components. Then you can link the price lists to the pricing part.
Apart from a pricing part and a pricing quantity, also provide a pricing unit of measure for best price calculation. The pricing quantity of (a pricing part associated with) an option is always expressed in terms of the pricing unit of measure that you enter in Configurator. For instance, if the unit of measure for an item or in a price list is gram and the unit of measure as entered in Configurator is kilogram, then a pricing quantity of 2 in the questionnaire means a quantity of 2 kilograms.
To enter pricing part, quantity based, and unit of measure correctly, you should first enter the data in Variable Maintenance and Feature Maintenance. In general the data as entered in Feature Maintenance is used, but there are two exceptions to this rule:
If Std Options is selected in Feature Maintenance, the data from the variable option is used.
If the feature is a logical and the answer in the questionnaire is equal to no, then Configurator uses 0 as the price for the feature. If the answer is yes then Configurator uses the pricing information as specified in Feature Maintenance.
Note: The price of the configuration as shown in the questionnaire is always the price of one unit of the configuration.