Fashion ecommerce suite (store + API + admin)
Boutique Commerce Suite
She's Trends fashion commerce—NestJS/MongoDB API, React admin, and Next.js storefront with PKR cash-on-delivery operations.
Background & Context
Botique is the She's Trends fashion commerce workspace: three packages—ecommerce-nest (NestJS REST under /api), ecommerce-dashboard (React CRA admin), and ecommerce-landing (Next.js 14 App Router storefront). Branding and defaults target shestrends.com, PKR currency, and cash-on-delivery. CORS allowlists shestrends.com and Vercel suffixes; Nest ships with a Vercel-oriented api/index.js entry.
Boutique fashion retail needs more than a generic product grid. Operators manage colors, fabrics/materials, occasions, seasons, sizes, patterns, size charts, banners, delivery charges, and inventory movements. Shoppers need cart, wishlist, addresses, and COD checkout. Spreadsheets and rigid hosted themes could not cover that merchandising depth for She's Trends.
Docs are explicit about honesty gaps: no Stripe; overlapping /api/auth controllers for admin vs customer; limited JWT guard coverage; upload/ module folder present but not imported into AppModule; landing GET /orders/customer/:id called from the storefront client but not present on Botique’s Nest OrderController.
The Challenge
A fashion retailer needed a coherent owned stack—customer storefront, commerce API, and operations dashboard—with fashion master data, inventory, banners, delivery charges, and COD order flows in PKR. Without a coherent fashion ecommerce suite (store + api + admin) foundation, Boutique Commerce Suite stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Boutique Commerce Suite: She's Trends fashion commerce—NestJS/MongoDB API, React admin, and Next.js storefront with PKR cash-on-delivery operations. Unified She's Trends retail stack owned by the brand—not a locked theme. Tekvers delivered a maintainable fashion ecommerce suite (store + api + admin) system for Boutique Commerce Suite using NestJS 10, MongoDB, Mongoose, Next.js 14, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
API as the shared commerce core
Eighteen Nest modules cover admin/auth, product (+ size charts), customer, brand, category, order, cart, coupon, payment (COD helpers), shipping/delivery-charges, inventory, review, notification (SMTP), health, analytics, master-data, and banner—Swagger at `/api/docs` when enabled.
Fashion ops in the admin
Dashboard routes manage products, categories, brands, inventory, fashion master-data families, orders, customers, delivery charges, banners, analytics, and settings behind client-stored JWT—lazy-loaded for code splitting.
Storefront UX for boutique retail
Landing supports shop/search/PDP, categories/brands, auth, customer dashboard areas, blog/help, recently viewed (localStorage), ipapi geo hooks, cookie consent, and WhatsApp contact—checkout posts COD orders in PKR without a card gateway.
What We Delivered
- NestJS `/api` commerce backend on MongoDB/Mongoose with JWT/Passport auth
- Eighteen feature modules including fashion master-data, size charts, inventory movements, banners, analytics, and COD payment helpers
- React TypeScript admin dashboard (Tailwind, Axios, Recharts) for catalog and order ops
- Next.js 14 storefront with cart drawer, wishlist/profile areas, and COD checkout
- Delivery-charges and shipping method surfaces for Pakistan operations
- Nodemailer SMTP notification configuration
- Vercel-oriented Nest deployment shape (`vercel.json` + serverless handler)
- Swagger documentation endpoint at `/api/docs` (when enabled)
Outcomes & Impact
- Unified She's Trends retail stack owned by the brand—not a locked theme
- Staff-managed fashion attributes, inventory, banners, and COD order states
- Storefront UX patterns (cart, geo, WhatsApp) tuned for boutique conversion
- Clear roadmap for hardening JWT/RBAC and aligning landing order-fetch routes
She's Trends runs browse-to-COD and back-office merchandising on one API contract. Tekvers delivered the fashion retail superset—store, server, and dashboard—while documenting COD focus and known auth/route gaps instead of inventing Stripe or deep RBAC that the repo does not enforce.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.