Desk Review: OpenTable's 'System of Record' — what restaurants are actually agreeing to on April 16

It is Wednesday morning and I am sitting at a host stand in a restaurant that does not open for another four hours, with a printed copy of the new OpenTable client agreement on the bar pass and the operator’s laptop open to the same document on screen. The operator is in the office doing a beverage count. We have been promising each other we would read this thing line by line since the email landed in his inbox on March 26. The document is twenty-three pages with appendices. The cover note says the new terms become effective on April 16, 2026, two weeks from today. The operator runs four units across two metros — three on OpenTable, one on Resy — and he has been told, in friendly terms, that he needs to make a decision about the fourth.

This is the desk review I have been wanting to write since the Restaurant Dive story broke on March 26. The contrarian thesis I want to mark up front, before I get into the contract language: this update is not, in product terms, about bad actors gaming the system. It is about defending OpenTable’s diner-data position against the Resy/Tock merger Pablo Rivero announced on February 24 and against SevenRooms-inside-DoorDash. The “system of record” language is the operator-facing surface of a competitive-defense move.

The scene at the host stand

The operator’s email from his OpenTable account manager landed March 26 at 4:11 PM Eastern. Subject line: “Important updates to your client agreement, effective April 16.” Three paragraphs, friendly in tone. The first thanked him for being part of the global network of more than 60,000 OpenTable restaurants. The second introduced the new “primary table management system” requirement. The third mentioned, in a sentence so short you could miss it on a first read, that the agreement now defaults to a 12-month auto-renewal term unless the operator opts out in writing thirty days before renewal.

The operator’s first read took ninety seconds. He registered the “primary system” change, dismissed it as not applying to him, and missed the auto-renew clause entirely. He is not unusual. Two other operators I have spoken with this week had the same first read. The trade-press coverage has surfaced both changes; the operator-facing email surfaces the first one and buries the second.

So we sat down on Wednesday morning with the PDF and we read it. Twenty-three pages. Two hours. By the end of it the operator had circled four clauses with a black ballpoint pen and put question marks next to three more, and we had a different conversation than the one he had been planning to have with his account manager on Friday.

What the contract actually changes

The substantive change in the new agreement, in plain language, is that OpenTable now requires participating restaurants to operate the platform as their primary table management and reservations system. The Restaurant Dive write-up lays out the operative language and the Restaurant Business piece from March 24 covers the same ground from a different angle.

The “primary system of record” clause is the headline. In operator-facing terms, a restaurant on OpenTable must use OpenTable to manage all of its bookable inventory, must not hold inventory back to route to a competing platform, and must operate OpenTable as the canonical view of its reservations book rather than as one of several parallel books. The clause does not, on a careful read, prohibit a restaurant from also being on a second platform. What it prohibits is a configuration in which OpenTable is one of several equally-weighted systems and inventory is partitioned across them.

The line between “primary system” and “exclusive system” is genuinely fuzzy in practice. If you hold back twenty percent of prime-time inventory for direct bookings managed in a SevenRooms or Tock instance, does that violate the new clause? OpenTable’s account-manager talking points say no. The contract language says it depends on whether the secondary platform is “operating as a parallel reservations system” or as a “guest-relationship or marketing tool.” That distinction gets argued about in enforcement rather than at signing.

The second substantive change, less covered in the trade press but more consequential, is the shift to a 12-month auto-renewal default. Under the previous agreement, OpenTable contracts were month-to-month with thirty-day termination notice. Under the new agreement, signing or remaining on the platform past April 16 enrolls the restaurant in a twelve-month term that auto-renews for successive twelve-month terms unless the restaurant gives written notice of non-renewal no fewer than thirty days before end of term. The first auto-renewal window for a restaurant that enrolls April 16 would be April 16, 2027, with notice due by March 17, 2027.

I want to mark this as interpretation: the auto-renew default is the real tell of what this update is for. A “system of record” clause without a term commitment is renegotiable. A “system of record” clause backed by a twelve-month auto-renewing term compounds. For an operator weighing whether to add Resy or Tock as a parallel system, the cost of being wrong has gone from “thirty days” to “thirteen months.”

The third change worth flagging is a tightening of the data-portability language. The agreement retains the operator’s right to export their guest list at end of term. What is new is the language around use of OpenTable-sourced reservation data within third-party CRM and marketing tools during the term. The clause is narrower than the trade-press headlines suggest — it does not prohibit syncing OpenTable bookings into Mailchimp or HubSpot — but it does narrow the use cases in which OpenTable-sourced data can power campaigns that route bookings away from OpenTable.

