Skip to content
Built from restaurant problems

Own the menu. Own the customer path.

MenuSpace started because a real restaurant needed something cleaner than a stack of disconnected monthly tools. The goal became simple: build a direct ordering system an operator could run, understand, keep, and use to bring customers back.

The story

Built the hard way, because the easy tools were not enough.

The first problem
A menu alone was not enough

The original need was simple: put a better menu in front of customers. That quickly exposed the bigger issue — the menu needed to connect to ordering, modifiers, kitchen tickets, receipts, payments, locations, and marketing.

The restaurant test
Every tool had to survive daily use

MenuSpace was shaped around the work operators actually do: change items, pause ordering, handle add-ons, print tickets, track delivery, accept reservations, promote products, and keep staff moving.

The growth problem
Taking the order is only half the job

Analytics, Wormhole campaigns, email campaigns, SMTP settings, rewards, and share tools were added because operators need to measure what works and bring customers back without paying for another pile of apps.

The product now
A self-hosted restaurant operating system

The current package brings ordering, KDS, reservations, locations, delivery assignment, receipts, analytics, Wormhole campaigns, email campaigns, SMTP, rewards, PWA support, marketing tools, themes, templates, and local JSON data into one PHP application.

The operator problem

Restaurants should not need six outside tools to run one customer relationship.

The front end now needs to make that clear. MenuSpace handles ordering and also includes the growth layer: analytics, Wormhole campaign links, email campaigns, SMTP settings, rewards, and share assets.

Measure

Analytics

Know what is selling, what customers are doing, and which campaigns are worth repeating.

Promote

Wormhole

Create focused campaign links that can live on social posts, partner pages, ads, QR codes, and printed material.

Reach

Email campaigns

Send local offers, updates, announcements, and reminders directly from the restaurant’s system.

Send

SMTP

Use the restaurant’s own sender for branded operational and campaign email.

Operator-first rules

What makes MenuSpace different.

The public website should explain the product the same way an operator thinks about it: control, speed, ownership, fewer rented tools, and direct customer relationships.

01

No order tax

MenuSpace does not take a percentage of restaurant orders. Your payment setup and customer flow belong to your business.

02

Built from the floor

The feature set comes from real operator problems: modifiers, tickets, staff tools, receipts, locations, campaigns, and kitchen flow.

03

Ownable software

You receive the PHP application package instead of renting another closed platform forever.

Plain position

MenuSpace is not a marketplace.

It does not sit between the restaurant and the customer. It is a self-hosted software package for businesses that want their own branded ordering path, their own data, their own campaigns, and their own operating setup.

Use it whenYou want direct orders on your own domain instead of sending customers through a third-party marketplace.
Use it whenYou want to edit menus, locations, ordering settings, receipt content, analytics, campaigns, and marketing from your own admin area.
Use it whenYou want source files and local data you can inspect, back up, export, and customize as your operation grows.
$199
One-time single-domain license.
0%
MenuSpace commission on restaurant orders.
Growth
Analytics, Wormhole, email campaigns, SMTP, and rewards.
PHP
Built for common hosting environments.
Next step

Review the real feature set.

The features page is organized around the actual modules included in the current MenuSpace application package.