How to use Location-Level Overrides for ECM In the Console
Last updated: August 8, 2026
How do we use ECM if a location, or locations, have variations from our core datasets?
When creating a new location using ECM controls, GRUBBRR's best practice try and limit the organization to one or two datasets, and then push those to all locations (more information can be found in our Intro to ECM guide). These datasets will help us manage the basic variants of the client's menu (i.e., a menu with alcoholic items and a menu without), without needing to manage separate menus for every location.
One way you can limit the number of datasets you have to create is to use location-level overrides for any "outliers" that may exist in an organization. For example, if only two restaurants in the entire organization aren't allowed to sell alcohol, we don't need to create a separate "Alcohol free" menu dataset. Instead, you can create a single dataset, then use Location-Level overrides to turn off alcoholic items at the impacted stores.
One way you can limit the number of datasets you have to create is to use location-level overrides for any "outliers" that may exist in an organization. For example, if only two restaurants in the entire organization aren't allowed to sell alcohol, we don't need to create a separate "Alcohol free" menu dataset. Instead, you can create a single dataset, then use Location-Level overrides to turn off alcoholic items at the impacted stores.
Go to reg.gcc.grubbrr.com
1. Once you've pushed the appropriate dataset from the ECM Menu...
2. Use the Scope Tool to navigate to the location that where you need to set up item overrides
3. Click "Menu Settings" in the left sidebar
4. Then select "Menu Override" from the dropdown
5. This page allows us to toggle the status of individual items from the Menu Dataset for this location
We can use this to activate items that are only available at this location, or deactivate items that the location doesn't sell from the Menu Dataset.
6. When you've finished making your configurations, remember to sync the changes to Kiosks at the location
Repeat this process as needed for any other locations with minor differences from the default dataset you pushed through ECM.