Full-StackB2BPartnerPortal

The Challenge

A fashion jewelry brand with 900+ products and a growing network of B2B partners needed a way for wholesale buyers to browse products, place orders, and manage their accounts — without the overhead of a full B2B e-commerce platform.

The existing process was manual: PDF catalogs, email orders, spreadsheet tracking. It worked at small scale but was breaking as the partner network grew.

What We Built

One Weekend Build

This project was built in a single weekend. Not a prototype — a production system. Here's what shipped:

Three Connected Portals:

1. Public Catalog — Browse the full collection. Product images, descriptions, pricing tiers. No login required. This is the storefront that potential partners see before applying.

2. Partner Portal — Authenticated access for approved wholesale buyers. Full catalog with wholesale pricing, order placement, order history, and account management. Partners can build orders, save drafts, and submit when ready.

3. Admin Dashboard — Internal tool for the brand's team. Manage products, approve partner applications, process orders, and track inventory. Full CRUD operations on every data model.

Technical Architecture

• Next.js App Router — Server components for the catalog, client components for interactive features
• Railway — Hosting and PostgreSQL database
• Cloudflare R2 — Image storage for 900+ product photos (optimized with sharp)
• SKU auto-matching — Products from multiple data sources matched automatically by SKU patterns
• Role-based access — Public, Partner, and Admin roles with middleware-enforced boundaries

Product Data Pipeline

The 900+ products came from multiple sources: spreadsheets, existing website scrapes, and photography sessions. We built an automated pipeline:

• CSV import with validation and deduplication
• Image processing: resize, optimize, generate thumbnails
• SKU normalization across data sources
• Category and tag auto-assignment based on product attributes

Why One Weekend?

This isn't about speed for its own sake. It's about understanding what matters:

• No custom CSS framework — Tailwind + shadcn/ui. Battle-tested components, zero design bikeshedding.
• No over-engineering — PostgreSQL, not a distributed database. Server actions, not a separate API layer.
• No feature creep — Three portals, each with a clear purpose. Nothing more.
• Deep domain knowledge — We'd already worked with this client on analytics and strategy. We understood the business before writing a line of code.

Key Metrics

Tech Stack

• Next.js 14 (App Router)
• Railway (hosting + PostgreSQL)
• Cloudflare R2 (image storage)
• Tailwind CSS + shadcn/ui
• NextAuth.js (authentication)