Skip to main content

Airport: boarding pass

To comply with airport and tax(-free) regulations, EVA allows for the uploading of flight data and to scan and match boarding passes to those flights.


The chapter is hidden if the inquiring user does not have a permission called "Flights" and a scope View. Permissions are managed from the Roles and rights chapter namely, from the functionalities card of a users role.


To enable the Flights functionality in your environment, configure the following setting and App setting:

  • Set BoardingPass:Required to true on the appropriate airport OU.
  • Set App:OrganizationUnit:AirportOU to true on the appropriate airport OU.

By toggling BoardingPass:Required to true, you will be returned a boarding pass order requirement. This will be false (and thus impede you from completing your order) until you have called the AddBoardingPassToOrder service with a successful outcome - the order requirement will become true and you can finish your order.

Uploading flights

Uploading flights is done best by uploading a flights file in the Flights tab of the airport OU (after configuration above). This tab also includes a template file to show you how the information should be formatted.

You can also upload via the ImportFlights service directly.

Either way, the following information can be included in the file:

  • OU ID
  • Airline code
  • Flightnumber
  • FromDate
  • ToDate
  • DestinationAirport
  • DestinationCode

Although all this information is stored, not all properties are actually used for validation when scanning a boarding pass: the two Date properties are included and displayed in-store for informative purposes only.

Note that if you try to import known flights (combination already exists), EVA will overwrite the destination code.


When actively matching flights to boarding passes with in-store scanning, the validation that takes place requires the OU ID to be the OU where the boarding pass is scanned and the AirlineCode, FlightNumber and DestinationAirport have to match the boarding pass.

If the boarding pass matches a stored flight, it will be attached to the order like so:

FlightInfo: {
"DepartingAirportCode": "STN",
"DestinationAirportCode": "LAS",
"FlightNumber": 2345,
"AirlineCode": "UES",
"OperatingCarrierPnrCode": "SD 2986"

Services used for scanning

Barcode scanning makes use of the following services:

  • The standard ParseBarcode service. When scanning, this service classifies the barcode as a 'Boardingpass' barcode type. The boarding pass barcode handler then converts the barcode into information usable by the employee (e.g. flight number).
  • Simultaneously, the service AddBoardingPassToOrder adds the scanned barcode to the currently active order.

You can optionally use the service GetBoardingPass to enter the OrderID and get the corresponding data of the boarding pass barcode handler returned to you once more.

In case of errors

In case you run into an error, it may be one of the following:

  • AddBoardingPassToOrder.FormatInvalid
    This error means that the format of the barcode did not match the format required to add a boarding pass to an order. Verify that you used ParseBarcode correctly.

  • AddBoardingPassToOrder.InvalidFlight
    This means that although the boarding pass was parsed and the format is correct, the resulting data indicates the boarding pass is invalid for this airport.