The Airline can configure various brands so the display on the Flights Page identifies flights by brand and provides information about what constitutes the brand (brand benefits).

Price by Brand

Airlines can price and ticket each reservation at the specific brand/fare that was selected by the passenger, even if the system default for automated pricing is set to price the lowest fare for the RBD used (which may not be the fare requested by the passenger).

Prerequisites

The airline must have branded fares filed in the Merchandising Manager.

Highlights

1. The airline calls /products/air/search POST to obtain the list of available flights to the passenger. The airline can format the information for display to the passenger.
2. The passenger selects a flight.
3. The airline submits /products/air POST to add selected flight to the itinerary.
4. The airline prompts passenger for passenger’s details e.g. passport information.
5. The airline uses /passengers POST to add passengers to the itinerary.
6. The passenger can continue shopping by selecting seats and ancillaries, according to the airline’s shopping sequence. Product cart is updated accordingly.
7. As an optional step the airline can call /products PUT to trigger an additional re-pricing before the passenger selects the payment (on the Payment Page). This new method recalculates products prices based on given context (e.g. prices based on awardSwitchState can be recalculated between points and cash, or it can simply recalculate the price of the basket when it is based on repricing).
8. When the passenger indicates that shopping is complete the airline obtains available payment options for the current itinerary by calling /paymentOptions GET. The airline can format the information for display to the passenger.
9. When the passenger selects the form of payment, completes the payment and decides to purchase, the airline initiates the purchase and ticketing process by calling /purchase POST; if authorization is successful, the /purchase service will create a PNR, EMD(s), etc.
10. The response indicates whether the purchase is successful. The airline formats this information for display to the passenger.
11. The passenger specifies a PNR for review.
12. The Airline submits a /pnr GET request. The Airline can format the information for display to the passenger.

AER Ticket Exchange by Brand

This feature is available to airlines which use Price by Brand concept of filing fares (which simplifies relation between RBD and brands mapping, allowing the airline to brand RBD to certain fare basis for certain brands). This is an extension of the mentioned project for exchange path.

Prerequisites

• Fares have to be filed with accordance to the Price by Brand concept,
• RBD vs Brand mapping has to be also set up according to Price by Brand concept.

Highlights

1. The passenger retrieves a booking either by supplying basic PNR information or by logging in to the passenger’s account.
2. The airline identifies a PNR, retrieves the information and formats it for display to the passenger. If the PNR is found, all the flight details are returned, including the payment details, such as forms of payment used.
3. After the passenger selects flight to be exchanged, the airline calls pnr/exchange request GET to initialize an Exchange process.
4. The airline obtains search criteria from the passenger and calls /pnr/exchange/products/air/search POST to get a list of flights matching the search criteria.
   The airline can format the information for display to the passenger.
5. The passenger selects a flight.
6. The airline submits /pnr/exchange/products/air POST to add selected flight to the itinerary.
7. After checking the re-association criteria, the airline uses /pnr/exchange/products/ancillaries operations to obtain the ancillaries available on the flights they have exchanged and to add any ancillaries selected by the passenger to the itinerary.
8. The airline uses /pnr/exchange/products/seats operations to show passengers the seats available on the flights they have exchanged and to add any seats selected by the passenger to the itinerary.
9. After the passenger has completed exchange process with changing the itinerary in the session (including exchange process for the ancillaries and seats) the airline obtains available payment options for the current itinerary by calling /pnr/exchange/paymentOptions GET.
   The airline can format the information for display to the passenger.
10. When the passenger selects the form of payment, completes the payment and decides to purchase, the airline initiates the purchase and ticketing process by calling /pnr/exchange/purchase POST; if authorization is successful, the /purchase service will create a PNR, EMD(s), etc.
11. The response indicates whether the purchase is successful.
    The airline formats this information for display to the passenger.