An online ordering app for restaurants — without the app store.
You do not need a $50,000 native app, and you do not need to rent placement in the marketplaces' apps next to your competitors. Zay-OS ships your ordering as a branded, installable web app on your own domain — one-tap reorder, saved cards, Apple Pay — commission-free from $499/month flat. The diner pays the per-order fee, not you.
An online ordering app for restaurants is the repeat-use layer diners order from: a home-screen icon, saved cards, and one-tap reorder. Most independents do not need a native App Store app — a branded installable web app (PWA) delivers the same reorder loop without the $15,000-$50,000+ build or the marketplace apps' 25-35% take. Zay-OS ships it as part of the platform from a flat $499/month per location, with a small flat service fee paid by the diner ($0.99 pickup, $2.99 delivery; 10% on catering) and zero commission on food revenue.
What a restaurant ordering app actually has to do.
Strip away the agency pitch and the app question comes down to five jobs. None of them require native code or an App Store listing — they require accounts, saved payment, re-engagement, and a kitchen screen that already shows everything else.
The whole reason a restaurant wants an app is the reorder. Saved cards, full order history, remembered modifiers — a regular reaches "Place order" in about 8 seconds. That speed is a checkout-and-accounts problem, not a native-code problem. Zay-OS ships it on your own domain, so the reorder loop belongs to you instead of to a marketplace.
Zay-OS ordering runs as an installable web app (PWA): diners add your icon to their home screen from the browser in two taps. No download wall between hungry and checkout, no App Store review queue, no developer account, no forced update prompts. Changes to your menu or hours are live for every diner the moment you publish them.
A native app's real pitch is push notifications — but you only get them from diners who installed and opted in. Zay-OS runs web push for opted-in regulars plus SMS via Twilio (A2P 10DLC handled) and email via Resend, all fired from the built-in CRM. Every diner who orders becomes a row you own: name, phone, email, order history, exportable.
Apple Pay, Google Pay, and saved cards via Stripe — the same one-sheet checkout diners get in the big marketplace apps, minus the 25-35% blended take on the restaurant side. With Zay-OS the diner pays a small flat service fee ($0.99 pickup, $2.99 delivery; 10% on catering) and the restaurant keeps 100% of food revenue and tips.
An app that prints to its own fifth tablet makes the rush worse, not better. Orders from the Zay-OS app land on the same kitchen tablet/KDS as your DoorDash, Uber Eats, and Grubhub tickets via Otter — one queue, one expediter view, 25+ POS systems supported. The app is the front door of a system, not another screen to watch.
App vs. system vs. concept.
Three pages, three different questions — on purpose. Here is how they split, so you land on the one that answers yours.
Our restaurant online ordering pillar covers the strategy — marketplace vs direct vs hybrid, and what to demand from any platform. Start there if you are still deciding whether to build a direct channel at all.
Read the pillar →The online ordering system page covers the full five-module stack — ordering site, kitchen tablet/KDS, CRM, Otter ingestion, and DAVO tax automation — and how the modules hand off to each other on one bill.
See the system →This page answers the app question specifically: whether your restaurant needs a native App Store app (usually no), what the marketplace apps really cost you, and how a branded installable web app delivers the reorder loop instead.
The app experience, included — not an add-on.
A custom native app is a $15,000-$50,000+ line item before maintenance. The marketplace apps take 25-35% of every order forever. The Zay-OS app experience ships inside the platform on one flat bill.
- Branded, installable ordering app (PWA) on your own domain
- One-tap reorder + saved cards (Apple Pay / Google Pay)
- Web push + SMS + email re-engagement via the built-in CRM
- Kitchen tablet + KDS the app orders land on
- Otter marketplace ingestion (keep the marketplace apps on your terms)
- DAVO sales-tax set-aside (all 50 states)
- No app store review, no developer account, no rebuild per iOS release
Should your restaurant build an app? Usually no.
Every operator gets the pitch eventually: an agency deck, a mockup of your logo on an iPhone, and a quote somewhere between $15,000 and $50,000+. The problem is not the quote — it is what happens after. The App Store is a discovery dead zone for a single restaurant; nobody stands in line at your counter because they were browsing "Food & Drink" that morning. Your regulars find you on Google, on Instagram, and on the sticker in your window, and every one of those paths leads to a browser, not an install screen. Put a download wall between a hungry diner and your checkout and a chunk of them simply will not cross it. Meanwhile the native app itself never stops costing: an Apple developer account, a review queue on every menu tweak you ship as an update, a rebuild every time iOS moves, and a developer on retainer when it breaks on a Friday night.
The marketplace apps solve distribution and then charge you for it forever. Inside the DoorDash and Uber Eats apps you are a row in someone else's catalog — listed next to your direct competitors, with sponsored placements sold against your own name, the diner's contact information withheld, and a 25-35% blended take on every order. At 650 marketplace orders a month and a $24-28 average ticket, a 25% take models out to $48,000+ a year — that is the modeled cost of renting a shelf in someone else's store instead of owning your own. The marketplaces are real demand and worth keeping for discovery, but they are the worst possible place for your regulars to reorder, because you pay acquisition pricing on customers you already earned.
There is a third path, and it is the one Zay-OS ships: a branded, installable web app on your own domain. A diner orders once from the browser — no install step — and if they want the app feel, they add your icon to their home screen in two taps. From then on it opens full-screen like any native app, with their cards, order history, and modifier choices saved, so the usual order is about 8 seconds from open to "Place order." Web push reaches your opted-in regulars, and SMS and email campaigns fire from the built-in CRM for everyone else. Updates ship instantly from one codebase with no review queue. This is exactly how it runs at Naya Grill, the Lebanese fast-casual with locations in Pompano Beach and West Palm Beach, Florida: a regular taps the same mixed-grill platter they order every Friday, and the ticket lands on the kitchen tablet in the same queue as the marketplace orders. Naya Grill is the only restaurant live on Zay-OS today — every other restaurant is now onboarding.
The last thing to understand is that the app is the front door, not the building. On its own, a great reorder screen still needs a kitchen display to land on, a CRM to write the customer into, a way to sit alongside the marketplace tickets without a fifth tablet, and sales tax set aside daily via DAVO instead of scrambled for at quarter end. That full stack is the online ordering system — the app described on this page is the diner-facing layer of it, and they ship together on one bill.
The app question, answered.
Does my restaurant need a mobile app?
What is the difference between an online ordering app, an online ordering system, and an ordering website?
How much does it cost to build a custom restaurant app?
What is a PWA, and is it as good as a native app for a restaurant?
Is being in the DoorDash and Uber Eats apps good for my restaurant?
Can customers really reorder in one tap?
How much does the Zay-OS ordering app cost?
Do diners have to download anything to order?
Your app. Your domain. Zero commission.
Run the free grader to see what the marketplace apps cost you last month — then put your own icon on your regulars' home screens.