This guide will be removed on April 29, 2022. Please use our new, easier-to-use Toast technical documentation site. All updated content is on the new site.

Creating a master version with location-specific versions for some locations

Some configuration entities, such as price levels or courses, may be used by most but not all of the locations in your enterprise. In this scenario, you can create a master version of the entity and set its Target and Owner to the corporate restaurant group. For any restaurant sub-groups or locations that need a modified version of the entity, you create a new version from the master and set its Target and Owner to the restaurant sub-group or location. This technique allows you to specify one configuration that is shared by most of your locations but also override that configuration for certain restaurant groups or locations.

Configuration entities that typically benefit from this approach include:

  • Menus, menu groups, and modifier groups (see Versioning at the menu group and modifier group level for more information)

  • Price levels

  • Courses

  • Dining options

    Note

    Dining Options are similar to Tax Rates in that the Toast platform automatically creates dining options for each location in your enterprise. Toast support recommends that you archive these auto-created dining options and create master dining options with location-specific versions if necessary.