To automatically calculate service prices, conditional price agreements are added to products. Filters can then be used within a price agreement to define when an agreement applies.

Note: All service pricing is controlled by price agreements, any products that are missing applicable price agreements will prompt the user to correct (depending on product setting).

Each price agreement consists of two parts –

• Conditional filters

• The price or percentage

Price agreement filters

Price agreement filters define the conditions a price agreement is valid and applicable. FBO One will automatically sort price agreements by most applicable (at the top with most filters) to least applicable (at the bottom with least filters).

Note: FBO One will always apply the price agreement that matches the most filters.

The following filters are mandatory for all price agreements: ‘FBO location’, a ‘Product’ and a ‘Valid before’ date, these filters define which FBO, product and start date the agreement applies.

Other filter values can include MTOW, debtor, flight type, handling category, form of payment and custom values.

Note: Multiple filters may be combined to ensure correct pricing for varying conditions.

Overview of all filters:

• FBO location: Applies only to the specified FBO location.

• FBO location group: Applies to a group of FBO locations, reducing duplication of price agreements per FBO location. Note: FBO location groups are defined in ‘Administration Station FBO Location groups.

• Product: Applies to this product only.

• Child product: If specified, the price agreement will apply a price to the child product based on the parent product relation.

• Valid from: Applies the agreement on and after this date. Can also be used for future agreements to be applied from a certain date, e.g. start of the following month.

• Valid before: The agreement expiry date. The before date is used to expire agreements before a certain date, e.g. before start of next month.

• Aircraft registration: Applies only to the specified aircraft registration.

• Debtor: Applies only for the specified debtor.

• Supplier: Applies only for the specified service supplier.

• Movement type: Defines which flight leg(s) the agreement should use from the order. Used in combination with one of the following filter filters: 'Flight type price category', 'Station group (arr/dep)' and/or 'Peak category value'. Available options are:

  • 'Arrival only' - Agreement applies if conditions are met from the arrival leg.

  • 'Departure only' - Agreement applies if conditions are met from the departure leg.

  • 'Both arrival and departure' - Agreement applies if conditions are met from both the arrival and departure legs.

  • 'Either the arrival or departure' - Agreement applies if conditions are met from either the arrival or departure legs.

• Flight type price category: Applies to the specified group of flight types only. This filter must be combined with ‘Movement type’. Note: Flight type price categories are defined in ‘Administration Order Flight Type Price Categories’.

• Station group (arr/dep): Applies to the specified station group only. This field must be combined with ‘Movement type’. Note: Station groups are defined in ‘Administration Station Station Groups’.

• Peak category value: Applies for the specified peak category only. This field must be combined with ‘Movement type’. Note: Peak category values are defined in ‘Administration Station Peak categories & Peak lists’

• Handling category: Applies for the specified handling category only. Note: Handling categories are defined in ‘Administration Product Handling Categories’

• Handling category group: Applies for the specified handling category group. Note: Handling category groups are defined in ‘Administration Product Handling Category Groups’

• Handling station group: Applies for the specified handling station group. Note: Station groups are defined in ‘Administration Station Station Groups’

• Form of payment: Applies the agreement when the specified form of payment is in use.

• Form of payment group: Applies the agreement only when the specified form of payment group is in use. Note: Form of payment groups are defined in ‘Administration Payment Form of Payment Groups’

• Consider custom values from: Defines where a custom value should be considered from. Must be used in combination with either the 'Custom value' or 'Custom value group'. Available options are:

  • ‘Registration or else debtor’ – Applies if custom value is present from the registration/ type or debtor.

  • ‘Trip support provider only’ – Applies if custom value is present from the trip support provider.

  • ‘Operator only’ – Applies if custom value is present from the operator.

  • ‘Supplier only’ – Applies if custom value is present from the supplier.

• Custom value: Applies if the custom value is present. This filter must be combined with ‘Consider custom values from’.

• Custom value group: Applies if the custom value group is present. This filter must be combined with ‘Consider custom values from’. Note: Custom value groups are defined in ‘Administration Backoffice Custom Value Groups’

• Handling: Applies the agreement to a single order. Note: This is the order number e.g. AMS-123.

• Template variable name: Applies the agreement based upon an order related field such as aircraft foot print, number of seats, order custom values. Must be used in combination with either the 'Template variable below'

• Template variable below: Applies if the template value is below a set figure. This filter must be combined with ‘Template variable name’

• MTOW below: Applies the agreement if the aircraft MTOW is below a specified weight. Agreements are automatically sorted, so the lowest 'MTOW below' is checked first.

• Quantity below: Applies the agreement if the service quantity is below the specified number. Agreements are automatically sorted, so the lowest 'Quantity below' is checked first.

• Currency of given price: Applies if the price entered differs from the default currency used by FBO One, the currency code should be added. Only required when the currency is different to the default currency.

• Unit of measure for the given price: Allows for a price to be entered in one unit and have the service break down the charge in to a smaller unit. E.g. fuel purchased per cubic meter but sold per litre.

Price or Percentage

For each price agreement, a price or percentage must be entered (not both).

Overview of Price or Percentage fields:

• Minimum amount: Used to ensure a price calculation should always meet a minimum price. Entering a price here ensures that if the calculation falls below the minimum, the 'Minimum amount' is charged.

• Maximum amount: Used when a price calculation should be capped at a maximum price. Entering a price here ensures that if the calculation is above the maximum, then the 'Maximum amount' is charged.

• Price: Enter the price itself. Note: For reductions use a minus symbol (-) before the number.

• Percentage: If the agreement is a percentage instead of a price, use this filter instead of the price field. This field is used for surcharges or discounts, so there should always be another price agreement created with a price. Note: For reductions use a minus symbol (-) before the number.

• SKU price component: Relates to the fuel module price component.

• SKU duty tax: Relates to the fuel module duty tax price component.

• Remarks: Enter free hand remarks to provide information to users concerning the price agreement.