Building a Territory That Matches How Your Team Sells

Every sales team splits up the map differently. Some managers just want a clean, named rollup of “my rep’s territory” without wading through a hundred store names. Some reps want the opposite: they want every door in front of them so they can add or drop specific accounts as relationships shift. Hoodie supports both as part of its cannabis dispensary distribution tracking, because a territory tool that only works one way ends up working for nobody.

There are two ways to build a custom territory in Hoodie: Tags and Views. They start from the same place (a set of dispensaries you care about), but they show up differently, and they’re built for different people.

Tags: the clean rollup

A Tag groups stores under a single label (“NE Territory,” “Rep: Maria,” “Tier 1 Accounts”) and that label is what shows up in the filter bar. You don’t see the individual store list every time you filter by it; you see the name, and the data behind it. That makes Tags the right tool when the point is a summary, not a list. A regional manager reviewing five reps’ books wants to flip between “NE Territory,” “SE Territory,” and “West Territory” and read the numbers, not scroll past forty store names to get there.

Views: the door-by-door list

A View lists every retail door directly in the filter bar. Nothing is hidden behind a label: you see the accounts, one by one, and you can select or deselect individual doors right there in the filter. That makes Views the right tool when the point is control at the account level: a rep who wants to pull one troublesome store out of the picture for a week, or build a shortlist of the eight accounts they’re calling on Thursday, without redefining an entire territory to do it.

Hoodie’s Territory Builder: filter to the dispensaries that matter, select them on the map, and save the result as a Tag or a View.

How to decide which one to use

Ask what you actually need to see day to day.

• If you want a named, repeatable filter that summarizes a whole group of stores without the clutter of every name, use a Tag.
• If you want to see and adjust individual doors on the fly, use a View.

Managers building reporting rollups tend to reach for Tags. Reps working a live call list, especially one that changes week to week, tend to reach for Views. Nothing stops a team from using both: a manager’s Tag for the quarterly view, a rep’s View for this week’s list, since they’re just two ways of pointing Hoodie at the same underlying stores.

A worked example

Say a rep covers the Northeast and wants a territory that matches their actual book of business, not a rigid zip-code map.

• Start from Hoodie’s store list and select the dispensaries the rep actually calls on. This can cross state or regional lines if that’s how the territory really works.
• Decide how it needs to show up. If the rep wants a clean label to filter by without scrolling through every store name, save the selection as a Tag called “NE Territory.” If the rep wants to see and tweak individual doors as accounts open or close, save it as a View instead.
• From there, that Tag or View becomes a standing filter across Sales Enablement: stockouts, price violations, and account performance all resolve to just that territory, without rebuilding the filter each time.

Either path gets to the same place: a territory defined by how the team actually sells, not by a boundary drawn on a map.