|
Originally Posted by ajnaro
(Post 23275325)
The conflict between a US credit card used in the US on the one hand and the origin of the ticket in India on the other hand may be the problem. At least it SHOULD be a problem if AA is policing its market restrictions properly. In principle, ex India fares are for use only by passengers in the Indian market, not the US market. A US credit card should be acceptable, but only if used in India. But I have no idea if oneworld has programmed such restrictions into their software.
I have booked tickets via the tool, from Australia, with an Australian credit card, starting in Japan or Korea. No issue, and charged at the Japan/Korea price (as it should). |
<del>
|
Can't get the tool to show codeshares. Does anyone else hade the same problem? What to do?
|
Originally Posted by Valmont
(Post 23303662)
Can't get the tool to show codeshares. Does anyone else hade the same problem? What to do?
Congratulations on your first post:D |
Originally Posted by Himeno
(Post 23279765)
Why do you assume that some booking a RTW ticket only does so from where ever their payment method happens to be registered?
I have booked tickets via the tool, from Australia, with an Australian credit card, starting in Japan or Korea. No issue, and charged at the Japan/Korea price (as it should). Taking an ex-ICN DONE3 fare, for instance (and this is a standard restriction in the xONEx fares), Code:
Sales restrictionsWere you charged in JPY/KRW or AUD? If it was the earlier then the country of sale was the country of origin, which is fine. Maybe that loophole was closed and they now pin your country of sale to your card billing address? Most of the fare rules are not validated for autopricing so probably the GDS+online tool cannot validate this without human intervention. Speculating, an easy way around that would be for the website to reject cards having a billing address in a different country. Although from your experience that is obviously not implemented properly, it might be in place for certain countries. Another speculation would be that the tool is trying to process the rule now and it just gives up when it realizes the pricing was wrong. |
Originally Posted by Calchas
(Post 23317831)
I don't think that's in line with the fare rules.
Taking an ex-ICN DONE3 fare, for instance (and this is a standard restriction in the xONEx fares), I read that as, if the ex-SYD price (say) is higher than the ex-ICN price, and you book out of the SYD office (virtually or otherwise), you will be charged the ex-SYD price. Were you charged in JPY/KRW or AUD? If it was the earlier then the country of sale was the country of origin, which is fine. Maybe that loophole was closed and they now pin your country of sale to your card billing address? Most of the fare rules are not validated for autopricing so probably the GDS+online tool cannot validate this without human intervention. Speculating, an easy way around that would be for the website to reject cards having a billing address in a different country. Although from your experience that is obviously not implemented properly, it might be in place for certain countries. Another speculation would be that the tool is trying to process the rule now and it just gives up when it realizes the pricing was wrong. The tool assumes you are in the country of origin and send the fare to the first marketed carrier's (or to AA in the case of JL, LA, RJ and a few others) local ticketing office. That silly rule has always been there for as long as I've been getting tickets. There used to be a rule allowing tickets to be sold in Canada at the price of the country of origin converted to CAD. That rule was removed ~2 years ago. The tickets I have been getting recently are xONE3's - which do not exist for travel from/via South West Pacific, South America or Africa. I have always been charged in JPY/KRW with the bank doing the conversion. I have used the tool to book DONE3's from JP/KR for 3 of the 4 I've booked. The 4th was issued via an agent in Toronto when the Canadian Exception was still around because the tool wasn't working (the tool has always been buggy). I am in the process of getting a ticket issued over email with CX Tokyo. |
Originally Posted by Himeno
(Post 23318001)
The tool assumes you are in the country of origin and send the fare to the first marketed carrier's (or to AA in the case of JL, LA, RJ and a few others) local ticketing office.
Originally Posted by Himeno
(Post 23318001)
I am in the process of getting a ticket issued over email with CX Tokyo.
|
Originally Posted by Calchas
(Post 23318332)
^^ Thanks for the confirmation. Actually it was a helpful post from my perspective as I am new to this.
QF Japan had problems charging my card due to a per day card limit I didn't know about. They saw that the billing address was in Australia and had QF Sydney contact me. Once I worked out what the problem was and lined everything up with the bank, I contacted QF Japan via QF Sydney and it all went through - still at the Japan price and charged to the card in JPY. The country of origin vs country of sale rule existed at the time, and QF still charged the JP price knowing full well that I was in Australia at the time (though I ended up paying more due to currency fluctuations and the delay in getting it all worked out). |
>_< I hate this tool so much.
Looking at JFK-CLT in mid Oct. Expert Flyer reports 6 ex JFK and 2 ex LGA flights with the required fare class available (x2 for US/AA codeshares, all A6 or more). Tool offers 1 flight. It still refuses to show codeshares that exist and are available (eg, AA7974 [QR722]). |
Originally Posted by Himeno
(Post 23372729)
>_< I hate this tool so much.
Looking at JFK-CLT in mid Oct. Expert Flyer reports 6 ex JFK and 2 ex LGA flights with the required fare class available (x2 for US/AA codeshares, all A6 or more). Tool offers 1 flight. It still refuses to show codeshares that exist and are available (eg, AA7974 [QR722]). In principle the fare class availability can differ by sales city but in practise it doesn't change much, especially far out. |
Wanted to add 1 more pax to a recently "validated by the tool" xONEx itinerary. Click save change. This is what I got for the last 15 minutes. :mad:
Re-confirming flight availability. Please wait... 16 of 16 Anyone had this experience? Should I kill it and restart? Guess so (answering my own Q). |
Originally Posted by Himeno
(Post 23372729)
>_< I hate this tool so much.
. Working on a xONEx itin. The tool does not offer non-stop service for PHX-PIT-PHX. But on aa com, there are non-stops. What gives !!! |
Originally Posted by allset2travel
(Post 23375291)
+1.
Working on a xONEx itin. The tool does not offer non-stop service for PHX-PIT-PHX. But on aa com, there are non-stops. What gives !!! See Rule 4(k) in the rule sheet So that's why you cannot have two non-stops However, the tool does seem to be having problems showing US flights (and AA flights that are codeshares on US flights). I cannot get it show the AUA-PHL non-stop. |
Originally Posted by pandaperth
(Post 23375737)
Latest version of the Oneworld Explorer rule sheet (dated August 1st) has added both Phoenix and Pittsburgh to the list of cities for which only one transcontinental flight is allowed
See Rule 4(k) in the rule sheet So that's why you cannot have two non-stops However, the tool does seem to be having problems showing US flights (and AA flights that are codeshares on US flights). I cannot get it show the AUA-PHL non-stop. |
The tool stuffs up, so I contact the airline.
I think there is a problem when I know more about the rules then the airline agents do... |
| All times are GMT -6. The time now is 2:47 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.