What Athletic Directors Need to Know About Team Stores

Athletic directors sit at a strange altitude with respect to team stores. Individual coordinators are obsessive about their team's gear; AD-level oversight has to balance consistency across twenty sports, protect the department's reputation, and avoid the ten thousand small operational fires that get delegated upward when something goes wrong.

This post is for that altitude.

The governance question

The central AD question about team stores is: "How much should I standardize versus delegate?"

Over-standardize and you end up with one giant athletic department apparel program that's administratively simple but feels generic — every team looks like a slightly different version of the same uniform. Under-standardize and you end up with twenty independent storefronts, each run by a different parent volunteer, with wildly different quality, payment practices, and visual identity.

The middle path most ADs settle into has three layers:

1. Identity standards are centralized (colors, logo usage, branding, what "official" means).
2. Production and payment infrastructure are centralized (the same vendor/platform across all sports so the AD doesn't have to vet twenty individual providers).
3. Store operation is delegated (each team's coordinator runs their own store with their own product mix, within the identity/platform guardrails).

This structure scales. An AD can govern ten sports this way as easily as one.

The financial questions you should be asking

Who actually receives the money? This is the first thing to nail down. When a parent places an order on a team store, the money can flow in several different directions:

• Directly to the booster club's bank account
• To a platform escrow, then to the booster club
• To the athletic department, then disbursed back per-team
• To the coordinator personally (a serious red flag)

The right setup varies by state and by how your district handles booster funds, but the answer should never be "the coordinator's personal Venmo." If it is, your program has an accounting exposure that will eventually become a problem.

Who pays the production cost? On-demand stores handle this cleanly — the production cost is deducted from each order and the remainder is the fundraising margin. On bulk/traditional orders, somebody has to front the inventory purchase, and that somebody is usually either the booster club or a parent who gets reimbursed later (badly).

What's the markup policy? Teams usually mark up their apparel 20–40% as fundraising margin. Most ADs find it valuable to set a ceiling (say, 40%) to prevent programs from pricing families out, and a floor (say, 15%) to ensure the fundraising is meaningful. Individual coordinators can pick within that range.

The brand standards conversation

This is where most AD-run programs underinvest. Without explicit brand standards, coordinators will:

• Use whatever version of the school logo they have a JPG of (often an outdated one).
• Apply school colors inconsistently — "navy" at one sport, a slightly different navy at another.
• Typeset player names in whatever font feels right, which rarely matches the school's actual design system.
• Add random graphics (a mascot with a different pose, a font effect, a drop shadow) that don't match any other team.

The fix is a one-page brand standards document. Not a design manual — a one-pager that says:

• Here is the school logo file. Use this one only.
• Here are the two primary colors, in hex and in apparel-print-spec (Pantone or equivalent).
• Here is the approved typeface for athlete names on jerseys.
• Here is what a compliant jersey design looks like. Here is what a non-compliant one looks like.

With this document, coordinators can make their own design choices while staying inside the program's visual identity. Without it, every season the department's visual consistency drifts, and eight seasons later you can look at tournament photos and not immediately recognize your own teams.

What to standardize vs. delegate

Standardize:

• Logo files, color palette, typography
• The apparel platform/vendor
• Financial flow (where the money lands)
• Data ownership (who has the list of customer emails — this matters for future seasons)
• Exchange and refund policies

Delegate:

• Product selection
• Store timing (align with each sport's season)
• Pricing within the approved markup range
• Coordinator choice (each team picks its own point person)
• Promotional cadence

The first group changes rarely and should be managed once. The second group changes every season and every team, and micromanaging it from the AD's office is how ADs burn out.

Common governance traps

The vendor sprawl trap. Every coordinator finds "their guy" locally. After three years, the department is spending across six different apparel vendors with six different quality levels, six different payment flows, and six different production timelines. Consolidating back is politically painful. Start consolidated.

The individual coordinator dependency trap. One super-coordinator runs five teams' stores because they're good at it. Then they move, and five teams lose their apparel operation in the same month. Every store should be documented enough that a new coordinator could pick it up cold.

The "we'll figure it out" trap. A storefront launches without a defined refund policy, because nobody wanted to write one. Then a family asks for a refund on a custom jersey, and the coordinator has no guidance, and the AD gets the escalation. Write the policy once.

The data-ownership trap. Team stores accumulate valuable email lists over the years. If those lists live inside a coordinator's personal account, the department loses them when that coordinator leaves. Insist on shared accounts or department-owned data from day one.

The one-page program policy

The shortest way to do this right: one page. A program-wide team apparel policy that a new coordinator can read in five minutes, signed by the AD, posted in the coach handbook.

It should cover: approved vendor, approved logo files, color palette, financial flow, markup limits, refund policy, data ownership, and who to call when something breaks.

That one page — more than any particular piece of technology — is what makes the difference between a twenty-sport program that looks intentional and one that looks cobbled together.