Football gear e-commerce platform
Strikers Gear
Three-app stack for strikergear.pk—NestJS/MongoDB API, React/MUI admin, Next.js storefront; COD and bank transfer checkout (no card gateway in-repo).
Background & Context
Strikers Gear sells football cleats and accessories (grip socks, jerseys, shin pads) via [strikergear.pk](https://www.strikergear.pk). The monorepo is three applications: NestJS 11 backend/, Mantis Material React admin, and Next.js 14 landing/ storefront. Docs correct earlier “API-only” descriptions—admin and storefront are first-class.
Search demand around football gear e-commerce platform and Strikers Gear keeps rising as operators look for proof—not slide decks—before they hire a build partner.
Tekvers framed Strikers Gear as a football gear e-commerce platform engagement with clear module boundaries, measurable outcomes, and a stack centered on NestJS 11, MongoDB/Mongoose 9, Redis (optional), React 19/Vite/MUI, Next.js 14.
Delivery covered software development, with SEO-ready surfaces and internal linking so the public story reinforces the product work.
This case study page targets buyers researching football gear e-commerce platform architecture, vendor evaluation, and implementation risk—paired with related Tekvers blogs and guides on the same niche.
The Challenge
A small football-gear retailer needed staff catalog/stock/order ops and a public shop with guest checkout—without pretending a card payment gateway exists when checkout is Cash on Delivery and bank transfer only. Without a coherent football gear e-commerce platform foundation, Strikers Gear stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Strikers Gear: Three-app stack for strikergear.pk—NestJS/MongoDB API, React/MUI admin, Next.js storefront; COD and bank transfer checkout (no card gateway in-repo). Operable football-gear store across API, admin, and storefront. Tekvers delivered a maintainable football gear e-commerce platform system for Strikers Gear using NestJS 11, MongoDB/Mongoose 9, Redis (optional), React 19/Vite/MUI, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Three-app ownership
Only the backend talks to MongoDB; admin and landing share one product/order model through the API.
Pragmatic ops auth
Shared admin password for a small operations team; standard JWT customer accounts for registered shoppers.
Honest gaps
Wishlist and blog remain UI-only; flat-rate shipping; no payment gateway; a documented order-status mismatch that can block review creation—called out rather than glossed over.
What We Delivered
- NestJS 11 + Mongoose 9 REST API with Passport JWT and optional Redis
- React/MUI (Mantis) admin for products, stock, orders, categories, brands, sizes, banners
- Next.js 14 storefront with Framer Motion and device-aware mobile components
- Guest and customer checkout (COD / bank transfer)
- Product review model and promotional banners
Outcomes & Impact
- Operable football-gear store across API, admin, and storefront
- Per-size stock management for cleats and accessories
- Guest checkout path suited to local payment habits
- Documented product gaps for the next engineering phase
Strikers Gear runs catalog, stock, and orders from one Nest/Mongo core—athletes shop on Next.js; staff operate on MUI—without Tekvers inventing Stripe or wishlist backends the docs mark absent.
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.