Changes

'''Pricing''' module automates the process of calculating calculation of commissions and charges for airline air tickets, managing management of carrier's commission rules for carriers, agency charges fees and commission rewards for subagentssub-agents' commissions. * allows you to quickly configure set up even complex commission rules,* allows you to build a convenient and understandable clear pricing scheme,* accurately comply with the complex difficult conditions provided by airlines,

* provides a tool for monitoring to control the accuracy correctness of calculations.

== Principle of operation ==The module 's operation is based on the agency's pricing rules that the agency sets.

'''Rule''' — a set ''of "commission and charge fee values'' и ''условия их применения''" and "conditions of their application". <br />'''Commission Values of commissions and charge valuescharges''' areis:<br />*commission from the airline commisssion, <br />*airline bonus, <br />

*comission commission for the subagents. <br />'''Commission Condition of application for commissions and charge application rulescharges''' — a set of flight parameters to which the comsissions fees and charges of the rule rules will apply (“validating carrier”"validating carrier", “GDS”"GDS", “flight type”"flight type", "passenger types", “passenger types” etc.).

Pricing rules are set defined in the a table, in the an XLS or XLSX file , where:* "Table string" - rule. <br />* " String cell" - parameter value. <br />* "Column header" - parameter name. <br /> Each line is a separate rule. <br /> ''For one flight, only one rule is selected by criteria and only one rule applies''.

*''Table string'' — rule. <br />*''String cell'' — parameter value. <br />*''Column heading'' — parameter name. <br /> Each string is a separate rule. <br /> '''For a single Before calculating the commissions, the pricing module determines the availability of the flight, only one for the ticketing and the rule is selected by criteria which the commissions and applied'''fees are calculated, using the following algorithm:

Before calculating commissions, # The module records which airline GDS has defined as the validating airline;# Finds all the rules for that airline in the pricing module determines file;# Selects the rules that match the flight by all parameters;# Selects '''one''' of the appropriate rules by priority criteria;# If the availability triggered rule does not contain an override of the flight for ticketing and validating carrier, the validating carrier obtained from the GDS is established.# * If the triggered rule by which commissions and fees are calculated according to contains an override of the validating carrier, the algorithm:overriding validating carrier is set.# The rule applies.

# The module records which airline is identified by GDS as validating;# Finds all the rules for a given airline in the pricing file;# Selects the rules that match the flight by all the parameters;# Selects agency may only issue online flights of '''onecontract airlines''' of the appropriate rules by priority criteria;#* If the triggered rule does not contain the validating carrier override, the validating carrier received from GDS will be set.#* If the triggered rule contains the validating carrier override, an overridden validating carrier An airline is established. # The considered a contract airline if it has at least 1 rule is appliedin its uploaded pricing file.

'''ATTENTIONAttention!''' Flight The flight '''cannot be issuedticketed''' if:* there are no rules for an the airline are not set. It is recommended to delete such flights from the search results by the filter “Airline output "Airline is not contract”contract".* rules for the airline are setestablished, but the flight parameters don’t match do not correspond to the rule parameters.Workflow <!--The module's working order is shown given in the following schemediagram:

<!-- {| class="wikitable"

|[[Файл:Pricing_schemeСхема_ценообразование.png|1000px]]

|Workflow of the Pricing module work scheme|} --> 

Commissions and charges '''are calculated at each time an order update by is updated according to the rules loaded into the system at the time of verificationchecking''':*when forming the search resultsare generated,*when at the time of booking,*when switching to payment and ticketing,*when refreshing updating the order page.

If , during the period between booking and ticketing, '''''rules were changed''''' between booking and ticketing, after аfter bookingб the booking of an order, the commissions will be calculated by according to the new rules; thus, so the price at the time of booking and the price may be different from at the ticketing pricemay differ. System The behavior for of the system in case of such situations a situation is set by the parameter '''''Recalculate service charge''''' in the '''under System settings Settings → Background processes Processes → Triggers settings section'''Synchronization Events. Calculation You can track the calculation of commissions, which are active valid at the time of booking, can be traced in the logs on order logs.

In the price details (on the order page) and in the itinerary receipt, information on fees the charges is presented by provided in accordance with one of the '''passenger charge separation modesof division of charges by passengers''':* Equally divided between non-zero ticket prices - agency and sub-agency subagency charges are divided equally between all passengers whose with fare and tax amount is greater more than 0. This mode is selected by default.* Equally Equivalent between all fares - agency and sub-agency subagency charges are divided equally among all passengers.* In proportion Proportional to fares - agency and sub-agency subagency charges are divided in proportion proportionally to the fare price for a specific particular passenger in the total amount of the order, i.e. the higher more the fare priceis, the greater more part of the charge is allocated to for it.* Only for to the first type of passenger - agency and sub-agency subagency charges are determined by allocated to the first type of passenger. * In proportion Proportional to the farefares , except for infants - agency and sub-agency subagency charges are divided in proportion proportionally to the fare price for a specific particular passenger in the total amount of the order, with the exception of the infant type passengerexcept for infants.Charges ''The fees in the price details are presented with the consideration of the breakdown division only if they are hidden in XP/XX feestaxes, otherwise they are displayed as aт individual a separate line without separationdivision.'' <br>The You can find the setting can be found in the '''«Product control → Aviatickets → Sales Management - Air Tickets - Pricing → Settings».- Settings - Passenger Fee Splitting Mode'''.

