QuickMunch documentation

Every screen in the product has a page here. Start with the business model — it decides which of the others you will ever need.

Updates, support and licensing. For new releases, support and your licence, visit the official product page on Codester. Every update is free for the life of the licence.

First, 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.

Model	How money moves	What 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

You choose this once, in Admin → Settings → Business model. See Choosing a business model before you go further — changing it later changes which screens exist.

Some pages also carry a “Needs …” badge. Features such as POS, kiosks, QR ordering, the kitchen display, TV screens and reservations each have their own switch in Settings → Services. A badge tells you which switch a screen depends on, so if the page describes something you cannot find, that switch is off. See Turning features on and off.

If you are setting up for the first time

1 · Check the serverWhat PHP, MySQL and extensions the application needs. 2 · InstallUpload, create the database and run the installer. 3 · Pick the business modelMarketplace, your own restaurants, or franchise. 4 · Your first hourThe handful of settings worth doing before anyone else logs in.

Find your way by who you are

Platform operatorYou run the site: settings, restaurants, money, content and reports. Restaurant ownerYou run one venue or several: menu, orders, tables, devices and billing. Restaurant staffYou work a shift: the till, the kitchen screen, the floor and the cash drawer. CustomerWhat the people ordering from you see, so you can answer them. DriverAccepting a delivery, following it through and marking it done.

How each page is laid out

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

Section	What it answers
What it is	One sentence, so you know whether to keep reading.
Where it lives	The exact path through the menus.
Set it up	Numbered steps, in the order you do them.
Fields	Every field on the screen and what it changes — only where that needs saying.
How it behaves	What the application does on its own, including the parts that surprise people.
When it doesn’t work	The 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.