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 every location

For some configuration entities, such as tax rates and prep stations, you should create a master version of the entity and then create location-specific versions from that master and assign them to each location. This approach has two benefits:

  • It prevents changes in one location from inadvertently affecting other locations. This is particularly important where taxes are concerned.

  • It makes assigning configuration on the Advanced properties page and menu details pages easier because only the names of the master versions are shown, reducing the number of options you have to pick from.

To understand why this approach makes assigning configuration easier, let's consider the tax rate example. By default, the Toast platform creates a state and local tax rate for each location in your enterprise. If you left this configuration in place, the Applicable Taxes column on the Advanced properties page would look similar to this:

The details pages for menu entities would also display a long list of local and state tax rates.

By following Toast support's recommendations of creating a master version with location-specific versions based on the master, you end up with an Applicable Taxes column that looks like this:

Each master version and its related location-specific versions are represented by one name in the Applicable Taxes menu (for example, State Tax Master), thereby reducing the number of items in that menu to choose from and making configuration simpler. The details pages for menu entities also benefit from a similar treatment. When you select a master tax rate for a menu entity, the Toast platform automatically calculates which version of the tax rate to use based on location. This statement holds true for other entities configured in this way.

Configuration entities that should use this approach include: