Desk Review: SevenRooms After Six Months Inside DoorDash

I spent Tuesday morning on the floor of my home office with two browser windows open. On the left, the DoorDash investor-relations page and the SevenRooms product pages. On the right, a notebook where I’d written one question across the top: six months in, has the data layer actually fused? The DoorDash acquisition of SevenRooms closed on June 13, 2025. It is now mid-January 2026. That is enough time for a serious integration team to have shipped the foundation of a unified guest record. It is not enough time for the platform to be done. Where on that curve is the actual delivered work?

I want to answer that with the public record, and I want to be honest about what the public record can and cannot tell me.

Methodology, openly

This is a Desk Review. Vibe Check’s normal format puts four to six operators on a vendor for thirty days and reports what we saw. We have not done that here, for a specific reason: the integration in question — the handoff between DoorDash’s delivery data graph and SevenRooms’ dine-in guest record — is an internal data-plane question. No single operator can see the inside of it. They can see what shows up in their SevenRooms back-end and what shows up in the DoorDash merchant portal. They cannot see whether the underlying records are unified, shadowed, joined, or running in parallel.

So I’m doing the next-best thing. I’m reading the DoorDash IR communications since close, SevenRooms’ product pages, and the trade press from June 2025 forward. I’m running five operator-setup scenarios against the public commitments and asking, for each, is the handoff real, partial, or aspirational? And I’m marking my confidence on every claim. Where I make a judgment call, I flag it. Where there’s a load-bearing number, there’s a link. We’ll come back with an operator panel when the install base has stabilised enough to make one informative.

What the deal promised

Go back to the June 13 close announcement. The promise — phrased carefully by both sides, because both sides were lawyers-up at that point — was that the combined entity would give restaurants “the tools to own their guest experience, grow their customer base, and thrive both inside and outside their four walls.” That’s Joel Montaniel, SevenRooms co-founder, in the DoorDash press release marking close (DoorDash, June 13, 2025). Parisa Sadrzadeh, DoorDash VP of strategy and operations, framed the same point from the buyer side: “We’re building a platform that makes it easier for local businesses to grow — whether that’s through delivery, pickup, reservations, or in-person hospitality.”

Notice what these two statements do and don’t say. They commit to combining the two product surfaces — delivery, pickup, reservations, hospitality — under one platform. They do not commit to unifying the underlying guest record. That distinction is the entire desk review.

A combined platform can mean a single login, a single ads buyer, a single rev share. It is a commercial integration. A unified guest record means that the diner who ordered from your restaurant on DoorDash last Tuesday and made a Friday reservation through your SevenRooms widget is one record in the operator-facing system, with both behaviours visible, tagged, and addressable. That is a data integration. Commercial integrations happen in months. Data integrations of this shape — across two organisations, two security postures, two consent regimes, two PII frameworks — typically take 18 to 36 months to do honestly. Anyone who has done one knows this.

So the question at six months is not “is it done?” It is “what’s the shape of the data work that’s been done, and is it tracking toward the unified record, or is it tracking toward something else?”

What’s shipping on the surface

The most visible product surface is DoorDash Reservations, which DoorDash launched into major US cities in the back half of 2025. SevenRooms confirms on its own product material that it powers DoorDash Reservations and notes the offering is “currently available in major cities across the U.S. and Australia but still expanding.” That is meaningful on two counts. First, the integration is one-directional in the most obvious sense: SevenRooms is the back-end, DoorDash is the front-end consumer surface. The guest-facing brand is DoorDash. The operator-facing system of record is SevenRooms. Second, the choice of US-and-Australia for the initial geographies makes sense — Australia is a DoorDash-strong delivery market post the Wolt arc, and SevenRooms has a real Australian presence through its hospitality customer base.

The other visible product surface is on the operator side: SevenRooms restaurants that opt in get reservations sourced through the DoorDash consumer app routed to their SevenRooms host stand. That handoff is, in practice, a booking-flow integration: DoorDash captures the diner intent, hands the reservation to SevenRooms, the host-stand workflow proceeds as normal. Operators I’ve spoken to off the record describe the booking-flow integration as functional and uneventful, which is the right outcome at this stage. A reservations integration that works invisibly is what you want.

So far, so unsurprising. What about the data?

The unified-diner-record question

This is the hard part. Here is what we can say with high confidence on the public record:

• SevenRooms powers DoorDash Reservations as a back-end (SevenRooms product page, current).
• The reservation flow from the DoorDash consumer app deposits the booking into the operator’s SevenRooms back-end (same source).
• Operators on SevenRooms can see the inbound reservation channel — i.e., they can see that a given reservation came in via DoorDash — and can run the guest CRM workflow against it (SevenRooms platform documentation, public).

