Menu & inventory

Menu page → Add category, then Add item inside it: name, price and optional description. Items appear on your customer page instantly; deactivate an item to hide it without deleting it. Both categories and items have a Sort box (lower numbers first), so you control the running order of the whole menu.

Every item has a Sort box — on the Add item form, and inside Edit on any existing item. Lower numbers come first within the category, and two items sharing a number fall back to alphabetical. Leave the box blank when adding and the item goes last in its category, so you can add first and arrange later. Categories have the same box on Menu → Manage categories, and the two work together: category sort decides the order of the sections, item sort decides the order inside each one. Your customer page updates the moment you save.

Every item form has a Photo control: press 'Upload a photo', pick any image, and it is squared to 800×800 and compressed on your own device before upload (WebP where your browser can make one, JPEG otherwise — always well under 300 KB), then attached when you save the item. You can also paste a hosted image URL instead, and the Excel bulk import's Image Filename column still takes full web addresses. Clearing the field and saving removes the photo.

Each item can carry option groups — for example a required 'Spice Level' with Regular/Spicy, and an 'Extras' group capped at 3 picks where Extra Cheese adds 3.00. Customers see them in the item popup: required groups must be answered before Add works, and prices update live. The same rules are enforced again on our server at checkout, so nobody can bypass them.

In the item form, under 'Choices and extras'. Press 'Add a group', type its name (for example Spice level), then add a choice for each answer with the extra charge beside it — leave the price blank when a choice costs nothing more. 'Must pick' makes the customer answer before they can add the item, and 'Max picks' caps how many they may choose. Groups and choices can be reordered with the arrows, and the order you set is the order customers see. Everything is checked again on our server when you save, with a specific message if something is wrong rather than a guess.

Not in the item form — that was replaced by real fields. The one-line format still exists in exactly one place, the Excel bulk import, because a spreadsheet cell has to carry a whole group structure in one box. The template's 'How To' sheet documents it in full. Anything you build with the form can be exported, edited in Excel and imported back.

In the item form, yes — renaming a choice keeps the same underlying record, so its stock count comes with it. Deleting a choice and adding a new one does not: that is genuinely a different choice and it starts fresh. Through the Excel import the answer is different, because a spreadsheet carries no record identity: a 'replace' import rebuilds the menu, so every option is new and per-option stock starts again.

Optional, per item and even per option. Give an item a stock count on the Inventory page; every order decrements it, and at zero the item flips to sold out by itself. Every movement (sale, cancel-restore, manual adjustment) is recorded in a ledger you can inspect.

Yes — a low-stock WhatsApp alert is sent when the count crosses your threshold. It fires on the crossing only, so you get one timely warning, not a nagging repeat every order.

An 'only N left' note on the item across all page designs. If a stale cart still holds an item that just sold out, checkout refuses politely — '"Item" just sold out — please adjust your cart' — and nothing is charged.

Yes. Cancelling restores the tracked stock of every line (items and options), and an item that had auto-flipped to sold out at zero comes back on sale automatically.

