Courts & Constitutional LawSoftware & PlatformsRisk & Compliance

Congress Asks Airlines How Algorithmic Pricing Strategies Are Decided

Congress asked eight airlines who decides whether an algorithm's price goes into effect. Three architectures answer that question differently, and only one of them means a person does.

Josh LynwoodFounder
Published
Read time
13 min
Share
Where Things Stand

One Fact Sits in a Court Filing and a Congressional Letter

Algorithmic pricing is four different things that share a name. A price that moves with demand is dynamic pricing. A price that moves with who you are is personalized pricing. A price built from data about you is what regulators have started calling surveillance pricing. And a price recommended by software that also serves your competitors is shared-data revenue management. Only the last one is an antitrust theory, and it is the one the courts have been busy with.

  • The Reversal. On July 29, 2026, the Third Circuit reversed a Rule 12(b)(6) dismissal in Cornish-Adebiyi v. Caesars Entertainment and remanded. The panel held the allegations, taken as true, made a horizontal agreement plausible. It made no factual findings, and it wrote that at this stage "such level of detail into the software's operations is neither required nor appropriate."
  • The Element. What the panel treated as probative was not that prices were high. It was the allegation that the vendor collected non-public commercial information from competing hotels and used the collective pot to suggest prices to each of them, together with an override said to be restricted to times of "need and extreme circumstances" and, on the same pleading, a vendor that scored each hotel on how often it overrode.
  • The Letter. On August 11, 2026, Representative Frank Pallone wrote to eight airlines. Question 8(c) asks what the process is for reviewing prices the algorithm calculates and who is responsible. Question 8(f) asks who decides whether those prices go into effect "or do they occur automatically." Responses were requested by August 25, 2026, covering everything since January 1, 2025.
  • The Authority. Pallone signed as ranking member, copied the chairman, and cited no rule. The answers are voluntary. In March, Oversight Committee chairman James Comer sent letters of his own to Booking Holdings, Expedia Group, Uber, Lyft and Instacart, invoking the committee's jurisdiction under House Rule X. Both inquiries ask for documents. Only one of them cites an authority.
  • The Gap. Across seven pages the letter uses some form of the word price eighty-three times and customer thirty-seven. It uses competitor, competing, rival and pool not at all. Every data question runs one direction: what comes in about the customer, or what goes out about the company. The committee filed the inquiry under the heading of surveillance pricing, and the outlets covering it followed. That is a different theory from the one the Third Circuit reinstated at the pleading stage.
Sources8See all 33
What separates reviewing a price from ratifying one?

What Happens to the Price if Nobody Looks at It?

A question about the review process admits three architectures, and an affirmative answer is true under all of them.

The distinction underneath is an old one. Engineers have argued about humans in, on, and out of the loop for decades, and nothing here improves on that vocabulary. What is new is that a congressional questionnaire and a federal appellate opinion now both turn on which rung a company occupies, and neither uses the word.

There are three rungs, and they are separated by one question: what happens if nobody acts. On the first, a person opens each recommendation, accepts or rejects it, and records why. Nothing publishes unless somebody acts. This is the only rung on which a human decides a price.

The Third Circuit has already tested what that authority is worth. It was undisputed in that case that the casino-hotels retained final pricing authority and could change any suggested price. The claims were reinstated anyway, on the reasoning that prices are fixed when they are agreed upon, whether or not the parties always adhere to them. Keeping the power to say no did not answer the question.

On the second rung, recommendations publish by default and a person may intervene. The ability exists and may go unused. Prices publish. On the third, nothing human happens at any point. Prices publish.

Underneath all three sits a configuration layer that is not a rung at all. Before the model runs, somebody sets the floor, the ceiling, how far a price may move in a day, and which competitors count as the comparison set. Those choices shape every price the system produces, and a company can make them once and never look again. All three rungs support the sentence "we review our prices."

The Justice Department drew the same line in its amended complaint against RealPage, a rental-housing pricing vendor, describing an A setting under which a recommended price publishes on its own unless a person intervenes before a deadline. feature whose parameters defaulted to three percent daily and eight percent weekly, and a rejection path that required specific business commentary routed to a vendor advisor who could escalate the matter to the landlord's regional manager, the person who supervises the property manager. On that account, accepting cost nothing and refusing cost a memo, a review, and a conversation with your own boss. RealPage itself recognizes, the complaint says, that acceptance rates are not necessarily the best measure of its influence.

