Originally Posted by
xliioper
As it turns out, UA does not actually have any fares filed on VCT-YQU (not too surprisingly). In this case, the pricing involves separate fares on each segment in both cases. But whether or not there are through O&D fares on a route, pricing is "supposed" to use married segment inventory to choose fares on itin even when multiple fares are involved. Clearly that is not happening with multi-city searches.
True - I guess my ‘should produce a ‘T’’ Is a little misleading. It should produce a ‘U’ given the married segment logic - and that logic
should be checked prior to purchase. Not sure if that check would typically be done during search or right before it brings up payment screen - likely the latter because checking that at search stage with multiple potential itineraries would take too long.
What I should have said is with the way United does its multi-city, it’s very likely to produce a ‘T’ assuming fares files for O-D market, or in this case, probably VCT-YYC and YYC-YQU (or with IAH instead of YYC). I’m not sure if multi-city ever does the fare validation.
what I will say is I’m surprised at this point it still hasn’t been addressed. In say, 2013/14, when the merger was still young and lots of other priorities than fixing this, I understand they were t rushing it. By now, you’d think they would have made the effort. Given that, either the company is naive and just doesn’t know/care about it, or they do but they think the loss of revenue either isn’t big enough to worry about or won’t have that much impact, or the lost revenue is less than the cost to access/fix it.