How Many Products Should an Employee Company Store Have?

Professional header image for educational tutorial: How Many Products Should an Employee Company Store Have?

An employee company store with 60 products can look more generous than one with 12. It can also work against itself. The real question is not how many products you can fit into a store, but how many employees will actually wear, reorder, and use for real work occasions. That is catalog discipline: a short, organized assortment where each item earns its place through sell-through data.

The evidence is not a simple rule. Large assortments can create choice overload, while shoppers still value some variety. The idea that a 60-product store always sells less than a 12-product store is an unverified hypothesis to test, not a fact to repeat. This piece walks through what that discipline looks like in practice: sizing the catalog to real use occasions, building the three starter tiers, and running a sell-through test that decides what stays. Common launch, variety, and multi-location questions are covered. OneStop Northwest helps Shelton-area and nationwide organizations simplify company stores and branded merchandise.

Why a Bigger Catalog Is Not Automatically a Better Benefit

In our experience building employee stores, a lean catalog of roughly a dozen items typically outsells a sixty-item one. That is an operating rule of thumb, not a measured benchmark or published statistic. The tension is real: large assortments make employees browse, compare, and second-guess, yet broader selections also draw people in and let them hedge against choosing wrong. Most assortment research comes from grocery and other novelty-driven categories. Logoed workwear is chosen on fit, role, durability, and weather, so the overload effect is at least as likely here, not less. The practical takeaway: catalog size is a management decision. The default of adding more is what quietly turns a benefit into clutter. Treating each uniform cycle as a one-off procurement event compounds that clutter, which is why a managed apparel program may fit growing organizations better.

What “Enough” Actually Means for an Employee Store

A catalog is managed by SKU: one style, color, and size combination that requires its own decoration setup, stock, and store photo. Enough is not a number. It is the smallest assortment covering every use occasion your workforce actually has, with a size run that fits them. Benefit stores, where employees choose items, and uniform programs, where everyone receives one item, have different right answers; mixing that logic bloats catalogs. Use the earned slot rule: no item goes live without a named occasion, role, and expected wear frequency. Buy-side economics now favor short catalogs. Through our national supplier network and more than $2 billion in collective buying power, many items carry low or no minimums, so a style no longer needs hundreds of units to earn its place. The guide How to Launch an Employee Company Store in 90 Days can help you sequence that first assortment.

Start With Use Occasions, Not Product Categories

The earned-slot rule gets practical once you organize people, not products. Sort the workforce by where they are seen and what they do: customer-facing, field or site, office and hybrid, and seasonal or event staff. For each group, ask who sees them, how often they wear the item, and what conditions the work involves. Then pick one anchoring occasion per group, such as a weekly in-office day, a customer presentation, a site visit, or a summer event series, and build that group’s items around it. Reject product-category organization. Category thinking says add another polo; occasion thinking says the polo need is already covered. Keep the occasion map on a single page and treat it as the filter every future request must pass, the discipline a managed corporate apparel program depends on.

The Three Tiers of a Starter Catalog

XPTsjTOAFdiRg KNpRXJy

With the occasion map in hand, sort every item into one of three tiers. Logoed layers for customer-facing roles carry most of the design attention, core basics get the widest size and color coverage, and the seasonal rotation keeps the smallest footprint. Match decoration to the job: embroidery on durable layers, screen print on high-volume basics, since every logo on every item adds a setup. Those setups add up quickly, as we explain in ordering promotional products with your logo. Then guard against tier creep: a seasonal item that sold well for one quarter does not automatically earn promotion to core. Make it earn that slot through repeated sell-through.

Tier 1: Logoed Layers for Customer-Facing Roles

Tier one is the smallest but most visible: cap it at two to three styles, one outer layer, one mid layer, and one shirt that works indoors. Choose durability and fit over trend. These garments appear in team photos and in front of clients, so pilling, shrinking, and a narrow size run become brand problems. Limit color choices to two that align with brand standards, and run the complete size range in both rather than six colors with gaps. Document embroidery placement as a written brand standard so a replacement order placed years later still matches the original. See the Corporate Apparel Buying Guide for HR and Operations Leaders for vendor evaluation and program structure.

Tier 2: Core Basics That Everyone Actually Wears

Where Tier 1 narrows choices for visibility, Tier 2 should narrow them for repeatability. Stock three to six basics employees reorder on their own: a tee, a fleece or hoodie, a cap, and one cold-weather layer. Favor neutral brand colors and a full, inclusive size run, since basics are judged on availability, not novelty. Track second and third purchases instead of the launch spike; a basic someone buys again has earned its slot. Keep replenishment predictable by making core items the first to restock and the last to retire. The same discipline applies when setting up a school spirit store, where steady core favorites outperform a crowded assortment.

