FOR
IN FINAL LAUNCH PREP
IN FINAL LAUNCH PREP88 Badminton House
A retail operating system for a badminton specialty shop — live inventory, a unified stringing queue, and an owner's dashboard, built around exactly how the shop runs.
Retail · Inventory · Service Queue·Next.js 16 · Prisma 7 · Supabase Postgres · Revenue Monster · Resend·2026
The owner's view: live stock, pending orders, and low-stock alerts that fire before a shelf actually runs out. Demo data — 88BH is in final launch prep, not yet public.
THE STORY
88 Badminton House sells rackets, strings, shoes — and stringing, the service that's the actual reason regulars keep coming back. The system goes past a storefront: real-time inventory with a full stock ledger, a stringing queue that unifies walk-in and online jobs by priority and due date, server-side price recomputation so a customer can't tamper with a total by editing a request, and an admin dashboard built around the one thing an owner actually needs on login — what needs attention right now, not a wall of numbers.
THE SYSTEM, ON SCREEN
WHAT'S ACTUALLY UNDER IT
- 41 API routes — admin and public, including CSV product import/export and a scheduled job that expires abandoned pending orders
- Every stock change writes to a stock ledger, and every admin action writes an audit log — who did what, when
- The server recomputes every order total from the database at checkout — a customer can't change what they're charged by editing a request
- Compare-and-swap status transitions inside database transactions — a double-click or a retry can't apply the same change twice
- Revenue Monster payment integration is built and cryptographically verified (RSA-SHA256 signing, 9/9 signing tests passing) — dormant until sandbox credentials land, not yet processing real transactions
- CSP, HSTS, and X-Frame-Options set at the framework level
- Passed an 8-dimension adversarial multi-agent code audit — 7 criticals plus every residual independently re-verified
88 Badminton House is in final launch prep. The build is done and audited — what's left is on the client's side: payment gateway credentials and a domain. No live URL yet, and nothing above is live traffic or revenue.