Restaurant Platforms: What You're Actually Renting

Every restaurant owner eventually gets the pitch: one platform for POS, online ordering, reservations, loyalty, delivery routing, website — "everything in one place." It's attractive. It works. Then three years in, you want to leave or negotiate, and you find out what you actually signed up for.

This isn't a hit piece. The big platforms do real things well, and for a lot of restaurants they're the right call. But they're rented, not owned — and the smart move is to read the fine print before you sign, not after.

Here's what to negotiate up front, and what to insist on keeping in your name no matter which platform you choose.

Three things that must stay in your name

Your domain. If the platform is hosting your website under a subdomain they control — yourbrand.ownersite.com, myrestaurant.toastsite.com — you're in a bad spot. When you leave, the URL leaves with them. Every menu card, business card, Google listing, and social post pointing at that URL becomes dead.

The fix is simple: own your domain at a neutral registrar (Cloudflare, Namecheap, Google Domains before it shut down). Point it at the platform via DNS. When you leave, you repoint the DNS at the new vendor and keep every link, ranking, and piece of print material working.

Your customer list. This is the big one. Every loyalty signup, reservation, online order, and review contains contact information — phone numbers, emails, visit history, spend data. That list is the most valuable asset your restaurant has.

Some platforms hand this over freely. Some make it a pain. Some genuinely try to keep it from you when you leave. Before you sign, ask to see the exact export format and frequency — not "can I export" but "show me the export from a comparable customer." If the answer is "there's an API" or "contact support when you're ready to leave," that's a yellow flag.

Plan to export monthly, regardless of how happy you are. A year of monthly exports is worth more than any conversation you'll ever have with their retention team.

Your Google Business Profile. This isn't a platform feature — it's your listing on Google. You verify it, you own it. But I've seen platforms "manage" your GBP during onboarding, get added as a listing owner, and never remove themselves. Check the owner list on your GBP dashboard right now. Remove anyone you don't work with directly.

Your GBP is where most of your local-search traffic comes from. It's too important to let any third party have admin rights to it.

The features they sell you vs. the features you actually use

Walk through the feature list they sold you. Seriously — go look at it. The all-in-one platforms typically include 40-60 features. Most restaurants meaningfully use 10-15.

What you're really paying for, month over month, is usually:

• POS and order-taking
• Online ordering (occasionally)
• Reservation intake (if that)
• Basic reporting
• Hardware you leased

The extra — loyalty programs nobody signs up for, marketing blasts that don't get opened, a CRM with a few hundred stale contacts, a "website builder" that made a template site — is almost always unused, but priced into what you pay every month. When you evaluate whether to renew or switch, look at actual usage, not feature counts.

The true cost of "free" onboarding

"Free setup" is almost never free. It's usually amortized into a longer commitment, higher per-transaction fees, or equipment leases you can't exit without paying.

Three questions to ask before signing:

1. What's the minimum term? If it's more than 12 months, negotiate that down hard or walk.
2. What happens to leased hardware if I cancel? Are you shipping it back on your dime? Owing the remaining balance? Buying it out at original list price?
3. What are the transaction fees and processing rates in writing, and can those rates change unilaterally? Some contracts reserve the right to adjust fees with 30 days notice. That's not a negotiation — that's a blank check.

None of these are deal-breakers by themselves. But if the answers get vague or deflect, you're about to sign a contract the rep hasn't read either.

What "partner, not vendor" looks like

Most of these points come back to the same thing I've been banging on about — you want a website and tech partner, not a vendor. The difference matters more when the stakes are high, and a restaurant's customer data plus menu content plus reservation flow is extremely high stakes.

A partner:

• Builds on open standards so your data is portable
• Integrates with your choice of POS/payment provider instead of forcing theirs
• Gives you direct API access without extra fees
• Lets you own your domain, hosting, and email
• Writes contracts that don't lock you into multi-year commitments

A vendor:

• Runs everything on their stack, their servers, their terms
• Charges "fair market value" for access to your own data
• Requires annual minimums and penalties for early exit
• Updates your agreement unilaterally

Both are valid business models. You just need to know which one you're buying.

What I'd do if I ran a small restaurant today

Decouple. Use a POS for what a POS is good at, a reservation tool for reservations, a website for your website, and let them all talk to each other via APIs or webhooks. That sounds harder than it is — modern tools integrate reasonably well — but the upshot is when any one of them raises prices or drops a feature, you can swap that piece out without burning down the rest.

For the website specifically, I'd build on a stack the restaurant owns — a domain you control, a CMS where the content lives in a repo somewhere, hosting you can move. That way the site can plug into whatever POS or reservation system fits best, and switch without dragging the whole website into the migration.

That's the way we built our Asian Gourmet client's setup, and it's been resilient across vendor changes on their end.

If you're already locked in

If you're reading this and realizing you're six months into a three-year contract with a platform that's treating you like a hostage — you've still got options:

• Start monthly data exports now, whether they like it or not
• Begin running a second domain you fully control, even if it just redirects for now
• Claim your GBP back into your personal Google account
• Read the termination clause. Calendar the exit window (there's almost always a 30-60 day notice period you have to hit exactly)

These are all reversible if you end up staying. But they give you leverage in the renewal conversation — and that leverage is what gets you a fair deal.

If you'd like a second set of eyes on a restaurant-platform contract before you sign (or before you renew), drop me a note. The hour it takes to read it now can save you years of regret.