A restaurant website builder where the site actually takes the order.
BentoBox and Popmenu sell you a site and meter the ordering on top. Zay-OS inverts it: the commission-free ordering system is the product, and a full branded website — menu, checkout, SEO schema, CRM — ships inside the flat $499/month. Zero commission. The diner pays the per-order fee, not you.
A restaurant website builder creates the diner-facing site — menu, hours, photos, and ordering. Most builders ship a brochure and treat the transaction as someone else's job. Zay-OS ships the website as the storefront of a commission-free ordering system: branded design, native checkout, SEO schema, and a customer CRM, included in a flat $499/month per location with no setup fee. The diner pays a small flat service fee ($0.99 pickup, $2.99 delivery; 10% on catering); the restaurant keeps 100% of food revenue.
Why brochure sites lose the order.
A restaurant website that cannot take the order is not a marketing asset — it is a referral page for DoorDash. Four ways the pretty-but-passive site leaks revenue, every single day.
A pinch-to-zoom PDF is where mobile diners give up. It cannot show photos per dish, cannot mark an item 86'd, cannot carry modifiers or prices into a cart, and Google cannot read a word of it. The diner who opened your site hungry closes it and searches "shawarma near me" instead — and the marketplaces own that result.
Most brochure builders wire the order button to a third-party page — a marketplace listing or an embedded widget on someone else's domain. The diner you earned with your own site finishes the transaction somewhere that charges you for it, and the customer record lands in someone else's database.
Search a restaurant's name plus "menu" and the DoorDash or Uber Eats listing frequently sits above the restaurant's own site — because the marketplace page has structured data, photos, prices, and a working order button, and the brochure site has none of that. A website without schema and native ordering hands its own branded search traffic to a 25-35% toll booth.
A brochure site takes no orders, so it builds no customer list. No emails, no phones, no order history — which means no reorder campaigns, no slow-Tuesday push, no way to tell your regulars about the new catering menu. Every visit starts from zero, and every marketing dollar has to buy the same diner twice.
What does the leak cost? On a modeled 650 marketplace orders a month at a $24-28 average ticket, a 25% blended marketplace take works out to $48,000+ a year — orders a working website would have captured commission-free. Run the free grader to model your own number.
What the Zay-OS website includes.
Every piece below judges itself by one metric: does it shorten the path to "Place order"? The design serves the checkout, the schema serves the search result, and the CRM makes the second order cheaper than the first.
A real designed site on yourrestaurant.com — your photography, your colors, your story — with the menu as structured data, not a PDF. Items, photos, prices, modifiers, hours, and scheduling all publish from one place; change a price once and the site, the checkout, and the schema update together.
The order button is the site, not a hand-off. Checkout runs on your own domain with saved cards, Apple Pay, and Google Pay; a repeat customer reaches "Place order" in about 8 seconds. You keep 100% of food revenue and tips — the diner pays a small flat service fee ($0.99 pickup, $2.99 delivery; 10% on catering), and you pay no commission at all.
Restaurant, Menu, and FAQ schema ship on day one, alongside local landing structure, Lighthouse-100 speed, and Google Business Profile alignment — so the "Order online" action on your knowledge panel can point at your site instead of a marketplace. This is the structural work that decides whether your site or the DoorDash listing wins your own name.
Every diner who orders becomes a row you own — name, email, phone, full order history, exportable. Reorder campaigns run over SMS and email, plus web push for opted-in regulars. This is the part no brochure builder can offer, because a site that takes no orders has no one to remember.
Hosting, SSL, and performance are included — no separate hosting bill, no plugin stack to babysit. The site runs on your own domain, and if you ever leave, the domain and the customer list leave with you. No setup fee, either: the website is part of the flat monthly platform fee, not a build project you finance up front.
Website-first vs. ordering-first.
The restaurant website builder category splits on one question: is the transaction the product, or an add-on? Here is where the three land — the fee-by-fee detail lives on the comparison pages.
Website-first: the designed site is the product, and online ordering is a module layered on top with its own pricing and per-order economics. Strong design pedigree — but the transaction is treated as an add-on to the brochure, not the reason the site exists.
Zay-OS vs BentoBox →Marketing-first: interactive menus and AI marketing tools around a subscription, with ordering and answering features metered on top. Plenty of features — but you are still assembling site, ordering, and marketing spend as separate line items on one growing bill.
Zay-OS vs Popmenu →Ordering-first: the commission-free ordering system is the product, and the full branded website ships inside it. Site, checkout, SEO schema, and CRM are one flat $499/month per location — no setup fee, no percentage of sales, no module math. The diner pays the small flat service fee ($0.99 pickup / $2.99 delivery), not you.
Website vs. system.
This page and our online ordering system page cover different jobs on purpose. Here is how they split.
The storefront itself — what a restaurant website must include to actually take orders, why brochure sites leak revenue, and how the website builders compare. Read this if the thing you are shopping for is the site.
The website is one module of five. The kitchen tablet/KDS, Otter marketplace ingestion, and DAVO sales-tax automation live on our online ordering system for restaurants page — read that if you are evaluating the whole operation, not just the storefront.
See the full system →Still deciding whether direct ordering is worth building at all? Start with the restaurant online ordering pillar — marketplace vs direct vs hybrid, from first principles.
Everything the website needs, one line item.
The alternative is financing a site build, then subscribing to an ordering add-on, a hosting plan, and a marketing suite — four line items that each bill separately. The ordering-first model collapses that into one.
- Branded design, menu, photos, modifiers, and hours
- Native commission-free checkout (Apple Pay / Google Pay / cards)
- Restaurant + Menu schema, SEO, and Google Business Profile sync
- Customer CRM — every order becomes a record you own
- Hosting, SSL, and Lighthouse-100 speed on your own domain
- Stripe payments — you keep 100% of food revenue and tips
- No setup fee — the diner pays the flat service fee ($0.99 pickup / $2.99 delivery)
A website is a storefront, not a brochure.
Here is the Friday-night failure mode every independent operator recognizes. A family decides on your food, pulls up your name on a phone, and hits your website — a nice template with the awning photo, an embedded map, and a PDF menu from two price changes ago. There is no cart. So they back out to Google, and the first result with photos, live prices, and a working order button is your DoorDash listing. They order there. The food still leaves your kitchen, but 25-35% of the check leaves with it — and the customer record stays with the marketplace. Your own website just referred your own regular to a toll booth. Multiply that across a year and the brochure is one of the most expensive pages on the internet.
A working restaurant website inverts every one of those steps, and Naya Grill — the Lebanese fast-casual group with locations in Pompano Beach and West Palm Beach, and the first restaurant live on Zay-OS — is what the inversion looks like in production. The menu is structured data, so the shawarma plates, mixed grills, and family platters render with photos and live prices on a phone instead of inside a PDF. The order button is the site: a Pompano regular re-ordering the usual for pickup reaches "Place order" in about 8 seconds, on the restaurant's own domain, with the restaurant keeping 100% of the check. And because every direct order writes a CRM row, a slow Tuesday can be answered with a text to the people who actually ordered last month — not with a boosted post shouted at strangers. To be straight about the scale: Naya Grill's two Florida locations are the only live deployment today. Every other restaurant on the platform is now onboarding.
The lesson from that deployment is that "website builder" is the wrong frame to shop with. Nobody's diners want a website — they want the menu, a price, and a confirm button, in under a minute, standing in a parking lot. The industry sells design because design is what demos well in a sales deck; the diner judges the site entirely by whether it takes the order. That is why Zay-OS does not sell a website at all. It sells a commission-free ordering system, and the website — design, menu, schema, checkout, CRM — is the storefront that system ships with, included in the flat monthly fee with no setup cost. If a page element does not move a diner toward the order, it is decoration, and decoration is what the brochure builders already sell.
The restaurant website, answered.
What is a restaurant website builder?
How is Zay-OS different from BentoBox or Popmenu?
Does the website include online ordering?
How much does a restaurant website cost with Zay-OS?
Do I own my domain and my customer data?
Will a Zay-OS website rank on Google?
Can I keep DoorDash and still run my own website?
How long does it take to launch the website?
Stop renting a brochure. Own a storefront.
Run the free grader to see what your current website hands to the marketplaces — then get a site that takes the order live in about a week.