=== Calculation of comissions Commission calculation for non-contract contractual airlines ===

Agency can '''The agency may "issue tickets of ''" to "non-contract'' contractual" airlines''' on the condition of pure "clean interline " terms between the airlines.

For example,* The agency does not have a has no contract with «АА» "AA" airline.* The agency has a contract with the airline «BB» "BB" airline.* Between the «АА» and «BB» companies, there There is an interline agreement allowing to issue between "AA" and "BB" companies, which allows issuing tickets for «АА» "AA" on the «BB» "BB" form.

In order to To issue «АА» tickets for "AA" airline tickets, the agency sets up has a rule for «АА» "AA" airline, which containsspecifies:# validating Validating carrier: '''''«АА»«AA»''''',# overriden redefined carrier: '''''«BB»''''',# share of interline segments: '''''1«1»''''',# airline commission: ''indicate specify the amount of the commission reward provided by «ВВ» "BB" for tickets with a 100% share of interline segments''.

'''ATTENTIONAttention!''' The Websky system does not track if there are monitor the presence of interline agreements between carriers. The agency is fully responsible Responsibility for redefinition lies entirely with the overrideagency.

=== Choosing Selecting the rule for calculations calculation ===Commissions for flights the flight are calculated by one rule. If several rules are suitable for a the flight, the system selects a chooses the rule for calculation by the priority criteria. The rules Rules are compared according to on the first criterion, if the criterion in this case is does not triggered - by work, on the second one and so on, until one rule is determineddefined.

Procedure for The order of comparing the rules for selecting to select the rule for the calculation:#'''By the ''"Priority'' " column''' - if the triggered rules have a priority indicated, then the rule with the highest priority is selected. #'''By the presence of an overriden overridden carrier''' - if several rules with the same priority are triggered (or the priority is not definedspecified), the rule with overriden the overridden VC is selected.#'''By For a non-empty nonempty ''ComissionCommission'' cell''' - the priority of the rules with set an established commission (even in 0%) is higher than По непустой ячейке ''Комиссия''''' - priority of rules with a set commission (even at 0%) is higher than priority that of the rules with an empty commission cell.#'''Additional Extra priority''' - ''Manually set manually'' in the section '''Product control → Aviatickets Avia tickets → Pricing → Settings''' section by the parameter '''''Additional Extra priority''''':#*'''''Not set''No''' - Additional no additional priority not is set.#*'''''Maximum commission from the airline comission''''' - selects the rule with the maximum commission from the airline comissionis selected.#*'''''By the number of parameters in the rule''''' - selects the rule with the largest number of non-empty parametersis selected.#'''Rule index 's ordinal number''' - if none of the priorities is applicable, the newer rule is considered the priority (located in the table below the others) is considered priority.

== Testing and debugging of rule triggering ==All the calculations at each stage of their application are logged and displayed in the debug table. The debug table is used to control the triggering of how the ruleswork, providing information on the application of about how the rules apply to the selected flight.

The link Link to the debug table is available to the manager and experts of the root agency manager:* on the to display search results, for each flight by the '''''ComissionCommission ''''' link, * on the order page, on in the flight price details detail, by clicking on the amount of the commission or charge.

<!-- {| class="wikitable"

|} -->

<!-- {| class="wikitable"

|} -->

<!-- {| class="wikitable"

|Links to the debug table on the price detail page|} -->

'''Table columns''' — pricing parameters . <br />'''Column headingheader''' — values of pricing parameters for the verified flightbeing checked.<br />'''Строки таблицыTable rows''' — pricing Pricing rules ''"for the validating carrier'' " of the flight.

The table shows the order of parameters’ verificationin which parameters are checked.

The parameters of each rule are compared to in the flight parameters:

## the cell is highlighted in green,## the next following parameter is verifiedchecked;# if the value of the flight parameter value does not match the value of the rule parameter value:## the cell is highlighted in red,## rule verification check stops.'''If the a rule matches by all the parameters, them the rule is appliedapplies, commissions and charges fees are highlighted with greenlight, and their calculated values are showndisplayed next to each other.''' 

<!-- {| class="wikitable"

|} -->

== Enabling the module. Rules Import and export of rules Export ==

To enable calculation of comissions via set the pricing rule: # Go to Product control → Avia tickets → Pricing, turn on → Excel import/export.# Press '''Upload in "xls" format''' or '''Upload in "xlsx" format'''. Open the file to edit.# Set the rule: '''Fill in the following optionsstring parameters'''. The format of data entry in each column must correspond to a strictly defined format (see Rules Import). <br /> Obligatory parameters to fill in: #* '''''validating carrier'''Commissions 2.0#* '''''commission'' and ## Save the changes to the file.# On the '''Charges and discountsExcel import/export''' page in the Product control → Avia tickets → Pricing → Settings sectionAdministration panel click '''Browse''', open the file.# Click '''Send''' to upload the file to the system.