The auto-renew default is the real tell

I want to spend a beat on the auto-renew clause because it most clearly tells you what the document is for.

If the update were primarily about cleaning up enforcement of a system-of-record norm that has been informally understood for years, the contract change would have been the “primary system” clause and nothing else. The term structure would have stayed month-to-month and the operator base would have read the change as housekeeping. That is not what happened. The auto-renew default converts a category in which operators have been able to multi-home cheaply into one in which multi-homing carries a real switching cost, and the switching cost is now in a public, machine-readable contract clause rather than in a back-and-forth with an account manager.

Read against the Resy/Tock merger, the auto-renew clause is doing a specific competitive job. Pablo Rivero, now CEO of the combined Resy and Tock entity and SVP, Head of American Express Global Dining, positioned the combined platform as “the singular app for the best culinary experiences used by the hospitality world’s most ambitious operators.” That framing — Resy as the destination platform for ambitious-operator restaurants — is a direct strategic threat to OpenTable’s most valuable segment: the high-cover-spend, marketplace-discovery-resistant fine-dining tier. OpenTable loses share in that tier because operators do not need the OpenTable marketplace to fill their books and resent the cover fee they pay for diners they would have gotten anyway. The merger consolidates the threat. The auto-renew default raises the cost of acting on it.

That is the strategic logic, marked plainly: the system-of-record clause is the surface, the auto-renew default is the lock, and the competitive defense is what the lock is for.

The operators pushing back

The trade-press coverage has surfaced two named operators objecting. I have spoken with three more this week who I will not name because they are still in active negotiations.

Byron Puck of the Wolfgang Puck Fine Dining Group is the most prominent named objector. The group operates fine-dining concepts across multiple US markets — Spago, Cut, the Wolfgang Puck Bar & Grill formats, the Vegas and entertainment-district concepts that anchor volume — and has historically run a mixed stack with OpenTable as the marketplace-discovery layer and a direct-booking and CRM layer on a separate platform. The mixed stack is the point. The new “primary system” clause threatens it, and the auto-renew default raises the cost of switching if enforcement turns out to be aggressive.

Rebecca Levine-Hough of Altamarea Group, which operates sixteen concepts globally and seven in the US, has been similarly pointed. Altamarea’s portfolio — Marea, Ai Fiori, the Osteria Morini and Vaucluse formats, the international outposts — is the kind of fine-dining base where OpenTable’s marketplace-discovery value is real but bounded, and where multi-homing has been a meaningful piece of the operator playbook. Levine-Hough’s objection is framed around operator optionality, which I read as code for “we want to keep the threat of switching credible.”

Both objectors operate from the same structural position: high-cover-spend, fine-dining-anchored portfolios that derive bounded value from the OpenTable marketplace and meaningful value from the option to multi-home. The new agreement raises the cost of multi-homing without raising marketplace value to this segment. The pushback is not about whether OpenTable is a good product. It is about whether the new terms accurately price the value the platform delivers to this operator profile. I read the framing as substantively correct and tactically loud — they are negotiating in the trade press because that is one of the few places they have leverage.

The antitrust dimension

The harder question, and the one the trade press has been gentler on than I think it should be, is whether the new agreement raises an antitrust exposure that OpenTable’s legal team has signed off on but a regulator might not.

OpenTable is the dominant US restaurant reservations platform. The 60,000-restaurant global figure includes meaningful international footprint, but in the US the platform’s share of the restaurants-that-take-reservations universe is, by any reasonable estimate, north of half. A primary-system clause from a platform with that kind of share is a different artifact than the same clause from a platform with twenty percent share. The exclusivity-adjacent framing — “primary” rather than “exclusive,” but with terms that make multi-homing materially more expensive — is the kind of structure that has, in other categories, drawn antitrust scrutiny under both Section 1 and Section 2 theories.

I am not a lawyer and I am marking this as a category-level concern rather than a prediction. The combination of a dominant platform, a primary-system clause with practical-exclusivity effects, and a twelve-month auto-renewing term structure is the kind of combination that gets a second look. Whether the second look produces an enforcement action is uncertain. That the second look is plausible is not.

The operator-facing implication is real but indirect. If the clause survives regulatory scrutiny, operators who sign in 2026 are signing into a category structure that consolidates further. If the clause is challenged and narrowed, operators are still bound by the contractual terms until those terms are modified by court order or settlement. The optionality risk runs in one direction: the cost of being wrong is borne by the restaurant, not by OpenTable.

