OpenTable's 'system of record' takes effect — and the WA AG is already looking

A reservation tablet on a host stand at dawn, an unopened client agreement folder beside it, a single overhead light cutting across a polished bar.

OpenTable's primary-system mandate switches on today across 60,000 U.S. partner restaurants. The contrarian read: this isn't a product fight anymore, it's an antitrust pressure point — and Washington State's AG has already opened the door to one.

I came into the newsroom before sunrise on a Thursday because today is the day. April 16. The OpenTable client agreement update — twenty-three pages, twelve-month auto-renew default, “primary system of record” language baked into the partner terms — goes live this morning across roughly 60,000 U.S. partner restaurants. By the time the dinner shifts close out tonight, every venue still on the network will have done one of three things: signed through, opted out, or done nothing and accepted by silence. Most will do nothing. That is how these rollouts always work.

The contrarian read I want to mark on the day itself: OpenTable’s April 16 mandate has stopped being a product story and started being an antitrust story, and the trigger date for that shift is not today — it was April 9, when a Seattle Latino Metropolitan Chamber of Commerce letter landed on the Washington Attorney General’s desk and the AG’s office said, on the record, that it would look into it. The reservations market has spent six weeks arguing about whether the rule would land. It has landed. The interesting question now is which regulator picks it up first.

What changes at midnight, and what doesn’t

The mechanics are what they have been since the March 26 partner email went out. Partner restaurants are now required to designate OpenTable as the primary system of record for table management — cover-count attribution flows to OpenTable first, channel-mix obligations cap how aggressively a venue can run a competing book alongside, and the agreement renews on a twelve-month auto-renew default unless a restaurant opts out inside a defined window. The Restaurant Business reporting from late March walked the contract language; the Restaurant Dive desk has a follow-up forthcoming gathering operator response in the days after the switch.

What does not change is the consumer-facing surface. The OpenTable app you open tonight looks identical to the one you opened last night. The 200 authorized partner integrations — including the new ChatGPT booking surface and the Uber Eats reservation handoff — remain in place; the partner roster, as Webpronews summarized this week, is one of OpenTable’s strongest cards heading into the rollout. None of that consumer machinery moves on April 16. What moves is the back-of-house contract, the cover-count plumbing, and the data attribution flowing to Booking Holdings’ parent ledger.

That is the gap I want to underline. The platform did not ship a product change today. It shipped a contract change. The asymmetry tells you what the rule is actually for.

The Wanless letter, and why it changes the frame

On April 9, Marcos Wanless — president and founder of the Seattle Latino Metropolitan Chamber of Commerce — sent a letter to Washington State Attorney General Nick Brown asking the office to examine OpenTable’s updated client agreement under state competition law. The Washington State Standard’s coverage from yesterday is the cleanest write-up. Wanless’s letter argues that the primary-system requirement, combined with the auto-renew default and the cover-count exclusivity, functions as a tying arrangement that disproportionately harms smaller and minority-owned restaurants that lack the legal capacity to negotiate around the boilerplate. The AG’s office told the Standard it would “look into the matter.” That phrasing is procedurally narrow — it is not an investigation, it is the door before the door — but it is on the record, and it is the first U.S. state-level signal that a regulator is reading the contract the way the operator pushback has been reading it.

Mark interpretation here. State AGs are the soft entry point for U.S. competition enforcement against vertical contract terms, and Washington in particular has a track record on antitrust referrals that punches above the state’s market weight. The Wanless letter on its own does not compel a thing. What it does is establish that an operator-side complaint with named plaintiffs and a structured legal argument is now in front of a state enforcement office on day one of the rollout. The reservations market has not had that shape of pressure before. The Resy/Tock merger announcement in February drew operator commentary; the DoorDash-SevenRooms integration build drew partner-side procurement scrutiny. Neither generated an AG letter. This one did, in seven days, before the rule even took effect.

The reservations system that spent the 2010s fighting on diner-network reach and the early 2020s fighting on CRM depth is now fighting on contract terms. That is the shift the reservation wars setup piece I filed on April 6 flagged as the structural read — the rule was data defense, not product offense. Today it gets a second name: it is also a regulatory-exposure surface. The two readings reinforce each other. You only need a contract this tight if your data moat is thinning. You only get an AG letter on day one if the contract is tight enough to look like a tying problem.

What I’m watching this week

Three things to mark between now and Monday. First: operator-side compliance behaviour in the first 72 hours. The honest read of an auto-renew default with a twelve-month tail is that most partner restaurants will simply accept the new terms by silence — not because they love them but because changing reservation systems mid-quarter is expensive and the spring procurement window does not open until late May. The number to watch is not opt-out percentage, which will be small. It is whether the loudest opt-outs cluster in a single metro or across markets. Seattle is the obvious tell, given the Wanless letter.

Second: whether any other state AG matches the Washington signal this week. New York, California, and Massachusetts all have offices that monitor restaurant-tech competition matters; any of them adding a “we are also reviewing” line by Friday would change the regulatory shape materially. None has yet. I am asking.

Third: Booking Holdings’ tone. The parent has been silent through the rollout build. If the day passes with attrition contained, Booking stays silent. If the AG signal spreads or operator press goes louder through the weekend, expect a parent-level statement before next Wednesday.

The rule is on. The system of record is OpenTable, on paper, in 60,000 dining rooms. The interesting fight is no longer at the host stand. It is in Olympia, and wherever the next letter goes.

— Hana edits the newsroom for TableTransfers. Tips: tips@tabletransfers.com.

Featured More

The Voice Agent Maturity Curve

mise

·

12 min read

The Four Margins of a Restaurant

mise

·

14 min read

The AI Premium in Hospitality M&A: Broker Story or Real Number?

the bottom line

·

9 min read

What the DoorDash/SevenRooms Deal Actually Buys

the bottom line

·

11 min read

Browse all 494 posts

Related posts

Toast Quietly Renamed Sous Chef. The Pilot Was the Point.

the pass

·

6 min read

Toast Quietly Renamed Sous Chef. The Pilot Was the Point.

Darden +4.2% comps and the boring Bahama Breeze ending

the pass

·

5 min read

Darden +4.2% comps and the boring Bahama Breeze ending

Bahama Breeze is closing. Darden's portfolio thesis just got tighter.

the pass

·

5 min read

Bahama Breeze is closing. Darden's portfolio thesis just got tighter.