To set a pricing rule:# Зайдите в раздел Product control → Avia tickets → Pricing → Import / export Excel.# Press '''Download in "xls" format''' or '''Download in "xlsx" format'''. Open file for editing.# Set During import, the rule: '''fill in the string parameters'''system will validate all entered values. The format for entering data If a value is entered in each column must correspond to a strictly defined cell in an incorrect format (see Rule Import). <br /> Required parameters:#* '''''validating carrier'''''#* '''''commission'''''# Save the changes to the file# On the '''Import / export Excel''' in the administration panel, click '''Browse''', open the file.# Press '''Send''' to upload the file to the systemwill report an error while saving all correctly defined rules.

While importing, the system validates all entered values. If a value is entered in an incorrect format in a certain cell, the system will report an error, while retaining all correctly defined rules. <!-- {| class="wikitable"

|Parameter Errors at parameter validation errors|} -->

After validation, the page displays a table is displayed on the page, in which showing all loaded rules are reflected in a short compressed form.

<!-- {| class="wikitable"

|} --> 

Invalid The table provides color-coded rules that are highlited by the following colors in the tablecurrently invalid:* rules which are that have not active yet come into effect (the sale begin start date is later higher than the current date, see pricing rule parametersParameters of Pricing Rules) are highlighted in orange;,* the rules that have expired rules (the sale end expiration date is later greater than the current date) are highlighted violetin purple.

== Pricing Rules Parameters rule parameters =='''Pricing Template of file for entering pricing rules file template:'''<br/>[[File:CommImportExampleV1.0.5.xlsx]]

'''ATTENTIONAttention!''' It is restricted forbidden to rename columns! <br/> It But it is allowed to swap change columns and delete remove unnecessary onescolumns.

To see parameter descriptions view the description of parameters <span style="background-color:gold">expand the table</span>:

|colspan="5"| '''Pricing Rules Parametersrule parameters'''

! scope="col" | HeadlineTitle

! scope="col" | Valid ValuesPermissible values

| Unique A unique record number from any external system (or database). Optional parameter. It is does not involved participate in the calculation logic and is used to conveniently identify rulesfor convenient rule identification.

| The airline for which the rule is set. Must be a the contract airline of the agent. If it is necessary to conduct make ticketing on the stock of another airline (by interline), the validating carrier is overriden redefined (see overriden Redefined validating carrier). If GDS the validating carrier from GDS is unacceptable by the specified pricing rules and is not overriden, overridden - the flight is considered unacceptable for ticketing and is removed from the search results with the appropriate filtering settings for the of resultsfiltering.

2-letter digit IATA airline IATA code

| overriden redefined vc

| If the validating carrier proposed by the GDS is not contract a contractual carrier or does not suit satisfy the commission agent, it can be overriden forcibly overridden through this field. The GDS VC is indicated in field indicates the VC field from GDS (or it is left empty), and this field indicates the carrier overriden redefined by the agency is indicated in this field.

The responsibility agent is responsible for the admissibility acceptance of the replacement and for the adequacy of the flight price (which was calculated by GDS for the carrier proposed by offered to it) is assumed by the agent. The priority for the rules with overrides the redefinition is higher than for the rules without it.

2-letter digit IATA airline IATA code

| first segment carriagescarriers

| A set of allowable acceptable marketing carriers for of the first segment of the route.

| A set of valid acceptable marketing carriers (interlines) on of any segment of the route. Permissible input options:* CODE,CODE,CODE&nbsp;: the rule applies if at least one marketing carrier from the flight is on the list.* CODE,CODE,CODE!&nbsp;: the rule applies if each marketing carrier from the flight is found on the list* <>CODE,CODE,CODE&nbsp;: the rule will not apply if at least one marketing carrier from the flight is found on the list* <>CODE,CODE,CODE!&nbsp;: the rule will not apply if all marketing carriers from the flight are found on the list.

Valid input options:* CODE,CODE,CODE&nbsp;: rule will apply if at least one marketing carrier from the flight is present in the list* CODE,CODE,CODE!&nbsp;: rule will apply if each of marketing carriers from the flight appears on the list* <>CODE,CODE,CODE&nbsp;: rule will not apply if at least one marketing carrier from the flight appears in this list* <>CODE,CODE,CODE!&nbsp;: rule will not apply if all the marketing carriers from the flight appear in this list| empty = any<br/>- one or several more values (see description)

| Allowability Permissibility of a flight being operated by another (operating) airline| empty — - all flights<br/>1 — - code sharing is required <br/>0 — - code sharing is restrictedprohibited

| Valid Permissible operating airlines (verified need to be tested on all segments).

Input variantsoptions:* CODE,CODE,CODE&nbsp;: the rule will apply applies if at least one operating carrier appears in of the flight is found on the list.* CODE,CODE,CODE!&nbsp;: the rule will apply applies if each every operating carrier of the flight is present found on the list.* <>CODE,CODE,CODE&nbsp;: the rule will does not apply if at least one operating flight carrier appears in is found on the list.* <>CODE,CODE,CODE!&nbsp;: the rule will not apply if all the operating carriers of the flight are present found on the list.| empty = any<br/>- one or several more values (see description)

| own segment share of own segments

