Hidden Fees in Reservation Systems: What They Really Cost

42% of restaurant operators were not profitable in 2025.

Their reservation system was still billing them per cover.

That statistic deserves to sit with you for a moment. Nearly half the industry is operating at a loss, and one of the tools they depend on every single day -- the system that handles the guests walking through the door -- is structured to charge more the busier they get. This is not a pricing model. It is a misaligned incentive presented as standard practice.

I am writing this as the co-founder of a reservation system that chose a different model. I have a bias, and I am going to be transparent about it throughout this piece. But the numbers here are not mine. They come from the National Restaurant Association, academic researchers, and the operators themselves. What you do with them is up to you.

The economics that make hidden fees dangerous

To understand why fee structures matter so much in this industry, you need to understand the margins.

Small full-service restaurants with sales below $2 million operate on a pre-tax income margin of 1.1%.

On $150,000 in monthly revenue, that is $1,650 in pre-tax profit. The median across all full-service restaurants is only slightly better, hovering around 2.8%.

At these margins, a few hundred dollars per month in unexpected fees is not a rounding error. It is the difference between staying open and closing.

Yet restaurants continue to increase their technology spending. 73% of operators said they increased their tech investment in 2024, even though the industry spends only 1.97% of revenue on technology -- compared to 7% for the average across all industries.

That 1.97% needs to work hard. Every dollar of it needs to earn its place.

How drip pricing works against you

The restaurant technology industry has borrowed a pricing tactic from airlines and ticketing platforms: show one price, charge another.

Researchers have a name for this. It is called drip pricing -- the practice of revealing additional fees incrementally throughout the purchase process, after the buyer has already mentally committed to the advertised price.

A large-scale study of millions of transactions on a major ticketing platform found that drip pricing increased total spending by 21%, but also caused 45% higher checkout abandonment.

That means drip pricing extracts more from those who stay, while driving away nearly half of those who realize they are being charged more than expected. A separate study by Santana, Dallas, and Morwitz published in Marketing Science found that consumers under drip pricing not only selected higher total-price options -- they remained dissatisfied with their purchase afterward.

Now apply this to reservation systems. The advertised price gets you in the door. The real cost unfolds invoice by invoice: per-cover charges, database overage fees, feature add-ons, automatic tier upgrades.

By the time you understand what you are actually paying, switching costs feel prohibitive -- your guest data, your integrations, the staff training, the operational disruption.

The airline industry extracted $148.4 billion in ancillary fees in 2024 alone.

The reservation system industry operates on a smaller scale, but the playbook is identical.

The four fee categories

Hidden fees in reservation systems tend to fall into four categories. Not every system uses all of them, but most use at least two.

Per-cover fees

This is the most consequential one. Per-cover fees typically range from $0.25 to over $2 per diner, depending on the platform and how the guest found you.

Let me show you the math that rarely appears on pricing pages.

A restaurant doing 150 covers per day at EUR 1 per cover:

• Daily cost: EUR 150
• Monthly cost (30 days): EUR 4,500
• Annual cost: EUR 54,000

Now put that in context. If that restaurant does EUR 150,000 in monthly revenue with a 3% net margin, its monthly profit is EUR 4,500. The reservation system's per-cover fees alone consume the entire margin. Every cent of profit goes to the software vendor for the privilege of accepting the bookings that generated the revenue in the first place.

This is not a hypothetical scenario. Castellucci Hospitality Group in Atlanta reported paying $2,000 to $3,000 per month per restaurant in per-cover fees before switching to a flat-rate system.

Vedge in Philadelphia saved $30,000 per year by leaving a per-cover platform.

Anne Quatrano of Bacchanalia in Atlanta saves roughly $11,000 per year on a flat-rate system versus what she was paying in per-cover fees -- the difference between approximately $1,000 per month and $89 per month.

These are not edge cases. They are the predictable result of a pricing model that penalizes volume.

Tiered feature gating

The base price covers basic reservations. The waitlist is an add-on. Multi-language support requires the premium tier. Guest analytics live behind the enterprise paywall. By the time you have assembled the features you actually need, you are paying two or three times the number that appeared on the sales page.

The opacity here is remarkable. Only 4% of SaaS product profiles publicly list their prices, according to a G2 internal audit.

That means 96% require you to "talk to sales" -- a process designed to assess your willingness to pay before quoting you a number. The price is not based on the cost of providing the service. It is based on the maximum they believe you will accept.

Automatic upgrades and overage penalties

