Skip to content

Manage locations and the active location

A company can run more than one room, and those rooms rarely share a tax rate or a tap wall. Locations is where each one is described.

Your Company is the business. A location is a place that pours. Settings that belong to the business live once at the company level; settings that differ between rooms live on each location.

That split is why moving between locations does not mean re-entering your catalog. Beverages, Distributors, and Producers belong to the company. Taps, taxes, and addresses belong to the room.

  • Location Name and Display Name — the internal name and the one guests see.
  • Address, City, State, and Phone — the public details.
  • Sales Tax — the rate for that room, because a second taproom in another jurisdiction rarely matches the first.
  • Round to Nearest — how prices are rounded once tax is applied, so your menu shows tidy numbers.

Two toggles let a location depart from the company settings rather than inherit them:

  • Customize Location Margin/Markup — give this room its own pricing strategy. See Set your markup strategy.
  • Customize Location Brand — give this room its own Primary, Secondary, and Tertiary brand colours, which flow through to menus generated for it.

Leave both off and the location follows the company. Turn one on only when the room genuinely differs; every override is something you will need to remember to maintain twice.

If a location has Clover connected, it also carries dropdowns that map your Clover categories onto BevWerk concepts such as Draft Inventory and In House Glass Pours. These tell BevWerk which Clover category means what, and they appear only once that integration exists — see Understand POS sync operations.

BevWerk always works in the context of one active location. It determines which taps, taplists, and inventory you are looking at, and it is remembered between sessions so you land where you left off.

If a screen shows data you did not expect — an unfamiliar tap list, inventory that looks wrong — check the active location first. It is the most common explanation, and the quickest to rule out.