October 2, 2026
Start with what OpenTable's fee actually buys you, because it's two different things bundled into one invoice. The first is a reservation and table-management system: a booking calendar, a waitlist, table assignments, guest notes and visit history, no-show tracking, and automated confirmation texts and emails. The second is a marketplace -- OpenTable's own app and search presence, where diners who've never heard of your restaurant find you and book a table. Those are not the same product, even though they ship as one subscription. As of 2026, OpenTable's pricing runs on three tiers, per reporting from Eat App: Basic at $149/month plus $1.50 for every cover booked through OpenTable's network, Core at $299/month plus $1 per network cover, and Pro at $499/month plus $1 per network cover. On top of that, OpenTable added a 2% service fee on transactions -- deposits, prepaid experiences, no-show penalties -- in early 2026. None of this is hidden exactly, but it compounds in a way that catches operators off guard once volume climbs.
Eat App's numbers lay out the scale of it: a restaurant doing roughly 1,500 network covers a month can rack up $1,500 to $2,250 in cover fees alone, before the base subscription is even added in. That per-cover network fee is, by their account, the single most common complaint from OpenTable operators -- and it's easy to see why. A flat software subscription is predictable. A fee that scales with every single guest who books through the network is not, especially in a business where covers swing with the weather, the season, and the calendar. The comparison operators keep reaching for -- that these fees can add up to more than rent -- isn't a throwaway line. Rent is fixed. You know what it is in January and you know what it is in July. A reservation bill that's a function of how many people walked through the door starts to feel less like a software cost and more like a second landlord, one that charges you for your own popularity.
Here's where the easy take -- OpenTable is a ripoff -- falls apart. If a meaningful share of your covers each month are diners who found you through OpenTable's app or search and would not have booked otherwise, you are not paying for a seating chart. You're paying for customer acquisition, and customer acquisition is never free. A restaurant that depends on that marketplace for new business is getting something real for its money, and the per-cover fee, annoying as it is, is tied to actual new revenue walking in the door. That restaurant should keep paying. The marketplace is doing its job. The mistake is treating every restaurant on OpenTable as if it's in that position. A lot of them aren't anymore.
There's a quieter, more common situation: a restaurant that built OpenTable into its workflow years ago, when the marketplace mattered more, and never re-examined whether it still does. A few signs you're in that second category: Your host stand can tell you, without pulling a report, that most of tonight's reservations came from your own website or a phone call -- not from someone searching OpenTable's app. If the front-of-house staff already know this intuitively, it's not a close call. Your per-cover fees are consistently in the same range as your rent, or close to it, month after month -- not as a one-time bad month, but as the steady pattern Eat App describes operators running into. Your team has started mentally converting booking volume into a bill rather than a benefit -- thinking "that's another $1.50" instead of "that's a new customer." That shift in language is usually the clearest signal that the marketplace stopped being the point a while ago, and the dining room is now mostly filled by repeat guests and word of mouth that happens to get logged through OpenTable's interface. If two or three of those are true most months, you're paying marketplace-acquisition pricing for a tool that, for your restaurant, is functionally just reservations and table management.
The reservation and table-management layer -- the calendar, the waitlist, table assignments, guest notes, no-show tracking, automated confirmations -- is well-understood software. It's not a black box that only a marketplace vendor can build. It's the kind of internal tool a restaurant group can own outright, built to fit how your dining room actually runs rather than a generic template with a fee schedule attached. That's the case for building it instead of renting it indefinitely. A restaurant whose bookings are already mostly direct doesn't need to keep paying per-cover tolls for discovery it isn't using. With ViibeStack's AI app builder, a reservation and table-management system is a buildable internal tool -- one your team owns, with a CRM layer for guest history and preferences baked in, rather than rented by the cover forever. It's worth running the same buy-vs-build math here that applies to any piece of your operations stack: is the ongoing fee buying you something you can't replicate, or just something you've gotten used to paying for? This isn't an argument for ripping OpenTable out on principle. If the marketplace is bringing you new diners, the fees are the cost of doing that business, and you should keep paying them. It's an argument for actually checking which restaurant you are before renewing on autopilot.
Reservations are one piece of running a restaurant, not the whole operation -- if you're also looking at the POS and back-office side of the business, see our piece on Toast's back-office add-ons. And if you're evaluating your broader software stack beyond the front of house, blog.viibestack.ai has more guides on restaurant and hospitality operations worth a look before your next renewal date.
Sources