The pricing process in QL involves the following steps:

1. Pricing Group Assignment: Each product in QL is associated with a Pricing Group, determined by the user's set of conditions and rules. If a product matches multiple groups, it will be assigned to the group with the lowest priority value. This assignment takes place during the pricing process. Each group is linked to a Pricing Strategy that contains conditions and rules to determine the appropriate pricing for the product. The recommendation for the product's price calculation is based on these rules.
   
    

2. Checking Limits: After the pricing calculation, the next step is to check the limits the user sets within the strategy. These limits ensure that the recommended price falls within an acceptable range. There are two options for handling cases where the recommended price exceeds the maximum limit or falls below the minimum limit:

   a. "Ignore Recommendation" Option: No new recommendation will be generated if enabled, and the pricing process stops.

   b. "Adjust to Margin" Option: If enabled, the recommendation will be modified to align with the limit set for that particular product.
   
    

3. Handling Limit Exceedances: Additionally, the strategy page has the option to activate the "Skip Limit Adjustments and Proceed to Next Rule" button. If the limits are exceeded, the system can move to the following rule in the strategy order. This process continues until a recommendation falls within the limits. If all rules are skipped, and no recommendation falls within limits, no new recommendation will be generated.
   
    

4. Pricing Rounding: After the recommendation falls within the acceptable limits, the recommended price undergoes pricing rounding. This feature allows rounding of the product's price to a specific suffix.
   
    

5. Custom Functions: It is important to note that custom functions, defined globally for the entire client key or specific to a pricing group or strategy, can impact the recommendation based on their logic. These custom functions can be either pre-processors, running before the pricing cycle mentioned in the article begins, or post-processors, running immediately after it.

For a more detailed explanation of custom functions and their execution order, please take a look at our documentation here.

Please refer to the flowchart below for a visual representation of the recommendation process: