Food Basics
How the Food module fits together
Menus, menu items, modifiers, products and ordering portals — what each one is for, and the order to set them up in.
Last updated September 2, 2026
The Food module holds everything a food business sells and how it is presented: the dishes, the choices a customer makes on each one, the menus those dishes are listed on, and the online ordering pages customers order from. It is built for networks, so one head-office menu can run across every location with local prices where they differ.
A tribe is one location, branch or business unit inside your organisation. Menus and products are built once at organisation level; tribes see them, and — if you allow it — adjust prices and switch items off locally.
The pieces
| Screen | What it holds |
|---|---|
| Menu items | Each dish or product you sell — name, description, default price, photo, nutrition, and which modifiers and products it uses. Built once, listed on any number of menus. |
| Menus | How menu items are presented: a menu has sections, each section lists items, and an item can carry a menu-specific price. This is what websites and ordering portals display. |
| Menu Item Attributes | Dietary and other tags shown on items — Vegetarian, Gluten Free — each with an icon. |
| Menu Modifiers | The choices a customer makes on an item: a modifier group is the question ("Choose your bread"), its modifiers are the answers, each with an optional extra price. |
| Individual Products | What actually goes into a dish — a product is made of components in given quantities. |
| Ingredients / Components | The raw ingredients you buy, each with a price history — what you paid, and from when. |
| Coupons | Discount codes customers use at an ordering portal. |
| Customer Ordering Portals | The online ordering pages, each tied to a menu and to the locations that fulfil its orders. |
| Platform mapping | How your menu items line up with the same products on ezCater and Toast, so orders from those platforms attach to the right Gorilla Dash product. |
Setting up, in order
Each piece is used by the one after it, so the order matters. You do not need all of them — a business that only wants menus on its website can stop after step 3.
- Create any attributes you will tag items with, and the modifier groups customers will choose from.
- Create your menu items — one per dish, with its default price, photo and the modifiers it offers.
- Build a menu: add sections, list the items in each, and set any menu-specific prices. Decide what tribes may change locally.
- If you want online ordering, create a Customer Ordering Portal for the menu and add the ordering locations that will take the orders.
- If you want to record what goes into each dish, add components with their prices, build products from them, and attach products to menu items.
- If you sell through ezCater or Toast, open Platform mapping and map their products to yours.
Where to find it
Open Food from the organisation menu. The left-hand menu lists the screens above, grouped: everyday menu work, then products and ingredients, then coupons and ordering portals. Platform mapping is a set-up job you do once per platform rather than everyday work. Tribe users get a smaller Food menu inside their tribe showing the menus that apply to them.