Here is what we can say with medium confidence:

• The integration roadmap, as flagged by Sadrzadeh in May 2025 interviews and reiterated in the close materials, targets a unified consumer record across delivery, pickup, and reservations as the longer-arc outcome (DoorDash, June 13, 2025).
• DoorDash leadership has consistently framed the SevenRooms purchase as the marketing/CRM extension of the DoorDash commerce platform — “marketing as a service” was Tony Xu’s framing on the Q1 2025 call — which implies a strategic intent to merge consumer-level identifiers across the two systems over time. See our prior DoorDash/SevenRooms Bottom Line read for the strategic logic.

Here is what we can say with low confidence, and where the desk review hits its limit:

• Whether the unified diner record is live today in the operator-facing tooling. As of this writing, there is no DoorDash IR communication, SevenRooms product page, or trade-press confirmation that an operator on SevenRooms can see the full DoorDash delivery history of a guest who walks in for a reservation. The promise is consistent. The shipped product surface is, as best I can tell from outside the company, not yet that.
• Whether the data flow is bilateral. The reservation-flow integration appears one-directional today: DoorDash hands reservations to SevenRooms. The reverse flow — SevenRooms guest data enriching the DoorDash consumer profile — has been publicly discussed as a roadmap item and not, on the public record, shipped as an operator-visible feature.
• Whether the legal-and-consent layer that a true unified record requires has been substantively completed. This is the hardest one. Different jurisdictions, different consent capture flows on the two sides, different data-rights clauses in the two sets of operator contracts. The work is real and largely invisible.

If you are a SevenRooms operator asking your account rep “when will I see my DoorDash delivery customers in my SevenRooms guest list?”, the honest answer in January 2026 is: the platform doesn’t show you that today, the roadmap commits to it, and we don’t have a public timeline. If your account rep gives you a more confident answer, ask them to put it in writing.

Five operator setups — running the handoff

I want to test the integration against five concrete operator setups. Each one is the kind of operation that would, in theory, get the most out of a unified diner record. For each, I’m asking: does the handoff between delivery and dine-in actually do useful work today, or is it still pre-fused?

Setup one: an urban casual concept doing 50/50 delivery and dine-in

This is the steel-man case for the integration. Half the revenue comes through DoorDash delivery. Half comes through the dining room. The operator’s marketing team wants one view of the guest.

What works today: the operator can opt in to DoorDash Reservations and source incremental reservation volume from the DoorDash consumer surface at zero cover fee. That is a real economic benefit and, in the launch markets, a real customer-acquisition lever.

What doesn’t work today: the operator cannot see, in their SevenRooms guest CRM, the delivery history of a given guest. The two views remain separate logins, separate dashboards, separate behaviour graphs. Confidence: high on the gap. The unified-view question is the entire premise of the deal, and there is no shipped operator-facing feature that delivers it at this point in the integration.

Judgment call. For this operator profile, the integration’s value at six months is the incremental reservation channel, not the unified record. If you’re modelling the deal on a unified-record assumption, you’re modelling forward 12 to 24 months, not modelling today.

Setup two: a hotel F&B group on SevenRooms with no delivery footprint

This is the SevenRooms install base’s centre of gravity — Marriott, MGM, Mandarin Oriental, Wynn — and the customer profile that the SevenRooms vs Tablecheck desk review covered in more detail.

What works today: SevenRooms continues to operate as it did pre-close. The Marriott preferred-provider relationship is intact. The hotel F&B operator gets the AI feature suite SevenRooms shipped in March 2025 — AI Responses, AI Feedback Summary, AI Note Polish — on the same product cadence as before.

What doesn’t work today, and may not be relevant: the unified-with-DoorDash piece. A hotel F&B group with no meaningful delivery footprint has nothing to integrate on the DoorDash side. Confidence: high that the integration is irrelevant for this profile in the near term. The watch item is whether DoorDash steers SevenRooms’ product roadmap toward delivery-adjacent features that compete for engineering attention with the hospitality-CRM features this profile actually uses.

Judgment call. For hotel F&B, the integration question matters less than the roadmap-priority question. Is your reservations vendor still building for you, or is it building for the delivery-and-dine-in profile? The honest answer at six months is: SevenRooms appears to be building for both, and the March 2025 AI feature cadence has continued. That’s the right read until proven otherwise.

Setup three: a fine-dining tasting menu with a heavy guest-data moat

Tasting menus are the canonical case where the guest record is the entire asset. Dietary restrictions, preference history, allergy data, spend tier, anniversaries, the four-top who came in for a 30th birthday and tipped 35%. None of this lives anywhere DoorDash has historically touched.

