Any time saved by ordering online and picking up the order has vanished chasing customer support people to fix something that would have taken a few seconds through their website.
Any time saved by ordering online and picking up the order has vanished chasing customer support people to fix something that would have taken a few seconds through their website.
And I never claimed they don’t have different prioritization. I’m just saying that one working doesn’t mean the other will also work.
The page may have not loaded because of a failed API call to the credit processor when requesting a refund. Charges and refunds are different API usages, and it’s wholly possible that an issue on the processor’s side can break pages on a merchant’s site. If for some reason Walmart’s site can’t communicate with Visa/MC/AmEx/whoever and their page isn’t configured to handle a specific failure, it will likely go to a default error landing page as a failsafe.
I’m not defending Walmart or anything; just explaining some of the technical reasons a refund page can break. API failures happen even to non-scummy stores, as well.
It didn’t even get that far.
This error quite literally came up when I click on the “request a refund” button within my order (where Walmart said I needed to. There should have been another page asking which item(s) I want to refund, and I would imagine ask me for a reason why. That’s well before it needs to call an API for credit processing.
In any case, this was mildly infuriating, more for the wasted time on something that should have taken two seconds.
FWIW, I can only hope that Walmart gets notified whenever these end user issues pop up on the website… so they can fix the problem. It’s been many hours already, and the page still errors out. Unless they’ve hired amateurs, this seems excessive. Would it take this long if their payment system was down?