Resy vs SevenRooms: Which Restaurant Platform Fits in 2027

Key Takeaways

• American Express plans to fold Tock into Resy and discontinue the Tock app and platform, according to Frequentmiler (2026), so a Tock-powered plan you sign today may change mid-contract.

• DoorDash owns SevenRooms and has said it will combine SevenRooms with its Commerce Platform, which makes DoorDash's product direction a question to put to the vendor in writing.

• Resy publishes named plans and prepayment fee rules, and standard payment processing fees apply on top of them.

• SevenRooms publishes no plan prices. Its pricing page shows tiers and routes buyers to a quote.

• Choose Resy if you want a named-plan, deposit-first setup and can accept a roadmap that is still moving. Choose SevenRooms if you expect to buy several add-ons, want marketing and integration depth, and can work through a quote.

• Before you sign with either vendor, get the fee schedule, add-on pricing, cancellation terms and API or export access in writing.

TL;DR: For one restaurant that mainly needs reservations, deposits and table management, Resy's named plans are easier to compare on paper. SevenRooms suits operators who will buy marketing and integration add-ons and can accept a quote-only buying process.

Who owns Resy and SevenRooms now

A restaurant reservation platform is the software that holds your booking calendar, table map and guest profiles, and it decides who can book and whether a party must pay a deposit first. Both products now sit inside larger companies, and that changes what you are buying over a multi-year contract.

DoorDash owns SevenRooms after completing the acquisition. DoorDash said it completed the deal on June 13, 2025, according to DoorDash (2025). DoorDash also said it would combine SevenRooms' CRM, reservations, guest experience and marketing tools with its Commerce Platform, and that SevenRooms' leadership would join DoorDash to keep building the product.

Deal value: $1.2 billion, all-cash according to Restaurant Dive (2025). For a buyer, the price matters less than the stated direction, which is to fold SevenRooms into DoorDash's commerce business.

American Express owns Resy. Tock purchase price: $400 million in cash according to Nashua Telegraph (2024). The same report says American Express had bought Resy about five years earlier, and that Resy's restaurant count had grown five-fold since then.

In a March 2, 2026 report, Frequentmiler said Amex intends to discontinue the Tock app and platform and fold it directly into Resy, with the change expected "this summer," according to Frequentmiler (2026). The same report places the announcement in late February 2026. At the time we checked, Resy's plans page still labeled its Essential and Premium plans as powered by Tock.

As of this guide's October 29, 2026 check, we could not confirm from a page we opened that the fold-in is complete, so ask both vendors for current status and written migration terms.

Each date in the table traces to a citation in the paragraphs above.

How we evaluated these two platforms

This comparison weights seven criteria by what a single-location operator decides on when choosing between these two products. The weights are our judgment as buyer's-guide authors, not a vendor score, and every factual claim traces to a page named in the text. Because the sources are public pages, trade press and review sites, this guide does not rate software performance or user satisfaction.

Weights total 100%. A "not published" answer counts against a vendor only where the criterion needs a published number, such as a fee rate.

Feature matrix: what each vendor documents

Read this matrix as a record of what the pages named in this guide say, not as a verdict on product quality. "Not published" means the item was absent from the pages we checked, and a quote may still include it.

Two gaps matter most. We could not open a developer reference for either vendor, so any integration claim needs written confirmation. Resy names POS integrations on its Platform and Premium plans, but SevenRooms does not name a POS integration as a standalone module on the pages we checked, so ask each vendor for the exact POS name and version you run.

Pricing and total cost of ownership

This section compares the cost structure each vendor publishes, because the fee rules matter as much as the headline price. Pricing checked October 29, 2026.

Resy's plans page lists 4 plans, Platform, Platform 360, Essential and Premium, and labels Essential and Premium as powered by Tock, according to Resy (2026). The page lists monthly amounts for each plan, so read them on the page itself and confirm current figures with Resy in writing before you compare. The same page says Resy has no per-cover fees, and it notes that standard payment processing fees still apply.