| The minimum allowable allowed share of own segments (segments where the validating carrier is equal to the a marketing one) must be greater than or equal to the specified a given value (any number from 0 to 1):* 1 — - all segments are own* 0.5 — - half or more of own segments * 0.25 — - a quarter or more of own segments * 0.01 — minimum - there is at least one own segment* 0 — - all segments are of interline

| interline segment share of interline segments

| The minimum allowable share allowed percentage of not own nonproprietary segments (segments where the validating carrier is not equal to the marketing one) must be greater than or equal to the specified value (any number from 0 to 1).* 1 — - all segments are of interline* 0.5 — - half or more own segments are interlineof interlines* 0.25 — - a quarter or more own segments are interlineof interlines* 0.01 — - there is at least one segment of the interline segmnt is present* 0 — - all segments are own

| Settlement system: BSP or ТКПTCH settlement system

| Global distribution system , in which the flight / PCC of specific Websky requisites / ID of the Websky requisite package ID is was found in {{NameProject1}} system.Listed in any order; sequence, you can mix different types. The "or" rule applies: if the whole Sabre is specified entirely, you don’t need to specify all of its PCC / packages are no longer indicated.

'''ATTENTIONAttention!''' When specifying the name of the GDS, strictly follow the name format specified in the documentation. If the name rule doesn’t match with the template, the rule it will not apply!| empty = any<br/>GDSГРС: <code>SABRE, GALILEO, AMADEUS, SIRENA, SITA, SIG23</code><br/>PCC: [letters+numbersdigits]<br/>package Package ID: [numbersdigits]

| start of sale beginning

| The minimum allowable checkout Minimum allowed date of order execution (not to be confused with the date of departure date). To trigger the rule, the current date must be greater than or equal to the specified one.

| end of sale end

| The maximum Maximum allowable checkout date (not to be confused with the departure date)for placing an order. To trigger the a rule, the current date must be lesser than less or equal to the specified onedate.

| International or domestic (all flights within one the same country) flight.Single One value

| Allowable Permissible flight numbers, can be indicated specified with or without the code of the marketing company code.

* NNN,NNN: the rule will apply applies if at least one flight number from a flight from any segment appears in is found on the list.* NNN,NNNNNNN!&nbsp;: the rule will shall apply if all flight numbers from all flight segments appear in are found on the list.* <>NNN,NNNNNNN&nbsp;: the rule will not apply if at least one flight number from the any flight appears in segment is found on the list. * <>NNN,NNNNNNN!&nbsp;: the rule will not apply if all the flight numbers from the flight appear in are found on the list.

| empty = any<br/>- one or several more values (see description)

| Valid Permissible aircraft codes, should must be indicated specified in the same form in which as the codes returned by the GDS returns them.

* CODE,CODE: the rule will apply applies if at least one aircraft code from any segment matches one from of the specified list.* CODE,CODE!&nbsp;: the rule will apply shall be applied if aircraft codes from all the flight segments are in the list.* <>CODE,CODE&nbsp;: the rule will not apply if at least one aircraft code from the flight is in the list.* <>CODE,CODE!&nbsp;: the rule will not apply if all the codes from the flight are in the list.

 | empty = any<br/>- one or several more values (see description)

| Valid fare Permissible tariff codes. At least one fare from the flight must match coincide with one from the preset given list. Under If there is a rule with denial rule, there should must be no matchmatches. The match is not exact: the code from the rule may be contained in the code from the flight (for example, the entered S1GREY26 will match the S1GREY26CH from the flight).

* CODE,CODE: the rule will apply applies if at least one fare appears in the list.* CODE,CODE!&nbsp;: the rule will apply be applied if all the fares of the flight are in the list.* <>CODE,CODE&nbsp;: the rule will not apply won't be applied, if at least one fare is in the list. * <>CODE,CODE!&nbsp;: the rule will not doesn't apply , if all the fares of the flight are in the list.

