What happened
PYMNTS reports that the U.S. Court of Appeals for the Third Circuit revived an antitrust case against several Atlantic City casino hotels involving Rainmaker, a shared revenue-management platform operated by Cendyn Group. The lawsuit alleges that competing hotels supplied non-public pricing information to the platform, which then generated room-rate recommendations from pooled data. The appeals court did not determine whether unlawful coordination occurred; it ruled only that the allegations were sufficient for the case to continue. The hotels deny wrongdoing. The account is based on PYMNTS reporting and a post from law firm Mandelbaum Barrett; the claims and legal interpretations have not been independently confirmed here.
PYMNTS reports that the Third Circuit allowed an antitrust lawsuit involving several Atlantic City casino hotels to move forward. The dispute centers on Rainmaker, described by the outlet as a shared revenue-management platform operated by Cendyn Group. According to the allegations summarized by PYMNTS, competing casino hotels entered non-public information into the same system, and the software used pooled data to produce recommendations for room rates. The source does not independently establish what data was submitted, how the system processed it, or whether any recommendation led to a coordinated price.
The plaintiffs argue that the platform functioned as a mechanism for coordinating prices among competing properties. PYMNTS says the hotels deny wrongdoing. The appeals court did not decide whether the alleged conduct violated antitrust law, whether the software caused specific prices to rise, or whether any defendant should be liable. Its ruling, as described by PYMNTS, was procedural: the allegations were serious enough for the litigation to continue. The article does not provide the full appellate opinion, the case number, damages claims or a schedule for the next proceedings.
PYMNTS bases its account in part on a recent post by Mandelbaum Barrett. The firm’s legal framing, as quoted by the outlet, is that antitrust rules focus on whether competitors coordinated prices, not on whether coordination occurred by telephone, at a conference or through software. The firm warns that using a technology vendor does not automatically shield a company from scrutiny. That is an interpretation attributed to the firm, not an independently verified statement of the court’s complete reasoning. The source also does not report a response from Cendyn Group or identify any independent technical audit of Rainmaker.
Read the primary source: pymnts.com ↗
Why it matters
The case could clarify how existing antitrust principles apply when competitors use a common algorithmic pricing system rather than communicating directly. It also highlights a practical governance problem for businesses that rely on pricing software without fully understanding which data the system uses or how recommendations are produced. A continuing case is not a finding of liability, but it may increase scrutiny of algorithmic pricing arrangements across hospitality and other consumer-facing industries.
The practical significance is that algorithmic decision-making may not create a separate legal category simply because no manager directly communicates with a rival. PYMNTS reports Mandelbaum Barrett’s view that the central question remains whether competitors coordinated pricing. If a common system uses sensitive information from competing businesses to shape recommendations, investigators and courts may examine the arrangement as closely as more traditional forms of coordination. The article does not establish that this occurred in Atlantic City; it describes an allegation that must still be tested in court.
The case also exposes an information gap inside businesses that purchase automated pricing tools. PYMNTS says hospitality operators may not know whether recommendations are based only on public market signals or also on private information supplied by competitors. They may likewise have limited visibility into how inputs are combined, how recommendations are generated and whether managers review them before adopting prices. Those observations come from the article and the law firm’s recommendations; the source provides no survey showing how widespread the problem is or how often hotels accept recommendations without review.
The broader public concern is not limited to casinos. PYMNTS says similar pricing tools are used by independent hotels, hotel brands, management companies and restaurant groups. If courts treat shared data and automated recommendations as relevant to traditional antitrust analysis, companies may face greater pressure to document data sources, preserve decision records and assign accountability to human managers. Consumers could be affected if unlawful coordination were ultimately proven, but the source does not report evidence of consumer harm, an established price effect or a finding that Rainmaker produced illegal outcomes.
What to watch next
The case returns to a lower court, where the allegations and evidence will be examined further. Important unresolved questions include what data entered the Rainmaker platform, whether competitors’ private information was used, how much discretion hotel managers retained, and what the vendor agreements required. Hotel operators and regulators may also press vendors for clearer data-use disclosures, audit records and human-review controls, but PYMNTS does not report any new rule or final judgment resulting from this decision.
The immediate next step is further litigation in the lower court. PYMNTS says the Atlantic City case now returns there, so the parties may seek discovery and present evidence about the platform, the participating properties, the information exchanged and the way recommendations influenced pricing. The source gives no timeline for trial, settlement or another appellate ruling. It also does not say whether the lower court has imposed restrictions on the software’s use while the case proceeds.
The factual questions will matter more than the existence of AI or automation alone. Key issues include whether the information supplied to the system was genuinely non-public, whether competitors could see or infer one another’s data, whether the platform’s recommendations were binding or merely advisory, and whether hotel employees independently reviewed them. PYMNTS does not answer these questions. It reports only the plaintiffs’ allegations, the hotels’ denial and the appeals court’s decision to let the case continue.
Mandelbaum Barrett recommends that businesses ask vendors and legal advisers what information enters a pricing platform, whether competitor data is used, how contracts govern shared information, whether managers review recommendations and whether compliance policies cover artificial-intelligence tools. Those are recommendations reported by PYMNTS, not requirements announced in the appellate decision. Watchers should also distinguish any future court finding from industry reaction or vendor marketing: this source reports no new regulation, no final liability ruling and no independent confirmation that the Rainmaker system violated antitrust law.
