The reservation wars enter Round 4: setting up OpenTable's April 16 deadline

I came into the newsroom on a quiet Monday with one date circled on the whiteboard: April 16. That is the Wednesday OpenTable’s new policy turns on — the one requiring partner restaurants to make OpenTable their primary reservations system, with cover-count and channel-mix obligations attached. Ten days out, the vendor inboxes are filling up with “what this means for you” notes, and three of OpenTable’s four competitors have spent the last six weeks repositioning around the assumption that the rule will land essentially as drafted. It will.

The contrarian read I want to mark before the deadline week absorbs the cycle: OpenTable’s April 16 mandate is a data-defense move, not a product move, and once you read it that way the whole four-way structure of the 2026 reservations market clicks into place. The features OpenTable has shipped this quarter are incremental. The policy change is structural. A platform confident in its product roadmap would not need a rule that forces restaurants to send it their cover counts first.

The four-way board, as of this morning

Start with the scoreboard. OpenTable carries roughly 60,000 restaurants on its network — the legacy incumbent number, broadly stable through the past year. Resy, post the Resy/Tock merger American Express announced on February 24, now sits at about 25,000 venues, having absorbed Tock’s wine-country and tasting-menu book under one roof. AmEx had bought Tock from Squarespace for $400 million in an all-cash deal back in June 2024; the February announcement folded Tock’s product into Resy’s American Express-funded distribution. SevenRooms is inside DoorDash following the $1.2 billion acquisition that closed last year, giving the combined entity a delivery-plus-reservations stack that no one else can match — DoorDash carries 67% of U.S. third-party delivery (Bloomberg Second Measure, March 2024), and SevenRooms is the CRM layer it can now bolt to that order flow. Yelp Guest Manager is the fourth seat at the table, smaller in restaurant count but with the only top-of-funnel discovery surface that rivals Google’s.

That is the four-way board. Now read OpenTable’s April 16 rule against it.

The Restaurant Business piece from March 24 walked the mechanics: partner restaurants will be required to designate OpenTable as primary, with cover-count attribution flowing there first and channel-mix obligations that cap how aggressively a venue can run a competing book alongside. The trade-press framing has been about whether this is enforceable — it is, contractually — and whether it will trigger operator complaints. It already has. A Seattle business-leader pushback is forthcoming through the state press later this month, and operator Slacks have been live with it since the policy memo dropped two weeks ago.

The product question the rule does not answer is: why now, and why this lever? OpenTable’s AI booking and discovery work that shipped with the Booking.com integration is real and incremental — better recommendation surfaces, marginal consumer-app improvements. None of it is the kind of step-change that compels a restaurant to deepen its commitment to a single platform. The April 16 rule does that compelling on the platform’s behalf. It substitutes contractual exclusivity for product gravity.

Why “defending data” is the right frame

Mark interpretation here. The asset OpenTable has that no competitor can easily replicate is two decades of structured cover-count and channel-mix data across 60,000 venues. That data underwrites the rate-card, the discovery surface, and every conversation with Booking Holdings about OpenTable’s place in the parent’s portfolio. The threat to that asset, post the Resy/Tock merger and post the DoorDash commerce stack expansion, is not that competitors will ship better consumer apps. It is that they will peel off enough cover-count attribution that OpenTable’s data moat thins year over year.

The April 16 rule does one specific thing: it ensures that for 60,000 partner restaurants, OpenTable remains the system of record. It does not improve the consumer experience. It does not ship a new feature. It defends the data asset against the structural fact that AmEx now controls 25,000 venues of premium-end cover data and DoorDash controls SevenRooms’ enterprise CRM book end-to-end.

A platform confident its product would keep restaurants as primary by gravity alone would not need the rule. A platform reading the four-way board and recognising gravity is no longer enough would need exactly this rule, on exactly this timeline. That is the tell.

What I’m watching through Wednesday

Three things to mark between now and April 16. First: the operator-side compliance reaction. The OpenTable Vibe Check I filed last Wednesday ran partner sentiment ahead of the rule landing; the question for this week is whether operators quietly running a secondary book on Resy or SevenRooms move that book to primary on OpenTable, or drop OpenTable to preserve flexibility. Both happen at the margins. The net direction is the story.

Second: Resy/Tock and SevenRooms-inside-DoorDash counter-positioning. Both have an obvious opening to pitch themselves as the “no exclusivity required” alternative this week. Whoever ships that pitch cleanly between now and Wednesday wins the spring procurement cycle for any restaurant on the fence.

Third: Booking Holdings’ silence or non-silence. The parent has been quiet through the rollout. If the rule lands cleanly and attrition stays contained, Booking stays quiet. If attrition is meaningful in week one, expect a parent-level statement by the following Monday.

Round 4 is a data fight dressed as a policy change. The April 16 rule is the move. The next ten days are how we find out whether it holds.

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