Full file example
Файл:Full file example.xls
| Title |
Operating name (used in the table file) |
Description |
Acceptable values |
Examples | |
|---|---|---|---|---|---|
| id | id | Unique record number, can be taken from any database/system. It's an optional parameter and isn't involved in any calculations (used only for imformational purpose). | any integer value | 123 | |
| GDS validating carrier | valCompanyId |
Carrier (airline) code is compared to the airline that is offered by GDS as a validating one. Agency must have a contract with this airline. In case if there is a need to issue tickets and assign another airline stock, you can redefine the validating carrier using the next column ("redefined carrier"). If the GDS validating carrier isn't confirmed by Nemo pricing rules as an allowed carrier and isn't redefined, Nemo considers this сarrier as an unauthorized one. You can exclude such flights from search results using a special search filter. |
empty value is ignored
2 letters/digits |
SU
LH | |
| redefined validating carrier | manualVV |
If an agency has no contract agreement with the GDS validating carrier (or it provides relatively low commission value), you can redefine the validating carrier on your side using this parameter. In this case the "validating carrier" value must be the same as the GDS validating carrier (or it can be empty). |
empty value is ignored |
SU | |
| first segment carriers | airlines |
List of allowed marketing carriers for the first route segment. |
empty = any values |
SU,LH,BA
<>S7,SU | |
| any segment carriers | airlinesAny |
List of allowed marketing carriers (interlines) for any segment.
|
empty = any values |
SU,LH,BA | |
| code-sharing | codeSharing | Code-sharing index (i.e. if a flight can or can't be operated by another airline). |
empty = all flights |
0
1 | |
| operators | operatingAirlines |
List of allowed operating carriers (for all segments)
|
empty = any values |
SU,LH,BA | |
| part of own segments | ownPart | Minimum allowed part of own flight segments (i.e. validating carrier is equal to a marketing carrier for these segments). It has to be greater than or equal to this value.
|
empty = any values |
0.88 | |
| part of interline segments | interlinePart | Minimum allowed part of interline flight segments (i.e. validating carrier is not equal to a marketing carrier for these segments). It has to be greater than or equal to this value.
|
empty = any values |
0.88 | |
| contract type | contractType | BSP or TCH system |
empty = any type, |
TCH | |
| GDS | gds | Here you can define the allowed GDS (Amadeus, Sabre, etc.), PCC or Nemo package ID for a specific pricing rule. Different types can be combined and listed in any sequence. For example, if you choose Sabre as the GDS, then there is no point to list all Sabre PCC's or packages you are going to use. |
empty = any |
SABRE,670P,123
AMADEUS,GALILEO | |
| start of selling | paymentDateFrom | Minimum allowed date of booking (it is NOT equal to the departure date). Pricing rule will be applied if current date is more or equal to the date defined in this column. | empty = any date DD.MM.YYYY |
01.01.2012
31.01.2010 | |
| end of selling | paymentDateTo | Maximum allowed date of booking. Pricing rule will be applied if current date is less or equal to the date defined in this column. | empty = any DD.MM.YYYY |
31.12.2022 | |
| flight type | airlineType | International or domestic flight (i.e. the whole flight with all transfers is within the same country. | empty = any IA (international airlines) DA (domestic airlines) |
IA DA | |
| flight numbers | flightNumber |
Allowed flight numbers, can be defined with the marketing carrier or code or without it. Acceptable values:
|
empty = any |
SU 123,SU 345 123,345 <>LH 555 | |
| aircraft type | aircraft |
Allowed aircraft codes, should be defined as returned by the GDS Acceptable values:
|
empty = any |
73C,DH4 735 | |
| fare codes | tariffs | Allowed fare codes. At least one fare from the flight must match with one of the fare codes listed in this column. There should be no matches, if you use negation in this column. Fuzzy matching is allowed: a code from the rule can be a part of the fare code from the flight (for example, value S1GREY26 from a rule will match to the S1GREY26CH from a flight).
You can also define a regular expression. All one has to do is to write this parameter as /XXX/. Examples:
|
empty = any |
WRUTH9PL,ARUTH9PL
| |
| maximum fare value | maxTariff | Limit for the maximum allowed value of the "base fare" (i.e. sum of all fares in a flight excluding airline taxes). If this value is defined, the whole pricing rule will be applied only in case if the flight fare is less or equal to this value. |
empty = any нет |
10000RUB | |
| private fare | privateFare | Pricing rule will be applied only in case if the flight fare is private (confidential). This characteristic is returned by the GDS. If a specific private fare code is already known, then this parameter is not mandatory. |
empty = any fares |
0 | |
| tax codes | taxes | Allowed airline taxes
Acceptable values:
where CODE is a sequence of uppercase latin letters. |
empty = any |
YQ,YR | |
| price is confirmed | priceIsActual | This parameter is verified by the system during the search step and after going to the checkout page. During and after a search request the flight price is considered as unconfirmed. Price is confirmed (and relevant) after making an availability check, when the user goes to an order page. |
empty = any flights |
0 | |
| validating carrier's fare is present in each flight segment | valSegmentsInTariff | System will check if there is at least one fare owned by the validating carrier in each segment. |
empty or 0 = any fares |
0 | |
| service classes | serviceClass |
Allowed service class categories
where CODE:
|
empty = any |
B,E | |
|
booking classes (letters) |
bookingClass |
Different latin letters are allowed (only one letter for each booking class).
|
empty = any |
A,B,C <>A,B,C | |
| airlines and classes | airlinesAndClasses |
Set of pairs "marketing carrier" + "booking class" for any segment of the flight route. Applicable format:
|
empty = any |
SU:A,LH:B,BA:C | |
| geo zones | zones |
Geographic zones of the flight. Pricing rull will be applied, if all segments of the flight are within one of the zones listed here. See also list of all countries and their zones
If a flight must belong to 2 zones at the same time ("EUSA, EUNA" - transatlantic flight):
|
empty = any |
AS,EU | |
| country zones | countryZones | All countries listed in this column define a specific zone for a flight, and no transfers, departures or arrivals are allowed outside this zone. | empty = any countries
CODE,CODE... |
RU,IT,DE,FR | |
| departure countries | depCountries | Allowed list of departure countries (only the first segment departure country is checked). |
empty = any countries |
RU | |
| arrival countries | arrCountries | Arrival country will be checked and compared to this column. For OW and CR flights arrival country is a last country of a last flight segment. For RT flights arrival country is the last country of the first leg. For example, for MOW-PAR-MOW flight France is the arrival (destination) country. For MOW-PAR-LON it's Great Britain. If you define FR as the arrival and departure country it doesn't mean domestic (internal) flight. Don't forget to use the flight type parameter (DA/IA). |
empty = any countries |
RU | |
| direct (non-stop flight) | isDirect | System will check if the flight has any transfers on the route. |
empty = any |
0 | |
| route type | routeType |
You can leave this column blank or define one of the following values:
|
empty = any type |
OW | |
| routes (for cities) | routeFull | Sequence of city IATA codes describing the whole flight route including all transfers, without any breaks or repeats. It's recommended to use IATA city code if it has several airports. For example, VKO-ORY,ORY-VKO flight should be written as MOW-PAR-MOW route. |
empty = any |
MOW-LON,LON-MOW | |
| parts of a route (for cities) | routePart |
Here you can describe only a part of the flight route, if the whole route doesn't matter. For example, if it's important to have a transfer in Berlin, then you just enter -BER-. |
empty = any |
-CAI- | |
| routes (for airports) | routeAirportsFull | Here you have to use only airports IATA codes (not cities). The column purpose is the same as for the "routeFull" parameter. | see description | see description | |
| parts of a route (for airports) | routeAirportsPart | Here you have to use only airports IATA codes (not cities). The column purpose is the same as for the "routePart" parameter. | see description | see description | |
| departures (airports, cities) | depAirports | Only the first segment airport is checked. Here you can list cities or airports IATA codes. |
empty = any countries |
MOW,PAR,BER <>VKO,LON | |
| arrival (airports, cities) | arrAirports | Arrival airport is defined in the same way as the "arrival country" parameter. |
empty = any countries |
MOW,PAR,BER <>VKO,LON | |
| departure date | dateBegin | First segment departure date must be more or equal to this value in the rule. | empty = ignored DD.MM.YYYY |
01.01.2012
31.01.2010 | |
| departure within (hours) | dateDepartureAfter | Maximum allowed amount of hours (or diapason) is defined here (starting from the current date). For examle, if you want to specify flights with departure in 5 days or less, then you should set a diapason [0,120]. | empty = without limits maximum value [x,x] - diapason |
13
[10,100] | |
| end of departure | dateEnd | Departure date of the first segment flight must be less than or equal to this value | empty = ignored DD.MM.YYYY |
31.12.2022 | |
| return no sooner than | dateBackBegin | Departure date of the last segment flight must be more than or equal to this value | empty = ignored DD.MM.YYYY |
31.12.2022 | |
| return no later than | dateBack | Departure date of the last segment flight must be less than or equal to this value | empty = ignored DD.MM.YYYY |
31.12.2022 | |
| flight duration (days) | daysDuration | Limit for the maximum range between the departure and arrival dates (in days). Can be defined as a diapason in brackets. Duration in days is calculated as mathematic difference between the dates. If departure and arrival are the same day, then the flight duration is equal to 0 days. |
empty = no limits |
13 | |
| days of week | dayOfWeek | Allowed days of week for the ferst segment departure date. Value is to be defined as a digit according to the day of week number (starting from Monday). | Допустимые дни недели для даты вылета первого сегмента маршрута. Значения указываются числом, соответствующим порядку дня недели, начиная с понедельника. | empty = ignored 1 - Monday |
2 |
| passenger types | passengers | Allowed passenger types for a flight. A rule will be applied only if all passenger types listed in the column are presented in a flight. |
empty = any |
INF | |
| priority | priority | If several rules are applicable for one flight, only one rule with the highest priority will be applied. If there are several rules with the same priority (or it isn't defined), then the newest rule (which is the lowest in a table) will be appllied. | integer number empty = 0 |
1 2 | |
| promoaction code | Universal promoaction coded. It's generated in the system settings panel (Loyalty program - Promoactions and promocodes). Available only if this module is activated for an agency. | any sequence of letters/digits/symbols | 12022014_Promo | ||
| utm source | utmSource | ID of the external traffic source, which is displayed in the table of traffic sources in system setting panel. Available only if the Metric module is activated for an agency. | empty = any CODE,CODE... <>CODE,CODE...(кроме) |
123,456 <>123,456 | |
| airline commission | commission | Agency's profit that will be got from the airline for selling its tickets. Mandatory parameter. This value is passed to GDS while the tickets are issued. Can be defined as & of the fare or as a flat value (per each passenger). A rule with zero commission value have a higher priority than the same rule with empty commission. |
"xxxКОД" (currency code) or "XX%" |
100RUB 13% | |
| subagency commission | agencyCommission | Part of the airline commision which can be paid by agency to its subagents. A value from this column will be applied as a discount for subagents, so the tickets will be cheaper for them. You can define IDs for specific subagents. If there is a commission defined for all subagents and also a commission defined for subagent X, then the total commission for subagent X will be calculated as a sum of these values. For example,: 5%,(123:6%), (345:8%)
|
see description |
100RUB 5%,(123:6%), (345:8%) | |
| commission per each segment | modeForSegment | Attribute will define whether the commision value should be multiplied by the total segments amount. For example, 1 EUR per each segment.
|
empty = 0 |
0 | |
| airline bonuse | bonus | Extra agency profit rewarded by the airline (it's not a commission) sometimes. It isn't involved in GDS requests. It's defined and calculated exactly the same way as the commission value. Previous parameter also can be used. The airline bonus is used in calculating the total profit amount for a specific flight. It can affect the mixer workflow and charge amount (if the "minimum profit" parameter is used). |
"xxxCODE" (currency code) or "XX%" |
100RUB 13% | |
| bonus per a segment (allowed airlines) | modeForAirlines | If this parameter is defined, then the airline bonus will be calculated for each flight segment (if the bonus is set as a flat value in currency), but only segments owned by the validating carrier or interline partners from this list will be considered. |
empty |
SU | |
| agency charge | charge | Here you're supposed to configure all the mark-ups and discounts that will be applied for a specific flight. You can specify several charge rules in the same column and divide them by passenger and/or user types. format = (subject: sum),(subject: sum),(subject: sum)...
If several charge rules are applicable in this column, then their sum will be applied. If you don't need this behaviour, you can separate charge rules in different pricing rules (lines) and rule them using priority value. |
see description |
see description | |
| extra charge | chargeExt |
This parameter helps to change the common calculation process and add some extra rules for charges (in addition to the main charge value (see the previous parameter).
|
empty = 0 |
0 | |
| minimum profit | minProfit | Minimum profit value that is guaranteed for an agency for a specific flight. If the whole calculated profit for a flight (which is equal to airline commission + mark-up + airline bonus - subagent commission) is less then a value in this column, then the agency mark-up will be automatically increased up to the needed value. Format is the same as for an agency charge. For charge calculation system will use the pricing rule that will be applied with airline commission. If you don't need this behaviour, then you should use the next parameter "minProfitPriority" (see below). | see decription | 50RUB*LEG*PAS | |
| minimum profit priority | minProfitPriority | Additional extra parameter for minimum profit calculation. A rule with the highest priority will be applied. If there are several rules with the same priority, then the rule in the lowest line will be applied. | Positive integer values. | 1, 2, ... | |
| rounding | chargeRounding | Rounding type for the mark-up value (used if mark-up is defined as %, not a flat number) | empty = 0, 0 = to the whole number, 0.1 = to decimals, 0.01 = to two decimals |
0.1 0.01 | |