Platform Mapping
Platform mapping: how ezCater and Toast line up with your menu
Why the same product exists three times, what a mapping is, which direction is which, and what the statuses mean. Start here.
Last updated September 2, 2026
If your locations sell through ezCater or run Toast at the till, the same product exists in three places: as a Gorilla Dash menu item, as an ezCater menu item, and as a Toast menu item. Each system names and identifies it its own way. Platform mapping is where you tell Gorilla Dash which is which, so that an order placed on a platform lands against the right product in your reporting, and so that a Gorilla Dash product can be expressed in the platform's own terms.
A tribe is one location, branch or business unit inside your organisation. Gorilla Dash keeps a mirror of every location's platform menus, so a mapping made once at organisation level covers every location that sells the product.
Two directions, two screens
A mapping joins one Gorilla Dash product to one platform product. You can look at that join from either end, and the module gives you a screen for each. The toggle at the top of both screens switches between them; the platform selector chooses ezCater or Toast.
| Screen | Rows are… | Answers the question |
|---|---|---|
| ezCater → Gorilla Dash | every product on the ezCater menus, across all locations | When an ezCater order comes in for this product, which Gorilla Dash product is it? Anything unmapped here cannot be attributed. |
| Gorilla Dash → ezCater | every Gorilla Dash product on an Active menu | Which ezCater product does this Gorilla Dash product correspond to, and at how many locations does that hold? |
Both screens edit the same mappings — mapping "Bread Box" to ezCater's "Bread Box" on one screen shows up on the other. The direction you start from is a matter of which list you are working through. Most people start from the platform side, because every platform product must map to something, while a Gorilla Dash product that is not sold on the platform is fine unmapped.
What the statuses mean
| Status | Meaning |
|---|---|
| Not mapped / Needs mapping | No link yet. An incoming order line for this product cannot be attributed. |
| Suggested | Gorilla Dash matched it by name but nobody has confirmed it. Suggestions are not used until confirmed. |
| Confirmed / Mapped | A person confirmed the link (or it was seeded from the platform's own data). This is the only state that counts. |
| Mapped at some locations | No organisation-wide link, but one or more locations have their own. Orders at the other locations cannot be attributed. |
| Mapped more than once | Two Gorilla Dash products are confirmed onto the same platform product organisation-wide, so an incoming line is ambiguous. Unmap one. |
| Imported | The platform product is only known from a spreadsheet you uploaded; the platform has not shown it on a real menu yet, so the mapping cannot take effect until it does. |
Reach: brand-wide or local
Each platform product shows how many of your location menus carry it. All 104 locations is a brand-wide product; Multi-location · 5 of 104 is carried by some; 1 location only is a product one franchisee added themselves. Neither ezCater nor Toast marks a product as "brand-wide" — this count is how you tell, and the Reach filter lets you work through the brand-wide products first, where each mapping does the most good.
What is not a mapping
- Mapping does not change your menus, your prices or anything on the platform. It is a lookup table.
- Mapping does not create Gorilla Dash products — unless you ask it to, from the ezCater → Gorilla Dash screen, when none of yours fits.
- Mapping is per platform. A product mapped for ezCater is not thereby mapped for Toast.