Most bars repeat the same physical logic: where the bartender stands, where backup bottles live, and where cold storage sits. The starter list on Build Your Bar mirrors how experienced operators already think about the room — not a rulebook you have to follow.
This is your map. Rename stations, delete what you do not have, add rooms we never imagined. The inventory program only needs names that match how you walk the bar.
Wells are the speed rail: open bottles in reach while the bartender faces guests. In a classic three-well layout, order usually follows traffic and pour volume.
The center of gravity — usually the middle well or the station with the highest-volume spirits. House vodka, house gin, core rums and tequilas, whatever moves every shift. If a guest orders "whiskey and soda" without a brand, it probably comes from here.
The service well — backup and support for the main during rush. Often mirrors the main with duplicates, or holds the second tier of call brands. Banquet bars, dining-room service bars, and cocktail stations frequently use this name even when they are the only well in the room.
The point of the bar — the station farthest from the service well, often at the end of the rail where the layout turns or dead-ends. Lower-volume or specialty pours live here: mezcal, aperitifs, niche amari. Physically it is the "far corner" of the bartender's reach, not a second main.
Back bar stations are display and depth, not the speed rail. We repeat Main · Point · Service so your voice walk sounds natural: "Back bar main, top shelf, left to right…"
Single-shelf room? Keep one back bar row and delete the other two. Long wall of shelving? Add rows like "Back Bar North" — whatever matches your walk.
Split beer between bar cooler and walk-in if that is how you count. Combine wine into one station if you only have a single fridge. The type badge is a hint for reporting later, not a law.
High-volume nightclub, hotel lobby, brewery taproom, or German hotel bar with a nine-day cycle: the templates are a starting sketch. Operators routinely:
You are building a map for counting, not passing a health inspection of nomenclature. Get the geography right for your team; the program handles the rest.