Pallone drew the same ladder without naming it. Question 8(c) asks about review after the fact. Question 8(b) asks whether the model weighs data elements differently, and if so which ones and how. Question 8(e) asks what parameters regulate the scope and scale of the algorithm, and gives as its example whether there is an upward limit to how high a price may be set. That is a ceiling, and a ceiling is the configuration layer. Question 8(f) asks who decides whether a price takes effect, and offers "automatically" as an available answer.

One number shows why the distinction is not academic, and it means less than it appears to. Both appellate opinions mention a figure of ninety percent. Both are reciting the same allegation: that the vendor said its clients charge the recommended rate that often. The Third Circuit recorded it as an allegation and treated it as supporting an inference of agreement at the pleading stage. The Ninth Circuit, in a case where the horizontal claim had been abandoned on appeal, noted that the precise rate at which the hotels actually implemented the recommendations was not in the record.

The same alleged marketing claim, in two courts, put to two uses. And an acceptance rate is not a fact about behavior in any case. It is a function of the The width of the gap from a recommended price that still counts as accepting it, chosen before any acceptance rate can be measured. chosen to define acceptance. The Justice Department's own filing shows the range: measured within one percent of the recommendation, the rate was forty to fifty percent; within two and a half percent, nearly sixty; within five percent, more than eighty-five. Same decisions, three numbers.

The version of algorithmic pricing most people can actually see works differently, and the evidence is thinner than the attention. Electronic shelf labels have drawn state bills and Senate letters on the theory that a store can raise a price the moment demand spikes. The only empirical study located for this piece, an unpublished working paper, finds no such effect. Temporary price increases were running at 0.0042 percent of products on an average store-date before the labels arrived, and the change afterward was six ten-thousandths of a percentage point, which is not statistically distinguishable from zero. A shelf label is a broadcast device. It shows one price to everyone in the aisle and cannot price a person.

The regulator has been working the personal side instead, as disclosure rather than prohibition. On August 19 the Federal Trade Commission proposed for comment a policy statement on personalized pricing, with a worked example of a grocery chain charging a delivery customer more for milk because data showed children in the household. The Commission says in the same document that it lacks authority to ban the practice in all circumstances. Four months earlier it had issued an advance notice of proposed rulemaking on food delivery fees, asking among other things about failing to disclose whether prices differ from those offered to other consumers on the platform.

Sources11See all 33
Intersections

Two Complaints Described One Product, and No Court Has Decided Which Is Right

A legal outcome that turns on what a system does is only as stable as the description of that system in the complaint. Where two descriptions of one product both survive to a ruling, the disagreement is about a fact nobody has established yet.

Courts & Constitutional Law. The Ninth Circuit and the Third Circuit reached opposite results about the same vendor's product family, and the difference is traceable to how the two complaints described its data flows. In Gibson v. Cendyn Group, decided in the Ninth Circuit in August 2025, the competitor-price input came from a rate shopping tool the opinion records as collecting public pricing information. In the Third Circuit case it was described as non-public, real-time information pooled from competing hotels.

Software & Platforms. Neither court determined which description is accurate. The Third Circuit said so directly. Which means the same unresolved fact decides two things at once: whether rivals' data was pooled, and which rung of the ladder a company was standing on. That makes it a discovery question rather than a legal one, and it means the operative fact in this area of law is currently a factual dispute about software configuration.

The Ninth Circuit also marked the boundary before anybody crossed it. In a footnote it wrote that its analysis might change if the plaintiffs had alleged that the vendor shared each competing hotel's confidential information among the licensees, adding that they did not allege it. Eleven months later, a complaint alleging exactly that produced the opposite result in another circuit.

The firm commentary has reached for split language in its headlines, but the memos themselves are more careful: Arnold & Porter, Axinn and Mayer Brown all locate the divergence in the facts pleaded rather than in the law, and Mayer Brown writes that the two decisions may not be in conflict. The Ninth Circuit never decided the horizontal question, because the plaintiffs abandoned that claim on appeal, and it assumed on that basis that there was no agreement among the hotels to license Cendyn's software products. A separate footnote is worth more than the split framing. Retained discretion, it wrote, would not immunize a defendant from Section 1 liability for horizontal price-fixing, because a vendor could make non-binding recommendations that competitors all agreed to follow. Such an agreement would be a An arrangement in which a common vendor is the hub and its customers the spokes, actionable under Section 1 only where the spokes also agree among themselves., and any claim of one had been waived.

What would make this wrong

A carrier's response to question 8(c), requested by August 25, states what publishes when no reviewer acts and gives any review rate with the tolerance band that defines it.

Open question

On the congressional side: does anyone ask the competitor-data question, and if not, what does a complete answer to the customer-data question actually establish?

Sources9See all 33
The Weave

