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.
On August 11, 2026, Representative Frank Pallone, the ranking member of the House Energy and Commerce Committee, wrote to eight airlines with a list of questions about how they set prices. Two of those questions, buried in a subpart, ask what happens between an algorithm producing a number and a customer seeing it. Thirteen days earlier, in Cornish-Adebiyi v. Caesars Entertainment, the Third Circuit had reversed the dismissal of an antitrust case that turned on almost the same point. It reinstated claims against a group of Atlantic City casino-hotels whose pricing software was supplied by Cendyn, a common vendor, holding that the allegations, taken as true, made a horizontal agreement plausible. It made no finding that any agreement existed, and declined to decide what the software does. The letter and the opinion are not about the same thing. Different statute, different plaintiff, different theory. The overlap is in what has to be described: how much room a person has between a recommended price and a published one. A company can answer that it reviews its prices and be telling the truth about three different architectures, only one of which means a human decides anything. The letter asks about the customer data going into the model. It does not ask whether other carriers' non-public data reaches it, and that is the element the court's analysis turned on.
- On July 29, 2026, a Third Circuit panel reversed a Rule 12(b)(6) dismissal and remanded. It made no factual findings, and wrote that at this stage "such level of detail into the software's operations is neither required nor appropriate."
- What the panel treated as probative was not that prices were high. It was the allegation that a common vendor collected non-public commercial information from competing hotels and used the collective pot to suggest prices to each of them.
- Question 8(c) asks what the process is for reviewing the prices an algorithm calculates and who is responsible for it. Question 8(f) asks who decides whether those prices go into effect, or whether they occur automatically.
- Three rungs sit under a truthful yes, and one question separates them: what publishes if nobody acts. Underneath all three is a configuration layer that is not a rung at all, where the floor, the ceiling and the comparison set are chosen.
- 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.
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.
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.
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.
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.
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?
The Government Has Been Writing a Specification, Not a Rule
An enforcement remedy that regulates a price is a judgment about a market. One that regulates a data pipe is a judgment about a mechanism, and mechanisms transfer between industries in a way market judgments do not.
Software & Platforms. Two federal proceedings in twelve months have produced remedies with a similar shape, and a third from 1994 drew the same kind of line. None of them sets the price of the product at issue. All of them specify what may move through a pipe and when. The RealPage judgment, entered on May 19, 2026, bars competitors' non-public data as a live input, permits it in training only when it is at least twelve months old and not drawn from active leases, forbids offering an auto-acceptance feature unless the licensee sets its parameters individually, and requires the controls governing departure to work symmetrically in both directions.
Risk & Compliance. The proposed judgment against Agri Stats, a data consultant serving meat processors, Filed with a court but not yet entered, which is the status of a proposed antitrust consent judgment during its statutory comment period. in May and awaiting court approval, works the same way: reports may not carry recent competitor information, must be aggregated above a minimum group size, and must be offered for sale to anyone rather than to processors alone. The Justice Department's carve-out is the sharpest part of it. Express Markets, Agri Stats' own subsidiary, may keep publishing. Its reports continue, the department said in announcing the settlement, because they are less detailed and are provided to all interested parties rather than only to processors. One company, two product lines, and the line between them is drawn partly on detail and partly on who can see the data.
Thirty-two years earlier, in United States v. Airline Tariff Publishing Co., the department settled a case about airline fare publishing on the same logic. It barred the signaling devices, the first and last ticket dates and the codes that let one carrier's intentions become visible to another, and left automated fare matching entirely alone. The line was information moving between competitors through shared infrastructure, and it has not moved.
The Agri Stats judgment enters stripped of its data-age and aggregation terms, and what survives governs what a report may be sold for rather than what it may carry.
On the architecture side: is the parameter layer where the real decisions are made, and if so, does any disclosure regime reach a decision made before a model runs?
Two Governance Controls Were Recited as Evidence
A control built to demonstrate oversight and a control built to discourage its use look identical in a policy document and opposite in a discovery record. The difference appears only in the telemetry, and telemetry a vendor holds is not a record a client can decide to stop keeping.
Courts & Constitutional Law. Two features designed as governance appear in the Third Circuit's account of the complaint as facts said to support an inference of agreement: an override restricted, as alleged, to times of need and extreme circumstances, and an alleged vendor practice of scoring each client on how often it used that override. What the court leaned on was narrower: overriding required permissions held by select staff.
Risk & Compliance. A compliance function documenting both would have believed it was demonstrating human control. In a pleading they read as evidence the control was nominal. A footnote in the Ninth Circuit case points the same way: overriding required permissions, and the complaint never alleged who held them.
The practical consequence is that the deliverable in this area is not a policy. It is a map of where data goes and a decision about what The records a system keeps about its own use, including who departed from a recommendation and how often. is retained. And because the override scoring in the alleged facts was performed by the vendor, a client cannot resolve it by changing its own retention schedule.
There is a second asymmetry in the same contract, and it is why one review will not cover both exposures. The privacy inquiry wants limits on customer data going out. The antitrust theory wants covenants against competitors' data coming in. An amendment written for one does nothing for the other, and a firm reading only the letter will negotiate the wrong clause.
Our read is that this shifts the compliance question from what a firm can say about its oversight to what its vendor contract lets somebody else record about it. That is a contract question before it is a technology question, and it is answerable this quarter.
The FTC's proposed personalized-pricing statement is adopted in a form that reaches a firm's use of competitors' non-public data, and one instrument covers both directions of the contract.
On the compliance side: if the override telemetry sits with the vendor, what contract term gives a client the right to see, correct or limit what is recorded?
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.
- Controls built to demonstrate oversight were recited as the alleged constraint on it.
- The compliance deliverable is a data-flow map and a telemetry retention decision.
- Vendor-side scoring cannot be deleted by the customer that is being scored.
- The Third Circuit held plaintiffs need not plead how the software works to reach discovery.
- Cert was denied in the Ninth Circuit case on April 20, 2026, before the Third Circuit ruled.
- Two complaints described one product family differently, and no court chose between them.
- A request carrying no subpoena power can still produce a written corporate record.
- A volunteered answer is written in the company's own words, and it chooses which ones.
- Two House inquiries, opposite parties, and only one of them cites any authority to ask.
- A truthful yes about pricing review fits three rungs whose defaults point opposite ways.
- What separates review from ratification is what the system does when nobody acts.
- A federal court has entered a configuration specification for one rental-housing pricing tool.
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.
Every issue
- 01Intersection of the week
- 02Impact of the week
- 03The week in review
Wiiver Weekly
One free email, Saturdays at 7:00 AM ET.
Unsubscribe anytime.
Primary sources27
- United States Court of Appeals for the Third CircuitCornish-Adebiyi v. Caesars Entertainment, Inc., No. 24-3006 (precedential slip opinion)Jul 29Primary · Where Things Stand · What separates reviewing a price from ratifying one? · Two Complaints Described One Product, and No Court Has Decided Which Is Right · Two Governance Controls Were Recited as Evidence · The Weave · Looking Forward
- Third Circuit docket, mirrored by the Free Law ProjectDocket, Karen Cornish-Adebiyi v. Caesars Entertainment Inc, No. 24-3006Aug 6Primary · Looking Forward
- United States Court of Appeals for the Ninth CircuitGibson v. Cendyn Group, LLC, No. 24-3576, 148 F.4th 1069Aug 2025Primary · Where Things Stand · Two Complaints Described One Product, and No Court Has Decided Which Is Right · Two Governance Controls Were Recited as Evidence
- Supreme Court of the United StatesGibson v. Cendyn Group, LLC, No. 25-1109, certiorari deniedApr 20Primary · Where Things Stand · Two Complaints Described One Product, and No Court Has Decided Which Is Right
- Committee on Energy and Commerce, U.S. House of RepresentativesLetter from Ranking Member Frank Pallone, Jr. to eight U.S. airlines on surveillance pricingAug 11Primary · Where Things Stand · What separates reviewing a price from ratifying one? · Two Complaints Described One Product, and No Court Has Decided Which Is Right · The Weave · Looking Forward
- Committee on Energy and Commerce, U.S. House of RepresentativesPallone Presses U.S. Airlines for Answers on Surveillance PricingAug 12Primary · Where Things Stand
- Committee on Oversight and Government Reform, U.S. House of RepresentativesComer Investigates Use of Artificial Intelligence to Set Prices for ConsumersMar 5Primary · Where Things Stand
- Committee on Oversight and Government Reform, U.S. House of RepresentativesLetters from Chairman James Comer to Booking Holdings, Expedia Group, Uber, Lyft and InstacartMar 5Primary · Where Things Stand
- U.S. District Court, Middle District of North CarolinaFinal Judgment as entered, United States et al. v. RealPage, Inc., No. 1:24-cv-00710May 19Primary · What separates reviewing a price from ratifying one? · The Government Has Been Writing a Specification, Not a Rule · The Weave · Looking Forward
- U.S. Department of Justice, Antitrust Division, in the Federal RegisterUnited States et al. v. RealPage, Inc.; Proposed Final Judgment and Competitive Impact Statement, 90 FR 56286Dec 2025Primary · What separates reviewing a price from ratifying one? · The Government Has Been Writing a Specification, Not a Rule
- U.S. Department of Justice, Antitrust DivisionCompetitive Impact Statement, United States v. RealPage, Inc., No. 1:24-cv-00710Nov 2025Primary · What separates reviewing a price from ratifying one? · The Government Has Been Writing a Specification, Not a Rule
- U.S. Department of Justice, Antitrust Division, in the Federal RegisterAmended Complaint, United States et al. v. RealPage, Inc. et al.Dec 2025Primary · What separates reviewing a price from ratifying one?
- M.D.N.C. docket, mirrored by the Free Law ProjectDocket, United States of America v. RealPage, Inc., No. 1:24-cv-00710Aug 12Primary · The Government Has Been Writing a Specification, Not a Rule · Looking Forward
- U.S. Department of Justice, Antitrust DivisionProposed Final Judgment, United States et al. v. Agri Stats, Inc., No. 0:23-cv-03009May 7Primary · The Government Has Been Writing a Specification, Not a Rule · Looking Forward
- U.S. Department of Justice, Antitrust DivisionStipulation and Order, United States et al. v. Agri Stats, Inc.May 7Primary · The Government Has Been Writing a Specification, Not a Rule · Looking Forward
- U.S. Department of Justice, Office of Public AffairsJustice Department Requires Agri Stats to End Exchange of Competitively Sensitive InformationMay 2026Primary · The Government Has Been Writing a Specification, Not a Rule
- D. Minn. docket, mirrored by the Free Law ProjectDocket, United States v. Agri Stats, Inc., No. 0:23-cv-03009Jul 2Primary · The Government Has Been Writing a Specification, Not a Rule · Looking Forward
- U.S. Department of Justice, Antitrust Division, in the Federal RegisterUnited States v. Airline Tariff Publishing Company, et al.; Proposed Final Judgment and Competitive Impact StatementMar 1994Primary · The Government Has Been Writing a Specification, Not a Rule · The Weave
- Federal Trade CommissionProposed Enforcement Policy Statement Regarding Personalized Pricing, File No. P034101Aug 19Primary · What separates reviewing a price from ratifying one? · Looking Forward
- Federal Trade Commission, in the Federal RegisterUnfair or Deceptive Fees in Online Food Delivery Services, advance notice of proposed rulemakingApr 16Primary · What separates reviewing a price from ratifying one?
- California Legislative CounselAB 325, Cartwright Act violations, Chapter 338, Statutes of 2025Oct 2025Primary · Looking Forward · The Weave
- California Legislative CounselSB 763, Chapter 426, Statutes of 2025, amending Cal. Bus. and Prof. Code section 16755Jan 1Primary · Looking Forward
- U.S. Government Publishing OfficeS. 3387, One Fair Price Act of 2025, as introducedDec 2025Primary · Looking Forward
- Congressional Research ServiceCongressional Oversight Manual, Report No. RL30240Mar 27Primary · Where Things Stand · Two Complaints Described One Product, and No Court Has Decided Which Is Right · Looking Forward
- Office of the Law Revision Counsel, U.S. House of Representatives49 U.S.C. section 41713, Preemption of authority over prices, routes, and servicePrimary · Looking Forward
- Federal Trade CommissionFTC Seeks Comment on Enforcement Policy Statement Regarding Personalized PricingAug 19Primary · What separates reviewing a price from ratifying one? · Looking Forward
- U.S. Department of Justice, Antitrust Division, in the Federal RegisterUnited States et al. v. Agri Stats, Inc.; Proposed Final Judgment and Competitive Impact Statement, 91 FR 34512Jun 5Primary · The Government Has Been Writing a Specification, Not a Rule · Looking Forward
Secondary sources, by sector6
- Arnold & PorterLeaving Las Vegas: Third Circuit Breaks From Ninth Circuit Ruling on Algorithmic Pricing ClaimsAug 2026Secondary · Two Complaints Described One Product, and No Court Has Decided Which Is Right
- AxinnWhat Happens in Vegas Stays in Vegas: Third Circuit Parts Ways with Ninth Circuit and Reinstates Atlantic City Algorithmic-Pricing ClaimAug 7Secondary · Two Complaints Described One Product, and No Court Has Decided Which Is Right
- Crowell & MoringRoom Rate Roulette: The Third and Ninth Circuit Wrestle with Antitrust Liability for Pricing AlgorithmsJul 31Secondary · Two Complaints Described One Product, and No Court Has Decided Which Is Right
- Mayer BrownAlgorithmic Price Fixing After Cornish-Adebiyi: The Third Circuit Revives Hub-and-Spoke Claims Against Shared Pricing SoftwareAug 3Secondary · Two Complaints Described One Product, and No Court Has Decided Which Is Right
- SSRN Electronic Journal (unpublished working paper)Electronic Shelf Labels Have Not Led to Surge Pricing in US Grocery Retail, Despite Regulator ConcernsJun 2025Secondary · What separates reviewing a price from ratifying one?
- UC San Diego Today and the Rady School of ManagementNew Research Debunks Fears of Supermarket Surge Pricing with Electronic Shelf LabelsJul 2025Secondary · What separates reviewing a price from ratifying one?