The services that provide the ability to obtain and display the ancillaries available for passenger-selected flights and process passenger selections of ancillaries have the following additions and enhancements:

• Airline determines whether a promotion applies, and if so, needs to use a specific custom SSR to drive the discount in the ancillaries and/or seats request.
  • SSR driven discounts for ancillaries and seats.
    Airline is able to send a special request SSR in the products/ancillary service (enhance ancillary contract to accept SSR in products/ancillaries and enhance products/seats contract to accept SSR for seats).
  • Rule ID exposure in the response.
    GET /products/ancillaries response includes rule ID coming back from the Dynamic Retailer.
  • Shopping cart update to display original and discounted amount.
    Once discounted ancillary or seat is added to the shopping cart, Digital Connect provides original amount and discounted amount in /products service.

This solution does not apply to exchange and post-booking path.

Airline can add the SSRs and/or remarks to the PNR by using PNR utility in the Purchase Request. See also the PNR Remarks section for related functionality.

Highlights:

Airlines can drive discounts for ancillaries with the following sequence of Digital Connect service calls:

The airlines defines the required SSR code as part of the OC record.

1. The passenger shops for flights and builds an itinerary.
2. The airline calls /products/ancillaries GET to obtain list of ancillaries available for the currently selected itinerary.
3. The passenger includes one or more promotional codes, which are passed to /products/ancillaries as query parameters.

   The airline provides SSR codes (promoSSRs) in GET /products/ancillaries to to obtain possible discounts for ancillaries (possible discounts are based on different factors, like tier level).
   The airline formats information about available ancillaries for display to the passenger.

4. When the passenger selects ancillaries, the airline calls POST /products/ancillaries to add any ancillary products selected by the passenger to the itinerary; the information passed includes information about the SSRs used for the promotional code ancillaries and text descriptions of these ancillaries.
5. The airline calls /products/seats GET to obtain seat map for the currently selected itinerary.
6. The passenger includes one or more promotional codes, which are passed to /products/seats as query parameters.

   The airline provides SSR codes (promoSSRs) in GET /products/seats to obtain possible discounts for seats (possible discounts are based on different factors, like tier level).
   The airline formats information about available seats for display to the passenger.

7. When the passenger selects seats, the airline calls POST /products/seats to add seats selected by the passenger to the itinerary; the information passed includes information about the SSRs used for the promotional code ancillaries and text descriptions of these ancillaries.
8. The airline can call /products GET operation to obtain a current list, with prices of products that the passenger has added to the itinerary and use this information to build and display a shopping cart. The response for the ancillaries and seats will include breakdown of original amount,discount and discount amount.
9. When the passenger is ready to purchase the itinerary, the airline adds field values for all applicable remarks, SSRs, and OSIs to the /purchase POST request.
10. The airline initiates the purchase and ticketing process by calling /purchase POST ; if authorization is successful, the /purchase service creates a PNR, EMD(s), etc. EMDs are be issued with discounted values.
11. The response indicates whether the purchase is successful.

    The airline formats this information for display to the passenger.

12. The airlines submits a /pnr GET request; the results include remarks.

    The airline can format the information for display to the passenger.

Support Dynamic Retailer with Special Service Requests for Discounting Ancillaries in the Post Booking Flows for Manage Your Booking – Modify Trip Options (MYB:MTO) Flow and Manage Your Booking – Change Itinerary (MYB:CI) Flow

Airlines can pass promotional codes to Ancillaries service in the Post Booking flows, and those services will obtain the information needed to sell and issue documents for the promoted ancillaries from ATPCO OC records. Note that the ancillary promotions must be previously set up with ATPCO.

If the Ancillaries request includes promotional codes, the Ancillaries services are able to obtain applicable information, including SSR codes, from the ATPCO OC record, and return it as part of the pricing response. If the passenger selects and purchases on of these ancillaries, the SSR codes will be added into the AE field as part of the AE creation process.

Airline determines whether a promotion applies and if so, needs to use a specific custom SSR to drive the discount in the ancillaries request.

• SSR driven discounts for ancillaries. An enhancement in the /pnr/mto/ancillaries, /pnr/exchange/ancillaries contract to accept SSRs for ancillaries.
• Rule ID exposure in the response. GET /pnr/mto/products/ancillaries and /pnr/exchange/products/ancillaries response will include rule ID coming back from the Dynamic Retailer.
• Shopping cart update to display original and discounted amount.
  Once discounted ancillary is added to the shopping cart, Digital Connect provides original amount and discounted amount in /pnr/mto/products and /pnr/exchange/products services.

