A menu item is one thing you sell — a board, a box, a drink. It exists once, at organisation level, whatever menus it is listed on. Everything that is true of the dish wherever it appears lives here; everything that depends on the menu (a special price, a different photo) lives on the menu listing instead.
Creating one
Go to Food → Menu items and click Create Menu Item. The form is in two halves.
| Field | What it is |
|---|---|
| Menu Item Name | What customers see. Required. |
| Menu Item Slug | The web address for the item, filled in from the name. Must be unique in your organisation. |
| Attributes | Dietary and other tags — Vegetarian, Gluten Free — from Menu Item Attributes. |
| Menu Item Description | The menu description. |
| Default Price | The price charged unless a menu listing or a tribe sets another. Enter dollars. |
| Servings From / To | How many people it serves, for catering menus. |
| Nutrition | Serving size (quantity and unit), energy (with its unit), and an allergy statement. |
| Square Photo | The image shown on menus and portals, with a description for accessibility. |
| Products | The products this dish is made from, with quantities — the recipe behind it. See Products and ingredients. |
| Modifiers | The modifier groups the customer chooses from when ordering this item. |
Modifiers on an item
Attach a modifier group and every customer ordering the item is asked that group's question — bread choice, add-ons, allergies. The groups themselves are built once under Menu Modifiers and reused across items, so changing the options in a group changes every item that uses it.
Editing and deleting
Editing an item changes it everywhere it is listed. Deleting one removes it from every menu and drops any platform mapping that pointed at it, so an incoming ezCater or Toast order for that product would no longer have anything to attach to. If a dish is off for the season, take it off the menu — or let tribes disable it — rather than deleting it.