Portfolio / case studyActive owned platform

Custom Cap BD

A factory commerce system, not just a storefront.

I built one connected product for cap selection, artwork preparation, order administration, invoicing, and production tracking. That engine also supports a wider wholesale, supplier, and marketing ecosystem. The current interface record below replaces the older gallery as the source of truth.

Current Custom Cap BD storefront hero
Current storefrontProduction evidence
Role
Founder · product · engineering
Status
Active build
Build span
2023 — ongoing
Users
Buyer · wholesale · supplier · admin
Current buildFour supplied walkthroughs · manual playback

The current product, moving.

These captures are the present build record: the public storefront, artwork workspace, operating ledger, invoice flow, and customer tracking surface. Playback is manual and every clip has a still fallback.

01 · Storefront and catalogueThe current public entry point, product range, and brand system.
Read transcript

CustomCapBD.com is a full-stack e-commerce platform I built solo for my own custom-cap factory in Bangladesh. It is an end-to-end build with no Shopify and no template. A built-in theme system puts dark and light variants on the same page, with Tailwind tokens driving every color.

Sanity owns the catalogue content, while Next.js revalidates the live site without a code redeploy. Next.js 16 and the App Router handle the front end; Convex holds real-time configuration state; Supabase Postgres stores orders with row-level security; and Clerk handles customer, admin, and factory identities.

The quote surface uses React Hook Form and Zod. Quantity checks live pricing bands in Supabase, while artwork uploads use Supabase Storage with row-level access for the customer and admin.

02 · Artwork studioA structured cap specification moves from visual choices into a production sheet.
Read transcript

A color or fabric change rerenders the cap in the browser without a reload. A customer can drop in a PNG logo; the app vectorizes it, extracts the brand colors, and lets the customer place it on the cap.

Every color, fabric, and logo choice fills a real production specification sheet for the factory. Quantity changes recalculate pricing against Supabase tiers, and submitting sends the design, artwork, and notes directly into the admin queue.

The operating stack is Next.js, Convex, Supabase, Clerk, and Sanity, with live order status, classification, artwork, and totals.

03 · Order and invoicing operationsOrders, line items, payment state, and PDF output live in the operating workspace.
Read transcript

From the accounting page, I create an invoice directly from an existing order. The order automatically supplies the line items.

An operator can edit the lines, apply a discount, add a cost, and attach an existing client account. The resulting invoice is tied to the wholesaler account.

The walkthrough generates the invoice and downloads the finished PDF from the same operating surface.

04 · Customer order trackingThe buyer sees production milestones and the same status record used by operations.
Read transcript

The customer opens the order-tracking page, finds the order in the list, and selects it to reveal the full status record.

Because the example order was only recently placed, it remains at the first production step. The page also gathers the production files the factory needs, including the artwork and logo, into the same customer-visible record.

System flowChoose · approve · operate · track

One order moves through the whole factory.

The useful part is not any isolated screen. It is continuity: buyer choices become artwork, the approved artwork stays on the order, and the operating record becomes the customer’s tracking view.

  1. 01

    Choose

    Buyer

    Cap, colour, fabric, size, quantity, decoration, and delivery intent.

  2. 02

    Compose

    Artwork

    Logos and decoration are positioned against an exact cap specification.

  3. 03

    Price

    System

    Quantity tiers, decoration, options, and freight build one visible total.

  4. 04

    Approve

    Buyer + ops

    The artwork record is reviewed before the order moves toward production.

  5. 05

    Operate

    Admin

    Orders, revisions, invoices, payment state, and files stay attached.

  6. 06

    Produce

    Factory

    The production team works from the same approved specification.

  7. 07

    Track

    Customer

    Milestones and order media surface back to the buyer.

Commerce surface

Products, volume pricing, customization choices, quotes, and order submission.

Production surface

Artwork sheets, approvals, assets, revisions, and factory-ready handoff.

Operations surface

Role-aware orders, invoices, status changes, accounting, and customer updates.

Partner ecosystemWholesaler · supplier · marketing

One engine. Four operating surfaces.

Custom Cap BD is the operational center of a wider cap ecosystem. Each partner has a different market role and public surface, while the shared engine keeps product, artwork, order, and production work connected.

Shared operating engine

Custom Cap BD

The core product model joins the catalogue, customization record, order administration, generated documents, and production status used across the connected operation.

Engine responsibility
Product catalogue
Engine responsibility
Artwork records
Engine responsibility
Order operations
Engine responsibility
Invoices + tracking
Open customcapbd.com
  1. 01DemandWholesaleruscustomcaps.comThe wholesale-facing operation brings US buyers, volume pricing, quotes, and order intake into the shared commerce and production model.
  2. 02SupplySuppliernrcapsbd.comThe supplier-facing operation connects manufacturing capability and production responsibility to the same product and order language.
  3. 03GrowthMarketingopmrewards.comThe marketing operation creates campaigns and customer acquisition around the ecosystem while the commerce engine carries fulfillment forward.

The sites do not perform the same job. Wholesale demand, supplier capacity, and marketing activity enter through different doors; Custom Cap BD provides the operating model that lets the wider ecosystem move as one business.

Screen recordSix current high-resolution captures

Current screen record.

Each image opens at full resolution. Together they show the present visual system across artwork, orders, configurable products, production status, the storefront, and inquiry routing.

Build ledgerProduct · data · identity · production

The build is the connection between surfaces.

I own the product decisions and implementation across the buyer experience, factory workflow, data model, generated documents, deployment, and the operating tools around them.

Build record
Product
Custom-cap commerce + factory operations
Ownership
Product, design, engineering, and deployment
Primary state
One order record across customer and operations views
Output
Artwork, order, invoice, and tracking records
Application
Next.js 16 · React 19 · TypeScript
Data
Supabase Postgres · Convex reactive state
Identity + content
Clerk · Sanity
Production media
SVG artwork · PDF documents · file storage
Interface
Tailwind CSS · Radix UI · role-aware workspaces

The stack changed as the product matured. The durable decision is the model: one order and its approved production record should not be re-keyed between storefront, factory, invoice, and tracking tools.

ArchiveSix older YouTube walkthroughs · superseded UI

Earlier builds, kept on the record.

These YouTube walkthroughs document older Custom Cap BD interfaces. They remain useful as development history, but their screens are superseded by the current captures above and should not be read as the present product state.

Archive boundary: historical functionality and interaction ideas are preserved; visual details, navigation, and workflow states may no longer match the live platform.

  1. Archived Custom Cap BD walkthrough: AI Quote System
    01 · AI Quote SystemArchived YouTube walkthroughOld UI
  2. Archived Custom Cap BD walkthrough: 3D Artwork Designing
    02 · 3D Artwork DesigningArchived YouTube walkthroughOld UI
  3. Archived Custom Cap BD walkthrough: Shipping Tracking System
    03 · Shipping Tracking SystemArchived YouTube walkthroughOld UI
  4. Archived Custom Cap BD walkthrough: Order Tracking System
    04 · Order Tracking SystemArchived YouTube walkthroughOld UI
  5. Archived Custom Cap BD walkthrough: Product Artwork Creation Suite
    05 · Product Artwork Creation SuiteArchived YouTube walkthroughOld UI
  6. Archived Custom Cap BD walkthrough: Ecommerce/Product Page
    06 · Ecommerce/Product PageArchived YouTube walkthroughOld UI
Build togetherOne workflow · one direct conversation

Need the storefront and the operation to behave like one product?

Send me the workflow you are trying to replace, the people who touch it, and the point where information currently breaks. I will tell you what should be one system and what should stay separate.

Open Custom Cap BD