zsty.us

Before / After · Case Study

B Your Best — a smoke-shop supplement line given a compliance-guarded storefront

  • Smoke Shops

B Your Best sells a four-SKU supplement line (B HARD / B LEAN / B SMART / B HAPPY, plus a counter-top Tower display) through smoke shops — a channel where the marketing language that sells the product is exactly the language that gets it banned. The build is a full e-commerce platform live at byourbestallday.com: storefront, multi-step checkout, a rep QR portal with a 20% commission ledger, a wholesale tier gate, and an admin console — with a CI compliance guard that fails the build if a banned drug-name marketing term ever lands in code or copy. Payments run through a Clover adapter currently in stub mode pending the merchant creds; everything else is production.

“In this category the copy that converts is the copy that gets you banned — so the ban list is enforced by CI, not by memory.”
byourbestallday.com↗Repo → og-gitclaw/byourbest↗
🔒byourbestallday.com
jackiej.events — modern site

Receipts — measured

Numbers that moved.

0
Product lines with real storefront pages
was 0
0%
Rep commission on attributed sales
was 0%
1
Banned marketing terms that can reach production
was 1
  • 4 supplement SKUs + Tower display, live at byourbestallday.com
  • Rep QR portal: per-rep attribution + 20% commission ledger
  • CI compliance guard — banned drug terms fail the build, not the review
  • Full domain wiring: Hostinger → Cloudflare → Vercel + Stalwart mail

The story

Problem · Insight · Build · Outcome.

  1. 01 · Problem

    A real product line with no storefront and a legal minefield for copy.

    B HARD, B LEAN, B SMART, and B HAPPY sold shop-to-shop with a Tower counter display — no website, no rep tracking, and a category where the obvious marketing language is banned. Any site build had to treat compliance as a hard constraint, not a tone preference.

  2. 02 · Insight

    Enforce the ban list mechanically and the rest of the build is normal e-commerce.

    The category risk isn't the checkout — it's a stray phrase in a product description six months from now. Encoding the banned-term list into CI turns a compliance program into a failing build, which is the only enforcement that survives staff turnover.

  3. 03 · Build

    Storefront + checkout + rep portal + wholesale gate + admin, one stack.

    Next.js 15.5 + Tailwind v4 + Drizzle/Neon. Multi-step checkout persisting to Neon with the Clover adapter stubbed; magic-link auth; rep QR portal with the 20% commission ledger; wholesale tier gate for shop accounts; admin console over orders and products. Product renders retouched to strip non-compliant printed copy.

  4. 04 · Outcome

    Live in production; one credential away from charging cards.

    byourbestallday.com is live with the full flow working end-to-end. When the Clover merchant creds land, the stub flips to live charges with no structural change — the same adapter pattern proven on cbd.restaurant.

Architecture

One chain replaced by another. Receipts above.

Old stack
  • No site
  • Cash-and-carry wholesale
  • Untracked reps
  • Non-compliant renders
↓
New stack
  • Next.js 15.5 storefront
  • Drizzle + Neon
  • Rep QR portal + commission ledger
  • Wholesale tier gate
  • CI banned-term guard
  • Clover adapter (stub → live)

What changed

Grouped by what kind of system shipped.

Each claim ships with concrete evidence — env vars, table names, cadence chips. No marketing fluff.

Retention

Compliance as a build gate, not a review step

A CI guard scans code and copy for the banned drug-name marketing terms this category can't legally use — a violation fails the build before it can deploy. The product renders themselves were digitally retouched to strip banned copy baked into the artwork, so the imagery passes the same standard as the text.

Before
Compliance depended on whoever wrote the copy remembering the rules.
After
A banned term can't ship — the pipeline rejects it mechanically.
  • CI job greps every commit for the banned-term list; red build on hit
  • Product renders retouched to remove non-compliant printed claims
  • The guard applies to marketing copy, metadata, and alt text alike
Agent backbone

Rep QR portal with a real commission ledger

Field reps carry QR codes that attribute every scan and sale to them. The portal shows each rep their attributed orders and a running 20% commission ledger — the incentive structure that makes a smoke-shop distribution network actually push the product, without spreadsheet reconciliation at month end.

Before
Rep sales were untracked; commissions were a manual argument.
After
Attribution and payout math accrue automatically per order.
  • Per-rep QR attribution on scan and order
  • 20% commission computed into a ledger per attributed sale
  • Wholesale tier gate keeps shop pricing separate from retail
Design

Full custom-domain + mail wiring, no SaaS shortcuts

The domain moved Hostinger → Cloudflare with the site on Vercel and brand mail on the portfolio's self-hosted Stalwart server — the same owned-infrastructure pattern as the rest of the catalog. byourbest.vercel.app and byourbest.oglife.app remain as alternate hosts.

Before
Domain parked at a shared host with no mail identity.
After
byourbestallday.com live on Vercel, brand mail self-hosted.
Retention

Honest payments state — stub until the creds are real

Checkout runs end-to-end against a Clover adapter that is explicitly in stub mode until the merchant account lands. The flow, order persistence, and admin views are production; the charge is the one deliberately-marked mock. No fake 'payments live' claim anywhere on the surface.

Before
N/A — no checkout existed.
After
Real multi-step checkout, one clearly-flagged stub awaiting a credential.

While the owner sleeps.

Autonomous surfaces

The agent backbone keeps the brand earning after hours. The owner approves; the system runs.

  • Attributes every scan and sale to the right rep

    on each scan / order

    QR scans and orders write attribution rows as they happen; the 20% commission ledger accrues without anyone reconciling a spreadsheet.

  • Blocks non-compliant copy at the door

    every commit

    The CI banned-term guard runs on every commit — a violating phrase in code, copy, or metadata fails the build before it can reach the storefront.

← All rebuilds

B Your Best — a smoke-shop supplement line given a compliance-guarded storefront — zsty.us