The Weave maps a single development across domains and across time. Each row follows one domain from where things stand now through the next eighteen months, and expands for the reasoning behind that trajectory.

Wiiver
SECTOR / DOMAINclick a domain to expand
As It Standsthe current status
Immediate0–6 months
Near-Term6–18 months
Business + Markets
Controls built to show human oversight are pleaded in the complaint as facts supporting an inference of agreement.
Controls read as evidence
The complaint pleads an override limited to 'need and extreme circumstances' and vendor scoring of its use, recited as the alleged constraint on retained authority.
Telemetry you do not hold
The scoring pleaded in this case is the vendor's, so the record of departures from a recommendation sits outside the customer's own files. Wiiver's inference.
Government + Policy
The Third Circuit has reinstated Sherman Act claims over a shared casino-hotel pricing algorithm and remanded.
Proof, not pleading
The panel declined to require pleading how the software works, so the mechanism is a matter for proof. Appellees have until September 11, 2026 to seek rehearing.
Pooling, pleaded or not
Gibson's plaintiffs did not allege the vendor pooled rivals' confidential data; Cornish-Adebiyi's did. What separates the two outcomes is one allegation, not one rule.
A ranking member has asked eight airlines who decides whether algorithmic prices take effect, without power to compel.
Volunteered, not compelled
A ranking member signed it and compulsory process runs through the committee, so August 25 is a request. Any answer is a characterization the company wrote itself.
Rule X versus no authority
House Oversight cited Rule X and signed as Chairman in its own March 5, 2026 pricing inquiry. The August letter cites no authority and signs as Ranking Member.
Technology + Engineering
Whether a recommended price publishes when no one intervenes is a configuration setting in pricing software.
Three rungs, one yes
Three rungs support a truthful yes about price review, and a configuration layer sits under them. Only per-recommendation adjudication stops a price when nobody acts.
A spec for the pipe
The RealPage judgment entered May 19, 2026 specifies runtime inputs, data age and who sets auto-accept parameters. It binds one vendor in one rental-housing market.
wiiver.co · 4 impacted domains shownWiiverv1 · August 19, 2026
Looking Forward

The Answers Are Voluntary, Which Is Why They Matter

Nothing filed this month obliges an airline to do anything. The letter cites no authority and the answers are volunteered. That is the reason to pay attention to them rather than the reason to dismiss them: a volunteered answer is drafted, and a company chooses its own words.

  • The Responses. Answers were requested by August 25, 2026. Whatever a carrier writes about who decides when a price takes effect becomes a characterization it has chosen, and a chosen characterization is harder to walk back later than a compelled concession.
  • The Entries. The RealPage judgment was entered in May and binds now. The Agri Stats judgment is lodged and awaits approval. The terms most likely to travel to other industries are the ones about defaults and data age rather than the ones about money.
  • The Remand. No mandate has issued, and none can issue until the rehearing window closes. All ten appellees hold an extension to September 11, 2026 to seek rehearing. If none comes, the case returns to the district court and the question the panel declined to reach becomes a discovery question: what the software actually does with data from competing licensees.
  • The Unasked Question. In the two federal instruments read for this piece, the August 11 letter and S. 3387, neither asks whether other carriers' non-public data reaches a pricing model. That is the element the Third Circuit's analysis turned on, and the letters ask about the customer side instead.
  • The Legislative Layer. California's AB 325, Chapter 338, effective January 1, 2026, added a Cartwright Act prohibition reaching pricing algorithms that use competitor data, and a pleading rule that no longer requires a complaint to allege facts excluding independent action. Federally, the federal One Fair Price Act of 2025, introduced in December by Senator Gallego, would reach air carriers and preserve private damages claims against the preemption that otherwise bars them. It defines its subject as data about a person, not data about a competitor. For airlines specifically, federal preemption of state claims about price, route and service is the wall that layer has to clear.

The question Congress asked is a good one and narrower than it looks. What happens to a price when nobody looks at it is answerable in a sentence, and the sentence differs for three systems that would all say yes as written. Our read is that until somebody asks the other half, about whose data goes into the model rather than whose comes out of the customer, the answers can be truthful and still settle nothing.

Sources16See all 33

Every issue

  1. 01Intersection of the week
  2. 02Impact of the week
  3. 03The week in review

Wiiver Weekly

One free email, Saturdays at 7:00 AM ET.

Unsubscribe anytime.

Sources and Verification
27 of the 33 sources cited here are primaryfilings, opinions, dockets, statutes and agency releases, read directly
Primary sources27
Secondary sources, by sector6
Government + Policy4
Business + Markets2
v1 · Reviewed by Josh Lynwood · August 19, 2026
Back to top