What works today: the platform continues to do what it has always done well for this profile. Guest profiles deepen. The AI Note Polish feature, which exists specifically to clean up the unstructured CRM notes hosts and servers add during service, is useful for exactly this operator.

What doesn’t work today: a tasting-menu operator opting in to DoorDash Reservations introduces a new acquisition channel that does not, by definition, have the guest-data depth the rest of the platform’s value depends on. The DoorDash-sourced diner walks in with no SevenRooms history, no notes, no preferences. The host stand sees a first-time guest. Confidence: medium-high on this gap. The handoff between the channels is structurally asymmetric for this profile.

Judgment call. If the unified record arrives in the back half of 2026 as promised, this asymmetry resolves: the DoorDash-sourced diner walks in with a known delivery history, which is at least something the host can act on. Until then, the channel is incremental volume without the platform’s main moat applied to it.

Setup four: a multi-unit casual group already heavy on DoorDash delivery

This is the setup where the conflict is sharpest. The operator runs significant delivery volume through DoorDash today. The operator is shopping for a reservations platform. SevenRooms is on the short list.

What works today: the commercial alignment is good. One vendor relationship across delivery and reservations. One quarterly business review. One account team.

What does not work today: the unified record is, again, not live in the operator-facing tooling. So the value of “one vendor for both” is procurement-level, not data-level. Confidence: high that the value at six months is procurement consolidation, not joined guest behaviour.

Judgment call. For this profile, the right question to ask the SevenRooms sales team is not “when will my delivery and reservation data be joined.” It’s “what specifically is in the integration roadmap that ships to my operator-facing dashboard in 2026, and which of those features are gated behind being on both DoorDash delivery and SevenRooms reservations?” Get the gating answers in writing. The lock-in question is real for this profile.

Setup five: an indie operator with no current DoorDash relationship

The smallest case. A single-unit, neighbourhood concept. No delivery program, or a delivery program with a different partner. Considering SevenRooms because of the CRM-first product pitch.

What works today: SevenRooms is, on the product side, the same platform it was pre-close. The CRM works. The guest profiles compound. The decision to sign with SevenRooms in January 2026 is, on product fit, substantively the same decision it was in January 2025.

What is different: the corporate context. The vendor you’re signing with is now a DoorDash subsidiary, and the long-run product priorities will track DoorDash’s commerce-platform strategy. Confidence: high on the corporate-context shift. Confidence: medium on whether that shift meaningfully changes the product experience for an indie operator in the near term.

Judgment call. For an indie operator with no DoorDash footprint, the corporate-context shift matters less today than it will matter in twelve months. The decision should still be made on product fit. The watch item is the renewal in 2027, not the signature in 2026.

The HIGH / MEDIUM / LOW confidence read, summarised

Pulling the five-scenario walk together:

• High confidence: SevenRooms continues to operate as a dedicated product. The booking-flow integration with DoorDash Reservations works. The economic case for opting in to DoorDash Reservations (incremental volume, zero cover fee) is real. The product roadmap has not visibly regressed.
• Medium confidence: The strategic intent to build a unified diner record is genuine and is being worked on. The 12-to-24-month integration timeline is the relevant frame. Cross-touchpoint analytics will arrive incrementally rather than as a single launch.
• Low confidence — open questions: Whether the unified record is live in operator-facing tooling today (best public read: no). Whether the data flow is bilateral or one-directional today (best public read: one-directional). Whether the consent and PII frameworks for a unified record are substantively complete (best public read: in progress, no public confirmation).

If you’re a vendor account rep telling an operator that the unified record is shipping this quarter, that claim is currently outside what the public record supports. Ask for the specific dashboard view, the specific date, and the operator reference.

The operator pain point nobody is fixing yet

One structural issue worth saying clearly: in January 2026, an operator on both DoorDash delivery and SevenRooms reservations is, in practice, managing two separate logins, two separate dashboards, and two separate operational rhythms. The commercial integration is real. The user-experience integration is not yet.

This is not a criticism. Single-pane-of-glass operator UX is the output of the integration, not its input. You merge the data layer, you merge the consent layer, you merge the analytics layer, and then you ship the operator dashboard. The dashboard is the last thing to ship, not the first. The twelve-month watch is whether it ships before the end of 2026; slipping into 2027 would mean the integration is behind schedule.

The competitive context

A desk review is incomplete without saying what the competitors are doing while DoorDash and SevenRooms integrate.

The Tock-into-Amex-and-Resy consolidation continues. Tock’s upscale-tasting-menu base is being absorbed into Resy under American Express’s commerce strategy. Amex’s incentive structure as a reservations owner is meaningfully different from DoorDash’s — payments network and card-spend marketing channel, not delivery aggregator — and operators picking between the two are picking between two different theories of what owning a reservations platform is for.

