Courts Just Said Your Revenue Management Software Might Be a Price-Fixing Conspiracy
A federal appeals court revived an antitrust lawsuit alleging that Caesars, MGM, and Hard Rock used shared AI pricing software to collude on Atlantic City room rates. If you're a hotel feeding your rates into a third-party RMS that also serves your comp set, you might want to read the ruling before your next pricing recommendation.
So here's something that should make every hotel operator using a revenue management system pause for about five seconds. On July 29, a federal appeals court in Philadelphia reversed the dismissal of a class-action lawsuit accusing Caesars, MGM's Borgata, and Hard Rock Atlantic City of using a shared AI pricing platform... Rainmaker, owned by Cendyn... to effectively fix room rates. The plaintiffs allege that these competing hotels fed non-public pricing and occupancy data into the same algorithm, accepted its recommendations roughly 90% of the time, and the result was artificially inflated rates. The 3rd Circuit said that's enough to let the case proceed.
Let me be clear about what's actually being alleged here, because the technology matters. This isn't about hotels using revenue management software. Every hotel uses revenue management software. This is about competing hotels feeding sensitive, proprietary data... real-time occupancy, rate positioning, demand signals... into a shared platform that then tells all of them what to charge. And they all listen. Think about that architecture for a second. You and your three biggest competitors are all sending your private data to the same system, and that system is telling all of you to raise rates at the same time. You don't need a phone call between GMs to coordinate pricing. The algorithm does it for you. That's the allegation, and honestly... the architecture makes it plausible. I've evaluated dozens of RMS platforms. Most of them ingest competitive data. The question the court is now asking is: at what point does "competitive intelligence" become "coordinated pricing"? And that's a question nobody in hotel tech has had to answer under oath before.
What makes this especially interesting (and by interesting I mean legally chaotic) is that the 9th Circuit in San Francisco dismissed a nearly identical lawsuit against Las Vegas casino-hotels using the same Rainmaker software last year. So now you've got two federal appeals courts looking at the same technology, the same vendor, the same defendants in some cases... and reaching opposite conclusions. That's a circuit split. For the non-lawyers in the room, a circuit split is basically the legal system saying "we have no idea, someone bigger needs to decide this." That someone bigger is usually the Supreme Court. The DOJ and FTC have already filed statements in similar cases arguing that using an algorithm doesn't shield you from antitrust liability. They're watching this.
Here's where this hits closer to home than Atlantic City casino floors. The RealPage lawsuits in multifamily housing... same theory, same structure, landlords feeding data into shared pricing software... have already resulted in DOJ intervention and settlements. Hotels are next in that crosshair. If you're an independent or a branded property using an RMS that also serves your comp set (and most of them do... that's literally how they build their datasets), you need to understand what data you're sharing and how the vendor uses it. I talked to a revenue manager last month who had no idea that her RMS was ingesting rate data from three of her direct competitors and using it to generate her pricing recommendations. She thought it was just pulling from public OTA rates. It wasn't. The vendor's data-sharing architecture was buried in page 47 of a terms-of-service document nobody reads.
Look, I'm not saying your RMS is a price-fixing tool. Most of them probably aren't. But the legal landscape just shifted, and "probably" isn't a defense. The question this case is forcing is whether the hub-and-spoke model... one vendor, multiple competitors, shared data, coordinated recommendations... constitutes an implicit agreement to fix prices. If courts start saying yes, that changes the entire economics of revenue management technology. Vendors will have to redesign how they handle competitive data. Hotels will need to understand exactly what they're feeding into these systems and what comes out the other side. The days of treating your RMS as a black box that just spits out a rate recommendation are over. Or they should be.
Here's what I want you to do this week. Pull your RMS contract. Find the section on data sharing... specifically, what data you're providing to the vendor, whether it's aggregated with competitor data, and whether competitor-specific information feeds into your pricing recommendations. If you can't find that section, or if it's vague, call your vendor and ask directly: "Do any of my competitors use your platform, and does their data influence my rate recommendations?" Get the answer in writing. If you're a GM at a branded property where the RMS is mandated by the brand, send this question up to your revenue leader and copy your ownership group. You don't need to panic. You need to know what you're plugged into. Because if this lawsuit sets precedent, the hotels that understood their data architecture will be fine. The ones that blindly accepted recommendations without understanding the mechanism... those are the ones that end up in depositions.