Problem
When a PNR with multiple passengers having different pricing conditions (e.g., one Free of Charge, one paid) is imported into Salesforce, the Costings view displays the combined total as a single cost for both travelers instead of showing separate per-passenger pricing. This makes it difficult to apply discounts or separate costs correctly.
What We Found
The Connect API correctly processes PNR data with individual fare records (TSTs) per traveler. The per-person pricing data IS available in Salesforce - you can view it by clicking āEdit PNRā on the flight itinerary line item in Builder (view-only mode). However, the Costings view aggregates totals and displays them as a combined amount with quantity, rather than per-passenger breakdown. This is expected behavior, not a bug.
Solution
- Open Costings for the booking
- Click the āAdd Customā button at the top of the Costings screen
- In the āAdd Custom Serviceā modal, select a supplier
- Select an item, set date and time
- Select the āCustom Discountā type
- Configure occupancy and set the discount cost amount (negative value for discount)
- Optionally select commission and cancellation groups
- Click Save
- Allocate the custom discount to the specific passenger(s) via the Passenger Allocations screen
Notes
- Per-person PNR pricing is visible in Builder by clicking āEdit PNRā on the flight itinerary line item (this is view-only)
- Use Custom Discount type in Costings to apply per-passenger adjustments like FOC discounts
- The custom service must be allocated to specific passengers using Passenger Allocations
Warnings
ā ļø Any subsequent API refresh or PNR update will return original fare values from the source and may overwrite manually added adjustments ā ļø Consider selecting the option to retain existing cost or sell prices when refreshing PNR data to preserve manual adjustments
Source: KHELP-12227