Uber Just Became a Hotel OTA. Your Distribution Costs Are About to Get Weirder.

So Uber is selling hotel rooms now.

Let that land for a second. The app that 90% of your guests already have on their phones... the one they open when they land at the airport, when they leave your lobby, when they need a ride to dinner... that app now has a "book a hotel" button. And behind that button is Expedia's entire inventory. Over 700,000 properties. Yours is probably one of them.

Here's what this actually is: Expedia's Rapid API plugged into Uber's interface. That's the technical reality. Uber didn't build a hotel booking platform. They didn't hire a hotel tech team. They partnered with Expedia and wrapped the existing inventory in Uber's UI. If you're already distributed through Expedia, you're already on Uber. Nobody asked you. Nobody had to. Your rates, your availability, your photos... all of it is now living inside an app that 150 million people use monthly for something completely unrelated to hotel shopping. And Uber One members (which the company has been aggressively growing) get 10% back in credits and 20% off select properties. That's not a loyalty program competing with Bonvoy or Hilton Honors. That's a discount layer sitting on top of your existing OTA distribution, siphoning rate integrity in a channel you didn't even know you were in.

Look, I get the "super app" pitch. Dara Khosrowshahi ran Expedia for over a decade before he ran Uber. This isn't a random pivot... this is the most logical partnership in travel tech right now. The man literally knows both codebases (metaphorically, probably literally too). And from a pure user-experience perspective, it makes sense. You land, you open Uber, you book your ride, you see a hotel deal, you tap. One app, one transaction, done. That's a real workflow. That's not vaporware. But here's what nobody's talking about: the attribution nightmare this creates. When a guest books through Uber, which is powered by Expedia, who "owns" that booking? What does your channel manager see? What does your brand's loyalty contribution metric look like when bookings are being driven by a ride-hailing app's discount program? I talked to a revenue manager last week who already manages six OTA channels, two metasearch feeds, and a direct booking engine that the brand redesigned twice in 18 months. She said, and I quote, "If one more channel shows up that I have to monitor, I'm going to start screening calls from my regional VP." She was half joking. Maybe less than half.

The real question here isn't whether Uber can sell hotel rooms. Of course they can. The question is what this does to the already chaotic distribution stack at property level. Your PMS talks to your channel manager, which talks to your OTA connections, which now includes an Expedia-powered feed inside a ride-hailing app that offers its own loyalty discounts on top of whatever rate you've already negotiated. If your channel manager doesn't surface Uber as a distinct source, you won't even know where these bookings are coming from until you see the commission hit. And Uber's taking a "thin commission," reportedly modeled on Airbnb's approach... but thin for Uber still means another hand in the revenue bucket for you. This is a distribution channel that didn't exist yesterday. Your tech stack wasn't built for it. Your rate parity agreements weren't written with it in mind. And the guest doesn't care about any of that... they just tapped a button because it was 20% off and they were already in the app ordering a car.

The Dale Test question here is obvious: when this booking comes through at 11 PM and something goes wrong with the reservation... wrong rate, wrong room type, wrong dates... what does your night auditor do? Call Uber? Call Expedia? Troubleshoot a booking that originated in a ride-hailing app? The system failure path on this is genuinely unclear, and if you've ever tried to resolve an OTA booking error at midnight with one person on shift, you know that "unclear" is the last thing you need. The technology is real. The workflow is logical. The chaos it introduces at property level is something nobody at Uber's product event in New York bothered to mention.