Airline can add the SSRs and/or remarks to the PNR by using PNR utility in the Purchase Request. See also the PNR Remarks section for related functionality.

Highlights:

Airlines can drive discounts for ancillaries with the following sequence of Digital Connect service calls (an example flow of the services for Manage Your Booking – Change Itinerary (MYB:CI) Flow):

1. The passenger retrieves a booking either by supplying basic PNR information or by logging in to a Frequent Flyer account. If the passenger is logged in, all their reservations are visible.
   Airlines can prompt passengers for information that identifies a PNR, retrieve the information and format it for display to the passenger.
2. The /pnr/exchange service GET operation returns information for the PNR specified in the parameters and initializes Exchange process.
3. The airline obtains search criteria from the passenger and submits a /pnr/exchange/products/air/search request, POST operation to get a list of flights matching the search criteria. Display the returned flights to the passenger.
4. After the passenger selects one or more flights, the airline submits the /pnr/exchange/products/air POST operation to add the flights to the itinerary and store the itinerary in the session.
5. After checking the re-association criteria, the airline uses /pnr/exchange /products/ancillaries operations to show passengers the ancillaries available on the flights they have exchanged and to add any ancillaries selected by the passenger to the itinerary.
6. The airline provides also SSR codes (promoSSRs) in GET /pnr/exchange/products/ancillaries to obtain possible discounts for ancillaries (possible discounts are based on different factors, like tier level).
7. When the passenger selects ancillaries, the airline calls POST /pnr/exchange/products/ancillaries to add any ancillary products selected by the passenger to the itinerary.
8. The airline can call /pnr/exchange/products GET operation to obtain a current list, with prices of products that the passenger has added to the itinerary and use this information to build and display a shopping cart. The response for the ancillaries and seats includes breakdown of original amount, discount and discount amount.
9. When the passenger is ready to purchase the itinerary, the airline adds field values for all applicable remarks, SSRs, and OSIs to the /pn/exchange/purchase POST request.
10. The airline initiates the purchase and ticketing process by calling /pnr/exchange/purchase POST ; if authorization is successful, the /pnr/exchange/purchase service will create a PNR, EMD(s), etc. EMDs will be issued with discounted values.
11. The response indicates whether the purchase is successful.
     

    The airline formats this information for display to the passenger.

12. The airline submits a /pnr/exchange GET request; the results include remarks.
     

    The airline can format the information for display to the passenger.

Dynamic Retailer Promotions for the Redemption - Ancillaries and Seats

Airlines create promotions to increase sale and acquire new customers. By discounting their extra services airlines encourage people to buy more and therefore create higher revenue.

Digital Connect includes an option to offer ancillaries and/or seats discounts also in the Redemption Flow (RBE) and to pay for ancillaries and/or seats discounts with loyalty points/miles in the Revenue Booking Flow (B2C), the Manage Your Booking – Modify Trip Options (MYB: MTO) and the Manage Your Booking – Change Itinerary Flow (MYB: CI). This is an extension of existing in the Revenue flow ancillaries and seats promotions supported via Dynamic Retailer.

With this feature the Frequent Flyer users are able to use their accrued loyalty points/miles to purchase discounted ancillaries and seats.

Prerequisites:

• Dynamic Retailer needs to be activated.
• Dynamic Retailer Ancillaries/Seats Promotions has to be configured.
• Loyalty Exchanges needs to be activated, points should be enable as a Form of Payment for Booking Flow (B2C) and for the Manage Your Booking – Modify Trip Options Flow (MYB: MTO).

Limitations:

• In the Manage Your Booking – Change Itinerary Flow (MYB: CI) supported via Loyalty Exchanges below conditions have to be met:
  • The original VCR paid by points or combination of cash and points.
  • No ancillaries or ancillaries paid by cash in the original booking.
• Digital Connect only allows adding seats in the new Exchange flow, there will be no option to add ancillaries.
• As there is no passenger indicator in /pnr/exchange/products service Digital Connect is not able to provide correct discount amount in the exchange flow if there are different discounts per passenger.

Highlights:

Generally the flow of services is the same as in case of standard RBE Flow, Points in the Revenue Flow (B2C), Points in the Post booking flows: The Manage Your Booking – Modify Trip Options (MYB: MTO) and Manage Your Booking – Change Itinerary Flow (MYB: CI). The only addition is the handling of ancillaries/seats discounts which now can be presented in points in appropriate services (like GET /products/ancillaries, GET /products/seats, GET /products, etc.).