You can define set a [httpshttp://enru.wikipedia.org/wiki/Regular_expressionРегулярные_выражения regular expression]. To do this, write the parameter in the /XXX/ format. Examples:* /ABC/ — code must contain "..ABC..", for example , "NBABCS"* /abc/i — case-insensitive check, the code may can contain characters in any case, for example "NBABCS" or "Abcof"

* /OW'''$'''/ — the code must end with "..OW", for example "SRSOW"* /'''^.'''L/ — first letter - any ( '''.''' — any symbol), the second letter in the fare code must be L, for example "QLFST"* /OK'''.*'''RT/ — ( '''.*''' = any number of any symbolscharacters) "..OK..RT..", for example "ANOKURTN"| empty = any<br/>- one or several more values (see description)

| Restriction on the maximum price value of the "base costprice" (the amount sum of all fares from the carriers on the flight or the price from the GDS minus taxes). If the parameter is set, the rule written in the line will is triggered only work if the flight fare is less than or equal to the specified value.| empty = no restrictionlimit<br/>xxxCODE (see examples)

| confidential Private fare

| To trigger the rule, the flight must have a fare with the attribute sign of confidential (private). Confidentiality of the fare This information is always reported provided by GDS. If, for an unambiguous definition of the rule, it is 's enough to indicate the a specific code of the a private fareto unambiguously define the rule, it is 's not necessary to set the attributesign.| empty = any fares<br/>1 — a private fare one must be present<br/>0 — there shpuld must be no private fares

| Allowable Permissible tax codes 

* CODE,CODE: правило применится, если любая такса из перелета встретится в спискеthe rule will apply if any tax from the flight is in the list.* CODE,CODE!&nbsp;: правило применится, если все таксы перелета встретятся в спискеthe rule will apply if all the flight taxes are in the list.* <>CODE,CODE&nbsp;: правило не применится, если любая такса из перелета встретится в спискеthe rule will not apply if any flight tax is in the list.* <>CODE,CODE!&nbsp;: правило не применится, если все таксы перелета встретятся в спискеthe rule will not apply if all the flight tax are in the list.where CODE — is a set of uppercase latin capital Latin letters.| empty = any<br/>- one or several more values (see description)

| Attribute An attribute of a confirmed flight price. After the search, the The flight price after search is considered unconfirmed, its status changes to “confirmed” "confirmed" (“relevant”"actual") when after creating an actual a real PNR or after requesting a price update within the framework of {{NameProject2}} Nemo Connect web services (before creating a PNR).| empty = any flights<br/>1 — the flight is in the PNR or its price is verified beforehand checked in advance <br/>0 — the flight has just been received retrieved from the search results

| presence availability of VC segments in for all the fares

| Verification: among segments of any fare there segment must be a segment of have a validating carrier segment (at least minimum one).| empty or 0 = any fares<br/>1 — - condition must be met

| Valid Permissible service class categories of service classes.

Input variantsoptions (one- or two-letter values are entered):* CODE: The rule applies if the class is in the list.* CODE: this rule is applied if a combination of classes is in the list.* CODE,CODE: a rule will apply is applied if a class from any segment appears is in the list.* CODE,CODE!&nbsp;: the rule will apply applies if all classes from all flight segments are in the list.* <>CODE,CODE&nbsp;: the rule will not apply if a class from any segment appears is in the list.* <>CODE,CODE!&nbsp;: the rule will not apply if all classes from all flight segments are in the list.where the CODE:

* E - economy* F - first

 | empty = any<br/>- one or several more values (see description)

| Allowed literas letters (singleone-letter codes) of booking classes. Must be in Latin letters; Russian , Cyrillic letters are valid allowed only for the Sirena supplier rules of supplier Sirena.

* CODE,CODE: the rule will apply applies if at least one class from any segment appears is in the list.* CODE,CODE!&nbsp;: the rule will apply applies if the classes from all the flight segments are in the list.* <>CODE,CODE&nbsp;: the rule will not apply if at least one class from any segment appears is in the list.* <>CODE,CODE!&nbsp;: the rule will not apply if the classes from all the flight segments are in the list.| empty = any<br/>- one or several more values (see description)

| carriers and classes

| A set Set of "marketing carrier" + "booking class" pairs of any segment of the route.  Permissible input options:

Допустимые варианты ввода* CODE:CODE,CODE:CODE,CODE:CODE : the rule applies if at least one flight segment matches one of the listed ones.* CODE:CODE,CODE:CODE,CODE:CODE! : the rule will apply if all the flight segments are in the list.* <>CODE:CODE,CODE:CODE,CODE:CODE : the rule will not apply if at least one flight segment would match any of the segments in the list.* <>CODE:CODE,CODE:CODE,CODE:CODE! : the rule will not apply if all flight segments are in the list.

* CODE:CODE,CODE:CODE,CODE:CODE : rule will apply if at least one flight segment matches one from the list.* CODE:CODE,CODE:CODE,CODE:CODE! : rule will apply if all flight segments appear in the list. * <>CODE:CODE,CODE:CODE,CODE:CODE : rule will not apply if at least one flight segment matches one from the list.* <>CODE:CODE,CODE:CODE,CODE:CODE! : rule will apply if all flight segments appear in the list.| empty = any<br/>- one or several more values (see description)

| zones

| Geographic Geographical zones of a the flight. The entire whole flight should must not go beyond exceed one of the indicated specified zones for the rule to triggerbe triggered. [http://www.geonames.org/countries/ division of countries into by specified zones].

* EUAN - Europe + AntarcticaAntarctic

* AFAN - Africa + Antarctica

* ANNA - Antarctica Antarctic + North America* ANOC - Antarctica Antarctic + Australia and Oceania* ANSA - Antarctica Antarctic + South America

Only the listed zone combinations of zones are allowed!| empty = any

| empty = any<br/>- one or several more values

| The listed above country codes form an area outside beyond which the an aircraft should must not land and take off.| empty = any<br/>CODE,CODE...

| countries of departure countries

| Valid Permissible countries of departure countries for the flight (only the country of departure country of the first route’s segment of the route is verifiedchecked).

| arrival countries of destination

| The destination country is verified checked (for OW and CR it : this is the last country of the last segment, for RT it : this is the last country of the first leg of the route). For example, for the flight MOW-PAR-MOWflight, the destination country is FR, for MOW-PAR-LON it is - GB. '''Rule “country Country of departure = RU, country of destination country = RU” RU does not mean a local flight''' - do not forget to indicate “DA” as specify the flight typeDA.

| Attribute of a direct Direct flightattribute| empty = any<br/>0 — only with transfers only<br/>1 — direct only<br/>extraadditionally:<br/>2 — initial flight is direct<br/>3 — initial flight is with transfers

| You can leave the field empty blank or specify one a single value:* OneWay -Way — OW,* Round Trip — - RT,* Complex Route — - CR.| empty = any<br/>КОДCODE (see examples)

| A chain Chain of IATA codes of cities or airports that describes , describing the entire route of the flight route including , taking into account transfers, without breaks and repetitions. You should always Always use the IATA area code of the city, if it is available (aggregating aggregation airport). For example, the flight a VKO-ORY, ORY-VKO flight is brought turned to the route MOW-PAR-MOWroute. 

| Indicates only a Only part of the route made up compiled similarly to a the previous oneis specified.

| Use the IATA codes of airports (not cities) in the IATA rule. The rest is similar to the "routes".| see “routes”"routes" parameter description.| see “routes”"routes" parameter description.

| Use the IATA codes of airports (not cities) in the IATA rule. The rest is similar to the "contains routes".| see "contains routes"parameter description.| see "contains routes"parameter description.

| Only the departure airport of the first segment is checked. When specifying you specify airport codes, you need an exact match is required. When While specifying city the codes of cities (aggregating aggregation of airports), the comparison is carried out made according to the internal airport directoryglossary of airports. It is recommended that you provide to specify the codes of specific airport codesairports.

| Arrival arrival (airports, cities)

| The airport of arrival airport is defined similarly to the "arrival countriescountry of destination". Checking The check for comparisons comparison is carried out made similarly to "departure (airports, cities)".

| start of departureflight

| Departure The departure date of the first segment must be greater than or equal to the specified date.| empty = anyignored<br/>DD.MM.YYYY

| Departure departure in (in hours)

| From the current date, the The maximum value or range of departure range is setfrom the current date. For example, if it is necessary you want to allocate select flights no later than 5 days before departure, then the range [0,120] is shall be set.

| end of departureflight

| The date of departure date of the first segment must should be less than or equal to the specified date| empty = ignored<br/>DD.MM.YYYY

| Departure The departure date of the last route segment of the route must should be greater than or equal to the specified date| empty = ignored<br/>DD.MM.YYYY

| Departure The departure date of the last route segment of the route must should be less than or equal to the specified date| empty = ignored<br/>DD.MM.YYYY

| Limit Restriction on the maximum gap in days between the first flight date of flight and the end of the route. You can specify a range. Duration in days is calculated as a mathematical date differencein dates. If the departure and return are in one day, the duration is will be equal to 0 days.| empty = no restriction<br/>number of days — - maximum value (inclusive)<br/>[X,X] — range

| weekdaysdays of the week

| Allowed Permissible days of the week for the departure date of the route's first segment of the route. Values are indicated specified by the ordinal number corresponding to the order of the day of the week, starting on from Monday as 1.| empty = ignored<br/>1 — Monday<br/>...<br/>7 — Sunday<br/>- one or several more values

| Allowed Permissible types of passengers on the flight. To trigger For the ruleto work, all the listed types of passengers must be present in the flight.| empty = any<br/>ADT — adult<br/>CLD — child (2-12)<br/>INF — infant (0-2)<br/>INS — infant with seat (0-2)<br/>- one or several more values

| A formal Formalized flight description of the flight in text format, to create complex rules. <br/> Will be added to the next version of the application.program

| If several rules are triggered, then the one with the highest priority is selected. If there are several rules with the same priority (or the no priority is not specified), a the newer rule is selected (located below in the imported table).| integerintegral number<br/>empty = 0

| promotion promotional code

| Unique promotion code. It is created in the administration Administration panel under in the section {{Menu|Product control| Modules|Loyalty Programprogram|Promotions and Promotional promotional codes.}}.| any set of letters/numbersdigits/characterssymbols

| Transition source ID, which is displayed in the "No.№" field of the transition source sources table in the metrics modulemetric.<br/> You can enter multiple Multiple sourcesare allowed.

| Agent 's profit , received from the airline for sold tickets sold. It is the mandatory The field, and it required for filling in must strictly correspond to the value specified indicated in the contract. The value is transferred to the GDS upon ticketing. May It can be indicated as a specified in percentage of the fare or in absolute value. The commission Commission is always calculated for each passenger.Rules with a specified zero commission has more have higher priority over rules with an empty commission.

| subagent commission for subagents

| Subagency commission Commission to a subagent is a part of the airline's profit from the airline, which the agent gives away sends to the subagents. The value of the commission acts as a discount for subagents, reducing the cost price of air tickets. Commission is always calculated for each passenger whose fare value is not equal to 0.

'''Commission Formats assignment formats for Subagentssubagents:'''

** ''X'' - commission amount, integer or decimal fraction number with dot as a dot separator: <code>60</code>, <code>-3</code>, <code>0.5</code>** ''RUB'' - IATA code of the currency:<code>EUR</code>, <code>UAH</code>.* Percentage of the fare: <code>X%</code>,**where ''X'' - a percentage of the fare, an integer or a decimal fraction number with a dot point separator: <code>60}</code>, <code>-3</code>, <code>0.5</code>.For specific selected subagents or subagent groupsof subagents:<br/>* <code>(ID:value),(ID:value),(ID:value),...</code>, where ''ID'' - number of subagent subagent’s (groupgroup’s) number in Websky, ''value'' - amount the size of the commission for this subagency (group) in the following format : <code>X%</code> or <code>XRUB</code>.

In one rule, you can combine the commission for all subagents and the commission for the specified subagents in the following a format:* <code>XX,(ID:YY),(ID:YY),(ID:YY),...}}, where:

