Modifying and Cancelling Paid Seating Optional Services
When a Paid Seat Optional Service is initially purchased, the PNR is imported from the carrier host system and a Universal Record (UR) is created or updated. The UR contains an OptionalService element which details the purchase. Data in the OptionalService includes the:
- Type of service, i.e., PreReservedSeatAssignement.
- Amount paid.
- Create Date when the service was purchased (depending on the supplier).
- Status
- Service Data with seat assignment.
- Remark or Description (if sent in the request).
Certain types of modifications are supported for Merchandising paid seats. The types of modifications available vary by supplier.
To modify a paid seat, the Merchandising flow is followed. At Air Merchandising Fulfillment, the old seat is cancelled and the new seat confirmed.
Important! Universal API requires Form of Payment data for API Carriers, such as DL, to fulfill the updated seat request.
API and LCC CarriersTo exchange paid seats, repeat the Merchandising process for the new paid seat. The carrier will automatically cancel the first paid seat so a cancellation request is not required.
Depending on the carrier and the type of paid seat that is modified, the same EMD number may be returned. For example, DL returns the same EMD number if a seat is modified to a new seat that is the same price. If the seat is a different price, then a new EMD number is returned.
United Airlines :
- If the original seat is less expensive than the new seat, a new EMD is created by UA, and the original seat purchase is refunded automatically by UA at the time of the modify. The refund does not display when the Universal Record is retrieved, but the new seat price does, signaling that the new charge and the refund were successful.
- If an attempt is made to modify existing paid seating in any currency other than the original booking currency (USD), a warning is returned in the Seat Map response and an error is returned in the Air Merchandising Fulfillment response. The fulfillment is not completed in such cases.
Universal Record and UR History
The cancelled paid seat OptionalService is deleted from the Universal Record, and the OptionalService is not returned with @ServiceStatus=”Canceled” in the Air Merchandising Fulfillment response.
The deleted Optional Service is moved to UR History regardless of schema version.
If a paid seat Optional Service is modified in AirMerchandisingFulfillment, the old OptionalService is deleted from the UR and not returned in the response.
ATPCO CarriersTo exchange paid seats, repeat the Merchandising process for the new paid seat. The carrier will automatically cancel the first paid seat so a cancellation request is not required.
Exchange of paid seats are considered an exchange of an EMD. The client application is responsible for determining the charges associated with any changes in payment. Only even exchanges are supported; extra costs are not refundable if the second paid seat has a lower charge than the first seat.
To exchange one standard seat for another, repeat the Merchandising process for the new standard seat, making sure the new seat is in the AirMerchandisingFulfillmentReq in SpecificSeatAssignment.
Universal API checks the request for both an OptionalService as well as a SpecificSeatAssignment, and to determine if the requested seat is available.
API and LCC CarriersBecause a seat already exists for the traveler on the flight, Universal API cancels the existing seat and adds the new seat from the Fulfillment request. AirMerchandisingFulfillmentRsp returns AirSeatAssignment with the new seat.
ATPCO CarriersTo exchange one standard seat for another, repeat the Merchandising process for the new standard seat. Universal API checks the request for both an OptionalService as well as a SpecificSeatAssignment.
Make sure the new seat is in the AirMerchandisingFulfillmentReq in SpecificSeatAssignment
Universal API sends the new seat to the provider, which confirms the new seat and cancels the old seat. AirMerchandisingFulfillmentRsp returns AirSeatAssignment with the new seat.
To exchange one paid seat for a standard seat, repeat the Merchandising process for the new standard seat, making sure the new seat is in the AirMerchandisingFulfillmentReq in SpecificSeatAssignment.
Universal API checks the request for both an OptionalService as well as a SpecificSeatAssignment, and to determine if the requested seat is available.
API and LCC CarriersBecause a seat already exists for the traveler on the flight, Universal API cancels the existing seat and adds the new seat from the Fulfillment request. The AirMerchandisingFulfillmentRsp returns AirSeatAssignment with the new seat.
Because an Optional Service already exists for the traveler on the flight, Universal API maps the existing Optional Service.
AirMerchandisingFulfillmentRsp returns:
- AirSeatAssignment with the new seat.
- OptionalService with Status=”Cancelled” and old seat number.
- OptionalService with Status=”Confirmed” and new seat number.
Universal Record and UR History
The cancelled paid seat OptionalService is deleted from the Universal Record, and the OptionalService is not returned with @ServiceStatus=”Canceled” in the Air Merchandising Fulfillment response.
The deleted Optional Service is moved to UR History regardless of schema version.
ATPCO CarriersUniversal API sends the provider the ASVC SSR of the old seat. The provider cancels the old seat and confirms the new seat.
AirMerchandisingFulfillmentRsp returns:
- AirSeatAssignment with the new seat.
Note that OptionalService is not returned because the old Optional Service is deleted.
To exchange one standard seat for a paid seat, repeat the Merchandising process for the new paid seat, making sure the new seat is in the AirMerchandisingFulfillmentReq in OptionalService.
Universal API checks the request for both an OptionalService as well as a SpecificSeatAssignment, and to determine if the requested seat is available.
API and LCC CarriersUniversal API sends the paid seat in the OptionalService to add the optional service.
Because a seat already exists for the traveler on the flight, Universal API cancels the existing seat and adds the new seat from the Fulfillment request. The AirMerchandisingFulfillmentRsp returns AirSeatAssignment with the new seat. Universal API returns the new OptionalService.
AirMerchandisingFulfillmentRsp returns"
- AirSeatAssignment with new seat.
- OptionalService with new seat.
ATPCO CarriersUniversal API sends the provider the ASVC SSR and the new seat. The provider cancels the old seat and confirms the new seat. '
AirMerchandisingFulfillmentRsp returns:
- AirSeatAssignment with new seat.
- OptionalService with new seat.
Important! Cancelling paid seating through Universal API is not supported for API Carriers, such as DL. If a booking that had a paid seat is cancelled by the provider, the seat is automatically cancelled and released back into inventory. If a refund is appropriate, the carrier will issue one.
For ATPCO carriers such as KL, if a new seat assignment is not requested, no special handling is required to cancel a paid seat purchased through Merchandising. In Universal API, UniversalRecordModifyReq/UniversalModifyCmd/AirDelete can be used to cancel a seat assignment.
However, it is important to note that most carriers do not issue refunds for paid seating or require requests directly to the carrier. Therefore, Universal API does not support refunds for paid seats that have been canceled.
If the segment for which an Optional Service was purchased was changed by the carrier because of a schedule change or other reason, the carrier is responsible for moving that Optional Service to the new flight. If the carrier cannot move the Optional Service, it is their responsibility to refund the purchase price to the client.
Universal API does not currently support re-accommodation of Optional Services to a new flight without additional charge. Universal API cannot distinguish between an involuntary change and a voluntary change and, therefore, will charge for the new service on the new flight.