Setting up pricing rules in X-1FBO gives you a ton of flexibility, so much that it can handle just about any pricing scenario you throw at it. But with that power comes some responsibility. Price rules follow a specific hierarchy, and understanding how that structure works is the key to making sure your rules apply the way you expect. If a rule isn’t working, it’s usually not broken—it’s just being outranked. This guide will walk you through how rule categories and priorities interact so you can troubleshoot like a pro.
First, think of each category as pyramid levels. From the bottom upwards, we find the rules for Aircraft, Payment Methods, Customer, Exceptions, and Fees.
Price rules with the highest priority/hierarchy level are found in the 'Fees' category. This means that any price rule in this group will apply over any other from the below groups and so on with each level downward.
The price rule with the highest priority level in ‘Aircraft’ is still lower than the rule with the lowest priority level in ‘Payment Methods”, for example.
Now, let's see some examples:
Aircraft rule:
- but, what if tenants in this category don't get charged a 'Facility Fee'?
1.1 Exceptions rule for Facility Fee:
The Exceptions rule will ensure that even if a tenant aircraft belongs to the 'Very Light Jet' category, this product gets waived on the invoice. Since Exceptions is at a higher level than Aircraft, this rule will take priority. Here, it does not matter the priority selected within the rule, since each belongs to distinct categories.
Price rules within the same category:
Here, priority levels within the rule are key because you may need to give rule 1 a "High" priority to replace rule 2 with a "Medium" priority.
One last scenario:
John Smith gets a jet a discount when paying retail (non-contract) but when they pay with "X" Contract Fuel, it needs to apply over the retail pricing:
Product: Jet A
Condition1: Customer = John Smith AND
Condition 2: Payment method ≠ X (applicable contract fuel payment method)