** YY - commission for a given the specified subagent in the format described above. In this case the size of the commission will be calculated:* for all subagents, except the specified: XX, * for the specified: XX + YY.

*Subagent comission commission under the number 123 is: 5% + 2% = 7% from of the fare.<br/>*Subagent comission under the commission number 123 is345: 5% + 3% = 8% from of the fare.If you want to enter the amount as decimal number, the fractional part is separated by "." , eg: <code>0.5%</code>

{{If the sum of the decimal is to be entered, the decimal part is separated with "." , for example: <code>0.5%</code> '''Attention|If !''' In case your agency plans to create a large number of individual pricing rules, each of which will indicate specify the value of the subagent commission for individual subagents / groups / users, then the recommended form of entry form is as follows : (12345,12346,12347:3%) instead of (12345:3%),(12346:3%),(12347:3%). Which means using the a grouping of the same values.}}

| segment-by-segment segmental commission calculation segment-by-segment

| Attribute of applying a commission or bonus to being applied for each flight segment of the flight. For example, 100 rub. rubles for each flight segment.| empty = 0<br/>0 — there is one commission for the entire flight <br/>1 — the commission must should be multiplied by the number of segments

| The agent’s additional Additional agent profit that the agency receives from the airline, but it is not included taken into account in requests to the GDS. It is set and calculated in exactly the same way as commissions (the calculation considers the parameter "segment-by-segment commission calculation"is taken into account when calculating). It is used to calculate the "profitability" of air travel, affects the operation of the mixer and may can affect the charge fee when setting the "minimum profit" parameter. 

