Commerce
Commerce
E-commerce platforms, supply chain, retail technology — the systems powering India's $200B+ digital commerce ecosystem and the world's fastest-growing retail market.
$70B+
India E-commerce 2024
500M+
Online Shoppers by 2030
10 Min
Quick Commerce Delivery
$350B
India E-comm Projection
Understanding Commerce— A Developer's Domain Guide
Commerce technology covers the complete stack of systems that power buying, selling, and moving goods — from e-commerce storefronts and order management to supply chain, warehouse management, and logistics. India is the world's fastest-growing e-commerce market, with Flipkart, Amazon India, Meesho, and JioMart running some of the most sophisticated commerce technology stacks in the world. Every major sale event (Big Billion Days, Great Indian Festival) stress-tests systems at a scale few other countries experience.
Why Commerce Domain Knowledge Matters for Engineers
- 1India's e-commerce market is projected to reach $350B by 2030 — massive growth
- 2Flipkart and Amazon India are among the largest engineering employers in India
- 3Commerce systems are deeply complex: inventory, pricing, search, payments, logistics all integrated
- 4Quick commerce (Blinkit, Swiggy Instamart, Zepto) is a uniquely Indian innovation
- 5Supply chain and logistics technology is a multi-billion dollar investment area
- 6Product management and system design interviews at Amazon, Flipkart focus heavily on commerce concepts
How Commerce Organisations Actually Operate
Systems & Architecture — An Overview
Enterprise Commerce platforms are composed of a set of core systems, data platforms, and external integrations. For a detailed, interactive breakdown of the core systems and the step-by-step business flows, see the Core Systems and Business Flows sections below.
The remainder of this section presents a high-level architecture diagram to visualise how channels, API gateway, backend services, data layers and external partners fit together. Use the detailed sections below for concrete system names, API examples, and the full end-to-end walkthroughs.
Technology Architecture — How Commerce Platforms Are Built
Modern Commerceplatforms follow a layered microservices architecture. The diagram below shows how a typical enterprise system in this domain is structured — from the client layer through the API gateway, backend services, data stores, and external integrations. This is the kind of architecture you'll encounter on real projects, whether you're building greenfield systems or modernising legacy platforms.
End-to-End Workflows
Detailed, step-by-step business flow walkthroughs are available in the Business Flows section below. Use those interactive flow breakouts for exact API calls, system responsibilities, and failure handling patterns.
Industry Players & Real Applications
🇮🇳 Indian Companies
Flipkart
E-commerce Marketplace
India's largest e-commerce platform — Walmart-owned, HQ Bengaluru
Amazon India
E-commerce Marketplace
India operations of global Amazon — Prime, Seller Central
Meesho
Social Commerce
Social commerce for Bharat — 150M+ customers, mostly Tier 2/3
Blinkit (Zomato)
Quick Commerce
10-minute grocery delivery — dark store model
Zepto
Quick Commerce
10-minute delivery — fastest-growing quick commerce startup
JioMart
Omnichannel
Reliance's O2O commerce — offline kirana + online integration
Nykaa
Vertical E-commerce
Beauty and fashion e-commerce — India's first unicorn with women founder
Delhivery
Logistics
India's largest logistics company — tech-first approach
🌍 Global Companies
Amazon
E-commerce & Cloud
World's largest e-commerce platform — AWS, Alexa, Prime
Alibaba
E-commerce Marketplace
China's e-commerce giant — Taobao, Tmall, AliExpress
Shopify
Commerce Platform
Commerce platform for 2M+ merchants — DTC enabler
Walmart
Retail
Largest retailer — omnichannel, acquired Flipkart for $16B
Stripe
Payment Infrastructure
Payment infrastructure powering millions of commerce businesses
🛠️ Enterprise Platform Vendors
Shopify
SaaS Commerce
End-to-end commerce platform — storefront to fulfillment
SAP Commerce Cloud
Enterprise Commerce
Enterprise commerce and order management
Magento (Adobe Commerce)
E-commerce Platform
Open-source e-commerce platform
Manhattan Associates
WMS/SCM
WMS and supply chain — used by Flipkart, large retailers
Core Systems
These are the foundational systems that power Commerce operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.
Business Flows
Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.
The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.
Technology Stack
Real Industry Technology Stack — What Commerce Teams Actually Use. Every technology choice in Commerceis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.
The pattern across Commerce is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern Commerceplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.
⚙️ backend
Java / Spring Boot
Core commerce services — OMS, catalog, pricing at Flipkart, Amazon
Go
High-throughput microservices — inventory, search ranking
Python
ML for recommendations, demand forecasting, fraud detection
Node.js
API gateway, real-time features, BFF layer
🖥️ frontend
React / Next.js
Storefront, seller portal, admin dashboards
React Native / Flutter
Mobile shopping apps
🗄️ database
MySQL / PostgreSQL
Transactional data — orders, customers, inventory
MongoDB
Product catalog — flexible schema for diverse categories
Elasticsearch
Product search — the most critical feature of any e-comm
Redis
Cart, sessions, inventory counts, flash sale locks
Apache Kafka
Order events, inventory updates, real-time analytics
☁️ cloud
AWS
Amazon India naturally; Flipkart uses private cloud + AWS
Google Cloud
Meesho, Nykaa — GCP ecosystem
Azure
Enterprise retail solutions
Interview Questions
Q1.How do you handle inventory during a flash sale to prevent overselling?
Preventing overselling in a flash sale requires: 1) Pre-event inventory staging — move stock to a fast cache (Redis) from DB. 2) Atomic decrements — use Redis DECR command which is atomic, preventing race conditions. 3) Soft reservation + TTL — on cart add, reserve with a 10-minute TTL; release if checkout doesn't complete. 4) Queue-based ordering — funnel all purchase requests through a queue (Kafka), process sequentially per SKU. 5) Optimistic locking at DB — use version numbers to detect concurrent updates. 6) Circuit breakers — if inventory service is overwhelmed, fail fast rather than oversell. Companies like Flipkart use pre-computed 'slots' so each purchase decrements from a pre-allocated bucket.
Q2.Design the architecture for a 10-minute delivery app (like Blinkit).
Quick commerce architecture key components: 1) Dark store network — small warehouse (2,000 sq ft) within 2-3 km of customer. 2) Real-time inventory per dark store — Elasticsearch for availability search filtered by location. 3) Assignment algorithm — assign nearest dark store with all items in stock. 4) Picking optimization — ML-trained picking path inside store to minimize pick time (SLA: 2-3 min). 5) Delivery partner assignment — nearest available partner via ride-matching algorithm (Haversine distance + travel time). 6) Dynamic ETA — continuously updated based on picker progress + rider location. 7) Hyperlocal search — catalog filtered by dark store inventory in real-time. Challenges: single-item orders (high delivery cost), weather disruptions, surge management.
Glossary & Key Terms
OMS
Order Management System — tracks orders from placement to delivery and returns
WMS
Warehouse Management System — manages inventory, picking, packing in warehouses
SKU
Stock Keeping Unit — unique identifier for each product variant
GMV
Gross Merchandise Value — total value of goods sold through platform (before returns)
Quick Commerce
Ultra-fast delivery (10-20 min) from hyper-local dark stores
Dark Store
Small urban warehouse serving only delivery orders, not open to walk-in customers
Marketplace
Platform model where third-party sellers list products (Flipkart, Amazon)
D2C
Direct-to-Consumer — brands selling directly without marketplace intermediary