What a restaurant website really costs

What a restaurant website really costs: domain, hosting, design, photos, online ordering and upkeep, plus a one-week plan to price your own site.

A manager reviews the daily numbers on a tablet in the back office.

The short answer

A restaurant website costs a yearly fee for the domain, a monthly or yearly fee for hosting or a site builder, and either your own hours or a designer's fee to build it. What moves the total far more than the site itself is what you attach to it: online ordering, photography, and the ongoing work of keeping the menu, prices and hours correct.

There is no honest single number. A website can be a one-page card with your address, or a site for several locations with ordering, catering forms and a careers page. Instead of a figure that will be wrong for your situation, this guide splits the cost into parts you can price yourself this week with local quotes. It also shows where the money usually leaks.

What you are actually paying for

  • Domain name: renewed every year. Register it in the owner's name with the owner's email, not a designer's or a former manager's. Losing control of the domain is the most expensive website mistake a restaurant can make, because everything else hangs off it.
  • Hosting or a site builder subscription: a monthly or yearly fee. Builders bundle hosting, templates and security updates. Separate hosting usually costs less, but someone has to maintain the software.
  • Design and build: your own time, a freelancer's project fee, or an agency project. This is the line with the widest range.
  • Photography: a shoot has a fee, but the photos get reused on the site, the ordering page, menu boards and social posts. Phone photos taken in daylight near a window beat stock images.
  • Copy and menu text: someone has to write the about section, the menu descriptions and the allergen notes, and keep them true.
  • Email on your own domain: usually a small monthly fee per person.
  • Online ordering: a commission on each order, a subscription per location, or card processing only, depending on what you choose.
  • Upkeep: menu changes, holiday hours, and fixes when something breaks.

Only the first two lines are truly fixed. Everything else depends on decisions you make, which is good news, because you control them.

Do it yourself, hire a freelancer, or use an agency

Each path costs something different. The trade-off is mostly money against hours and control.

Building it yourself with a template builder costs the subscription plus your evenings. It works for a single location with a simple menu, as long as one person owns the site and actually updates it. The risk is a site that looked fine at launch and is wrong six months later.

A freelancer charges a project fee and often a monthly care fee. You get a cleaner result and someone to call. Before you sign, ask who owns the domain, the hosting account and the design files, and what happens if the freelancer stops answering. Get it in writing that every login is in your name.

An agency costs the most. It makes sense for groups with several locations, a brand to protect, or catering and events pages that need real design work. Ask for a fixed scope, a written list of what counts as a change request, and the turnaround time for a menu update. An agency that bills by the hour for every menu edit can turn a modest build into a steady monthly expense.

Ask every builder these four questions

Who owns the domain and the hosting account? Can I edit the menu and hours myself without calling you? What does a change cost after launch? If I leave, how do I leave, and what do I take with me?

Online ordering is the line item that changes the math

For many restaurants the website is mostly a front door to ordering. How you add ordering affects your yearly cost more than how the site was built.

There are three common models. Marketplace apps take a commission on each order and hold the guest relationship. Some site builders sell an ordering add-on. Some restaurant systems give you an ordering page that you link to or embed on your own site, and you pay a subscription plus card processing. Compare them on three things: what you pay per order at your real volume, who keeps the guest's contact details, and whether orders reach your kitchen without someone retyping them.

This is where Opero fits, if you are already looking at a restaurant system. Each location gets a pickup ordering page. You can add it to the site you already have as a button or an embedded frame, and there are step-by-step instructions for common site builders. When the page sits inside a frame, the card step opens in a new tab. Guests choose ASAP or a pickup time later the same day, and orders land on the same kitchen screens as the register and kiosk. The page reads the same menu as the register, so a price change or an 86 shows up on the ordering page within seconds. Opero takes no marketplace commission; card processing is quoted per business. The Opero plan is $149 per location and Opero Full-Service is $249 per location. There are honest limits too: the page takes cards only, with no phone wallet payments and no pay-at-counter option, and a location has to be approved to take cards before its page goes live.

The hidden cost is keeping it true

The website expense nobody budgets for is the time someone spends each week keeping it accurate, or doesn't spend. Wrong holiday hours send guests to a locked door. An old menu with old prices starts an argument at the counter. A menu file last updated two seasons ago tells guests nobody is paying attention.

  • Put the menu on the page as real text, not only as a file or photo. It reads properly on a phone, and search engines can read it too.
  • Keep one source for menu items and prices. If the website menu is typed separately from the register menu, the two will drift apart. Decide which one is the master and copy from it on a set day each week.
  • Change holiday hours on the site and on your map listing on the same day you decide them.
  • Name one person responsible for the site, give them the logins, and name a backup.
  • Once a week, check the site on your own phone: menu, hours, address, phone number and the ordering button.

Count this time as part of the cost. A cheap site that needs an hour of fiddling every time the menu changes is not cheap. That hour comes out of a manager's shift.

What a restaurant website actually needs

Most restaurant sites carry pages nobody visits. Guests arrive on a phone wanting answers to four questions: are you open, where are you, what do you serve, and how do I order or book. Build those first and build them well, then add anything else.

  • Hours, address and phone number near the top of every page.
  • The menu as text, with prices and allergen notes.
  • One clear button to order, call or book.
  • Photos of your real dishes and your real room.
  • Accessibility basics: readable text sizes, descriptions on images, and buttons big enough for a thumb.
  • A catering or private events page, but only if you actually do that work.

You can safely skip these at first: a blog nobody will update, animated intros, pop-ups that cover the menu, and pages that repeat what the menu already says. Each one adds build cost and upkeep without helping a hungry person decide.

Price your website in one week

  • Day one: find out who owns your domain and hosting today, and move every login to the owner's email.
  • Day two: list what the site must do, such as menu, hours, ordering, catering, jobs or several locations.
  • Day three: get two or three quotes, or start building on a template, and use the four questions above.
  • Day four: price online ordering on its own, at your real weekly order count, comparing commission, subscription and card processing.
  • Day five: estimate how many hours of upkeep the site needs each month, and decide who will do them.
  • Day six: take daylight phone photos of your ten best-selling dishes.
  • Day seven: choose the option with the lowest total cost over a full year, not the lowest launch price.

See how an Opero ordering page sits on the website you already have.

Explore online ordering

Frequently asked questions

Is a free or very cheap website good enough for a restaurant?

It can be, if it shows correct hours, address, a text menu and a way to order or call, and if the domain is in your name. The trouble with the cheapest options is usually upkeep and control, not looks. Check that you can edit the menu yourself and take your domain with you if you leave.

Do I need a custom design?

Most single-location restaurants do not. A clean template with good photos and an accurate menu covers what guests need. Custom design starts to make sense when you run several locations or brands, or when catering and events are a real part of the business.

Should online ordering live on my own website?

Linking or embedding ordering on your own site keeps guests with you rather than sending them to a marketplace. Compare options on what you pay per order at your real volume, who keeps the guest's contact details, and whether orders reach the kitchen without being retyped.

How often should I update my restaurant website?

Update it whenever the menu, prices or hours change, and check it on your phone once a week. Holiday hours deserve special attention: change them on the site and your map listing on the same day.

Who should own the domain and logins?

The owner, using an email address the business controls. Designers, managers and agencies come and go. A domain held in someone else's name can take the whole site down when that relationship ends.

Run your whole restaurant on one platform

POS, kiosk, QR ordering, kitchen display, and payments on one spine, you bring the tablets, and the card reader is the one piece you must buy from us. Unlimited devices, no per-device fees.

Explore the platform

Keep reading

Opero™ is a product of Tack On LLC. · The Restaurant Operating System