Of all the triggered rules that triggered, the bonus will be taken into account only from one of them according to by the following priority:* Maximum priority for the triggered commission rule* If there is no bonus in the commission rule, the a bonus will be used from another triggered '''non-commission''' rule (an additional rule with an empty commission)will be used. If there are several such rules, the rule with the highest identifier is used (below in the table)will be used.

| segment bonus (allowable allowed for airlines)

| Setting the current parameter forces forcibly enables the mode of bonus calculation mode for each flight segment of the flight (for an absolutely specified bonus), but only segments with validating or interline carriers from the list specified here are taken into account.| empty<br/>CODE (airline code)<br/>CODE,CODE ...

| All markups/discounts that will be applied to the flight described by the rule are indicated specified here. You can specify several price rules in one field, by dividing them by user typetypes.<br/>format = (subject:amountsum),(subject:amountsum),(subject:amountsum)...<br/>subject = group ID of the groups, users user ID and two "B2C" values, "B2B" values with the possibility of <>denialrejection<br/>amount sum = term subclause + term subclause + termsubclause. ...[restriction]<br/>restriction = range of the total charge value, is set as [price,price]<br/>term sum = price*multiplier*multiplier...<br/>price = "xxxCODExxCODE" (currency code) or "XX%" (percent percentage of the total cost price (fare + taxes) ГРСof GDS)<br/>multiplier = one of the values:* PAS — - total number of passengers (including INF)* ADT — - number of adults* CLD — - number of children (2-12)* INF — - number of infants (0-2)* INS — - number of infants with seat (0-2)* SEG — - number of flight segments (flight from A to B with 1 transfer => 2 segments)* LEG — - number of legs (flight from A to B with 1 transfer transplant => 2 segments1 shoulder)* TRF — - to get the fare price, equal to the total amount of faresfare sum* SGV — - number of segments of the validating carrier’s segmentscarrier

* 100RUB*SEG&nbsp;: plus 100 rubles to the order value for each segment* 150RUB*SEG*PAS;: plus 150 rubles for each segment, for each passenger. For example: a flight with two segments and two passengers = 600 rubles.* -10%*TRF&nbsp;: 10% discount from a the fare.

* (<>123,345: 100RUB), (123,345: -100RUB)&nbsp;: subjects 123 and 345 will receive a discount of 100 rubles., the rest - a of the markup of is 100 rubles.* (B2B: 1000RUB*ADT — - 100RUB*CLD[-10%,-1%]), (B2C: 10% [10USD,]), (123: -1000RUB)&nbsp;: B2B users receive will get a markup of 1000 rubles for each adult ticket and a 100 rubles discount for each child ticket, but not less than 1% of the total price cost and not more than 10%. B2C users get receive a 10% markupsurcharge, but no not less than $ 10. User with ID=123 will receive a discount of 1000 rubles.

If several price rules separated , listed by comma , are triggered, their total amount is taken. If this is not a suitable behavior, separate divide the price rules into separate flight rules (stringsrows), they can be adjusted by priority.