The competitive frame: four platforms, four theories

The OpenTable update does not happen in a vacuum. The four major US-relevant reservations platforms — OpenTable, Resy plus Tock, SevenRooms (now a DoorDash subsidiary), and Yelp Guest Manager — are each pursuing a distinct strategic theory of what a reservations platform is for.

OpenTable, with this update, is declaring itself the system of record for the operator’s bookable inventory. The theory is that the platform’s value is the canonical reservations book and the diner-side marketplace that fills it. The new agreement makes that theory contractually binding, and it dovetails with the OpenTable AI-and-booking roadmap I will be returning to in a forthcoming review. The strategic logic is diner-data defense against the Resy/Tock consolidation and against the DoorDash-led delivery-adjacent CRM stack.

Resy plus Tock, post-merger, is declaring itself the destination platform for the fine-dining and ambitious-operator tier. Rivero’s “singular app for the best culinary experiences” is the theory in one sentence. The strategic logic is that the high-cover-spend tier is the most defensible segment of the category. The Amex-Global-Dining anchor is the consumer-side reach that monetizes the theory.

SevenRooms, as I argued in the companion Vibe Check on March 18, is increasingly a frontend for delivery-led marketing automation. The theory is that the most valuable diner-data asset is the unified profile that crosses on-premises and off-premises behavior, and that a reservations platform owned by the dominant US delivery aggregator is uniquely positioned to construct it.

Yelp Guest Manager has the most distinctive theory of the four and gets the least trade-press coverage. The theory is that a reservations platform should be the operations layer behind the dominant local-discovery surface, and that the value is the inbound flow it sources rather than the depth of the CRM. The product is competent and the price point is the lowest of the four.

Read in this frame, the OpenTable update is OpenTable defending its theory against the three other theories. The system-of-record clause is operator-facing. The auto-renew default compounds. The diner-data clauses are aimed at the Resy/Tock and DoorDash/SevenRooms platforms specifically.

The scorecard

I want to put numbers on the four platforms with the standard Vibe Check caveat: this is a desk scorecard from the operator-vendor-evaluation side, not an audit of every feature. Categories are operator-relevant. Interpretation is marked where I am marking it.

Marketplace-discovery value to a US operator (1 to 5):

• OpenTable: 4.5 — the largest diner-side marketplace in the US category by reach. Marketplace value is highest for casual-to-upscale operators in marketplace-discovery-dependent geographies and lowest for fine-dining-anchored portfolios in destination markets.
• Resy plus Tock: 4.0 — the marketplace is smaller than OpenTable’s by reach and meaningfully more concentrated in the high-cover-spend tier, which for the right operator profile is more valuable per cover than OpenTable’s broader reach.
• SevenRooms (DoorDash): 3.0 — the consumer-facing marketplace is the DoorDash Reservations surface, which is younger and less marketplace-deep than OpenTable or Resy. For delivery-leaning operators the cross-channel value is real.
• Yelp Guest Manager: 3.5 — the Yelp discovery surface is the value, and for operators in geographies and segments where Yelp is a primary inbound channel it is non-trivial.

Contract flexibility post-April-16 (1 to 5, higher is more flexible):

• OpenTable: 2.5 — the new primary-system clause and the twelve-month auto-renew default narrow operator optionality materially. The export rights at end of term are retained; the cost of getting to end of term is higher than before.
• Resy plus Tock: 3.5 — post-merger terms are still settling. The Amex-anchored framing has historically been more operator-friendly on term structure than OpenTable’s new posture.
• SevenRooms (DoorDash): 3.0 — terms are now structured to support the bilateral data-enrichment roadmap; data-rights and exclusivity clauses warrant a careful read.
• Yelp Guest Manager: 4.0 — month-to-month terms remain the default and the contract structure is the lightest-touch of the four.

Diner-data-defense posture (1 to 5, higher is more operator-aligned):

• OpenTable: 3.0 — the new clauses defend OpenTable’s data position; the operator’s data position is preserved on the export-rights dimension and narrowed on the in-term-use dimension. Interpretation, marked.
• Resy plus Tock: 3.5 — the Amex anchor and the high-cover-spend operator focus produce a more operator-aligned posture in practice than the contract language alone reveals.
• SevenRooms (DoorDash): 2.5 — the bilateral data-enrichment roadmap is value for some operator profiles and risk for others. I argued this at length in the March 18 companion piece.
• Yelp Guest Manager: 3.5 — the platform’s diner-data ambitions are bounded by the reservations-product scope and the Yelp parent’s broader data posture rather than by a delivery-aggregator parent.