Tier 3: A Small Seasonal Rotation With a Planned Exit

Core basics carry the everyday load; the seasonal tier carries novelty. Keep this rotation to two or three items, each with a fixed window of eight to twelve weeks on the store. Set the exit date before launch, plus a written rule for leftovers: sell through, carry over once, or retire. That gives employees a place to look for something new without widening the core catalog. Enforce one in, one out: a new seasonal item enters only after the previous window closes. Treat the window as a commitment, not a suggestion.

How Many Products Is Enough? A Sizing Method

Seasonal rotation is capped. The rest of the catalog needs a cap too.

Size by counting occasions, not products. Take the occasion map, assign one item per occasion per layer, and treat that total as a floor, not a target. As a starting point to test rather than a benchmark, many single-location employers land around ten to fifteen active items across the three tiers. Replace that estimate with your own sell-through data after the first quarter.

Add an item only when a real occasion must be covered twice: two climates, two visibility levels, or two very different work conditions. Inside a style, cap variety at two colors with a complete size run, not five colors with gaps. Write the add and remove rules on day one, so policy, not the loudest request, bounds growth.

2QThxJcEoui8fNf68XNuA

The Sell-Through Test: Keep, Reorder, or Retire

With the catalog sized, the review rhythm decides what stays. Sell-through is units sold divided by units available in the period, measured by style and color, not style alone. Review at thirty, sixty, and ninety days, then seasonally. Restock fast movers. Give slow movers one more window. Exit items that never move.

Read the size curve, not just the total; healthy overall sales can hide remaining stock in two sizes nobody orders. Separate a weak item from a weak listing. Low visibility, a poor photo, a missing size, or no occasion map entry is a merchandising fix, not proof the product fails. That distinction matters when weighing branded uniforms vs. off-the-shelf workwear on total cost.

Keep the review on one page and bring it to a quarterly meeting with whoever owns the store. Cuts become routine decisions, not arguments.

What an Overstuffed Catalog Costs

The sell-through review exposes costs that trace back to catalog size. In our experience across employee store programs, decoration setup and art approval run per item, per logo, and per location, and late additions rarely sell enough to repay that setup. Budget freezes in the tail: slow sizes and low-demand colors tie up money you could use to restock what employees want. Presentation suffers when uneven size coverage makes a long catalog read like a clearance rack, and employees stop trusting it to have their size. Administration multiplies with more SKUs to track, more size questions, exchanges, and HR or procurement exceptions. Test this against your own order history. If you are weighing a managed portal against one-off orders, see company store vs. bulk promo order.

How Often to Rotate Without Churning the Catalog

Given those costs, discipline means timing changes deliberately rather than freezing the catalog. Set the review cadence by tier.

  • Core: review twice a year. Change an item only for a supplier discontinuation or a clear sell-through signal. Stability is the feature, not a sign of neglect.
  • Customer-facing: refresh when roles, seasons, or customer expectations genuinely change, not because a calendar says so.
  • Seasonal: keep fixed windows, set the exit date before launch, and write down the carryover rule.
  • Outside the schedule: apply one in, one out to every addition, so mid-year requests cannot quietly expand the catalog.

Protect continuity above all. Keeping the same core fit and color across multiple years builds reorder behavior and reduces size confusion among employees. That cadence keeps the catalog stable enough to audit against real order history.

Run a First Catalog Audit in Five Steps

Q 5Wws LoMaPGLswNOjKh

When a scheduled review arrives, or before you inherit a store you did not build, run the audit in this order.

  1. Pull twelve months of order history and sort it by style and color, not by product name. Product names hide duplicates.
  2. Map each item to a use occasion and a tier. Flag the orphans that map to nothing.
  3. Sort by sell-through and mark every item keep, reorder, or retire.
  4. Check size coverage on the keepers. Close the gaps before you cut anything else.
  5. Rewrite the store page to match the audited list. Then publish the add and remove rule so the catalog stays bounded.

Done on a single page, the audit turns catalog decisions into routine housekeeping instead of annual debate. You can also hand it off. OneStop Northwest supports the store platform, decoration, fulfillment, and ongoing program support from Shelton, serving organizations across the Pacific Northwest and nationwide.

Employee Company Store Assortment Questions

With the audit complete, here are the questions we hear most when a store launches.

