Quickmunch WordPress documentation

Welcome! Quickmunch is a complete multi-restaurant food ordering, delivery and management platform for WordPress. This guide takes you from the ZIP you downloaded to a running, configured site — and then documents every screen the product has.

What you get

The product

  • Online ordering — delivery, pickup and dine-in from one storefront
  • Three business models — marketplace, your own restaurants, or franchise
  • Restaurant dashboard — menu builder, orders, customers, staff and billing
  • Point of sale — a full till, with cash drawer and shift reports
  • Kitchen display — the live order board, by station
  • Self-order kiosks and TV menu screens
  • QR table ordering — tables and printable QR cards
  • Reservations — booking calendar and reminders
  • Loyalty, rewards and deals
  • Driver app — accept and complete deliveries
  • Staff roles — managers, kitchen and floor staff, each with their own screens
  • Analytics — for the platform and for every restaurant
  • Pages & blog — WordPress pages and posts, with homepage sections you arrange yourself
  • Messaging — branded email templates and SMS
  • Subscription plans, royalty invoicing and sponsored-ad revenue

What it works with

  • WooCommerce payments — cash on delivery built in; Stripe, PayPal, Square, Mollie, Razorpay, Paystack, Flutterwave, Mercado Pago and Payfast as optional gateways
  • Page builders — WPBakery bundled, and every section also available as a Gutenberg block and an Elementor widget
  • Maps & location — distance search and delivery maps
  • AI assistant — your own provider key
  • SMS — Twilio, for order and table notices
  • Translation-ready — every string in a .pot file, with right-to-left styles included
  • One-click demo import — two demos, one built in WPBakery and one in Elementor

The integrations are optional and off until you add your own key. Nothing in Quickmunch calls out to a provider you have not configured.

Built with

LayerStack
PlatformWordPress 7.0+ · WooCommerce · PHP 7.4+ (8.2 recommended) · MySQL 5.7+ / MariaDB 10.4+
Front endTheme templates · Bootstrap 5 · plain JavaScript — everything ships pre-built
Page buildingWPBakery Page Builder (bundled) · Gutenberg blocks · Elementor widgets
DeploymentAny WordPress host — shared hosting or VPS, Apache or Nginx

If you are setting up for the first time

Want to look around before you configure anything? Import the demo in the last step of Installing Quickmunch. It brings the restaurants, menus and pages, so every screen has something in it while you learn.

Then, tell the guide how you sell

Quickmunch runs three different businesses from the same code, and they do not share screens. Use the business model tabs at the top of this page to pick yours. Pages that cannot exist in that model disappear from the contents, so you are never reading about a screen your installation does not have.

ModelHow money movesWhat you will not see
Marketplace Independent restaurants. You take the online payment and pay each restaurant, keeping a commission. Royalty invoices
My own restaurants One owner, many venues. Every payment is your own revenue, consolidated. Plans, subscriptions, sponsored ads, payouts, royalty invoices
Franchise Each restaurant takes its own payments with its own gateway. You charge a royalty on their sales. Payouts

Every install starts as a marketplace. To check or change it, see Choosing a business model.

Some pages also carry a “Needs …” badge. It names the feature a screen depends on. If a page describes something you cannot find, check that feature is switched on — see Turning features on and off.

The folder structure at a glance

The download holds the theme, its plugins, the demo and this guide, side by side:

Your download/
├── Theme Files/
│   ├── quickmunch.zip               the theme — upload this in Appearance → Themes
│   └── Child Theme/
│       └── quickmunch-child.zip     for your own code changes; updates never touch it
├── Plugins/                         the bundled plugins, for installing by hand
│   ├── sigma-core.zip               page-builder elements, post types, widgets, demo importer
│   ├── sigma-restaurant.zip         the platform: restaurants, dashboards, POS, billing, email, SMS
│   └── js_composer.zip              WPBakery Page Builder
├── Demo-Content/                    the demo as files — the importer carries its own copy
│   ├── content.xml · widget.wie · customizer.dat · redux.json · users.json
│   └── Elementor/                   the same demo built with Elementor, as files
├── Documentation/                   this guide — works offline in any browser
└── List of used Plugins.txt

quickmunch/                          inside the theme
├── inc/                             setup, the Theme Options panel and helpers
├── template-parts/                  header, footer, restaurant and blog building blocks
├── woocommerce/                     WooCommerce's pages, restyled for Quickmunch
├── assets/                          styles, scripts, fonts and images — all pre-built
├── languages/quickmunch.pot         the strings to translate
└── style.css · functions.php · screenshot.png

sigma-restaurant/                    inside the platform plugin
├── includes/modules/                one folder per area: vendor, admin, pos, tv, driver, billing, emails, sms…
├── templates/                       every dashboard screen
└── languages/sigma-restaurant.pot

What each part of the download is for, file by file, is in What's in the package.

Find your way by who you are

How each page is laid out

Every page follows the same order, so you can skim to the part you need:

SectionWhat it answers
What it isOne sentence, so you know whether to keep reading.
Where it livesThe exact path through the menus.
Set it upNumbered steps, in the order you do them.
FieldsEvery field on the screen and what it changes — only where that needs saying.
How it behavesWhat the application does on its own, including the parts that surprise people.
When it doesn’t workThe failures we see most, and what to check first.
Screen names are exact. Where this guide names a button, a field or a menu row, it is written exactly as it appears in the application. If the wording on your screen differs, you are either on a different version or looking at a different screen.