Language Selection

English French German Italian Portuguese Spanish

That fare you see may not be the fare you get

Filed under
Web

WOULD you tolerate a department store that raised the price on a sweater between the time you picked it off the rack and the moment you paid for it? Not likely.

Yet something similar sometimes happens when shopping for airfares at third-party travel websites such as Orbitz, Expedia and Travelocity, according to several recent studies from Consumer Reports WebWatch, a project of the nonprofit Consumers Union based in Yonkers, N.Y.

"What we see is shoppers are being advertised a price that's not available," said William J. McGee, consultant to Consumer Reports WebWatch. "There is no other place in the market where that's acceptable."

The phenomenon is called "fare jumping," and it occurs when an airfare changes price (usually an increase) during the online purchase process. According to a WebWatch study released last fall, airfares on Orbitz increased 21% of the time and decreased 5% of the time. Orbitz declined to comment for this story.

The problem was less pronounced at Orbitz's largest competitors, the study showed. Expedia showed an increase 5% of the time and a decrease 2%; Travelocity fares increased 1% of the time and decreased 1%.

Fares can change quickly because the lowest fares are sold in limited quantities. The fare you see one moment may be bought out the next by another shopper, said Kari Swartz, a spokeswoman for Expedia.

"If a confirmed shopper is further along in the search, then that seat's no longer available for us to sell," Swartz said.

Current technology doesn't allow checking every possible airfare combination and holding every one of those fares while the customer decides whether to purchase the ticket.

"Online agencies connect, for the most part, to the airlines through an intermediary," said Jared Blank, an analyst for New York-based Online Travel Review, which publishes travel industry updates. The most efficient way for the intermediary to perform is to store fare data and update them regularly. When a consumer says, "Yes, sell me that ticket," the online agencies query the airline sites directly to confirm real-time availability.

"There is a time lag," Blank said. "The [intermediary] is not passing on information to you in real time."

To address the problem, the third-party agencies have added warnings when a fare changes during the booking process. That's important because the difference can be as little as $5 or $10, which consumers may miss.

Fare jumping does not appear to be an issue on the airlines' own websites, according to WebWatch, which found no instances of it there: "Going directly to an airline site [would] be the best bet because they connect directly to the airline's reservation system," Blank said.

Expedia and Travelocity disagreed that fares were more stable on the airlines' sites.

"The number of test queries was dramatically skewed with [WebWatch's] findings, with only 36 trials evaluating the supplier sites versus 144 trials evaluating the third-party sites like Expedia," Swartz said.

If it does happen on an airline site, a consumer's choices are limited to that airline's inventory, so third-party sites may give consumers an advantage.

"Unlike the airline website, we may very well be able to find that customer the same fare on another airline," said Travelocity spokesman Joel Frey.

Travelocity has tried to give consumers a heads-up that a fare might be vulnerable to change. It provides a note next to a fare when three or fewer seats are available so consumers know they must act quickly.

By JAMES GILDEN
The Los Angeles Times

More in Tux Machines

How Linux became my job

I've been using open source since what seems like prehistoric times. Back then, there was nothing called social media. There was no Firefox, no Google Chrome (not even a Google), no Amazon, barely an internet. In fact, the hot topic of the day was the new Linux 2.0 kernel. The big technical challenges in those days? Well, the ELF format was replacing the old a.out format in binary Linux distributions, and the upgrade could be tricky on some installs of Linux. Read more

Linux 4.16-rc2

It's been a quiet week, and rc2 is out. I take the fairly quiet rc be a good sign for 4.16, but honestly, rc2 is often fairly calm. That's probably because people are taking a breather after the merge window, but also simply because it might take a while to find any issues. But let's be optimistic, and just assume - at least for now - that it's because all is well. The diffstat is fairly odd, but that often happens with small rc's just because then just a couple of pulls will skew things easily in one or two directions. This time the patch is about one third architecture updates (arm64, x86, powerpc), one third tooling (mostly 'perf') and one third "rest". And yes, the bulk of that rest is drivers (gpu, nvme, sound, misc), but those drivers are still distinctly *not* the bulk of the whole patch. Go out and test, it all looks fine. Read more Also: Linux 4.16-rc2 Kernel Released

OpenStreetMap in IkiWiki and Why OpenStreetMap is in Serious Trouble

  • OSM in IkiWiki
    Since about 15 years ago, I have been thinking of creating a geo-referenced wiki of pubs, with loads of structured data to help searching. I don't know if that would be useful for anybody else, but I know I would use it! Sadly, the many times I started coding something towards that goal, I ended blocked by something, and I keep postponing my dream project.
  • Why OpenStreetMap is in Serious Trouble
    That said, while I still believe in the goals of OpenStreetMap, I feel the OpenStreetMap project is currently unable to fulfill that mission due to poor technical decisions, poor political decisions, and a general malaise in the project. I'm going to outline in this article what I think OpenStreetMap has gotten wrong. It's entirely possible that OSM will reform and address the impediments to its success- and I hope it does. We need a Free as in Freedom geographic dataset.

Linux KPI-Based DRM Modules Now Working On FreeBSD 11

Thanks to work done by Hans Petter Selasky and others, this drm-next-kmod port is working on FreeBSD 11 stable. What's different with this package from the ports collection versus the ported-from-Linux Direct Rendering Modules found within the FreeBSD 11 kernel is that these DRM modules are using the linuxkpi interface. Read more