Per-Cover Fees Are a Tax on Your Success
In February 2026, OpenTable launched an ad network built on top of diner reservation data. Think about that for a second. Restaurants pay per-cover fees for every seated guest. OpenTable collects that data. And now they're selling advertising against it.
This is where per-cover pricing was always headed. It was never just about the $1 per cover. It was about building a data asset on the back of your restaurant's guest relationships and then monetizing it in ways you don't control.
But let's start with the straightforward math, because the math alone is damning enough.
The numbers
OpenTable's Core plan costs $299/month plus $1.00 per cover for bookings through their network. Their Pro plan starts at $499/month plus the same per-cover fees. Here's what that looks like at a typical volume:
| Plan | Base Fee | ~500 Network Covers | Monthly Total | Annual Total |
|---|---|---|---|---|
| OpenTable Core | $299/mo | $500 | $799/mo | $9,588/yr |
| OpenTable Pro | $499/mo | $500 | $999/mo | $11,988/yr |
Now bavoli:
| Plan | Monthly Cost | Annual Cost |
|---|---|---|
| Free | $0 | $0 |
| Starter | $20 | $192 (annual) |
| Professional | $50 | $480 (annual) |
A restaurant on OpenTable Core pays roughly $9,600 a year. The same restaurant on bavoli Starter pays $240, or $192 billed annually. Over $9,000 in difference.
I keep coming back to what that $9,000 could do for a small restaurant. That's real money. That's a reach-in cooler. That's three months of a part-time prep cook. That's the margin between a good year and a stressful one.
The incentive problem
Per-cover pricing creates a backwards incentive structure.
When you're slow (empty tables, quiet nights), your reservation costs are low. The platform is cheap precisely when you don't need it.
When you're busy (full houses, waitlists), your costs spike. You're paying the most when you're working the hardest and need the platform the least.
Most other business tools don't work this way. Your POS doesn't charge per transaction. Your accounting software doesn't charge per invoice. Your scheduling tool doesn't charge per shift. Only reservation software managed to normalize this.
The network value argument
Look, I'll be direct about this. Platforms like OpenTable do provide some network value. Diners browse the marketplace and discover restaurants they wouldn't have found otherwise. For restaurants that need that discovery channel, paying for those specific bookings can make sense as a form of customer acquisition.
But per-cover fees don't just apply to marketplace-sourced bookings. If a regular guest books through the widget on your own website, you're still paying the per-cover fee. You're paying an acquisition cost for guests you already have.
For most established independents, marketplace-sourced bookings are a small fraction of total reservations. The fee applies to everyone regardless. And now, with the ad network launch and what Restaurant Business is reporting as a "system of record" mandate, where OpenTable wants to be the central platform restaurants depend on for everything, the per-cover model starts to look less like a pricing structure and more like a long-term strategy to own the restaurant-diner relationship.
I wrote about guest data ownership in more detail, including the DoorDash-SevenRooms acquisition and what it signals.
Flat pricing
With flat monthly pricing, you know what your reservation software costs. Whether you seat 100 guests this month or 10,000, the number on your bill doesn't change.
That means predictable budgeting. Aligned incentives. One line item, same every month. We don't earn more when you seat more guests.
If you're currently paying per-cover fees, pull up your last three months of invoices and do the comparison. I think the numbers will speak for themselves.
