Platform Mapping
Food settings: platform menus and order push
Pulling a fresh copy of a platform menu so the mapping screens have something to work with, and setting the rule for writing accepted ezCater orders into Toast.
Last updated September 16, 2026
Select Food in the left-hand menu, then Settings. Two things live here, and both concern the ordering platforms your tribes trade on rather than your own menus: keeping Gorilla Dash's copy of a platform menu current, and deciding what happens to an accepted order.
Platform menus
The platform mapping screens work against a mirror — Gorilla Dash's own copy of what each platform currently has on its menu. Without that copy there is nothing on the platform side of the mapping screen to point at, which is why a tribe that has just been connected shows nothing to map.
The Platform menus card lists every platform connected to a tribe in your organisation, with how many of its locations have been mirrored and how recently. "No menu has been mirrored yet" means exactly that, and Pull menus is the remedy.
- Select Pull menus.
- Choose the Platform.
- Choose the Locations you want. Leave the box empty to pull every location.
- Select Pull now.
One job runs per location, in the background, so nothing appears instantly. The mapping list fills in as the menus land, and a large network pulling every location will take a while — start it and come back rather than watching it.
Pull menus again whenever a platform menu has changed — new items, renamed items, a seasonal range. Until you do, the mapping screens are working from the old menu and the new items will not appear to map.
Order push
When a catering order is placed on ezCater, somebody has to enter it into the tribe's point of sale before the kitchen can act on it. Order push does that automatically: once the order is accepted, it is written into Toast for you.
The Order push card sets the rule. There is one organisation default, and any tribe can be given its own rule instead.
| Setting | What it decides |
|---|---|
| Push | On or off. Off means accepted orders are not written into the point of sale and somebody enters them by hand, as before. |
| Before the event | How long before the event the order is written. The default is two hours, and it can be set up to a week. |
| On cancel | What happens if the customer cancels after the order has already been pushed: Email the tribe, so somebody voids it themselves, or Void automatically. |
The reason for a lead time rather than pushing immediately is that a Toast order cannot be edited once it is written. Holding the order until shortly before the event means a customer who changes their mind, or adds to the order, is still handled by ezCater rather than leaving a wrong order sitting in the kitchen system. Set the lead time to however long your tribes need to prepare, and no longer.
Giving a tribe its own rule
The table beneath the default lists every tribe connected to either platform, with the connection it has on each side, whether it follows the organisation default or has a rule of its own, and what that rule is.
- To change one tribe, select the pencil on its row.
- To change several, select them and use Edit selected.
- In the dialog, turn Use the organisation default off to set the tribe's own rule, or on to send it back to following the default.
The same rule can be set from the tribe's own side, under Sales then Settings, which is where a tribe user would find it. Both screens are editing the same setting.
A tribe needs a live connection on both sides before any of this happens — an ezCater connection to receive the order and a Toast connection to write it into. The connection chips on each row are the quickest way to see which tribes are not ready.