Quickmunch pricing.
Pick your stack.

Four ways, and you can run all of them at once: a monthly or annual plan each restaurant pays you, a commission on every order that comes off the top automatically, your own delivery with per-distance fees instead of an aggregator taking the margin, and internal ads — restaurants buying hero slides, home boxes and listing banners on your storefront. See the other way a platform earns and three ways to operate, or work out what you would earn.

They are yours entirely. Create as many subscription tiers as you like, each with its own price, billing cycle and feature set, and decide per plan whether a restaurant pays a flat fee, a percentage, or both. Nothing is hard-coded and there is no revenue share with us — see how the models work.

Whichever you choose, and you can change it later. In marketplace mode you collect everything and pay restaurants out on a settlement run; in franchise mode each venue collects through its own gateway and you invoice a royalty; in my own restaurants mode every payment is simply yours. One switch in the dashboard — the three models.

Completely. Your logo, your colours, your name, your domain, your favicon — and the branding reaches the e-mails, the receipts and the printed menus, not just the header. There is no "powered by" anywhere a customer or a restaurant can see, and one setting recolours the entire platform: white-label ready.

No. It runs on your server, so the only ceiling is your hosting. No per-order fee, no per-restaurant fee, no monthly cost to us, however large the platform grows — that is the whole point of buying it once. Branch groups and multi-venue owners are handled natively: one owner, every location.

Approving restaurants that apply, watching payouts settle, and deciding plans and campaigns — the rest runs itself. Six reports on the platform side tell you what is earning, and the AI assistant answers questions about your own data. See reporting and running it.

Yes — every one of the eight in-venue systems is a switch. Turn off the storefront and use it purely as a till; turn off delivery and run pickup and dine-in only; add the kiosk next year. You are never forced to replace something that already works: eight services, one platform.

Each role only ever sees its own job — the kitchen sees the pass, the waiter sees the floor and the till, the host sees the book. Screens are PIN-locked, so a shift change is a four-digit code rather than a logout, and nobody can wander into settings by accident: everyone sees their job.

In one queue, on one board, with the channel marked and the clock running from the moment it arrives. The kitchen never has to watch four devices, and nothing is retyped between systems: every channel, one board.

Yes — a booking page on your own storefront, a host calendar for the day, and an interactive floor plan where the tables sit where they really stand, shared with the reservation book. See filling the room and the floor plan.

Only if you want them. Set a radius, charge by distance, and follow each order to the door with the rider app — or switch delivery off entirely and run pickup and dine-in. See set the radius, charge by distance.

One thing. The menu, prices and stock live in one place and every surface reads it — storefront, till, kiosk, QR table, the TV boards above the counter and the printed menus. Mark it sold out once and it is gone everywhere: design once, every screen follows.

PHP 8.2+ with MySQL or MariaDB. The Laravel edition is framework-native Laravel 12 — Blade views, artisan commands, an automated test suite. The Vanilla edition is the same platform in plain PHP with its own small core, no framework. Both ship the full source, commented, nothing obfuscated or encoded.

None of them. Every asset is compiled in the download, so deployment is upload, open the address, answer four screens. Node is only needed if you want to edit the CSS partials or scripts and rebuild them.

PHP 8.2 or newer with the usual extensions (pdo_mysql, mbstring, openssl, gd, fileinfo, curl, zip, intl), MySQL or MariaDB, and a writable storage folder. Ordinary shared hosting is fine. The installer checks every requirement before writing anything and names whatever is missing.

Yes. Installation is $59, for any of the four formats. Buy your edition, then send us a message on Codester with your hosting details, and the people who wrote it set it up on your own hosting.

Yes, and that is the argument for the Laravel edition: standard structure, standard tooling, so your team works the way it already does. Integrations are keys in settings rather than hard-wired code — what it plugs into.

The schema is versioned and updates run as migrations, so your data and your edits to unrelated files stay put. You control when an update is applied — nothing phones home or updates itself. Full detail lives in the documentation.

None to run. A default install makes zero external requests — no CDN, no tracker, no phone-home. Payments, maps, messaging, marketing and AI are optional: paste a key in settings to switch one on, leave it blank and the feature simply stays off.