Overview
Hamuzair is a made-to-order custom apparel brand in India. The differentiator is that customers need no design skill: they describe a graphic in plain English, an AI model renders the artwork, and they position it live on a 3D garment before ordering. We built the whole platform as a single Next.js 16 monorepo covering three surfaces — a customer storefront with a React Three Fiber configurator, an operator admin dashboard, and a super-admin control plane with product CRUD, refunds, and live AI quota settings. Because every garment is produced only after an order is placed, the business carries no inventory risk.
Challenges
Design Skill as a Barrier
Custom apparel usually requires the customer to arrive with artwork. Most do not have any, and generic template pickers produce forgettable results.
Visualising Before Buying
A flat mockup does not tell a customer how a print will actually sit on a garment, which drives hesitation and returns.
AI Cost Abuse
An open image-generation endpoint is an invitation to run up an OpenAI bill. It needed quota control that survives anonymous traffic and race conditions.
Two Very Different Audiences
Customers and operators need entirely separate capabilities, and a compromise of one account type must never grant access to the other.
Key Features
Plain-English AI Artwork
Customers describe a design in words and the platform renders it with OpenAI's image models — no design tools, no uploads required.
Interactive 3D Configurator
A React Three Fiber viewport where garment, colour, and size are chosen and AI decals are dragged, rotated, and scaled across front and back panels in real time.
Dual Isolated Auth
Customers authenticate through BetterAuth with email or Google; operators use a completely separate JWT system. Breaching one cannot impersonate the other.
Abuse-Resistant AI Quotas
Per-user daily limits and a one-shot anonymous allowance, enforced with atomic database updates plus a burst guard, and adjustable live from the admin panel with no redeploy.
Hardened Payments
Two-step Razorpay flow with HMAC signature verification, idempotency enforced by a unique database index, and retry plus circuit-breaker wrappers on every gateway call.
Immutable Order Audit Trail
Every order state change writes an event recording who acted, the previous state, and the new one — giving operators a complete, tamper-evident history.
Technology Stack
Framework
3D
Styling
Database
Auth
Payments
AI & Storage
State & Infra
Results & Impact
3
Portals Shipped
Customer storefront, operator admin, and super-admin control plane
2
Auth Surfaces
Fully isolated — a breach of one cannot reach the other
Zero
Inventory Risk
Made-to-order: nothing is produced until payment clears
Prevented
Duplicate Charges
Idempotency enforced at the database index level, not in application code
Future Scope & Scalability
Automated end-to-end test suite with Playwright
Sentry error monitoring activation (already scaffolded in the logger)
International shipping and multi-currency checkout
Push notifications for order status updates
Real-time order tracking over WebSockets or Server-Sent Events
Sleeve decal panels and an admin mobile app
Conclusion
Hamuzair turns a design problem into a conversation: describe what you want, see it on the garment, buy it. Underneath that simplicity is a platform built for operational reality — isolated auth surfaces, quota controls that hold up against anonymous abuse, payment idempotency enforced by the database rather than hopeful application logic, and an immutable audit trail behind every order. The made-to-order model means the brand carries no inventory risk while still offering an effectively unlimited catalogue.