OpenTable, separately, has been defending the incumbent moat through contract structure: tightening client agreements with primary-platform language and longer commitment terms, the move you make when you’ve identified meaningful multi-homing churn risk. (The Restaurant Dive operator-response reporting is from after this column’s date; I cite it as the cleanest available later writeup of the directional move that was already visible in 2025 trade-press conversations.)

The third bloc — Uber via its OpenTable partnership — is structurally the cheapest version of what DoorDash did by buying SevenRooms outright. The durability question on that partnership is one I covered in the DoorDash/SevenRooms Bottom Line. The shape of the category at six months post-close: three blocs, two integrating-while-running, one defending.

How this connects to the wider reservations stack

The strategic logic of the deal — that DoorDash bought the first-party in-venue guest data it didn’t have — is covered in the DoorDash/SevenRooms Bottom Line. The product comparison against an independent peer is in the SevenRooms vs Tablecheck desk review; read that if you’re evaluating SevenRooms against a corporate-context alternative that does not have a delivery-platform owner. The OpenTable side of the table is covered in our OpenTable AI piece, which reads the incumbent’s product priorities as a Booking Holdings strategy.

The closing thought from those three holds for this one: the reservations category is now a contest, not an incumbency, and whether the DoorDash/SevenRooms integration delivers the unified diner record on schedule is the single biggest variable in the category over the next 18 months.

Reach For It / Hold Off

Reach for SevenRooms if:

• You run hotel F&B or a CRM-heavy hospitality concept. The product fit is unchanged from pre-close, and the AI feature set continues to ship.
• You’re in a Going Out / DoorDash Reservations launch market and the incremental reservation volume at zero cover fee is meaningful to your unit economics.
• You want one vendor relationship across delivery and reservations and you’re explicit-eyed about the lock-in trade-off that consolidation creates.
• You’re indifferent to or actively interested in being on the DoorDash consumer marketplace.

Hold off on SevenRooms if:

• You’re a tasting-menu or fine-dining concept where the guest-data moat is the asset and you’re not yet convinced the unified record will arrive in a form that helps you. Revisit in late 2026 when the data layer is closer to operator-facing.
• You explicitly do not want your reservations vendor to be owned by a delivery aggregator, and the corporate-context shift outweighs the product fit. The Tablecheck comparison is the structural alternative in this case.
• Your operations problem is host throughput and channel capture rather than guest profiling. The SevenRooms product centre of gravity is the CRM, and the operations-first alternatives may serve you better.

Don’t sign anything yet if:

• You’re already on a multi-homing reservations setup and a vendor is selling you a primary-platform contract structure. Read the data-rights and exclusivity clauses carefully. The category is consolidating, and the contract language is the leading indicator of how the consolidating parties intend to defend their position.

What I’m watching in the next earnings call

DASH reports Q4 2025 in mid-February. Three things I’ll be looking for on the transcript.

Any specific SevenRooms KPI. Since close, DoorDash has talked about SevenRooms qualitatively — “early days,” “expanding,” “going out.” Q4 is the first opportunity for an operator-relevant number. Useful ones: SevenRooms-sourced reservation volume routed through DoorDash, attach rate of SevenRooms operators opting in to DoorDash Reservations, and an operator-cohort retention figure post-close. The retention figure is the one to push for; it’s the cleanest signal of integration-induced churn risk.

Any Going Out commentary that touches the unified record. Watch the phrasing: “unified guest profile” is the strong version, “cross-touchpoint analytics” is the weaker version, “marketing as a service” is framing-only.

Any reference to the SevenRooms enterprise base. The deal economics depend on whether Marriott, MGM, Mandarin Oriental have been retained at pre-close attach rates. A specific hospitality-vertical comment is the leading indicator on enterprise stickiness. I’ll re-anchor this desk review against the print.

Closing

Six months in, the SevenRooms-inside-DoorDash integration looks like what a competent integration looks like at six months: the commercial layer is working, the booking-flow layer is shipped, the data layer is in progress, and the operator-facing unified view is still ahead. The promise of the deal — a unified diner record across delivery and dine-in — is the right promise. The honest read on January 21, 2026 is that the promise is being worked on rather than delivered.

For operators making vendor decisions this quarter: the integration is a positive signal on commercial alignment and an open question on data alignment. Sign for the product fit you have today. Watch the next two earnings calls for the data-layer evidence. We’ll come back with a panel of operators when the unified record is either shipped or honestly delayed; if you operate on SevenRooms today and also run meaningful DoorDash delivery volume — particularly in a Going Out launch market — I’d like to hear from you for that future panel.

— Sofia leads vendor reviews for TableTransfers. Tips: sofia@tabletransfers.com.