Prepayment fees: 3% on Essential, 2% on Premium according to Resy (2026). Because these rates apply to deposits, they scale with the prepaid volume you run rather than with the number of seats in the room.

SevenRooms's pricing page names its Starter, Growth and Premium tiers and prints no plan prices. Its only dollar figures appear in customer testimonials, and its buttons route buyers to a contact or quote form.

Add-ons are where SevenRooms totals can move. An independent review site lists 6 add-ons sold separately from every tier, including email marketing, event management, voice AI, WhatsApp and text marketing, API and integrations, and a group portal, according to Frontdesk Review (2026). That site says it publishes no dollar estimate of its own, and the third-party estimates we read varied too widely to use in a comparison.

The figures in this table repeat the ones cited in the paragraphs above.

Worked example: deposits and no-shows for one dining room

Illustrative scenario, not a customer result: a 60-seat dining room books 20 parties a night at 3 guests each, which is 60 booked guests. If 15% of parties no-show, that is 3 parties and 9 guests unused each night. If 60% of the 60 booked guests prepay $20 each, that is 36 prepaid guests and $720 held per night. At the Essential prepayment rate from the pricing section, the fee on $720 is $21.60 a night, or $108 across a five-night week. The deposit does not stop no-shows by itself, so the operator also needs to spot repeat no-shows before the next deposit decision, which takes a sync that keeps each no-show party's contact linked to its visit record, and HubSpot's ASSOCIATION_ADDED event is the kind of trigger that confirms those links were created.

Where the no-show and follow-up work lives

The pain sits in the gap between the booking screen and the host stand. Two workflows a proposed US Tech Automations build could configure are below. They are design proposals, not a description of a live deployment, and each depends on data the vendor must export or expose.

Proposed deposit follow-up: the trigger is a new reservation with a prepayment in a reservation export or API feed. The workflow checks whether the deposit cleared, queues unpaid parties for a call, and sends a confirmation text 24 hours before service only where the guest has opted in. Its output is a daily exception list for the host lead, sorted by service time. Prerequisites are a CSV export or approved API access from Resy or SevenRooms, a messaging account with consent records, and a named owner for the exception list. Human review points are fee reversals, which staff approve, and any decision to charge a no-show, which a manager makes.

Proposed visit-record sync: the trigger is a change in a party's status to seated or no-show in the exported reservation data. The workflow creates or updates the guest's HubSpot contact and links it to the visit record. Its output is a weekly list of repeat guests for a person to review. Prerequisites are HubSpot app credentials, a field mapping agreed with the front-of-house lead, and a retention rule for guest data. Human review points are marketing lists, which a person approves before any message goes out, and opt-outs, which must be excluded automatically. HubSpot's webhook documentation says 429 responses include a Retry-After header, according to HubSpot, so a configured sync can back off rather than fail silently. The same page lists ASSOCIATION_ADDED, which fires when two objects become associated.

Zapier, Make and n8n can build the same steps without code. When someone configures them, each can keep run histories, retry failed steps, branch on errors and store audit records. The buyer still designs and owns what breaks in production: idempotency so a guest is not texted twice, escalation when a deposit check fails, access controls for guest data, and upkeep when an export format changes. A proposed US Tech Automations design would set those pieces up front, with an idempotency key per reservation, an exception queue with a named owner and an escalation time, and scoped credentials for each connected system. It would need the same prerequisites as a DIY build, namely export or API access, consent records and a human approver for fees, so a team with time to maintain its own stack can reasonably choose that route instead.

Resy: best fit, limits and rollout

Resy fits a restaurant that wants named plans, deposit rules it can read before a sales call, and a parent company in card payments. Its plans page makes the comparison easier on paper than SevenRooms's quote-only tiers, and it names POS integrations on two of its plans.

The limits are the Tock fold-in and limited developer access. Essential and Premium are labeled as powered by Tock, so ask Resy which plan terms, prepayment rules and POS integrations carry over after the move. Resy's API access appears limited to approved partners who go through its partnerships team, and we found no public self-serve reference, so a custom workflow depends on that approval.

