So let me get this straight. The platform that every revenue manager in the industry uses to benchmark occupancy, ADR, and RevPAR against their comp set... the one your brand probably requires you to subscribe to... is now at the center of a UK antitrust investigation. The CMA announced on March 2 that it's looking into whether Hilton, IHG, Marriott, and CoStar (which owns STR) used that shared data to effectively coordinate pricing without ever picking up the phone. And honestly? I've been waiting for this shoe to drop.

Look, I need to explain what "algorithmic collusion" actually means here, because the headlines are going to make this sound like three CEOs met in a back room. That's not it. The concern is more subtle and, frankly, more interesting from a technology perspective. STR collects non-public performance data from hotels... occupancy, rate, RevPAR... aggregates it, and sells it back as benchmarking reports. Revenue managers then feed those benchmarks into their RMS platforms to set pricing. The CMA's theory is that this cycle (share data, aggregate data, price off aggregated data, repeat) creates a feedback loop where competitors are essentially reacting to each other's rate moves in near-real-time without ever directly communicating. It's coordination by algorithm. And if you've ever watched an RMS automatically adjust rates based on comp set performance data, you've seen the mechanism they're investigating.

This isn't new territory. A class action in Illinois last year targeted hotels using Amadeus's Demand360 platform for the same basic theory. Another suit in San Francisco went after the IDeaS RMS for algorithmic price-fixing. CoStar and the major chains beat a similar US consumer lawsuit (dismissed sometime in 2024-2025, depending on who you ask). But here's what's different: the CMA isn't a plaintiff's attorney looking for a settlement. It's a government regulator with subpoena power and a mandate to act. And the timing matters... this follows the exact playbook regulators used against RealPage in the US rental housing market, where the DOJ argued that sharing real-time pricing data through a common platform suppressed competition. That case reshaped how the entire multifamily industry thinks about revenue management technology. Hotels are next.

Now here's the Dale Test question (what happens to the least technical person on the smallest shift when this plays out?). If the CMA finds that STR data sharing constitutes anticompetitive behavior, the remedies could fundamentally change how revenue management works. We're talking potential restrictions on what data can be shared, how granular it can be, how quickly it's available. Imagine your RMS suddenly can't pull real-time comp set data. Imagine STR reports delayed by 90 days instead of delivered monthly. Your revenue manager is now pricing blind... or at least pricing with one eye closed. The technology stack that every branded hotel depends on for rate optimization could get kneecapped by regulators who don't care about your RevPAR index. I talked to a revenue director at a mid-scale portfolio last month who told me, "Without STR, I'm basically guessing." That's 60% of the industry.

The real question isn't whether the CMA finds wrongdoing (they've been careful to say no assumptions should be made). The real question is what this investigation does to the data-sharing infrastructure the entire industry runs on. IHG shares dropped 5% on the announcement. CoStar says it's "surprised" that a decades-old benchmarking platform is suddenly under scrutiny. But the regulatory trend is clear... algorithmic pricing tools are getting examined across every sector, and hospitality's argument that "we've always done it this way" is not going to hold up. If you're a technology vendor building revenue management tools, start thinking about what your product looks like without third-party comp set data. If you're a hotel relying on that data to set rates... start thinking about what your pricing strategy looks like without it. Because that future just got a lot more plausible.