{{'''Attention| If your agency plans !''' In case you plan to create a large number of individual pricing rulesfor your agency, each of which will indicate specify the value of the agency charge fee for individual subagents/groups/users, then the recommended form of entry form is as follows : (12345,12346,12347:3%) instead of (12345:3%), (12346:3%), (12347:3%). It Which means that you need to use using a grouping of the same values.}}

If you want need to enter the amount as a decimal fraction, the fractional part fraction is separated with "." , for example: <code>0.5%</code>

|Commission for metasearchMetasearch commission|MetasearchCommission|The comission is Commission, charged by the metasearch meta-search system (for Websky at the moment it is only Aviasales) and is calculated at the search stage. The value should be indicated specified as a decimal representation of the interest rate - it is a fraction of 1 if you, for example, specify if you set 0.05 - 5%. You can It is possible to specify it with/without the sign "%" sign. The commission Commission is calculated from the amount = the flight price from the supplier + fees/discounts + additional fees + min. profit. The calculated value is rounded to 2 characters after the separator. This parameter is described in more detail[http://support.nemo.travel/ru/%D0%92%D0%B7%D0%B0%D0%B8%D0%BC%D0%BE%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D0%B5_%D1%81_%D0%BC%D0%B5%D1%82%D0%B0%D0%BF%D0%BE%D0%B8%D1%81%D0%BA%D0%BE%D0%B2%D0%B8%D0%BA%D0%B0%D0%BC%D0%B8#%D0%9A%D0%BE%D0%BC%D0%B8%D1%81%D1%81%D0%B8%D1%8F_%D0%BC%D0%B5%D1%82%D0%B0%D0%BF%D0%BE%D0%B8%D1%81%D0%BA%D0%B0 here].

|0.05

| extra charge attribute of an additional charge

| The setting allows you to change the charge calculation procedure for calculating the charge, by adding additional settlement calculation rules to the final result.* 0 — - Standard charge fee (default value). Of all these the feesspecified, the one wih highest priority will be appliedby priority.<br/>* 1 — - Additional chargefee. Charges indicated Fees specified as optional additional fees are verified checked separately. SimilarlyIn the same way, one extra charge with the highest maximum priority will be is applied.* 2 — Mandatory charge- Obligatory fee. Will It will be applied obligatory to apply if all charge collection parameters are satisfied. Priority is ignored.

| The minimum Minimum profit that the agency will receive for the order. If the calculated agency profit of the agency is less than the minimumprofit, then the charge fee will be increased to the required value.The format is similar to the that of an agency charge format. For calculations, the value from the rule according to by which the airline commission will be determined will be applied. If you want need to change this behavior, you must should set the parameter "priority of the min. profit" parameter (see below).

| min. minimum profit priority

| An additional parameter responsible for calculating the minimum profit. The rule with the highest priority will workbe triggered, and if the priority matches, the rule located below will be used.

| roundingroundoff

| Arithmetic The procedure of arithmetic rounding procedureof the charge| empty = 0,<br/>0 = to an integer valuevaue,<br/>0.1 = to tenths,<br/>0.01 = to hundredths

== Additional rule settings parameters for Websky platform ==

Parameters for working with private (confidential) fares management.

To view the options description of the parameters <span style="background-color:gold">expand the table</span>:

|colspan="5"| '''Additional additional rule settingsparameters'''

! scope="col" | HeadingTitle<br/>

! scope="col" | Valid Permissible values<br/>

| Tour codeТур код<br/>| any value<br/> On the example of Amadeus: if it is not necessary to specify PAX (passengerType), we specify only the RU084P tourcode, before the tourcode on the supplier side, * (asterisk) is always added, and the entered command in the terminal looks as FT *RU084P. If it is necessary to specify PAX (passengerType), you need to to specify it with the tourcode without space PAXRU084P, in the terminal, the entered command looks like FT PAX *RU084P.| 15ZU<br/> RU084P

| any value<br/> or %VAT_VALUE% to transfer the value of VAT value to in the endorsement only for GDS Amadeus, SaberSabre, Galileo, GalileouAPI and S7 NDC; for Sabre, the value is transferred to the GDS, but does not fall into to the itinerary receiptItinerary Receipt

| 100RUB<br/>2%

| tour code discount subject by a tour code

| ID of the subject who will receive be given a discount by on the tour codetourcode

| discount by a tourcode

| СкидкаDiscount <br/>

| authorization authorisation code

| Authorization Authorisation code<br/>

In the section "Product control → Aviatickets Avia tickets → Pricing → Settings" section, there is a setting an option '''Issue EMD by order charges amountcharge value'''. It is responsible for issuing the EMD to a collection for the agency 's charge (available only to Siren Sirena Travel). How it worksPrinciple of operation: if , for the agency that which buys the ticket has there is an agency charge in the pricing rules for the validating air carrier company of the carrier in the pricing rules, then , when issuing an order, in addition to the itinerary receipt and EMD for additional services, a separate EMD will be issued for agency charge will be issued. If there are several people in the order, then the charge will be divided between them, the total amount of the charge fee will not increasebe increased.<!-- == See also ==* [[Ценообразование для субагентов|Pricing for subagents (rus)]]* [[Валюта|Currency(rus)]] -->