How are refunds and exchanges handled?

Refunds:

Segments that have been refunded do not result in any emissions as they have effectively been cancelled and thus no travel has occurred. The Thrust Calculator matches the refunded segment with the original booking segment within the uploaded spreadsheet or spreadsheets that have been previously uploaded. The same also happens for data coming into Thrust Calculator via a data feed. This matching process is done using a unique identifier such as PNR+EmployeeID+Leg. These original bookings that match with a row marked as a refund are then also removed from the Calculator so no carbon emissions are associated with those segments (original booking and refunded booking). As such, in the CSV file that can be exported from Thrust Calculator there is no mention of refunded segments. 

Exchanges:

Segments that have been exchanged do have a carbon emission associated with them. An exchange is representing a change to the booking such as class, departure date or route. In this case, the original booking needs to be removed so that double counting of emissions does not occur (we don’t want to count emissions from the first booking and also the exchanged booking). Like with refunds, a unique identifier is used to match the exchanged segments with their original booking. Hence, the exchanged segment still remains, but the original booking is removed. As such, in the CSV file that can be exported from the Thrust Calculator there is a column which highlights which segments are exchanges. In some cases one booking may be exchanged multiple times, in this case the most recently “exchanged” segment will be the segments that is present in the Calculator.

Please note, while Thrust Calculator is able to match refunded and exchanged segments to the original booking, this process fully relies on a suitable unique ID being used and with all segments containing these data points.

For more information on using unique IDs please see this article.