Case Study
Live & in productionForce Supplier
A B2B wholesale affiliate platform, not a storefront. Force Supplier (FDW) runs an affiliate network with encrypted onboarding, its own admin panel, and a text-editable CMS across every page, built on a JWT auth system instead of a drop-in auth provider.
The Problem
A wholesale network that needed real onboarding, not a contact form.
Force Supplier (operating as FDW, a dual-entity FD&W / Force Retailer business) runs a B2B affiliate and wholesale network. That means onboarding partners with sensitive identity data (including SSNs for tax/compliance purposes), managing an affiliate hierarchy, and giving non-technical staff the ability to edit site copy without ever touching code.
A standard ecommerce auth library wasn't the right fit for the affiliate/invite model this business actually runs, so the auth layer was built directly rather than bolted on.
What Was Built
A custom auth layer and a full content-editable CMS.
- JWT auth via jose: a hand-built authentication layer instead of NextAuth, fitted to the affiliate/invite onboarding flow rather than a standard consumer login.
- Encrypted onboarding: a
/invite/[token]flow that collects and encrypts sensitive onboarding data (including SSNs) at rest, not just in transit. - Admin panel: affiliate management, invite generation, and product administration, backed by Prisma over Postgres.
- Text-only CMS: a
SiteContentPrisma model exposing roughly 30 editable text fields across the homepage, product pages, and the request-access flow, so copy changes don't require a deploy. - QuickBooks integration: bookkeeping-sync built out for the business's accounting workflow (payments integration was separately and permanently denied by Intuit for this business category, a known constraint handled outside the codebase).
Outcome
A live wholesale network with real affiliate operations.
forcesupplier.com runs its affiliate portal, admin panel, and encrypted onboarding in production today. Non-technical staff can update site copy directly through the CMS, and the custom JWT auth layer handles the invite-based onboarding model the business actually needed instead of forcing it into a generic signup flow.