Download the template, fill one row per item (category, name, price, description, and options in the one-line format the template's 'How To' sheet documents), and upload. Choose 'append' to add to your current menu, or 'replace' to swap the whole menu in one move — replace deactivates the old menu and inserts the new one.

Replace treats the upload as a brand-new menu — old items are retired rather than edited. That also means a cheaper price in a re-uploaded menu is a new item's price, not a 'price drop' on the old item, so price-drop notifications deliberately do not fire from an import.

Yes — secret menu items are hidden from the normal page and unlock through a special link you share (for example with your regulars or a promotion). There is also a wallet-exclusive item that only customers carrying your loyalty card in their phone wallet can order — it shows locked to everyone else, which does the teasing for you.

A menu line with a hidden identity — the customer orders 'the mystery box' at a set price and the kitchen decides what goes in it. Great for clearing stock playfully; you control its price and availability like any other item.

A rotating featured dish — the system highlights a different pick from your chosen list so the page always has something 'today only'. You choose how picks rotate; the highlight updates automatically.

Retired dishes can be put to a customer vote. Past customers get a voting link, votes are weighted by how often someone has actually ordered from you, and you see the tally — a low-risk way to decide what returns to the menu.

Yes — when you lower a price in the menu editor, customers who ordered that dish can be notified (you control the window and frequency). Note it fires from a real price edit on an existing item, not from re-uploading a menu file.

Yes — toggle its availability. It disappears from customers instantly, keeps its history and photos, and can be re-enabled any time. Deleting is for items that are gone for good.

Yes. Saving in the admin clears your page's cache on the spot, so a refresh shows the change instantly. (Only edits made outside the admin — direct database changes by our team — can take up to a minute to appear.)

Yes, though last save wins per item — if you and a manager edit the same item simultaneously, the later save is what stands. For bulk work, one person with the Excel import is cleaner.

No practical one — the platform comfortably runs menus with hundreds of items across dozens of categories. For very large menus, the Excel import and the text-only page designs (built for long menus) are your friends.

Their page was loaded before your change. The moment they try to order, the server re-checks everything against the live menu — removed items, changed prices and sold-out stock are all caught, the customer gets a clear message, and nothing wrong is ever charged.

In 'Add to current menu' mode you get a SECOND COPY of every item — Add never updates or removes what is already there, and the screen warns you in amber before you confirm. Re-uploading a corrected sheet should use 'Replace menu' instead: it hides your entire current menu and rebuilds it from the file. Nothing is deleted either way, so past orders keep their history.

In Add mode a category is reused only when the name in your sheet matches a VISIBLE category exactly — capitalisation and spacing included. 'Burgers' and 'burgers ' are two different categories to the importer, and a hidden category is never reused. Copy the name straight from Manage categories if you want rows to land in an existing section.

No. 'Check file' gives a preview: the count of valid rows and every problem listed as Row 12 · Price: …. If you confirm, the valid rows import and the problem rows are left out — the screen says so. Fix those rows in the sheet and upload again.

Delete only unlocks once a category is empty — until then the page says 'Delete unlocks when the category is empty'. Move or delete its items first, or simply untick 'visible', which takes the category and its items off your customer page while keeping everything.

The Available/Sold-out pill on the Menu page is a manual switch. Stock tracking, on the Inventory page, is a running count: orders take units off it, the item flips itself to Sold out at zero, and a cancellation puts units back and brings it back on sale. Until you press 'Track stock' an item shows '—' and only the manual switch applies.

At the bottom of the Inventory page under 'Stock movements' — when, item, change, reason and note, newest first, 50 per page. Reasons are order, cancel, restock and adjust, so a count that looks wrong can always be traced to the order or the person that moved it.

It picks the dish that has gone longest without being featured — and among dishes that never had a turn, the one that sold least in the last 90 days. Every dish gets a turn before any gets a second one, and it deliberately does not feature your bestseller. The other modes are 'I choose it myself' and 'Work through a list I set'.

Nothing goes out until the new price has stood untouched for the waiting period you set (default 24 hours) — so a corrected typo never reaches a customer. The drop must also clear your minimum percentage (default 10%) and be worth at least AED 1.00. The 'Recent price changes' list shows each change as 'still waiting', 'told N customers' or 'no message sent'.

Model 1 nominates a fixed pool of dishes and prints the pool's combined allergens; model 2 allows any dish with a blanket 'we cannot guarantee allergens' warning; model 3 lets the customer state what they cannot eat and picks around it. Model 3 is a food-safety promise: only dishes explicitly DECLARED free of the excluded allergen are offered — an undeclared dish never — and if nothing qualifies, the order is refused rather than falling back to 'pick anything'.

Two different statements. 'Declare' with nothing ticked means 'I checked this item and it contains none of the fourteen'; 'Clear declaration' means nobody has said anything at all. A model-3 mystery box will never offer an undeclared item — not-stated is not the same as contains-nothing.

That is what Retire is for, on Marketing → Price drops & comebacks: the dish comes off the menu but keeps its history and can collect bring-it-back votes; 'Bring it back' restores it in one click. One catch: if it tracks stock and the count is zero, it returns as sold-out rather than buyable.