Best-fit operator profile:

• OpenTable: large-marketplace-dependent casual-to-upscale operators in major US metros who derive meaningful cover value from the OpenTable consumer side.
• Resy plus Tock: fine-dining-anchored portfolios and ambitious-operator concepts where the Amex Global Dining tie-in monetizes the diner relationship.
• SevenRooms (DoorDash): delivery-leaning multi-unit casual operators and hotel F&B groups for which the unified profile is structurally valuable. See the March 18 piece for the long-form argument.
• Yelp Guest Manager: small-and-medium independent operators who derive their inbound flow from Yelp and who want a competent reservations layer behind it.

I do not weight these to a single composite number. Operator weights vary. The scorecard is a starting point for your own evaluation, not the endpoint.

The bet: what to do before April 16

If you have read this far you want to know what I would actually tell my operator at the host stand. So here it is, partitioned by operator profile.

If you are a casual-to-upscale operator in a major US metro that derives meaningful cover value from the OpenTable marketplace and you are not actively multi-homing today: read the agreement carefully, sign through inaction if you have decided you are going to stay on OpenTable for the next year regardless, and put a calendar reminder on your phone for March 1, 2027 with a subject line that says “OpenTable auto-renew opt-out window opens in two weeks.” The new terms are largely consistent with how you were already operating. The auto-renew default is the part you should know about. The system-of-record clause is the part that does not change your practice.

If you are a fine-dining-anchored portfolio that has been multi-homing across OpenTable and Resy or Tock: the decision is genuinely hard and you have two weeks to make it. The case for sticking with OpenTable is the marketplace reach. The case for shifting to Resy-plus-Tock as your primary platform is the Amex-Global-Dining anchor, the high-cover-spend operator focus, and the contract-flexibility position post-merger. The case for staying on both is now meaningfully more expensive than it was a month ago. My read, marked as interpretation: if your portfolio is two-thirds or more fine-dining and you have a credible Resy-or-Tock relationship today, this is the right moment to make Resy-plus-Tock your primary system and let OpenTable revert to a secondary marketplace-discovery channel, taking the cost of the partition rather than locking into the new OpenTable terms for thirteen months.

If you are a delivery-leaning multi-unit casual operator or a hotel F&B group that is already on SevenRooms: the OpenTable update probably does not change your stack materially. Your primary reservations system is already SevenRooms or another platform; OpenTable, if you are on it, is operating as a marketplace-discovery channel and the new primary-system clause is, depending on how aggressively it is enforced, either tolerable as a friction or a reason to drop OpenTable from your stack entirely. The companion question is whether the SevenRooms-side roadmap is going in a direction your business wants to go in; that is a different question for a different review.

If you are a small-or-medium independent operator considering Yelp Guest Manager: the OpenTable update arguably makes Yelp Guest Manager a more attractive entry-level option than it was a month ago. The contract-flexibility position is the strongest of the four and the price point is the lowest. The marketplace value is geography-dependent and bounded. If your business needs are bounded and your geography is right, this is a reasonable place to land.

The watch item across all four profiles: the next two pieces of trade-press coverage to watch are (a) any FTC or state-AG signal on the system-of-record clause in the next ninety days, and (b) the first round of operator-level enforcement actions OpenTable takes under the new clause once it is in effect. Both will tell you more about how the new agreement actually operates than the contract language itself does. I will return to this in a follow-up review at the end of Q2 and again at the end of the year.

I am closing the laptop now. The operator is back at the host stand, his coffee is cold again, and he is squinting at the calendar on his phone. He has decided to ask his account manager on Friday for a written commitment that the primary-system clause will not be enforced against his fourth unit’s existing Resy configuration through the end of 2026, and to put that commitment in writing as a side letter to the new agreement. He has also decided to put a calendar reminder on for March 1, 2027. He has not decided what he will do if the account manager declines the side letter, and he does not have to decide that today.

April 16 is in two weeks. The new terms are written down. The auto-renew clock starts the moment you sign through inaction. Read the agreement. Mark your calendar. Make the bet that fits your portfolio. The decision compounds for thirteen months either way.

— Sofia leads Vibe Check vendor reviews for TableTransfers. Tips: vendors@tabletransfers.com.