Scan a website for consumer and competition risks, report a problem, and search live cases. Not a law firm.

CounterLayer
← Case library

US · ongoing · ~6 min read

In re Extended Stay Hotel Antitrust Litigation

2026–present · extended-stay hotels

An extended-stay hotel pricing case is still open. A judge kept software firm SAS in the suit on September 15, 2026.

The story

Guests allege extended-stay hotels and IDeaS and SAS fixed rates with the G3 algorithm. On September 15, 2026 the court refused to dismiss SAS. A broader motion was still ahead.

Why it matters

Guests pay the rate posted for an extended-stay room. They do not see whether hotels and a software firm built the pricing tool together.

What was claimed

Plaintiffs say SAS helped build the tool and move sensitive data, including with Hilton and IDeaS.

The other side

SAS can say it sold a component. The court said the complaint alleges joint development, which is why SAS stayed in the case on September 15, 2026. A broader motion was still ahead.

What it means for you

The order does not refund a hotel stay. It keeps SAS in the case while another motion is pending.

Bottom line

The extended-stay hotel algorithm case is live.

Timeline

  1. 2026

    Record

    Guests allege extended-stay hotels and IDeaS and SAS fixed rates with the G3 algorithm. On September 15, 2026 the court refused to dismiss SAS. A broader motion was still ahead.

Key dates

SAS stays in
15 September 2026

Formal snapshot

Summary: Guests allege extended-stay hotels and IDeaS and SAS fixed rates with the G3 algorithm. On September 15, 2026 the court refused to dismiss SAS. A broader motion was still ahead.

Regulator / plaintiff argument: Plaintiffs say SAS helped build the tool and move sensitive data, including with Hilton and IDeaS.

Outcome: SAS remains a defendant. The court has not decided whether a Sherman Act claim is ultimately stated.

Conduct tags

price fixdata lockin

Laws referenced

  • Sherman Act §1 — 15 U.S.C. §1

Companies

Sources

Reader signals

0 reads · synced via local demo storage — add NEXT_PUBLIC_SUPABASE_* to enable shared likes and comments

Comments

    No comments yet — start the thread.