How many products should a company store launch with?

For the launch itself, start near a dozen active items, split across the three tiers. Treat that number as a testable starting point, not a benchmark. Then let sell-through data move it up or down.

A launch catalog should stay small because the first quarter is when you learn what employees actually order: which sizes run out, which colors they choose, and which roles use each item. A crowded launch hides those signals in thin demand and excess stock. Launch lean, read the first ninety days, and let evidence set your next catalog size.

Do employees want more variety than a short catalog offers?

Yes, and the demand deserves respect. Asking people to commit to one shirt for a whole year creates a small uncertainty, and the standard human response is to want options in reserve. That instinct is exactly why the seasonal tier exists: a fixed window with two or three new items gives people something fresh to consider without widening the core.

The mistake is answering the request literally. Variety inside a disciplined catalog comes from structure, from tiering and rotation, not from stocking eight versions of the same polo. Show employees where the customer-facing layer, the basics, and the rotation live, and most of the “we need more options” conversation takes care of itself.

Can one short catalog serve multiple locations or departments?

That same tiering logic scales across locations. Organize one storefront by role, not by building: a core basics section that serves every site, plus customer-facing sections that vary only where the work or visibility genuinely differs. A field crew in two towns usually needs the same basics and the same visibility layer, so separate catalogs only add duplication and uneven stock. Split into multiple catalogs only for a real operational difference, such as regulated safety gear or site-specific uniform requirements. Otherwise, role-based sections keep one short catalog coherent, measurable, and easier to maintain as you add locations.

Make Catalog Size a Decision, Not a Default

That role-based structure only holds when the catalog itself stays bounded. Audit before you expand: map every item to a use occasion, then cut what maps to nothing. Size the catalog to occasions, start near a dozen active items, and let sell-through decide what survives the first two quarters. Hold seasonal items to fixed windows with one in, one out, so variety has a home without widening the core. Discipline at launch, reinforced by the sell-through review cadence above, is what keeps the store useful years later.

Conclusion

A stronger employee store is not a bigger one. Size the catalog to real use occasions, build it in clear tiers, and let sell-through decide what stays. Customer-facing layers, core basics, and a small seasonal rotation give employees variety without the clutter, duplicate stock, and maintenance burden of an overstuffed store. That same role-based structure can serve multiple locations and departments when the differences are operational, not imagined. The next step is practical: run the five-step catalog audit before you add another product, map each item to a use occasion, and set your thirty, sixty, and ninety day review. OneStop Northwest can help you apply that discipline as a single-source partner. Make catalog size a deliberate decision, then keep refining from evidence.

Frequently Asked Questions

How many products should a company store launch with?

Start near a dozen active items, split across the three tiers: logoed layers for customer-facing roles, core basics, and a small seasonal rotation. Treat that number as a testable starting point rather than a benchmark, then let sell-through data move it up or down. A launch catalog should stay small so the first quarter reveals which sizes run out, which colors employees choose, and which roles use each item.

Do employees want more variety than a short catalog offers?

Yes, and the post treats that demand as legitimate. Committing to one shirt for a whole year creates uncertainty, so people want options in reserve. The seasonal tier addresses this with a fixed window of two or three new items, giving employees something fresh without widening the core. Variety should come from structure, such as tiering and rotation, not from stocking many versions of the same item.

Can one short catalog serve multiple locations or departments?

Yes. The post recommends organizing one storefront by role rather than by building, with a core basics section serving every site and customer-facing sections that vary only where the work or visibility genuinely differs. Separate catalogs are only justified by a real operational difference, such as regulated safety gear or site-specific uniform requirements, since multiple catalogs add duplication and uneven stock.

How do I decide whether a slow-selling item should be kept or retired?

Use the sell-through test. Sell-through is units sold divided by units available in the period, measured by style and color. Review at thirty, sixty, and ninety days, then seasonally. Restock fast movers, give slow movers one more window, and exit items that never move. Also read the size curve and separate a weak item from a weak listing, since low visibility, a poor photo, a missing size, or no occasion map entry is a merchandising fix rather than proof the product fails.

How do I keep the catalog from growing back after it has been audited?

Write the add and remove rules on day one so policy, not the loudest request, bounds growth. Apply one in, one out to every addition, and only add an item when a real occasion must be covered twice, such as two climates, two visibility levels, or two very different work conditions. Set review cadences by tier: core twice a year, customer-facing when roles or expectations genuinely change, and seasonal on fixed windows with exit dates set before launch.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top