Everything a restaurant runs on.
Storefront

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.

Buy HTML if you have a backend team and want every screen designed and coded, ready to wire up. Buy PHP Vanilla if you want the whole platform running today on ordinary shared hosting, with no build tools. Buy PHP Laravel if your developers work in Laravel and you intend to extend it yourself. Buy WordPress if your site already runs on WordPress and you want the platform as a theme on WooCommerce, with pages you edit in WPBakery or Elementor. Undecided between the two PHP editions? Take Laravel. Compare all four.

The same product. Same screens, same eight in-venue systems, same four applications, same design. What differs is the codebase underneath — static pages, plain PHP, Laravel, or a WordPress theme on WooCommerce. Nothing is held back from the cheaper one: one install, four applications.

257 static pages covering every screen — six homepage layouts, the customer storefront, both dashboards and the design studio — with full RTL and zero CDN calls. It is the complete front end for a team building its own backend. Open the HTML demo.

The theme and a child theme, the companion plugins that carry the platform, and WPBakery bundled. Orders, payments and accounts run through WooCommerce and its gateways, alongside the POS, kiosks, QR table ordering, kitchen display, and the TV and printable menus. Import the WPBakery or Elementor demo in one click and every page is yours to edit. See the WordPress edition.

Functionally nothing; operationally quite a lot. Vanilla has no framework and no Composer, so it lands on cheap shared hosting and stays simple to hand over. Laravel gives you Blade, artisan, migrations and a test suite, which is what you want if the platform will keep growing. Same price, so choose by team, not by budget.

Yes — all four share one design, and the HTML screens map directly onto the PHP editions. They are separate products, so moving means buying that licence, but nothing is wasted and nothing has to be redesigned.

A Regular licence covers one project — one website or app, with its development, staging and live copies — whether you run it yourself or build it for a client. It is paid once and never expires: no subscription, no per-order fee, no renewal to keep it running, with updates and upgrades included through the marketplace you bought it from. A second project needs a second Regular licence, or one Extended licence covers them all. Compare the licences.