Wholesaler · United States
US Custom Caps
A wholesale sales surface built for the conversation before production.
The current site is deliberately lean: product discovery, proof from real cap programs, direct access to Joseph, and quote intake. The heavier artwork, commerce, and order operations belong to the Custom Cap BD engine.
- Ecosystem role
- Wholesaler · demand channel
- Market
- United States
- Current surface
- Independent Next.js spoke
- Operating link
- Tenant-tagged shared intake
Keep the public site close to the buyer.
US Custom Caps does the focused work of a wholesale storefront. It earns the inquiry, captures the right context, and keeps operational complexity out of the first buying conversation.
What this spoke owns
- SEO product catalogue and cap-program education
- Wholesale quote and contact intake
- Patch, embroidery, and decoration guidance
- Direct buyer relationship with Joseph
What stays with the engine
- Artwork designer and production-ready specifications
- Priced commerce, cart, and checkout
- Customer, wholesaler, and admin workspaces
- Invoices, production status, and tracking
The current surface, not the old pitch.
These images come from the active project repository and the live public route. They are the visual source of truth for this record.
A lead enters once, with its source attached.
The spoke remains independent, while contact and quote submissions call the shared Convex backend owned by Custom Cap BD. Source identity is derived server-side and travels with the record.
- 01
Discover
Browse cap styles, program examples, decoration options, and wholesale guidance.
- 02
Qualify
Call Joseph or submit quantity, artwork, timing, and product context.
- 03
Stamp
The server records the USCC tenant and source domain with the submission.
- 04
Operate
The shared operating backend receives the inquiry without a second data entry.
Current state
Live now: the marketing site and tenant-tagged contact and quote intake.
Boundary / next state
Next rollout: move the spoke to Coolify, then route selected commerce and account surfaces to the hub on the USCC domain. That proxy is planned, not live.
Lean at the edge, connected underneath.
The implementation separates the fast public catalogue from the operating backend. The spoke consumes shared functions; it does not own or deploy the hub schema.
- Product role
- Wholesale acquisition
- Audience
- Teams · dealers · brands
- Owner
- Custom Cap BD ecosystem
- Status
- Live · evolving
- Public app
- Next.js 16 App Router with an SEO-first product and content surface.
- Catalogue
- Sanity-backed factory products and marketing product pages.
- Intake
- Server actions call shared Convex contact and cap-quote functions.
- Source safety
- Tenant slug and source domain are resolved on the server, not trusted from browser input.
- Current
- Live storefront, gallery, FAQ, contact, and wholesale quote flow.
- Connected
- USCC submissions enter the shared backend with USCC source identity.
- Planned
- Coolify migration followed by the same-domain hub handoff.
Build together
Need a wholesale surface that still connects to the real operation?
I design the public buying path and the backend handoff together, so the marketing site stays focused without creating another operational silo.