Categories restructured around the actual sales channel
Flower / rosin / extracts / trim / smalls / pharma (pending supply line). Each is its own surface, not a single 'Products' page.
Before / After · Case Study
Buck Mountain Cannabis — buckmountaincannabis.com → buckmountain.farm
- Hemp / CBD
Brand restart on a new domain. The legacy site was a static brochure; the rebuild restructures the catalog around the actual sales channel — flower, rosin, extracts, trim, smalls, plus a pharma category that ships when its supply line is ready. Wires Nabis (wholesale), Metrc (batch compliance), and OgLife.app (QR rewards) into one storefront.
🔒jackiej.events
The pixel diff
Overview, then the walkthrough.
Left: everything the legacy site shipped — frozen in place. Right: an auto-scrolling tour of the rebuild, from hero to booking. No slider to fight with.
🔒djjackiej.com
This is everything the legacy site had to offer above the fold. No pricing, no calendar, no booking — the funnel ended at a mailto.
🔒jackiej.events
Auto-scrolls through the modern site so you can see the booking surface, the package grid, the pricing table, and the calendar inline — without leaving this page.
The four beats
Problem · Insight · Build · Outcome.
Scroll past the legacy frame. The four beats land in order. At the end, the modern site fades into the same window.
- 01 · Problem
A brand with no infrastructure under the catalog.
The legacy site was a brochure. No wholesale integration, no batch-level compliance surface, no shared identity layer across the brand portfolio.
- 02 · Insight
Don't run the same store as BMH — restart the catalog around real channels.
Flower, rosin, extracts, trim, smalls, and pharma (when ready) are real sales channels with different unit economics. The catalog reflects that.
- 03 · Build
buckmountain.farm on the same headless stack — different shape.
Next.js 15 storefront, Medusa 2.x backend, Nabis wholesale ingestion, Metrc compliance, OgLife identity. Shared infrastructure where it makes sense (chat widget, payment rails); brand-specific structure where it matters (category tree, copy, photography).
- 04 · Outcome
A brand restart that's part of a portfolio, not a one-off.
Same stack as BMH and LGP means a new SKU added to Buck Mountain inherits the messaging infrastructure, the payment policy, the chat widget, and the QR rewards layer for free.
🔒djjackiej.com
01 · Problem
A brand with no infrastructure under the catalog.
The legacy site was a brochure. No wholesale integration, no batch-level compliance surface, no shared identity layer across the brand portfolio.
02 · Insight
Don't run the same store as BMH — restart the catalog around real channels.
Flower, rosin, extracts, trim, smalls, and pharma (when ready) are real sales channels with different unit economics. The catalog reflects that.
03 · Build
buckmountain.farm on the same headless stack — different shape.
Next.js 15 storefront, Medusa 2.x backend, Nabis wholesale ingestion, Metrc compliance, OgLife identity. Shared infrastructure where it makes sense (chat widget, payment rails); brand-specific structure where it matters (category tree, copy, photography).
04 · Outcome
A brand restart that's part of a portfolio, not a one-off.
Same stack as BMH and LGP means a new SKU added to Buck Mountain inherits the messaging infrastructure, the payment policy, the chat widget, and the QR rewards layer for free.
🔒jackiej.events
What changed
Grouped by what kind of system shipped.
Each claim ships with concrete evidence — env vars, table names, cadence chips. No marketing fluff.
Nabis + Metrc + OgLife wired into one storefront
Wholesale catalog comes from Nabis; batch-level compliance tracking is Metrc-backed; QR scans on packaging route through OgLife to a unified rewards layer that spans BMH and LGP.