Originally Posted by
Lobengula
Ok, fair enough, but the fact is that EF can retrieve the information if I know the airline code. So the information is indeed available.
I'm not a programmer but in my simple mind, it should be possible to search flights departing JNB and arriving BUQ without the need for a customer to specify an airline code. I don't mind if it searches multiple GDS. I only know that I can get the info if I provide a specific airline code, this shouldn't be necessary.
I do understand that it must be almost an impossible task to cover 100% of the many thousands of airlines out there, especially when it comes to countries in turmoil. But in this case, it seems to be possible.
This is just EF minimizing their costs. They
could fix this. It would be relatively simple: they just need to query
all GDSes instead of just their primary one. Of course, running queries on several GDSes does increase the cost, although GDS searches are typically a tiny cost (less than a cent per transaction, as I recall). EF is going to tell you that it's too expensive to do this, and while I have to kind of
at that, I at least do understand it and probably would be willing to pay a touch more for a "pro" option that does things like this.
The alternative would be for them to script their GDS retrieval engine to search GDS #2 when a certain query is put in (like a flight from JNB to BUQ). This is certainly feasible, too, but it would require EF's staff to more actively monitor the state of airline affairs and know where to put these custom tweaks in. They'll probably tell you they can't afford to do that, either.