The Reservation Wars, Mapped: What Each of the Three Stacks Actually Owns
CNBC ran the consumer cut on the DoorDash–SevenRooms, Uber Eats–OpenTable, and AmEx–Resy/Tock stories this morning. Here's the operator-side map: who owns what, where the integrations actually live, and how to pick.
It’s Wednesday morning and the CNBC piece is on the second tab. I filed the AmEx/Tock–Resy read yesterday, and the version of the story running in the consumer wires today is the version operators have to translate. CNBC frames it as a “wars” piece — three stacks, three corporate parents, three checkout buttons your guests will see at the bottom of a confirmation email. That’s the right map for diners. It’s the wrong one for the people running the floor.
The operator question isn’t who wins the consumer flow. It’s who owns what’s under the floorplan view, which POS the guestbook actually talks to, and which delivery-marketplace fee table the booking is sitting next to in the same parent-company P&L. Here’s the version I’d hand a multi-unit director picking a stack this quarter.
DoorDash–SevenRooms: the CRM-first stack
What DoorDash bought when it closed the SevenRooms deal for $1.152 billion is not, primarily, a reservations book. It’s a CRM. The SevenRooms press release lists the surface in order: CRM and guest experience, reservations and waitlist, marketing automation, revenue management, reputation, table management, online ordering, events, voice AI. The grid is one of nine product surfaces. The data layer is the asset.
The customer-mix tell is in the same release: 13,000-plus venues across “dining, hotel F&B, nightlife and entertainment,” with Marriott, MGM, Nobu, and Dishoom as references. That’s an enterprise-skewed book — hotel groups, multi-unit fine dining, hospitality conglomerates. POS-agnostic by design, because enterprise hospitality doesn’t standardize on a single POS.
Operator read: pick this stack if your CRM is your asset, your group runs more than one concept on more than one POS, and you’d rather own a guest-data layer than a booking-flow conversion rate. The DashPass surface is the upside option. The CRM is what you’re paying for.
AmEx–Resy/Tock: the Toast-wired stack
Tock folds into Resy this summer per Restaurant Business’s read on the merger. The combined platform clears 25,000 venues. AmEx now owns Resy (2019), Tock (2024), and the Rooam middleware. The integration tell the consumer pieces don’t lead with is the Toast partnership — Resy guestbook data piping into Toast handhelds so a server reading the table sees wine preference and birthday notes in the same view as the order screen.
That’s a wired stack. If your POS is Toast, the friction between reservation, seating, and check is the lowest in the category. If your POS is anything else, the integration is shallower and the value of the AmEx-cardholder demand layer has to carry more of the case on its own. Tock’s pre-paid bookings and tiered-experience features survive the transition; the standalone Tock site and app shut down.
Operator read: pick this stack if you’re on Toast, your guest base over-indexes on AmEx cardholders, and you want the booking-to-check loop closed inside one vendor’s integration story. The summer cutover is the date to plan around.
Uber Eats–OpenTable: the supply-side stack
OpenTable’s distribution moat is still the largest of the three — over 60,000 venues globally, per the same Restaurant Business piece. The Uber partnership turns Uber Eats into an additional supply surface for OpenTable inventory, not a new booking platform. Booking Holdings still owns OpenTable; Uber gets to surface reservations next to delivery in the same app. The AI strategy underneath OpenTable is the Booking Holdings playbook running in a restaurant-shaped lab.
Operator read: pick this stack if reach is the thing you’re optimizing — most search-engine demand, most Uber-app demand, the broadest cover-fee economics. The product depth is shallower than SevenRooms’ CRM or Resy’s AmEx-cardholder demand. The volume is the moat.
How to pick
Three questions, in order. One: what’s your POS? If Toast, the AmEx stack’s integration value is the highest. If anything else, the SevenRooms data layer or the OpenTable volume play are the live options. Two: what does your guest base over-index on — AmEx cardholders, DoorDash subscribers, or open-web search demand? That picks the demand-side parent. Three: are you paying for a CRM or for a booking funnel? SevenRooms is the first; OpenTable is the second; Resy under AmEx is becoming both, on a Toast-shaped subset of the market.
The CNBC piece runs the consumer cut today. The operator cut is that the three stacks are not, anymore, substitutes for each other. They’ve specialized — by POS, by demand surface, by what they own under the floor. Pick on what you actually need.
— Maya covers restaurant tech for The Pass. Tips: maya@tabletransfers.com.
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