Skip to content

Switch to Remi

The website was an add-on to your POS. The bill — and the lock-in — weren’t.

It made sense at the time: you were signing up for the register or the ordering system anyway, and the website was right there in the bundle. One vendor, one login, done. Here’s what that decision quietly turned into — and what leaving actually looks like. (No, you don’t have to leave your POS to leave the website.)

Sound familiar?

The “cheap” website isn’t the bill you actually pay

The website module was advertised at one price. Then ordering was another module. Loyalty another. Email marketing another. Gift cards another. Each one reasonable on its own — and together, a stack that runs hundreds a month for the digital side of a restaurant whose margins are measured in single digits.

Your site looks like every other restaurant on the same system

The website was never the provider’s main product — the register was. So the site is a template: same layout, same menu page, same photo grid as thousands of other restaurants. Your dining room has a personality. Your website got a theme dropdown.

Nobody checked whether a screen reader can read your menu

Was your menu uploaded as a PDF? Are your photos described for guests who can’t see them? Can someone book a table using only a keyboard? Bundled site tools don’t ask these questions, and roughly 1 in 4 U.S. adults has a disability. Every one of those gaps is a guest turned away — and the exact thing demand letters cite first.

You can’t take it with you

This is the part that keeps people stuck: the site was built inside their system, in their editor, on their hosting. Cancel, and it stops existing. Your menu, your pages, your photo galleries — there’s no export button. Leaving doesn’t mean moving your website. It means losing it and starting over.

What switching to Remi looks like

The big fear — “I’ll have to change my whole setup” — is backwards. Remi is the website layer. Keep the POS, the ordering, the loyalty program you actually use; we link out to them. What changes is that your website becomes yours.

  1. Scan your current site — free

    We read your live site the way a screen reader does and show you what fails, who it locks out, and what a rebuilt version looks like. No email required to see it.

  2. We move everything — free

    Menu, photos, pages, hours, reservation and ordering links. Real people do the migration, not an import script you'll have to clean up after. You pay nothing for it, ever.

  3. You review a working preview

    Your new site is fully built before anything changes in public. Click through it, try it on your phone, have your pickiest friend try it. Nothing goes live until you say so.

  4. We repoint your domain. You own everything.

    Same web address, new site underneath. Your domain, your content, your logins, your data — exportable anytime. Cancel the old service when you're ready, not before.

Keep what works. Lose what doesn’t.

  • Keep your POS. Remi doesn’t replace your register. If you take online orders through Square, they sync straight into your Remi site — and that makes the whole site free.
  • Keep your reservations. Already using a reservation service? We link to it — or use Remi’s built-in reservation book, included on the flat plan.
  • Lose the module math. One price, month-to-month, no annual contract. The number on the pricing page is the number on the card statement.
  • Lose the hostage dynamic. Your domain, your content, your data — exportable anytime. If you ever leave Remi, your site goes with you.

The bottom line

Leaving the bundle doesn’t mean leaving your POS. It means your website finally belongs to you.

Start with the free scan — see what your current site fails and what a rebuilt version looks like. We migrate everything for free, you review a working preview, and only then does anything change in public.

Take online orders through Square and your whole site is free — $0/mo, no bill, ever. Dine-in only? $99/mo founding pricing (regular $149), reservations included. Migration is free either way.

Industry context, not legal advice. WCAG 2.2 AA is published by the W3C and referenced by the ADA, Section 508, the European Accessibility Act, and the AODA.