Some systems advertise an attractive entry-level price tied to a low booking limit. Exceed that limit -- even for a single month during your busy season -- and you are automatically bumped to a higher tier. That tier comes with features you did not ask for and a price you did not agree to. Downgrading is either impossible or delayed until the end of a billing cycle.

The average monthly technology spend for restaurants is $196.

When an automatic upgrade doubles that overnight, it is material. And it often happens precisely when the restaurant can least afford the surprise -- during the transition from a strong month back to normal volumes.

Administrative and processing fees

Setup fees, onboarding charges, database storage limits, no-show processing fees, premium support tiers. Each one is individually small. Together, they create a gap between the advertised price and the actual invoice that can reach 50-100% of the base subscription.

The most telling version of this pattern comes from outside the restaurant industry. When a major restaurant technology company added a 99-cent fee charged directly to customers on every order, the backlash was swift and severe. The CEO reversed the decision, publicly calling it a "mistake."

The fee was small. The damage to trust was not.

Regulatory momentum is building

Regulators are catching up to drip pricing. The FTC's Junk Fees Rule, effective May 2025, requires all-in pricing for ticketing and lodging. California's SB 478, effective July 2024, mandates all-in pricing across all consumer transactions.

The restaurant technology industry is not yet directly covered by most of these regulations. But the direction is clear. The legal and cultural consensus is moving toward transparency. Pricing models that depend on obscuring the true cost are unsustainable.

If your current vendor's pricing model would not survive a requirement to show the all-in price upfront, that tells you something about the model.

How to evaluate what you are actually paying

Before signing or renewing with any reservation system, run this exercise:

Calculate your real monthly cost. Take your actual cover count from your busiest month last year. Apply the per-cover fee, if any. Add the subscription. Add every add-on you use. Add any overage fees that would trigger at that volume. That number -- not the one on the pricing page -- is what you are evaluating.

Model the growth scenario. If your covers increase by 20% next year, what happens to your reservation system bill? With a flat-rate model, nothing. With per-cover pricing, a 20% increase in covers means a 20% increase in fees. Growth should lower your per-unit cost of technology, not raise it.

Request a sample invoice. Ask the vendor: "Show me what my invoice would look like at 100 covers per day, with 3,000 guests in my database, using the waitlist and analytics features." If they cannot or will not give you a straight answer, that is itself an answer.

Check switching costs. Can you export your guest data? How much notice do you need to give? Are there early termination fees? The harder it is to leave, the less pressure the vendor has to keep their pricing honest.

For a deeper comparison of specific pricing structures across the market, we published a detailed pricing comparison that breaks down exact numbers.

Why we chose flat-rate pricing

I want to be honest about this section. I am the co-founder of Nine Tables and I am going to explain our pricing philosophy. You should read this knowing that context.

When we designed Nine Tables, we spent a long time on the pricing question. Per-cover models have a clear appeal for the vendor: revenue scales automatically with usage. It is also genuinely cheaper for very small restaurants that process only a handful of covers per day. I acknowledge that trade-off.

But we kept coming back to the same problem. A restaurant operating on 1.1% margins cannot afford a variable cost on its highest-volume line item. The reservation system touches every guest. If that system charges per guest, it becomes the single largest variable cost in the technology stack -- potentially exceeding the restaurant's entire profit.

So we chose flat-rate. One price. All features. Unlimited covers. Your bill does not change because you had a strong Saturday night. We wrote more about the reasoning behind that decision in why we do not charge per booking.

The trade-off is real. We do not capture the upside when a restaurant grows from 50 to 500 covers per day. Our revenue stays the same while our infrastructure costs increase. We are betting that delivering clear value at a predictable price keeps restaurants with us longer, and that long retention is worth more than extracting maximum revenue per transaction. Whether that bet pays off is on us, not on our customers.

We also believe the same tools should be available to a 30-seat restaurant as a 200-seat one. Feature gating creates a two-tier industry where the restaurants that need good technology the most are the ones who can least afford it. We wrote about that in small restaurants deserve the same tools.

The transparency question

The restaurant industry runs on trust. Guests trust that the price on the menu is the price they pay. Suppliers trust that invoices will be honoured. The relationship between a restaurant and its technology vendor should operate on the same principle.

When a reservation system advertises one price and charges another -- through per-cover fees, through automatic upgrades, through add-ons that should be standard features -- it is not being creative with pricing. It is eroding the trust that makes long-term business relationships work.

42% of restaurants were not profitable last year. They deserve to know, before they sign, exactly what their technology will cost. Not approximately. Not "starting at." Exactly.

The all-in price. Every month. No surprises.