Appzotic
Portfolio Chunmun Stores
Websites · E-commerceWebsite + admin + APILive

Chunmun

Fashion commerce for a multi-store retail brand

A fashion storefront and Store OS for Chunmun — catalog, checkout, discounts, and multi-store operations.

See every view Build something like this
This product holds
  • Men, women, boys, and girls merchandising
  • Store OS for catalog and discounts
  • Razorpay checkout and invoices
  • Shared inventory and locations
Chunmun Stores · Women’s campaign
Product
Chunmun Stores
Industry
Fashion retail
Platform
Website + admin + API
Status
Live
Year
2025–2026
What’s inside

The product, module by module.

Everything a client would actually use — not a feature dump, the operating pieces of the system.

01

Department merchandising

Men, women, boys, and girls collections with size guides and seasonal banners.

The brand can merchandize like the store, not like a generic grid.
02

Store OS

Products, collections, discounts, customers, and store staff in one console.

Merchandisers do not need engineering for a campaign.
03

Checkout and invoices

Account addresses, Razorpay, and branded invoices from the order backend.

Orders close in a way finance and logistics can operate.
Commerce strategyWeb engineeringProduct designCloud platform
How it looks

Every view we shipped.

Click any screen to open it full size. These are the live product surfaces — dashboards, flows, and themes.

The brief

Why it exists, and what it changed.

The problem

A multi-store apparel brand needed digital merchandising, checkout, and store ops without fragmenting inventory.

What we built

Ship a Next.js website, Vite admin (Store OS), and NestJS commerce API covering catalog, discounts, invoices, and logistics.

What changed

Men, women, boys, and girls collections sell online while stores keep inventory, POS, and promotions in one backend.

01

Family fashion catalog

Departments, size guides, collections, and seasonal merchandising all had to share one product model.

Impact · A generic Shopify theme would have flattened how Chunmun sells.
02

Store vs website

Tax, locations, staff, and POS needed to stay aligned with the public catalog.

Impact · Without a Store OS, online stock would diverge from the floor.
03

Checkout trust

Indian retail checkout needs addresses, invoices, and a payment path customers already use.

Impact · Razorpay, invoices, and account addresses were first-class, not plugins.
How it’s built

Delivery path, stack, and system shape.

Phase 01

Storefront

Next.js commerce site with department merchandising, PDP, cart, wishlist, and checkout.

Phase 02

Store OS

Admin for products, collections, discounts, banners, orders, analytics, and stores.

Phase 03

Commerce API

NestJS services for catalog, inventory, checkout, invoices, and storefront settings.

Next.js
React
NestJS
MongoDB
Razorpay
Experience
Chunmun website
Store OS admin
Edge & trust
Next.js
CDN assets
Application
Catalog
Checkout
Discounts
Invoices
Data
MongoDB
Cloudinary
Operations
Orders
Manifest
Store locations
Encrypted in transit and at rest End-to-end observability Independently scalable services
Impact

What a buyer should feel after launch.

4

department shops

1

commerce catalog

OS

for stores and web

One catalog

Merchandising and inventory stay on one product record.

Self-serve merch

Stores can launch looks without a release.

“The site looks like Chunmun because the operating system behind it was designed for our stores, not a generic theme.”
Retail operations
Chunmun Stores
More work

Other products in the studio.

Project FAQ

The details behind the delivery.

How long did the project take?

The core engagement ran for a multi-release commerce program. Discovery and architecture came first, followed by incremental releases and a structured transition into continuous improvement.

Why was this technology stack selected?

Next.js, React, NestJS, MongoDB and Razorpay provided the best balance of team fit, ecosystem maturity, security, delivery speed and long-term operating cost. Every major choice was documented through architecture decisions.

How were security and scalability handled?

Threat modeling, least-privilege access, automated security checks and observability were built into delivery. Load and failure testing validated the critical paths before launch.

What support followed launch?

Appzotic provided launch command, operational monitoring, knowledge transfer and a prioritized evolution roadmap. The client could choose continued product support or full internal ownership.

Start your project

Want a product that looks this considered?

Bring the workflow, the constraint, or the screenshot of what you wish existed. We’ll shape the system around it.

Schedule a discovery call Back to portfolio