GDS Remarks — Order & booking control
Remarks that route, assign and control orders, customers and PNRs.
Customer ID
Used to uniquely recognize the order's customer. It is the customer's id from the Midoco Midoffice CRM (its value is a positive integer).
AMADEUS
- Provided as AP information in the I- segment
I-002;[dd]TEST/JENS MR;;TEST.JENS
<A7>TEST.COM+49 TEST BUCHUNG//CUSTOMER_ID: 76//JENS_TEST<A7>TEST.COMTEST BUCHUNG ;;
- Provided as remark
RM*CUSTOMER_ID:76
RM*MIDOCO_CUSTOMER_ID:76
Travelport
Remark Entry in Travelport to transmit the Midoco Customer ID 76
- DI.FT-CUSTOMER-ID76
- A14FT-CUSTOMER-ID76
- A15FT-CUSTOMER-ID76
SABRE
- 5.CUSTOMER*ID-76
Customer Debtor
Used to uniquely recognize the booking's customer by his/her debtor (financial account assigned to a customer - an positive integer). The debtor number is maintained/assigned in the Midoco Midoffice CRM.
AMADEUS
- RM*[.*]VERK+:KD-NR:100001
- RM*[.*]SYS+:KD-NR:100001
Travelport
Remark Entry in Travelport to transmit the Midoco Customer Account ID 100001
- DI.FT-VERK:KD-NR:100001
- A14FT-VERK:KD-NR:100001
- A15FT-VERK:KD-NR:100001
SABRE
- Agent Input: 5.KDNR-100001
- IUR result: M8KDNR-100001
Customer Name and Address
You can create or match an order customer using VERK resp. SYS remarks. Please stick to one set of remarks (either VERK or SYS, pls. do not mix them up).
These remarks may contain one or more key-value pairs separated by ‚&‘.
The required key is NAME2 for a company resp. NAME for a private person.
The available keys are:
- NAME: depends on use case, pls. check examples below
- NAME2: depends on use case, pls. check examples below
- STR: Street and no.
- PLZ: Postal code
- ORT: city
The exact VERK resp. SYS remark prefix is dependent on the external system:
- AMADEUS: VERK+: resp. RM*SYS+:
- Travelport: FT-VERK: resp. FT-SYS:
- SABRE: VERK* resp. SYS*
The key-value separator also depends on the external system:
- AMADEUS: „:“
- Travelport: „:“
- SABRE: „-“
AMADEUS
Companies with contact person
- Organisation name – RM*VERK+:NAME:[.*] or RM*SYS+:NAME:[.*]
- Contact person – &NAME2:[.*] or RM*VERK+:NAME2:[.*] or RM*SYS+:NAME2:[.*]
- City – &ORT:[.*] or RM*VERK+:ORT:[.*] or RM*SYS+:ORT:[.*]
- Postal code – &PLZ:{[..]-}[.*] or RM*VERK+:PLZ:{[..]-}[.*] or RM*SYS+:PLZ:{[..]-}[.*]
- It has the format country_code-postal_code. The country_code is the ISO 2-letter country code and it is optional. Default country_code value is DE also if left blank.
- Street and street number – &STR:[.*] or RM*VERK+:STR:[.*]or RM*SYS+:STR:[.*]
All the information in one remark:
- RM*VERK+:NAME:TEST FIRM LTD&NAME2:MRS SAMANTHA TEST&ORT:TESTCITY&PLZ:DE-51373&STR:TEST STREET 10
or as individual remarks:
- RM*VERK+:NAME:TEST FIRM LTD or RM*SYS+:NAME:TEST FIRM LTD
- RM*VERK+:NAME2:MRS SAMANTHA TEST or RM*SYS+:NAME2:MRS SAMANTHA TEST
- RM*VERK+:ORT:TESTCITY or RM*SYS+:ORT:TESTCITY
- RM*VERK+:PLZ:DE-51373 or RM*SYS+:PLZ:DE-51373
- RM*VERK+:STR:TEST STREET 10 or RM*SYS+:STR:TEST STREET 10
Companies without Contact Person
- Organisation name: RM*VERK+:NAME2:[.*] or RM*SYS+:NAME2:[.*]
- City: &CITY:[.*] or RM*VERK+:CITY:[.*] or RM*SYS+:CITY:[.*]
- Postal code: &PLZ:{[..]-}[.*] or RM*VERK+:PLZ:{[..]-}[.*] or RM*SYS+:PLZ:{[..]-}[.*]
- It has the format country_code-postal_code. The country_code is the ISO 2-letter country code and it is optional. Default country_code value is DE also if left blank.
- Street and street number: &STR:[.*] or RM*VERK+:STR:[.*]or RM*SYS+:STR:[.*]
All the information in one remark:
- RM*VERK+:NAME2:TEST FIRM LTD&ORT:TESTCITY&PLZ:DE-51373&STR:TEST STREET 10
or as individual remarks:
- RM*VERK+:NAME2:TEST FIRM LTD or RM*SYS+:NAME2:TEST FIRM LTD
- RM*VERK+:ORT:TESTCITY or RM*SYS+:ORT:TESTCITY
- RM*VERK+:PLZ:DE-51373 or RM*SYS+:PLZ:DE-51373
- RM*VERK+:STR:TEST STREET 10 or RM*SYS+:STR:TEST STREET 10
Private Person
- Person name: RM*VERK+:NAME:[SALUTATION] FORENAME LASTNAME or RM*SYS+:NAME:[SALUTATION] NAME FORENAME
- City: &CITY:[.*] or RM*VERK+:CITY:[.*] or RM*SYS+:CITY:[.*]
- Postal code: &PLZ:{[..]-}[.*] or RM*VERK+:PLZ:{[..]-}[.*] or RM*SYS+:PLZ:{[..]-}[.*]
- It has the format country_code-postal_code. The country_code is the ISO country code and it is optional. Default country_code value is DE.
- Street and street number: &STR:[.*] or RM*VERK+:STR:[.*]or RM*VSYS+:STR:[.*]
All the information in one remark:
- RM*VERK+:NAME:MRS SAMANTHA TEST&ORT:TESTCITY&PLZ:DE-51373&STR:TEST STREET 10
or as individual remarks:
- RM*VERK+:NAME:MRS SAMANTHA TEST or RM*SYS+:NAME:MRS SAMANTHA TEST
- RM*VERK+:ORT:TESTCITY or RM*SYS+:ORT:TESTCITY
- RM*VERK+:PLZ:DE-51373 or RM*SYS+:PLZ:DE-51373
- RM*VERK+:STR:TEST STREET 10 or RM*SYS+:STR:TEST STREET 10
Travelport
The remarks from A14 and A15 segments are considered. The examples show only one prefix.
Company with Contact Person
Information combined in one remark:
- DI.FT-VERK:NAME:TEST FIRM LTD&NAME2:MRS SAMANTHA TEST
- A14FT-VERK:NAME:TEST FIRM LTD&NAME2:MRS SAMANTHA TEST
or as individual remarks:
- DI.FT-VERK:NAME:TEST FIRM LTD
- DI.FT-VERK:NAME2:MRS SAMANTHA TEST
- DI.FT-VERK:ORT:TESTCITY
- DI.FT-VERK:PLZ:DE-51373
- DI.FT-VERK:STR:TEST STREET 10
- A14FT-VERK:NAME:TEST FIRM LTD
- A14FT-VERK:NAME2:MRS SAMANTHA TEST
- A14FT-VERK:ORT:TESTCITY
- A14FT-VERK:PLZ:DE-51373
- A14FT-VERK:STR:TEST STREET 10
Company without Contact Person
All the information in one remark:
- A14FT-VERK:NAME2:TEST FIRM LTD&ORT:TESTCITY&PLZ:DE-51373&STR:TEST STREET 10
or as individual remarks:
- A14FT-VERK:NAME2:TEST FIRM LTD
- A14FT-VERK:ORT:TESTCITY
- A14FT-VERK:PLZ:DE-51373
- A14FT-VERK:STR:TEST STREET 10
Private Person
All the information in one remark:
- A14FT-VERK:NAME:MRS SAMANTHA TEST&ORT:TESTCITY&PLZ:DE-51373&STR:TEST STREET 10
or as individual remarks:
- A14FT-VERK:NAME:MRS SAMANTHA TEST
- A14FT-VERK:ORT:TESTCITY
- A14FT-VERK:PLZ:DE-51373
- A14FT-VERK:STR:TEST STREET 10
SABRE
The remarks from M7, M8 and M9 segments are considered. The examples show only one prefix.
Company with Contact Person
All the information in one remark - Sabre has got a restriction to the number of chars in a remark which is 64 chars, so this remark might not work in Sabre - please use the individual remarks.
- M7[dd]VERK*NAME-TEST FIRM LTD&NAME2-MRS SAMANTHA TEST&ORT-TESTCITY&PLZ-DE-51373&STR-TEST STREET 10
or as individual remarks:
- M7[dd]VERK*NAME-TEST FIRM LTD
- M7[dd]VERK*NAME2-MRS SAMANTHA TEST
- M7[dd]VERK*ORT-TESTCITY
- M7[dd]VERK*PLZ-DE-51373
- M7[dd]VERK*STR-TEST STREET 10
Company without Contact Person
All the information in one remark:
- M7[dd]VERK*NAME2-TEST FIRM LTD&ORT-TESTCITY&PLZ-DE-51373&STR-TEST STREET 10
or as individual remarks:
- M7[dd]VERK*NAME2-TEST FIRM LTD
- M7[dd]VERK*ORT-TESTCITY
- M7[dd]VERK*PLZ-DE-51373
- M7[dd]VERK*STR-TEST STREET 10
Private Person
All the information in one remark:
- M7[dd]VERK*NAME-MRS SAMANTHA TEST&ORT-TESTCITY&PLZ-DE-51373&STR-TEST STREET 10
or as individual remarks:
- M7[dd]VERK*NAME-MRS SAMANTHA TEST
- M7[dd]VERK*ORT-TESTCITY
- M7[dd]VERK*PLZ-DE-51373
- M7[dd]VERK*STR-TEST STREET 10
Order Related Remarks
Order Number – import in an Existing Order
It is used to uniquely recognize the order by its id (an positive integer). The booking will be imported to the order with the given order number.
AMADEUS
- RM*AUFTRAG:123456
Travelport
Remark Entry in Travelport to transmit the Midoco Order Number 123456
- DI.FT-AUFTRAG123456
- A14.FT-AUFTRAG123456
- A15.FT-AUFTRAG123456
SABRE
- M7[dd]5.AUFTRAG-123456
- M8[dd]5.AUFTRAG-123456
- M9[dd]5.AUFTRAG-123456
Push PNR into Specific OrgUnit
when a RM*ORGA is found, the org unit specified there is checked to be included in the entire Midoco-System.
Umlauts will be mapped while importing the message
AMADEUS
RM*ORGA unit name
RM*ORGA A +B
RM*ORGA ALPHA & OMEGA
Travelport
- DI.FT-ORGA:unit name
- RI.FT-ORGA:unit name
- A14FT-ORGA:unit name
- A15FT-ORGA:unit name
SABRE
- M7[dd]ORGA-unit name
- M8[dd]ORGA-unit name
- M9[dd]ORGA-unit name
Push a PNR into an existing order with same TRIP ID
From Midoco Release 20.2 you can force linked PNRs into the same Midoco Order by using the linking parameter Trip ID.
This Trip ID is stored as an order attribute. To make the value visible in the order, please create an order attribute "TRIP_ID_FROM_REMARK" in the master data of the organizational unit. The localization of the attribute is up to you.
When an item exists in Midoco having been imported with the Trip ID remark and e.g. 2 days later another PNR arrives having the same Trip ID, this new PNR´s items are added to the existing order for this Trip ID.
AMADEUS
- RM*TRIPID-[Trip ID]
- RM*TRIPID-A1B2D3
SABRE
- 5.TRIPID-[Trip ID]
Travelport
- DI.FT-TRIPID-[Trip ID]
Set Broker ID in the Order
Using the VNR (DE:Vermittler Nummer / EN: Broker ID) remark, you can set the broker id of the order.
AMADEUS
RM*VNR:M1234
Travelport
The segments A14 and A15 are respected.
A14FT-VNR:M1234
SABRE
The segments M7, M8 and M9 are respected.
M7[dd]VNR-M1234
Find a Booking with a Reference Filekey
Example: If Farelogix imports a booking and Amadeus wants an update of the already imported booking but uses a different filekey, then it is needed to add this remark with the existing filekey for the booking to find and update it.
AMADEUS
- RM*FILEKEY_REF:filekey
Saving Remarks
These remarks provide saving information in ticket detailsin an order. Segment association of the savings information is mandatory.
AMADEUS
- RM*LF-nnn.nn/HF-nnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X
- example: RM*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S3
- example: RM*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S2-3
- example: RM*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S1,3
Die Ausgabe im AIR sieht wie folgt aus:
- example: RM*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH;S3
Explanations:
LF = Lowest Fare
HF = Highest Fare
RC = Reasoncode 1
RC2 = Reasoncode 2
HC = Tarif Code / Fare Code
ALF = Airline Lowest Fare
Travelport
- DI.FT-LF-nnn.nn/HF-nnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X
Die Ausgabe im MIR sieht wie folgt aus:
- A14FT-LF-nnn.nn/HF-nnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X
- example: A14FT-LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S3
- example: A14FT-LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S2-3
- example: A14FT-LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S1,3
SABRE
- M7[dd]LF-nnn.nn/HF-nnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X
- M8[dd]LF-nnn.nn/HF-nnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X
- M9[dd]LF-nnn.nn/HF-nnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X
- example: M7*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S3
- example: M7*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S2-3
- example: M7*LF-100.00/HF-500.00/RC-AB/RC2-CD/HC-EF/ALF-LH/S1,3
Please get in contact with our Midoco Helpdesk to get this functionality. Please let us know, if you require custom made remark syntax here.
Savings Currency
From Release 20.1 (29.04.2026) an optional currency code can be added to the savings remark prefixing the low/high fare values.
When applying the currency code, please make sure you apply it both to HF and LF.
AMADEUS
- RM*LF-USDnnn.nn/HF-USDnnn.nn/RC-XX/RC2-XX/HC-XX/ALF-XX/Sx
Travelport
- DI.FT-LF-USDnnn.nn/HF-USDnnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X/Sx
Sabre Example
- M7[dd]LF-USDnnn.nn/HF-USDnnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X/Sx
- M8[dd]LF-USDnnn.nn/HF-USDnnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X/Sx
- M9[dd]LF-USDnnn.nn/HF-USDnnn.nn/RC-XX/RC2-XX/HC-XX/ALF-X/Sx
Additional Source System
It is possible to transfer an additional source system to Midoco, which is shown in sell item in CRS.
AMADEUS
- RM*SOURCE_EXT_SYSTEM:
FARELOGIX
- RM*SOURCE_EXT_SYSTEM:
Travelport
- A14FT-SOURCE-EXT-SYSTEM:
- A15FT-SOURCE-EXT-SYSTEM:
SABRE
- M7[dd]SOURCE-EXT-SYSTEM-
- M8[dd]SOURCE-EXT-SYSTEM-
- M9[dd]SOURCE-EXT-SYSTEM-
In CRS you will see first the original booking system / the source system, e.g Amadeus/Cytric.
If a source system is already send via booking message, e.g for Atriis and Bridge-It the remark will be ignored
Individual (Order or Item) Attributes
NOTES:
- The separator is ":". Only for SABRE, the separator is "-".
- In the currently documented form the Remark will be put to each item in an order. (Behaviour will be changed with GLOBAL-602 - Individual sell_item attributes from remarks/GDS Geschlossen )
- functionality extended to recognize assignment of segment or ticket with release 14.1
- segment assigment needs to be present when the attribute is set up as sell item attribute in Midoco Midoffice
AMA AIR:
- RM*MIDATTR:ATTRNAME:ATTRVALUE/Sx-y (segment relation)
- example: RM*MIDATTR:udf_20:hello world/S2,5
- Output in AIR: RM*MIDATTR:UDF_20:HELLO WORLD;S2,5
- RM*MIDATTR:ATTRNAME:ATTRVALUE/Tn (ticket relation)
- example: RM*MIDATTR:FIRMENEIGENECC:VI1/T220-3371873153
- Output in AIR: RM*MIDATTR:FIRMENEIGENECC:VI1;T220-3371873153
Sabre IUR:
- 5.MIDATTR-ATTRNAME-ATTRVALUE/Sx-y (segment relation)
- example: 5.MIDATTR-udf_20-hello world/S2,5
- Output in IUR: M8[dd]MIDATTR-UDF_20-HELLO WORLD/S2,5
- 5.MIDATTR-ATTRNAME-ATTRVALUE/Tn (ticket relation)
- example: 5.MIDATTR-udf_20-hello world/T220-3371873153
- Output in IUR: M8[dd]MIDATTR-UDF_20-HELLO WORLD/T220-3371873153
Note: working with M7, M8, M9 sections.
Travelport MIR:
- DI.FT-MIDATTR:ATTRNAME:ATTRVALUE/Sx-y (segment relation)
- example: DI.FT-MIDATTR:udf20:hello world/S2,5
- Output in MIR: A14FT-MIDATTR:UDF20:HELLO WORLD/S2,5
- example: DI.FT-MIDATTR:udf20:hello world/S2,5
- DI.FT-MIDATTR:ATTRNAME:ATTRVALUE/Tn (ticket relation)
- example: DI.FT-MIDATTR:udf20:hello world/T220-3371873153
- Output in MIR: A14FT-MIDATTR:UDF20:HELLO WORLD/T220-3371873153
This remark also works on order level → in this case it needs to come without ticket or segment relation.
Fee Related Remarks
Booking Channel
Additional information for a booking. It will be parsed and saved (optionally via a rule) into the BOOKING_CHANNEL sell_item_attribute.
The information is saved for every item which is created during the import (no segment relation is needed)
Phone
AMADEUS
- RM*[.*]TAF+:TEL
Travelport
- DI.FT-TAF:TEL
- A14[.*]TAF:TEL
- A15[.*]TAF:TEL
SABRE
- M7[dd]TAF*TEL
- M8[dd]TAF*TEL
- M9[dd]TAF*TEL
Fax
AMADEUS
- RM*[.*]TAF+:FAX
Travelport
- DI.FT-TAF:FAX
- A14[.*]TAF:FAX
- A15[.*]TAF:FAX
SABRE
- M7[dd]TAF*FAX
- M8[dd]TAF*FAX
- M9[dd]TAF*FAX
AMADEUS
- RM*[.*]TAF+:EML
Travelport
- DI.FT-TAF:EML
- A14[.*]TAF:EML
- A15[.*]TAF:EML
SABRE
- M7[dd]TAF*EML
- M8[dd]TAF*EML
- M9[dd]TAF*EML
Personal
AMADEUS
- RM*[.*]TAF+:PERS
Travelport
- DI.FT-TAF:PERS
- A14[.*]TAF:PERS
- A15[.*]TAF:PERS
SABRE
- M7[dd]TAF*PERS
- M8[dd]TAF*PERS
- M9[dd]TAF*PERS
IBE (Online/Offline)
It is saved as an order attribute with the attribute name = ONLINE_OFFLINE.
AMADEUS
- RM*[.*]TAF+:IBE
Travelport
- DI.FT-TAF:IBE
- A14[.*]TAF:IBE
- A15[.*]TAF:IBE
SABRE
- M7[dd]TAF*IBE
- M8[dd]TAF*IBE
- M9[dd]TAF*IBE