Creating pricing rules in X-1FBO gives you powerful control over how charges are applied from basic fee overrides to dynamic fuel pricing. This guide walks you through how to build safe, effective pricing rules step by step.
Get Started - Choose the Rule Category
Before setting up a rule, choose where the rule should live. The category determines what type of pricing logic you’re applying.
Available Rule Categories:
Category | Used For |
Fees | Charges for services like lavatory, GPU, facility fees, parking, etc. |
Exceptions | Overrides retail pricing, typically for fuel or services. |
Customers | Pricing tied to specific customers or accounts. |
Payment Methods | Adjustments based on how the payment is made. |
Aircraft | Pricing based on aircraft type, weight class, or model. |
💡 Choose the category first, then build your logic inside that framework.
Define What the Rule Applies To
Next, choose what this rule targets:
Options:
Product/Service – A single item (e.g., Jet-A or Lav Service)
Category – A group of related products or services
All – Everything under the selected category
⚠️ Note: Rules applied to "All" affect every transaction in that category — use carefully.
Name the Rule and Set Priority
Rule Description (Name)
Give the rule a clear, descriptive name that reflects its purpose.
✅ Examples: “Jet-A Discount – AKI Jets – 100+ gal” or “Facility Fee Waived – Based Aircraft”
🚫 Avoid: “Test Rule”, “Customer X”, “Something Fuel”
Rule Priority
Set a priority to determine which rule wins when multiple match:
Lowest
Low
Medium (default)
High
Highest
Critical
🧠 Tip:
Use Critical for override-level rules (e.g., contractual pricing), and Lowest for broad, default pricing.
Set Rule Timing (Optional)
Control when the rule goes into effect:
From Date & Time – When the rule becomes active
To Date & Time – When it expires
✅ You can set rules in the past — helpful for backdated invoices.
🧠 Best Practice: When updating a price, don’t overwrite the old rule. Expire the old one and create a new one. This maintains pricing history and ensures accuracy on older invoices.
Define the Rule Conditions
Conditions are the filters that tell X-1FBO when this rule should apply. You can define one or more conditions, and the rule will only trigger when all selected conditions are met.
Available Conditions:
Customer – Specific account or operator
Aircraft Tail Number – One or more tail numbers
Aircraft Model – Specific aircraft (e.g., Gulfstream G550)
Aircraft Model Category – Groupings like Light Jet, Turboprop, etc.
Tenancy Type – Based or Transient
Flight Type – Arrival, Departure, or Turn
Fuel Minimum Quantity – Trigger only if uplift meets/exceeds this amount
Payment Method – Card, cash, contract, etc.
Contract Fuel – Yes/No
Promo Code – Applied during request
Customer Description – Freeform customer label/category
Set Up the Price (Price Computation)
Now it’s time to tell the system how to calculate the price. This is the core of the rule: it defines the math that gets applied when all your conditions are met.
You can choose one of the following pricing methods:
⚠️ Heads Up:
Creating a rule with no conditions means it will apply every time, to every transaction that matches the selected category or product. This is rarely what you want, and it can lead to widespread unintended pricing.
We strongly recommend adding at least one condition to control when your rule fires. Even something simple like "Tenancy Type = Transient" adds a layer of protection.
Methods:
Method | Description |
Fixed | Set a specific amount (e.g., $100 or $0 to waive fee) |
Previous List | This helps you create a rule that applies to another rule |
Retail | This sets your regular retail pricing for an item |
Week Cost | This is used to set the price based on your weekly (daily, monthly or otherwise) fuel price. |
Highest Lot Cost | Use highest available cost from available inventory |
True Cost | Use actual cost from the lot used for fueling. |
Formula | Use variables for custom math: |
Formula Variables:
Q
= Quantity upliftedW
= Aircraft Empty Weight (lbs)C
= Fuel Capacity (gal)S
= Aircraft SqFtT
= Max Takeoff Weight (lbs)L
= Length (ft)MLW
= Max Landing Weight (lbs)
✅ Example: Create a ramp fee formula that scales by aircraft size or fuel capacity.
🧠 Pro Tip: Formula pricing gives you ultimate flexibility. but test carefully. Even small errors in logic can result in unintended charges.
Add an Additional Product (Optional)
Want a second product or service added automatically when this rule applies?
Use the Add Product option to insert another line item on the invoice.
✅ Example: If AKI Jets buys Jet A, and you want to also charge a Credit Card Fee, add it here. Both will be invoiced together when the rule fires.
Final Step: Save the Rule
After reviewing all inputs, click Save to activate the rule.
🧠 Best Practice: Test your new rule using a mock invoice or internal request to confirm it behaves as expected, especially if you're stacking logic or using formulas.
Best Practices for Maintained Pricing Accuracy
Provide Complete Setup Information
Always populate the 'Cost' field during item setup to prevent manual intervention later.
Review and Update Rules Regularly
Schedule periodic reviews of pricing rules to identify conflicting or outdated rules.
Record and Reconcile Changes
Document price updates and their effective dates to ensure accuracy and transparency in all transactions.
Check Fuel Ticket Dates Carefully
Ensure the fuel ticket date/time aligns with the pricing period to avoid errors on invoices.
Need Help?
Still have questions? Contact our dedicated X-1 Support Team anytime!