zsty.us

Before / After · Case Study

B Your Best — a shop-to-shop supplement line given its own store with the ban list built in

  • Smoke Shops

Four supplements and a counter-top display sold shop-to-shop with no website, no rep tracking, and a category where the marketing language that sells is exactly the language that gets you banned. The brand now has a full online store at byourbestallday.com — with a rep program that credits every scan and sale automatically, and a guard that makes it mechanically impossible to publish a forbidden phrase.

“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

At a glance

What this rebuild covers.

  • Security

    A banned-word guard is wired into the publishing pipeline itself — if a forbidden marketing term shows up in copy, product descriptions, or even behind-the-scenes labels, the update refuses to go live instead of relying on someone catching it in review.

  • Selling & payments

    A real multi-step checkout takes orders end to end, wholesale pricing stays gated behind approved shop accounts, and card charging is deliberately held in a marked test mode until the merchant account paperwork lands — it flips to live with no rebuild.

  • App builds

    Field reps carry personal QR codes and get their own portal — pull it up on a phone in a shop, and every scan and sale is credited to them with a running 20% commission tally, no month-end spreadsheet argument.

  • Design

    The original product renders had non-compliant claims printed right into the artwork, so the images were digitally retouched — the photography now passes the same standard as the text.

  • Email

    The brand got real email addresses on its own domain, running on mail infrastructure the owner controls instead of a shared-host inbox.

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
  • No website → full online store
  • 5 product lines with real storefront pages
  • Reps earn a tracked 20% commission
  • 0 banned marketing terms can reach the live site

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.

For the technically curiousHow it was done
  1. 01

    Where it started

    B HARD, B LEAN, B SMART, and B HAPPY sold shop-to-shop through smoke shops with a Tower counter display — no website at all, the domain parked at Hostinger with no mail identity, rep sales completely untracked, and product renders carrying non-compliant printed copy.

  2. 02

    The real constraint

    In this category the copy that converts is the copy that gets the product banned. The risk isn't the checkout — it's a stray phrase in a product description six months from now. So compliance had to be a hard mechanical constraint, not a tone preference: the banned-term list was encoded into the build pipeline, where any commit containing a forbidden term fails the build before it can deploy. The guard covers marketing copy, metadata, and alt text alike — the only enforcement that survives staff turnover.

  3. 03

    The rebuild

    One codebase on our hosting platform: storefront pages for all five product lines, a multi-step checkout persisting orders to a managed database, magic-link sign-in, a rep QR portal computing a 20% commission ledger per attributed sale, a wholesale tier gate keeping shop pricing separate from retail, and an admin console over orders and products. The product renders were digitally retouched to strip the banned claims baked into the artwork.

  4. 04

    The wiring

    The domain moved off Hostinger onto managed DNS with the site on our hosting platform and brand mail on the portfolio's self-hosted mail server — the same owned-infrastructure pattern as the rest of the catalog, no rented pieces left behind.

  5. 05

    What runs now

    byourbestallday.com is live in production with the full flow working end to end. QR scans and orders write attribution rows as they happen, the compliance guard runs on every commit, and the card-processing adapter is explicitly in stub mode until the merchant credentials land — when they do, the stub flips to live charges with no structural change, the same adapter pattern already proven live on a sister storefront.

Architecture

Old stack
  • No site
  • Cash-and-carry wholesale
  • Untracked reps
  • Non-compliant renders
↓
New stack
  • modern web framework
  • managed Postgres
  • Rep QR portal + commission ledger
  • Wholesale tier gate
  • CI banned-term guard
  • Clover adapter (stub → live)

What changed, with evidence

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 shop-to-shop supplement line given its own store with the ban list built in — zsty.us