333
edits
Changes
Jump to navigation
Jump to search
Created page with "'''Pricing for Subagents''' is the module of Websky system for subagencies, which allows them to establish and manage their own fees, markups and subagent discounts for air ti..."
'''Pricing for Subagents''' is the module of Websky system for subagencies, which allows them to establish and manage their own fees, markups and subagent discounts for air tickets. Works only for "Air Tickets" component.
==Principle of Operation==
The module works together with the '''[[Pricing (Air tickets) | Pricing] module]]'''.
The module's operation is based on the pricing rules that the subagency establishes.<br />
'''Rule''' - a set of ''charge parameters'' and ''conditions of charge application''. <br />
''Conditions of charge application'' is a set of flight parameters to which the charge from the rule will be applied ("validating carrier'', ''GDS'', ''flight type'', ''passenger types'' etc.).
The pricing rules for subagencies are contained and created in '''Product control → Aviatickets → Modules → Pricing rules for subagents''' section.
When the system analyses each flight, the [[Pricing (Air tickets) | general pricing]] module rules set by the root agency manager are first triggered and then the available rules for the particular subagent are checked:
* The module applies a rule that corresponds to the flight by all parameters and calculates the charge of the subagent.
* If more than one rule applies to the flight, the module "calculates the fee for one rule" or "summarizes the fee for all applicable rules" depending on the settings you have configured. (see [[Pricing for Subagents#Module Setup Parameters | '''Module Setup Parameters''', parameter ''subagent charges strategy'']]).
* If no suitable rules are found, only the charges from the basic pricing rules are applied to the flight.
The charge is a markup (or discount) applied to the total price of the flight, or to the price of the ticket to each passenger, for each segment of the flight and/or for each passenger, depending on the selected parameters.
'''Attention!''' If a basic pricing rule has not been applied for the flight, the flight cannot be [[Ticketing | ticketed]] even if there are suitable pricing rules for the subagents (see [[Pricing (Air tickets)]]).
==Enabling the module==
The module is installed by a Websky administrator. If you want to connect the module, create a query in the [http://helpdesk.nemo.travel| project tracker]. The module connects to the entire agency, and agency manager can configure access of its subagents to the module in '''Product control → Aviatickets → Pricing → Settings → Access to pricing rules for subagents'''.
==Creation of a pricing rule==
Pricing rules for subagents can be created by both the root agency manager and the subagency manager. Experts do not have access to these settings.
To create a rule:
# Go to '''Product control → Aviatickets → Modules → Pricing rules for subagents'''.
# Click the button '''Create a new record''.
# Set the ''conditions of the charge application''.
# Enter the "charge parameters".
=== Rules parameters ===
==== Conditions of charge application ====
'''Attention!''' If the parameter is empty, this parameter is ignored when selecting rules.
{| class="wikitable mw-collapsible mw-uncollapsed"
|-
! scope="col" | Parameter name
! scope="col" | Description
! scope="col" | Permissible values
! scope="col" | Examples
|-
| width="10%"| Flight type
| width="40%"| International or domestic (all flights within the same country) flight. Select one value or leave it blank.
|width="15%"|
*Any
*International flight
*Domestic flight
|width="10%"| see description
|-
| Class of service
| Permissible service class categories.
| Leave the field blank or select values:
*Economy<br/>
* Business<br/>
* First
| see description
|-
| Route type
| Flight route type.
| Leave the field blank or select values:
* One way,
* Round trip,
* Complex route.
| see description
|-
| Validating carrier from GDS
| Airline acting as a validating one.
| Format: CODE, CODE...
| SU,LH,BA
|-
| Start of sale
| Minimum allowed date of the order placement (not to be confused with the date of departure). For the rule to be triggered, the current date must be greater or equal to the specified one.
|
Format: DD.MM.YYYY
| 01.01.2012
31.01.2010
|-
| End of sale
| Maximum allowable date of the order placement. For the rule to be triggered, the current date must be less or equal to the specified date.
|
Format: DD.MM.YYYY
| 31.12.2022
|-
| Cities/airports of departure
| Code of the airport of departure of the first segment. When specifying the city codes (aggregation airports), the comparison is based on the internal airport directory, so it is not recommended to use them.
| Format: CODE, CODE...
| MOW,PAR,BER
|-
| Cities/airports of arrival
| Code of the airport of arrival (last segment). When specifying the codes of cities (aggregation of airports), the comparison is made according to the internal airport directory, so it is not recommended to use them.
| Format: CODE, CODE...
| MOW,PAR,BER
|-
| Permissible carriers of the first segment
| Set of acceptable marketing carriers of the first segment of the route.
| Format: CODE, CODE...
| SU,LH,BA
|-
| Permissible carriers (interline) of any segment
| Set of acceptable marketing carriers (interline) of any segment of the route. At least one marketing carrier of the flight must be on this list for the rule to work.
| Format: CODE, CODE...
| SU,LH,BA
|-
| Permissible operating airlines
| Permissible operating airlines which are checked on all segments. To trigger the rule, at least one operating carrier from the flight must match the carrier from the given list.
|
Format: CODE, CODE...
| SU,LH,BA
|-
| Minimum allowed share of own segments
| The minimum allowed percentage of segments in which the validating carrier is equal to a marketing one should be greater than or equal to the specified value.
| Format: any number from 0 to 1 (fraction separator - point).
For example:
* 1 - all segments are airline's own
* 0.5 - half or more of own segments,
* 0.25 - a quarter or more of own segments,
* 0.01 - at least one own segment is present,
* 0 - all segments are interline.
| 0.88
|-
| Minimum allowed share of interline segments
| The minimum allowed percentage of segments in which the validating carrier is not equal to a marketing one should be greater than or equal to the specified value.
|Формат: any number from 0 to 1 (fraction separator point).
For example:
* 1 - all segments are interline,
* 0.5 - half or more segments are interline,
* 0.25 - a quarter or more segments are interline,
* 0.01 - there is at least one interline segment,
* 0 - all segments are the airline's own.
| 0.5
|-
| Flight numbers
| Permissible flight numbers, separated by commas.
|Формат: CODE, CODE...
| SU 123,SU 345<br/>123,345
|-
| Fare codes
| Permissible fare codes. At least one of the flights must coincide with one in the given list. If you use a denying rule, there should be no matches. The match is not exact: the code from the rule can be contained in the code from the flight (for example, the entered S1GREY26 will match S1GREY26CH from the flight). Any fare must match with one of the given list.
| Format: COD, COD...
| WRUTH9PL,ARUTH9PL
|-
| Permissible booking classes
| Permissible codes separated by commas.
| Format: CODE, CODE...
| B,E
F
EB,EF,F
|-
| Geographical zones of the flight
| The entire flight must not go beyond one of the specified zones for the rule to trigger. [http://www.geonames.org/countries/ division of countries into specified zones].
| Leave the field blank or select values:
*Europe
*Asia
*Africa
* North America
* South America
*Australia and Oceania
*Antarctica
| see description
|-
| Countries of departure
| Permissible countries of departure for the flight (only the country of departure of the first segment of the route is checked).
| Format: CODE, CODE...
| RU,LV,LT
|-
| Countries of arrival
| The destination country is checked (for OW and CR it is the last country of the last segment, for RT it is the last country of the first leg of the route). For example, for MOW-PAR-MOW flight, the destination country is FR, for MOW-PAR-LON - GB. '''Rule "country of departure=RU, country of destination=RU" does not mean a domestic flight''' - do not forget to specify the flight type DA (Domestic Airlines).
| Format: CODE, CODE...
| RU,LV,LT
|-
| Direct flight
| The option includes using the rule for direct flights only.
| see description
| see description
|-
| Routes
| A chain of IATA codes of cities or airports, describing the entire route of the flight, including transfers, without breaks and repetitions. You should always use the IATA code of the city, if it is available (aggregation airport). For example, a VKO-ORY, ORY-VKO flight is given to a MOW-PAR-MOW route.
| Format: CODE-CODE, CODE-CODE...
| MOW-LON,LON-MOW
|-
| Contains routes
| Only part of the route, compiled by analogy with the previous one, is specified.
| Format: CODE-CODE...
| -CAI-
|-
| Start of flight
| The date of departure of the first segment should be greater than or equal to the specified date.
| Format: DD.MM.YYYY
| 01.01.2012
31.01.2010
|-
| End of flight
| The date of departure of the first segment should be less than or equal to the specified date.
| Format: DD.MM.YYYY
| 31.12.2022
|-
| Return no later than
| The departure date of the last route segment should be less than or equal to the specified date.
| Format: DD.MM.YYYY
| 31.12.2022
|-
| Days of the week
| Permissible days of the week for the departure date of the first segment of the route.
| Select the values from the list.
| see description
|-
| Duration in days from/to
| Restrict the maximum gap in days between the first date of flight and the end of the route (for round-trip routes). You can specify a range.
| Format: number
| 13
[3,13]
|-
| Settlement system
| Type of contract. BSP or TCH settlement system. For a direct airline session you also need to select the type of BSP.
|
* any
* TCH
* BSP
| see description
|-
| Apply to
| Defines the parameters for which the settings will be applied. (if you choose "To each passenger", the settings field: "Indicate specific types of passengers" will appear additionally).
|
Leave the field blank or select values:
* To every flight segment
* To every passenger
| see description
|-
| Round up to
| Rounds the value with the selected accuracy.
|
* integer value
* tenths
* hundredths
| see description
|-
|-
| Indicate specific types of passengers
| This setting appears if the "Apply to" setting is set to "For each passenger". It allows selecting the type of passenger for which the selected settings will be applied.
|
Leave the field blank or select values:
* Adult
* Child
* Infant under 2 years old
* Infant with a seat
|see description
|-
|-
| Charge
| Allows you to set the charge in relative or absolute values.
|
Format: number
|15
|-
|-
| Amount of the charge not less than
| Allows you to set the lower limit of the charge in relative or absolute value.
|
Format: number
|15
|-
|-
| Amount of the charge not more than
| Allows you to set the upper limit of the charge in relative or absolute value.
|
Format: number
|15
|-
|}
====Charge parameters ====
'''Attention! Parameters from the following list refer only to calculations, not to checking for rule applicability / non-applicability. (The rule's applicability conditions are listed above and refer only to the parameters of the flight itself).'''
{| class="wikitable mw-collapsible mw-uncollapsed".
|-
! scope="col" | Parameter name
! scope="col" | Description
! scope="col" | Permissible values
! scope="col" | Examples
|-
| width="10%"| Agency fee
| width="40%"| It is possible to specify the value of the charge in a currency (for this purpose, you need to select a specific currency in the drop-down list under this field, and to specify a numerical value in the charge field, the currency code should not be specified here), as a percentage of the order value or as a percentage of the fare ((for this purpose, in the drop-down list under this field, you need to select the type "Percent" or "Percent of the fare" respectively and to specify a numerical value in the charge field, the symbol % should not be specified here).
| width="15%"| see the example
| width="10%"| 500 Russian Ruble<br /> 2 Percent<br /> 5 Percent from the fare
|-
| Charge amount not less than
| The minimum charge that a sub-agency will receive for an order. If the calculated amount of the sub-agency's charge is less than the minimum, the fee is increased to the minimum value.
| see the example
| 100 Russian ruble<br /> 5 Percent<br /> 7 Percent of the fare
|-
| Charge amount no more than
| Maximum amount of subagency charge. If the calculated amount of the subagency's fee is larger, the fee will be reduced to the maximum value.
| see example
| 100 Russian ruble<br /> 5 Percent<br /> 7 Percent of the fare
|-
|Apply to
| Method of charge calculation:
* For each flight segment - markup (or discount) is added to the price of each flight segment.
*Fare for each passenger - markup (discount) is added to the price for each passenger. If this option is chosen, you can automatically choose specific types of passengers for which the charge should be calculated: adult, child, infant under 2 years old, infant with a seat. If this option is selected to apply to each passenger, but the specific types of passengers are not selected, the fee will be applied to each passenger.
|see description
|see description
|-
| Round up to
| The parameter is relevant for the fees specified in percentages. Choose one of the ways of arithmetic rounding the fee.
|
* integer value
* tenths
* hundredths
|see description
|-
| Apply to group/user
| Allows you to specify a user or group to which the selected settings will be applied. You can enter the user group ID manually or select a subject from the agency tree.
|
Format: number
|15
|-
|}
==Module configuration parameters==
The root agency manager can set the availability of the '''Pricing for Subagents''' module as well as the availability of specific settings in the '''Product control → Aviatickets → Pricing → Settings''' section (this section is not available for subagency's managers). The parameters can be set both for the entire agency and for individual companies by selecting a user at the top of the page.
The following settings are available only for the agency's manager, and only if an agency has the '''Pricing for Subagents''' module enabled.
* '''Access to pricing rules for subagents''' - includes a module for a subagency. If the subagent does not have access, the module will not be available in the company's settings panel, but the root agency's manager will be able to set up the rules for this subagent and they will be applied.
* '''Allow the use of negative margins (discounts) for the subagent''' - enables you to set discounts. If this option is disabled, the subagent will be able to set only positive markups.
* '''B2B fees strategy''' - defines the calculation principle of the total amount of the subagent's charge in case if more than one rule of subagent's pricing is suitable for the flight:
**'''''Sum''''' - each matching subagent rule is applied to the flight, the total subagent fee is calculated as the sum of applied fees for each triggered rule.
**'''''One rule with a major amount of parameters''''' - the subagency charge is calculated by one rule, which is selected by the largest number of completed rule parameters (the more parameters of the rule are completed, the higher its priority). If there are two or more suitable rules with the same number of parameters is selected last rule in the list as a higher priority (created later than the others).
* '''Billing Strategy for Subagents''' - determines the order of calculation of the final amount to be billed for managers and experts of subagencies. This setting can significantly simplify settlements between subagents and their agents, because the commission and/or the subagent's own charge will not be deducted from the subagent's deposit during payment, but will be immediately recorded in the subagent's account as profit. By default, both the charge and the commission of the subagent are deducted from the deposit, which means that the root agency manager will have to return the net profit to the subagent in the future, which makes settlements more complicated. The following two options are available for setting up:
** '''''Deduct the commission of subagents (for managers and experts) (if it has not already been deducted by the Strategy for using the subagent commission setting)''''' - the subagent's commission will be deducted from the final price of the order, '''unless it is deducted by setting up ''Strategy for using the subagent commission''''' (section '''Product control → Outdated settings → Pricing 1.0 → Setting commissions'''). It means that, if the setting "Billing Strategy for Subagents" is set to "Apply but not subtract from the price" and the option "Subtract Subagent Commission" is enabled, then the subagent's orders will record the full price with the subagent's commission, the same full price will appear in Websky's itinerary receipts and reports, but the order value will be deducted from the deposit with the subagent's commission. If the setting "Application strategy of subagent commission" is set to "Apply, deduct from the total for all Subagent's users (default)", the subagent's orders will immediately show the price with the deduction of his commission, the same amount will be deducted from the deposit and will be included in the itinerary receipts and Websky reports. In this case, the "Deduct the commission of subagents" option is no longer relevant.
** '''''Deduct subagent's own charge (for managers and experts)''''' - reduces the final price of the order by the amount of the subagent fee.
** '''''Deduct subagents's own services''''' - reduces the final price of the order by the amount of additional agency services added to the order.
* '''Hide fields in the pricing rule table for subagents''' - this setting allows you to hide certain pricing parameters from the subagent visibility, if the manager of the root agency does not want the subagent to use them to configure their charges. You can select several parameters. By default, everything is available. The options are listed in the table above.
In '''Sales Management → Aviatickets → Outdated settings → Pricing (1.0) → Commission settings''' (available only to the root agency manager), the following parameters are located:
* '''Display commission (subagents)''':
** '''''Yes''''' - the subagent's commission will be displayed to all users of the company
** '''''B2B only''''' - the subagent commission will be displayed only to the manager and experts of the company.
** '''''No''''' - the subagent commission will not be displayed to any user of the company
* '''Application strategy of subagent commission''':
** '''''Do not apply''''' - the commissions specified in the pricing table for subagents will not be applied.
** '''''Apply, deduct from the total for all Subagent's users (default)'''''.
** '''''Apply, deduct only for manager or experts (B2B)''''',
** '''''Apply but not deduct out of the cost'''''.
== See also ==
* [[Pricing (Air tickets)]]
* [[Charge (term)]]
* [[Currency]]
==Principle of Operation==
The module works together with the '''[[Pricing (Air tickets) | Pricing] module]]'''.
The module's operation is based on the pricing rules that the subagency establishes.<br />
'''Rule''' - a set of ''charge parameters'' and ''conditions of charge application''. <br />
''Conditions of charge application'' is a set of flight parameters to which the charge from the rule will be applied ("validating carrier'', ''GDS'', ''flight type'', ''passenger types'' etc.).
The pricing rules for subagencies are contained and created in '''Product control → Aviatickets → Modules → Pricing rules for subagents''' section.
When the system analyses each flight, the [[Pricing (Air tickets) | general pricing]] module rules set by the root agency manager are first triggered and then the available rules for the particular subagent are checked:
* The module applies a rule that corresponds to the flight by all parameters and calculates the charge of the subagent.
* If more than one rule applies to the flight, the module "calculates the fee for one rule" or "summarizes the fee for all applicable rules" depending on the settings you have configured. (see [[Pricing for Subagents#Module Setup Parameters | '''Module Setup Parameters''', parameter ''subagent charges strategy'']]).
* If no suitable rules are found, only the charges from the basic pricing rules are applied to the flight.
The charge is a markup (or discount) applied to the total price of the flight, or to the price of the ticket to each passenger, for each segment of the flight and/or for each passenger, depending on the selected parameters.
'''Attention!''' If a basic pricing rule has not been applied for the flight, the flight cannot be [[Ticketing | ticketed]] even if there are suitable pricing rules for the subagents (see [[Pricing (Air tickets)]]).
==Enabling the module==
The module is installed by a Websky administrator. If you want to connect the module, create a query in the [http://helpdesk.nemo.travel| project tracker]. The module connects to the entire agency, and agency manager can configure access of its subagents to the module in '''Product control → Aviatickets → Pricing → Settings → Access to pricing rules for subagents'''.
==Creation of a pricing rule==
Pricing rules for subagents can be created by both the root agency manager and the subagency manager. Experts do not have access to these settings.
To create a rule:
# Go to '''Product control → Aviatickets → Modules → Pricing rules for subagents'''.
# Click the button '''Create a new record''.
# Set the ''conditions of the charge application''.
# Enter the "charge parameters".
=== Rules parameters ===
==== Conditions of charge application ====
'''Attention!''' If the parameter is empty, this parameter is ignored when selecting rules.
{| class="wikitable mw-collapsible mw-uncollapsed"
|-
! scope="col" | Parameter name
! scope="col" | Description
! scope="col" | Permissible values
! scope="col" | Examples
|-
| width="10%"| Flight type
| width="40%"| International or domestic (all flights within the same country) flight. Select one value or leave it blank.
|width="15%"|
*Any
*International flight
*Domestic flight
|width="10%"| see description
|-
| Class of service
| Permissible service class categories.
| Leave the field blank or select values:
*Economy<br/>
* Business<br/>
* First
| see description
|-
| Route type
| Flight route type.
| Leave the field blank or select values:
* One way,
* Round trip,
* Complex route.
| see description
|-
| Validating carrier from GDS
| Airline acting as a validating one.
| Format: CODE, CODE...
| SU,LH,BA
|-
| Start of sale
| Minimum allowed date of the order placement (not to be confused with the date of departure). For the rule to be triggered, the current date must be greater or equal to the specified one.
|
Format: DD.MM.YYYY
| 01.01.2012
31.01.2010
|-
| End of sale
| Maximum allowable date of the order placement. For the rule to be triggered, the current date must be less or equal to the specified date.
|
Format: DD.MM.YYYY
| 31.12.2022
|-
| Cities/airports of departure
| Code of the airport of departure of the first segment. When specifying the city codes (aggregation airports), the comparison is based on the internal airport directory, so it is not recommended to use them.
| Format: CODE, CODE...
| MOW,PAR,BER
|-
| Cities/airports of arrival
| Code of the airport of arrival (last segment). When specifying the codes of cities (aggregation of airports), the comparison is made according to the internal airport directory, so it is not recommended to use them.
| Format: CODE, CODE...
| MOW,PAR,BER
|-
| Permissible carriers of the first segment
| Set of acceptable marketing carriers of the first segment of the route.
| Format: CODE, CODE...
| SU,LH,BA
|-
| Permissible carriers (interline) of any segment
| Set of acceptable marketing carriers (interline) of any segment of the route. At least one marketing carrier of the flight must be on this list for the rule to work.
| Format: CODE, CODE...
| SU,LH,BA
|-
| Permissible operating airlines
| Permissible operating airlines which are checked on all segments. To trigger the rule, at least one operating carrier from the flight must match the carrier from the given list.
|
Format: CODE, CODE...
| SU,LH,BA
|-
| Minimum allowed share of own segments
| The minimum allowed percentage of segments in which the validating carrier is equal to a marketing one should be greater than or equal to the specified value.
| Format: any number from 0 to 1 (fraction separator - point).
For example:
* 1 - all segments are airline's own
* 0.5 - half or more of own segments,
* 0.25 - a quarter or more of own segments,
* 0.01 - at least one own segment is present,
* 0 - all segments are interline.
| 0.88
|-
| Minimum allowed share of interline segments
| The minimum allowed percentage of segments in which the validating carrier is not equal to a marketing one should be greater than or equal to the specified value.
|Формат: any number from 0 to 1 (fraction separator point).
For example:
* 1 - all segments are interline,
* 0.5 - half or more segments are interline,
* 0.25 - a quarter or more segments are interline,
* 0.01 - there is at least one interline segment,
* 0 - all segments are the airline's own.
| 0.5
|-
| Flight numbers
| Permissible flight numbers, separated by commas.
|Формат: CODE, CODE...
| SU 123,SU 345<br/>123,345
|-
| Fare codes
| Permissible fare codes. At least one of the flights must coincide with one in the given list. If you use a denying rule, there should be no matches. The match is not exact: the code from the rule can be contained in the code from the flight (for example, the entered S1GREY26 will match S1GREY26CH from the flight). Any fare must match with one of the given list.
| Format: COD, COD...
| WRUTH9PL,ARUTH9PL
|-
| Permissible booking classes
| Permissible codes separated by commas.
| Format: CODE, CODE...
| B,E
F
EB,EF,F
|-
| Geographical zones of the flight
| The entire flight must not go beyond one of the specified zones for the rule to trigger. [http://www.geonames.org/countries/ division of countries into specified zones].
| Leave the field blank or select values:
*Europe
*Asia
*Africa
* North America
* South America
*Australia and Oceania
*Antarctica
| see description
|-
| Countries of departure
| Permissible countries of departure for the flight (only the country of departure of the first segment of the route is checked).
| Format: CODE, CODE...
| RU,LV,LT
|-
| Countries of arrival
| The destination country is checked (for OW and CR it is the last country of the last segment, for RT it is the last country of the first leg of the route). For example, for MOW-PAR-MOW flight, the destination country is FR, for MOW-PAR-LON - GB. '''Rule "country of departure=RU, country of destination=RU" does not mean a domestic flight''' - do not forget to specify the flight type DA (Domestic Airlines).
| Format: CODE, CODE...
| RU,LV,LT
|-
| Direct flight
| The option includes using the rule for direct flights only.
| see description
| see description
|-
| Routes
| A chain of IATA codes of cities or airports, describing the entire route of the flight, including transfers, without breaks and repetitions. You should always use the IATA code of the city, if it is available (aggregation airport). For example, a VKO-ORY, ORY-VKO flight is given to a MOW-PAR-MOW route.
| Format: CODE-CODE, CODE-CODE...
| MOW-LON,LON-MOW
|-
| Contains routes
| Only part of the route, compiled by analogy with the previous one, is specified.
| Format: CODE-CODE...
| -CAI-
|-
| Start of flight
| The date of departure of the first segment should be greater than or equal to the specified date.
| Format: DD.MM.YYYY
| 01.01.2012
31.01.2010
|-
| End of flight
| The date of departure of the first segment should be less than or equal to the specified date.
| Format: DD.MM.YYYY
| 31.12.2022
|-
| Return no later than
| The departure date of the last route segment should be less than or equal to the specified date.
| Format: DD.MM.YYYY
| 31.12.2022
|-
| Days of the week
| Permissible days of the week for the departure date of the first segment of the route.
| Select the values from the list.
| see description
|-
| Duration in days from/to
| Restrict the maximum gap in days between the first date of flight and the end of the route (for round-trip routes). You can specify a range.
| Format: number
| 13
[3,13]
|-
| Settlement system
| Type of contract. BSP or TCH settlement system. For a direct airline session you also need to select the type of BSP.
|
* any
* TCH
* BSP
| see description
|-
| Apply to
| Defines the parameters for which the settings will be applied. (if you choose "To each passenger", the settings field: "Indicate specific types of passengers" will appear additionally).
|
Leave the field blank or select values:
* To every flight segment
* To every passenger
| see description
|-
| Round up to
| Rounds the value with the selected accuracy.
|
* integer value
* tenths
* hundredths
| see description
|-
|-
| Indicate specific types of passengers
| This setting appears if the "Apply to" setting is set to "For each passenger". It allows selecting the type of passenger for which the selected settings will be applied.
|
Leave the field blank or select values:
* Adult
* Child
* Infant under 2 years old
* Infant with a seat
|see description
|-
|-
| Charge
| Allows you to set the charge in relative or absolute values.
|
Format: number
|15
|-
|-
| Amount of the charge not less than
| Allows you to set the lower limit of the charge in relative or absolute value.
|
Format: number
|15
|-
|-
| Amount of the charge not more than
| Allows you to set the upper limit of the charge in relative or absolute value.
|
Format: number
|15
|-
|}
====Charge parameters ====
'''Attention! Parameters from the following list refer only to calculations, not to checking for rule applicability / non-applicability. (The rule's applicability conditions are listed above and refer only to the parameters of the flight itself).'''
{| class="wikitable mw-collapsible mw-uncollapsed".
|-
! scope="col" | Parameter name
! scope="col" | Description
! scope="col" | Permissible values
! scope="col" | Examples
|-
| width="10%"| Agency fee
| width="40%"| It is possible to specify the value of the charge in a currency (for this purpose, you need to select a specific currency in the drop-down list under this field, and to specify a numerical value in the charge field, the currency code should not be specified here), as a percentage of the order value or as a percentage of the fare ((for this purpose, in the drop-down list under this field, you need to select the type "Percent" or "Percent of the fare" respectively and to specify a numerical value in the charge field, the symbol % should not be specified here).
| width="15%"| see the example
| width="10%"| 500 Russian Ruble<br /> 2 Percent<br /> 5 Percent from the fare
|-
| Charge amount not less than
| The minimum charge that a sub-agency will receive for an order. If the calculated amount of the sub-agency's charge is less than the minimum, the fee is increased to the minimum value.
| see the example
| 100 Russian ruble<br /> 5 Percent<br /> 7 Percent of the fare
|-
| Charge amount no more than
| Maximum amount of subagency charge. If the calculated amount of the subagency's fee is larger, the fee will be reduced to the maximum value.
| see example
| 100 Russian ruble<br /> 5 Percent<br /> 7 Percent of the fare
|-
|Apply to
| Method of charge calculation:
* For each flight segment - markup (or discount) is added to the price of each flight segment.
*Fare for each passenger - markup (discount) is added to the price for each passenger. If this option is chosen, you can automatically choose specific types of passengers for which the charge should be calculated: adult, child, infant under 2 years old, infant with a seat. If this option is selected to apply to each passenger, but the specific types of passengers are not selected, the fee will be applied to each passenger.
|see description
|see description
|-
| Round up to
| The parameter is relevant for the fees specified in percentages. Choose one of the ways of arithmetic rounding the fee.
|
* integer value
* tenths
* hundredths
|see description
|-
| Apply to group/user
| Allows you to specify a user or group to which the selected settings will be applied. You can enter the user group ID manually or select a subject from the agency tree.
|
Format: number
|15
|-
|}
==Module configuration parameters==
The root agency manager can set the availability of the '''Pricing for Subagents''' module as well as the availability of specific settings in the '''Product control → Aviatickets → Pricing → Settings''' section (this section is not available for subagency's managers). The parameters can be set both for the entire agency and for individual companies by selecting a user at the top of the page.
The following settings are available only for the agency's manager, and only if an agency has the '''Pricing for Subagents''' module enabled.
* '''Access to pricing rules for subagents''' - includes a module for a subagency. If the subagent does not have access, the module will not be available in the company's settings panel, but the root agency's manager will be able to set up the rules for this subagent and they will be applied.
* '''Allow the use of negative margins (discounts) for the subagent''' - enables you to set discounts. If this option is disabled, the subagent will be able to set only positive markups.
* '''B2B fees strategy''' - defines the calculation principle of the total amount of the subagent's charge in case if more than one rule of subagent's pricing is suitable for the flight:
**'''''Sum''''' - each matching subagent rule is applied to the flight, the total subagent fee is calculated as the sum of applied fees for each triggered rule.
**'''''One rule with a major amount of parameters''''' - the subagency charge is calculated by one rule, which is selected by the largest number of completed rule parameters (the more parameters of the rule are completed, the higher its priority). If there are two or more suitable rules with the same number of parameters is selected last rule in the list as a higher priority (created later than the others).
* '''Billing Strategy for Subagents''' - determines the order of calculation of the final amount to be billed for managers and experts of subagencies. This setting can significantly simplify settlements between subagents and their agents, because the commission and/or the subagent's own charge will not be deducted from the subagent's deposit during payment, but will be immediately recorded in the subagent's account as profit. By default, both the charge and the commission of the subagent are deducted from the deposit, which means that the root agency manager will have to return the net profit to the subagent in the future, which makes settlements more complicated. The following two options are available for setting up:
** '''''Deduct the commission of subagents (for managers and experts) (if it has not already been deducted by the Strategy for using the subagent commission setting)''''' - the subagent's commission will be deducted from the final price of the order, '''unless it is deducted by setting up ''Strategy for using the subagent commission''''' (section '''Product control → Outdated settings → Pricing 1.0 → Setting commissions'''). It means that, if the setting "Billing Strategy for Subagents" is set to "Apply but not subtract from the price" and the option "Subtract Subagent Commission" is enabled, then the subagent's orders will record the full price with the subagent's commission, the same full price will appear in Websky's itinerary receipts and reports, but the order value will be deducted from the deposit with the subagent's commission. If the setting "Application strategy of subagent commission" is set to "Apply, deduct from the total for all Subagent's users (default)", the subagent's orders will immediately show the price with the deduction of his commission, the same amount will be deducted from the deposit and will be included in the itinerary receipts and Websky reports. In this case, the "Deduct the commission of subagents" option is no longer relevant.
** '''''Deduct subagent's own charge (for managers and experts)''''' - reduces the final price of the order by the amount of the subagent fee.
** '''''Deduct subagents's own services''''' - reduces the final price of the order by the amount of additional agency services added to the order.
* '''Hide fields in the pricing rule table for subagents''' - this setting allows you to hide certain pricing parameters from the subagent visibility, if the manager of the root agency does not want the subagent to use them to configure their charges. You can select several parameters. By default, everything is available. The options are listed in the table above.
In '''Sales Management → Aviatickets → Outdated settings → Pricing (1.0) → Commission settings''' (available only to the root agency manager), the following parameters are located:
* '''Display commission (subagents)''':
** '''''Yes''''' - the subagent's commission will be displayed to all users of the company
** '''''B2B only''''' - the subagent commission will be displayed only to the manager and experts of the company.
** '''''No''''' - the subagent commission will not be displayed to any user of the company
* '''Application strategy of subagent commission''':
** '''''Do not apply''''' - the commissions specified in the pricing table for subagents will not be applied.
** '''''Apply, deduct from the total for all Subagent's users (default)'''''.
** '''''Apply, deduct only for manager or experts (B2B)''''',
** '''''Apply but not deduct out of the cost'''''.
== See also ==
* [[Pricing (Air tickets)]]
* [[Charge (term)]]
* [[Currency]]