For rollout, get three items in writing before you sign: the confirmed POS name and version for your plan, the prepayment fee rules that apply to your deposit types, and the cancellation and data export terms. The primary evidence for this profile is Resy's plans page, cited above, and it should be the first document you request.

SevenRooms: best fit, limits and rollout

SevenRooms fits operators who plan to run guest marketing, events and integrations as an ongoing program and expect to add modules over time. Its site lists CRM and segmentation, marketing automation and events among its modules, and it sells several of them as add-ons. The vendor's pricing page is the clearest evidence of how little is public: Plan prices published: 0 of 3 tiers according to SevenRooms (2026).

The limits are the lack of a published price, add-ons sold only through a quote, and developer documentation that appears limited to approved partners. A quote-driven contract can be heavy for a very small independent restaurant, and a base quote can understate the final cost once several add-ons are included. DoorDash's stated plan to combine SevenRooms with its Commerce Platform also makes the roadmap a question to settle in writing, not a reason to rule the product out.

For rollout, request the API access process early, because a custom workflow depends on it. Ask for an itemized quote that lists every add-on, the contract length and the cancellation rule. The primary evidence for this profile is SevenRooms's pricing page and DoorDash's completion announcement, both cited above.

Who should choose which

Who this is for

Choose Resy if your priority is a fixed set of named plans, deposit rules you can read before any sales call, and a parent company in card payments. Choose SevenRooms if you plan to buy marketing, events, voice AI or API access as add-ons, you are comfortable with a quote-driven onboarding, and you have someone who can own integration work.

Red flags: you cannot get a written total before you sign, you need public API documentation before you buy, or the POS you run is not confirmed for the plan you would buy.

When NOT to use US Tech Automations

For the cases below, a simpler setup wins, and US Tech Automations would add setup and review work without much return. If the built-in reminders and deposit rules already solve your no-show problem and nobody has time to review an exception list, skip a custom workflow. If the vendor will not provide export or API access, skip it too, because a workflow that depends on screen capture breaks without warning. If you run one service a week from a paper book, a manual call list is easier to keep accurate than any automation.

Common mistakes and a decision checklist

Common mistakes:

• Comparing Resy's published plan list against a SevenRooms quote without asking for the same scope in writing.

• Leaving prepayment fees and card processing out of the total, because both sit on top of the plan price.

• Treating an integration as real because a plan mentions POS integrations, without confirming the exact POS name and version.

• Signing before the Tock migration terms are written down.

Decision checklist:

• A written total for the term you plan to sign, with each add-on itemized.

• The prepayment fee rule for each deposit type you will use.

• Cancellation and data export terms.

• A confirmed POS name and version for the plan you are buying.

• API or export access confirmed in writing, with a named contact.

Frequently asked questions

Is Resy still owned by American Express?

Yes, American Express owns Resy, and the ownership section above explains the planned fold-in of Tock.

Who owns SevenRooms now?

DoorDash owns SevenRooms after completing the acquisition described in the ownership section above.

Does Resy publish its prices?

Yes, Resy publishes its plans, fee rules and monthly amounts on its plans page, so confirm current figures with the company.

Does SevenRooms publish its prices?

No, SevenRooms's pricing page names its tiers and routes buyers to a quote rather than printing plan prices.

Is Tock going away?

Reporting on the deal says Amex intends to discontinue the Tock app and platform and fold it into Resy, and we could not confirm from a page we opened that the move is complete.

Can I connect either platform to a custom workflow?

Possibly, but Resy's API access appears limited to approved partners, and SevenRooms's developer documentation appears limited in the same way, so confirm access in writing before you scope a build.

What to do next

Start with the two answers that decide most of this comparison: the written total and the ownership and migration terms. Ask each vendor for a quote that itemizes add-ons, the prepayment fee rule for each deposit type, a migration plan if its product line is changing, and written API or export access. If you already know you need deposit follow-up and a visit-record sync, see how US Tech Automations configures this for a deposit-and-exception design before you choose an add-on list.