onecabinetsource
A storefront that prices their real product the way they actually sell it, instead of forcing it into a platform's assumptions.
Visit onecabinetsource.com ↗client
OneCabinetSource
role
Solo build, from scratch
launched
July 2026
status
Live
// the problem
Cabinets do not fit a flat product catalog. Price depends on door style, brand, RTA versus assembled, and exact dimensions, and freight is a real cost that changes with weight and distance. A generic e-commerce platform forces that into flat SKUs and flat shipping, which means either wrong prices or someone correcting every order by hand. There was no off-the-shelf store that modeled how this business actually sells, so it was built from the ground up.
// what I built
A custom storefront with a catalog of 11,981 SKUs and products priced across door style, brand, RTA versus assembled, and dimensions, plus a product configurator, a quote-request portal for larger orders, and a staff admin for order management. Checkout is server-authoritative: subtotal, shipping, and tax are recomputed on the server from the database on every request, so a price can never be set by the browser. Shipping runs through a custom engine (a weight-by-mileage freight formula for cabinets and a flat-rate small-parcel path for samples and accessories). Stripe handles payments (PaymentIntents, Stripe Tax, webhooks), Resend handles transactional email, and the whole thing sits on Prisma and Neon Postgres behind a 190-plus test Playwright suite in CI.
// technical highlights
- ▹Server-authoritative checkout: subtotal, shipping, and tax are recomputed server-side from the database on every request. The client never sets a price.
- ▹Custom shipping engine: a weight-by-mileage freight formula for cabinets, plus a flat-rate small-parcel path for samples and accessories.
- ▹Stripe Tax with Florida state nexus, and a graceful $0 fallback that logs failures for admins instead of blocking checkout.
- ▹Maintenance-gated test mode: runs the live store against the Stripe sandbox for safe on-prod testing, with test orders segregated from real data.
- ▹Consent and legal compliance: Termly CMP with Google Consent Mode v2 and versioned policy acceptance.
- ▹Full transactional email suite (order confirmation, status, refund, cancellation, verification, invites) with an audit log.
- ▹Admin: order pipeline with distributor assignment, inline product editing, a blog CMS, and role-based permissions.
- ▹190-plus end-to-end regression tests (Playwright with Docker Postgres) running in CI.
// the impact
Built to fit how they actually sell, not how a platform assumes they sell. It just launched, so these are the capabilities it shipped with, not measured results.
Have a similar problem?
Let's talk about what to build.