Headless e-commerce
SheStrends
She’s Trends fashion commerce—NestJS/MongoDB API, Next.js storefront, and React admin with PKR and cash-on-delivery (not Stripe).
Background & Context
botique is the She’s Trends (shestrends.com) fashion commerce workspace: NestJS MongoDB API (ecommerce-nest, 18 modules), React admin (ecommerce-dashboard), and Next.js 14 storefront (ecommerce-landing). Defaults target PKR and cash on delivery (COD). No Stripe integration—older case-study Stack/Tagline claiming Stripe is incorrect per docs.
Storefront covers shop/search/products, cart drawer, COD checkout, auth, customer dashboard areas, WhatsApp float, cookie consent, recently viewed, personalization helpers, and ipapi geo. Admin covers catalog, fashion master data (colors, materials, occasions, seasons, sizes, patterns, etc.), inventory, orders, delivery charges, banners, analytics. Gaps: overlapping /api/auth controllers; landing GET /orders/customer/:id not on Nest OrderController; upload/ module unused; limited JWT guard coverage; shipping zones/tracking still mock-style alongside real delivery-charges.
The Challenge
A fashion brand needed a custom store and operator console with full catalog/order control—without Shopify platform constraints—using COD-friendly Pakistan checkout norms. Without a coherent headless e-commerce foundation, SheStrends stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
SheStrends: She’s Trends fashion commerce—NestJS/MongoDB API, Next.js storefront, and React admin with PKR and cash-on-delivery (not Stripe). Brand-owned fashion commerce path from merchandising to COD fulfillment. Tekvers delivered a maintainable headless e-commerce system for SheStrends using NestJS 10, Next.js 14, MongoDB, Mongoose, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Fashion-rich commerce core
Master-data families, size charts, inventory movements, banners, delivery charges alongside products/categories/brands/cart/orders/coupons/payments(COD)/shipping.
Dual surfaces
Customer landing for browse→COD checkout; admin for ops analytics (Recharts) and settings.
Deploy posture
Vercel-oriented Nest (`vercel.json` + `api/index.js`); CORS for shestrends.com and `*.vercel.app`; SMTP via Nodemailer.
What We Delivered
- NestJS modules: admin, auth, product, customer, brand, category, order, cart, coupon, payment, shipping, inventory, review, notification, health, analytics, master-data, banner
- Next.js storefront with COD checkout and customer areas
- React admin for catalog, master data, orders, customers, delivery charges, banners, analytics
- PKR currency defaults; COD helpers on payments/orders
- WhatsApp, cookie consent, recently viewed, personalization UX
- Documented gaps: Stripe absent, auth path overlap, customer-orders fetch mismatch, unused upload module
Outcomes & Impact
- Brand-owned fashion commerce path from merchandising to COD fulfillment
- Operator inventory and banner control without a hosted template lock-in
- Clear non-claims vs Stripe-centric portfolio drafts
SheStrends owns catalog and fulfillment workflows on a Tekvers headless stack that matches how the brand actually collects payment (COD)—not an invented card-processor story.
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.