Buying Guide — Company stores
How to set up a company store for employee uniform and merch ordering
A company store lets your employees order their assigned uniform pieces and approved branded merch directly — no HR back-and-forth, no individual approvals, no manager sign-off on a polo. Here's exactly how OTIA stands one up, what we need from you to launch, and how the program runs once it's live.
01 · The outcome
What you walk away with at the end of this.
At the end of this you have a branded self-service portal at /stores/<your-company> where employees authenticate, browse the SKUs HR has approved for their role, place orders against a per-employee or per-role budget, and we fulfill directly to their address or to a central location. HR isn't in the middle of individual orders. Managers aren't approving polo purchases. Decoration is locked in at the SKU level — no employee can accidentally reorder the logo at the wrong size or color. The store runs on autopilot once configured; you only touch it for new-hire onboarding, role changes, and the occasional SKU refresh.
02 · The steps
In order.
Step 01
Step 1 — Lock in your SKU list and tier structure
Before the store can stand up we need the locked-in product list — typically 4-12 SKUs covering the polo, layering pieces, headwear, and any program-specific items (vests, jackets, scrub tops for healthcare). For multi-tier programs we configure separate SKU sets per role: staff sees the staff polo, managers see the manager polo, executives see the premium tier. Use our Best Polos for Company Uniforms guide as a starting point if your SKU list isn't locked yet. We finalize the list, confirm color/size availability with the manufacturers, and lock decoration placement and logo files for each SKU. This step is typically a single 60-minute working session with HR plus operations or brand.
Step 02
Step 2 — Decide on the budget model
Three common patterns: (a) Company-paid — every order is invoiced to the company, employees order against an approved SKU list with no individual budget cap. This is the simplest model and the right call for most uniform programs. (b) Per-employee allowance — each employee has an annual or per-period budget allowance (e.g. $200/year), orders within budget are company-paid, orders above the allowance require employee payment. Common for healthcare scrubs and trades workwear. (c) Employee-paid merch — for branded merch stores (non-uniform), employees pay personally with corporate-discount pricing. Each model maps to a different store configuration in the OTIA backend; we set this up at launch.
Step 03
Step 3 — Provide the assets
We need: company logo as vector (SVG / EPS / AI), brand color Pantones or hex values, the storefront name (e.g. 'NorthShore Uniform Store'), a single hero image or photo we can use on the landing screen (or we'll use a clean OTIA-branded default), and the employee directory or domain restriction list. For employee authentication we typically use single-sign-on against your existing email domain — anyone with an @yourcompany.com email can authenticate; non-employees are filtered out automatically. Larger programs sometimes use a per-employee invite code system instead; both work, SSO is faster.
Step 04
Step 4 — Approve the storefront preview
We build a private storefront preview at /stores/<your-company>-preview and walk HR and brand through it. Verify: storefront branding (logo, colors, hero), SKU list matches what was locked in step 1, role-based visibility works correctly (staff don't see the executive polos, etc.), pricing displays correctly, decoration mockups render right (each SKU shows the embroidered logo positioning at the size it'll actually be produced). This is usually a 30-minute review call — most programs need 0-2 small tweaks before approval. Once HR and brand sign off, we promote the preview to the public storefront URL.
Step 05
Step 5 — Onboard employees with a launch email
We draft a launch email template you can send through your existing HR channel: subject line, intro copy explaining the store, the direct URL with SSO link, a one-paragraph FAQ block (typical questions: what's covered, what's my budget, when does it ship, who do I contact if a SKU is wrong). Most programs launch with a single companywide email; multi-location programs sometimes do region-by-region rollout. We provide the template; HR sends it from their address for credibility. From the moment the email lands, employees can order — no further setup needed.
Step 06
Step 6 — Set the ongoing fulfillment cadence
Once employees start ordering, the store runs on one of two fulfillment models. (a) Per-order shipping — every employee order ships individually to the employee's address as soon as production completes (typically 7-10 business days from order placement). Higher shipping cost overall, fastest delivery to the employee. (b) Batched shipping — we collect orders over a defined window (typically weekly or biweekly), produce them as a batch, ship the consolidated batch to a single corporate location (HR office or main location) for internal distribution. Lower shipping cost, longer lead time per employee. Most programs start with per-order and shift to batched as volume grows.
Step 07
Step 7 — Operate the store on autopilot
After launch, the store needs minimal operational attention. New hires authenticate against SSO automatically — no per-employee setup. Role changes (staff → manager → executive) are managed in your existing HR system and propagate to the storefront visibility rules. SKU refreshes (color additions, new pieces, retirement of an old SKU) we handle on request — typically 24-48 hour turnaround on a SKU update. Invoicing runs against your account on the cadence you set (monthly, quarterly, or per-order). HR's only ongoing role is the new-hire onboarding email mentioning the store URL and the occasional escalation when an employee has a size issue.
03 · Common mistakes
What we see go wrong.
Launching the store without a locked SKU list
Programs that launch with 'we'll figure out the products as we go' end up with constant SKU changes, mismatched embroidery setups across orders, and HR back in the middle of every order. Lock the SKU list before the storefront preview. SKU additions after launch are fine; SKU instability at launch wrecks the program.
Trying to manage employee directories outside the store
Some programs try to email a static URL to employees and skip the SSO setup. Within 6 months you have ex-employees ordering against the company-paid budget, current employees unable to authenticate, and HR fielding 'how do I sign in' tickets weekly. Set up SSO at launch — it's a one-time configuration that eliminates ongoing identity management overhead.
Tier-mixing in a single SKU list
Putting the executive polo in the same SKU list as the staff polo and trusting employees to order the right one creates avoidable mistakes — staff order the executive piece (over budget, wrong fit signal), executives order the staff piece (under-presented to customers). Use role-based visibility for tier separation. Staff sees their tier only; managers see staff + manager; executives see all three.
Skipping the storefront preview review
Programs that launch without HR and brand walking through the preview together usually discover within a week that the embroidery placement is wrong on the manager polo, or the brand color displays differently on the live storefront than the brand guide expected. Always run the 30-minute preview review before promotion to the public URL — it catches 95% of post-launch issues.
Mixing uniform stores with retail merch stores
Uniform stores (HR-approved SKUs, company-paid or per-employee budget) and retail merch stores (employees buying branded gifts and personal-use apparel) have different operational requirements and should run as separate storefronts. Trying to combine them creates pricing confusion, visibility issues, and tax/invoicing complications. Run them as two independent stores under the same /stores parent if both are needed.
Ignoring the SKU lead time on launch volume
The first 2-4 weeks after launch is when volume peaks — every employee orders at once. If your SKU list includes blanks with extended manufacturer lead times (custom dye-lots, specific high-tier brand SKUs), the initial order surge will hit the lead-time ceiling and employees will wait 4-6 weeks for their first delivery. For launch we recommend SKUs with same-week blank availability; introduce custom-dye-lot or premium-tier SKUs as supplemental options 60 days post-launch once initial volume has cleared.
FAQ
Questions buyers actually ask.
How long does it take to stand up a company store from kickoff?
Standard timeline is 7-14 business days from the kickoff conversation. The SKU lock and asset collection is the gating step — once we have the locked SKU list, brand assets, and SSO domain confirmed, the storefront preview is ready in 3-5 business days. From preview approval to public launch is typically same-day.
Is there a setup fee for a company store?
No setup fee for standard storefronts. We absorb the configuration cost as part of the program — our revenue comes from the per-piece order pricing. For programs requiring extensive custom development (custom checkout flows, ERP integrations, specialized invoicing logic) there may be a one-time engineering fee discussed at scope review.
Can the company store integrate with our HR or procurement system?
We support SSO against most identity providers (Okta, Microsoft Entra, Google Workspace) for employee authentication. For payment and invoicing integrations with procurement systems (Coupa, Ariba, SAP) we configure per-program at scope. ERP-grade integration is available for enterprise programs with the appropriate scope discussion.
What happens to unused per-employee budgets at year-end?
Configurable per program. Most clients choose either (a) annual reset — unused budgets expire at end of period, or (b) rollover — unused budget carries into the next period up to a cap. We set this at launch and can adjust during the program lifecycle. Annual reset is the most common pattern; it keeps the budget logic simple and avoids long-tail liability accumulation.
Can employees order non-uniform branded merch through the company store?
Yes — many of our programs include a 'gifting' or 'merch' section alongside the uniform pieces. Employees can order branded gifts, personal-use apparel (sweatshirts, caps, totes), and welcome-kit pieces. We typically run uniform pieces as company-paid and merch as employee-paid with corporate-discount pricing, but the budget model is configurable per SKU category.
What's the minimum company size to justify a dedicated company store?
We've stood up stores for clients as small as 12 employees and as large as 800. The breakeven is closer to 'will employees order frequently enough that ad-hoc ordering creates friction' than 'is the company big enough.' If your team orders uniform replenishment more than 3-4 times a year per location, a company store will eliminate operational overhead. Below that volume, ad-hoc ordering through /quote works fine.
Next step
Ready to spec it out?
Tell us your headcount, SKU shortlist, and budget model. We'll come back with a storefront preview within 5 business days — no setup fee.
Keep reading
Related to this decision.
Company stores
OTIA's company store program — self-service uniform ordering, HR-approved SKUs, automated fulfillment.
Corporate apparel programs
How OTIA builds and runs corporate apparel programs at scale — uniform tiers, replenishment, company stores.
Best polos for company uniforms
Picking the polo SKUs to put in the company store — across staff, manager, and executive tiers.
Custom embroidery
In-house embroidery on Long Island — the decoration method most uniform stores standardize on.
Corporate uniforms collection
Curated polo and uniform pieces that pass the corporate-uniform bar — pre-filtered.