90 incidents on record · 2026 Headlights Incident reports by Ellie Harris · Melbourne
10 new this week Library last updated 13 July 2026
← The incident library
HD-INC-090
Retail & hospitality · United States · 2026 · Opaque AI operations system

A franchisee that runs 111 Pizza Huts is suing the chain for more than $100 million over a mandated AI dispatch system it says let DoorDash drivers cherry-pick orders

By Ellie Harris · Filed Dragontail deployed to the franchisee from 2024; lawsuit filed 6 May 2026

Alleged: Pizza Hut LLC (a Yum! Brands company); Chaac Pizza Northeast LLC (franchisee, plaintiff) developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

A franchisee that runs 111 Pizza Huts is suing the chain for more than $100 million over a mandated AI dispatch system it says let DoorDash drivers cherry-pick orders

What happened

It was reported that on 6 May 2026 Chaac Pizza Northeast, a franchisee operating 111 Pizza Hut restaurants across New York, New Jersey, Maryland, Washington DC and Pennsylvania, filed suit against Pizza Hut LLC in the Business Court of Texas. The franchisee alleges that Pizza Hut breached the franchise agreement by requiring it to adopt Dragontail, an AI kitchen-management and delivery-dispatch system that Pizza Hut’s parent, Yum Brands, acquired in 2021, without accommodating the fact that Chaac relies on DoorDash for its delivery drivers. According to the complaint, Dragontail gave those third-party drivers visibility of order and tip information and let them choose which orders to take, so more profitable orders were claimed quickly while others sat waiting, in some cases more than fifteen minutes, leaving food to cool.

It was then reported that the franchisee alleges the effect on service was severe: delivery times, it says, rose from under thirty minutes for about ninety per cent of orders to forty-five minutes or more for half of them, and it links the change to falling sales, claiming that year-on-year revenue growth in New York went from around ten per cent before the system was deployed to around minus ten per cent afterwards. It also alleges Pizza Hut now holds the national contract with DoorDash, which it says removed its ability to manage or communicate with the drivers delivering its orders, and that Pizza Hut did not properly train its operators on the system or answer their requests for support. It is seeking more than $100 million for lost business and enterprise value. The company did not comment on the litigation, saying it does not discuss pending legal matters. These are the franchisee’s allegations, untested in court, and the case turns in part on a question that is hard to answer from the outside: what the system was actually doing, order by order, and whether anyone running the restaurants could see it or change it.

What an auditable version would have shown

All of it comes back to what Dragontail actually did, and who could see it. The franchisee says it showed tip amounts to DoorDash drivers and let them pick the best jobs. Pizza Hut has not answered that publicly, and from the outside there is no way to know. A dispatch system can be built to record what it offered each driver, what those drivers could see, and who was able to overrule it. A record like that would not decide who is right about the contract, but it would make the software’s behaviour something both sides could examine rather than something each of them describes differently.

Where the gap was

As the franchisee tells it, it was made to run its restaurants on a system it did not choose, that system showed order and tip details to outside drivers, and when its operators asked for training and support they did not get it. A ConstraintGate holds the rules such a system has to follow, what it is allowed to show and to whom, so that putting tip details in front of outside drivers, if that is what happened, would need someone to sign off on it rather than happening by default. A ConductRecord keeps what the system showed and did, order by order, so that its effect on a store is something the people answerable for that store can look at rather than argue about afterwards.

What governance should have looked like

When a business is made to run on an automated system, the people answerable for it need two things: to see what it is doing, and to be able to step in when it goes wrong. Without the first, trouble only shows up in the numbers, a quarter of falling sales, long after it could have been caught. Without the second, they can watch it go wrong and still not be able to stop it. Best practice would be for an operations system like this to show, on the record, what it is doing and what it is sharing, and to leave a person with the authority to override it, so whoever is carrying the risk can see how it is behaving and fix it, rather than find out at the end of the quarter.

Failure Pattern: an operator was required to run its business on an automated system it did not control, and says it could not get the information or support to correct what the system was doing.

Governance Principle: an automated system that controls operations should expose what it is doing, and to whom, on the record, and let an authorised human override it.

The reference implementation of ConstraintGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

No tracking. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Pizza Hut LLC (a Yum! Brands company); Chaac Pizza Northeast LLC (franchisee, plaintiff) could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

Last reviewed June 2026. This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →