julieyue.dev
← All case studies

Case study 01

Replatforming tacticalgear.com to BigCommerce Catalyst

Client
Galls / tacticalgear.com
Role
Frontend web developer, Galls
Status
Live · progressive production rollout
Stack
BigCommerce Catalyst · Next.js · TypeScript · GraphQL · Tailwind CSS · Cloudflare

Context

tacticalgear.com is one of several brand storefronts run by a multi-brand public safety and tactical retailer. The existing platform is a legacy server-rendered system that the business has outgrown. [CONFIRM: how you want the legacy stack described publicly. "Legacy server-rendered platform" is safe; anything more specific should be cleared first.]

The replatform moves the storefront to headless BigCommerce with a Catalyst frontend. Catalyst is BigCommerce's Next.js reference storefront, so this is a full Next.js App Router build against BigCommerce's GraphQL storefront API, at a catalog scale of [METRIC: SKU count or order of magnitude, e.g. "tens of thousands of SKUs"].

My work

This is my primary project. I work across the Catalyst frontend day to day: page templates, data fetching against the GraphQL storefront API, and the integration seams where the new storefront has to match years of legacy behavior. [CONFIRM: tighten this to the areas you personally own, and add anything missing, e.g. PDP, category pages, checkout integration, search, ERP or fulfillment hooks.]

The rollout

The interesting engineering problem is not the rewrite. It is running two storefronts against the same catalog and the same customers, and moving traffic between them without breaking SEO, analytics, or checkout.

The new storefront is live at new.tacticalgear.com and serves a controlled slice of production traffic, routed at the edge, while the legacy platform serves the remainder. Rollout percentage increases as parity holds. A second brand storefront follows on the same Catalyst foundation. [SIGN-OFF: this paragraph names the rollout approach but deliberately omits the exact traffic percentage and the second brand's name and timeline. Confirm you are comfortable with this level of detail, and name workboots.com here only after it ships.]

Why this matters to you

If you are pitching or delivering a Catalyst migration, this is the exact work I do every day, at enterprise scale, in production. I know where Catalyst's defaults end and the real integration work begins.