Commerce
E-Commerce & Marketplaces
Comprehensive guide to e-commerce platforms, marketplace systems, order management, catalog management, and online retail technology.
$6.3T
Global Market
$80B+
India Market
10M+
Daily Orders
75%+
Mobile Share
What Engineers Miss When They First Enter E-Commerce & Marketplaces
E-commerce systems appear deceptively approachable — there are products, there are carts, there are orders. Every developer has shopped online and has a mental model of what the experience should be. The surprise comes when you look underneath: catalog management at a large marketplace means 500 million product listings with multiple sellers competing on the same ASIN, pricing engines that adjust in real time based on competitor signals, and search indexes that have to reflect live inventory changes within seconds. The surface is simple, the machine underneath is not.
India's e-commerce market has unique engineering characteristics that have shaped the thinking of engineers who've built there. Social commerce platforms like Meesho handle resellers who create their own storefronts from an underlying marketplace catalog — which means any change to catalog structure or image guidelines cascades into millions of reseller-created listings that were never built to be compatible with the new format. Quick commerce platforms like Blinkit operate on margin economics so tight that an extra 30 seconds in pick time can make the difference between a unit economics positive and negative delivery. These constraints produce engineering cultures that are intensely focused on operational efficiency.
The seller-side of e-commerce is often where the hardest problems live, because sellers are not always technical and they are not always compliant with platform rules, but they are the source of inventory and the party whose behavior most directly affects customer experience. Catalog ingestion pipelines have to handle feeds in 50 different formats, with missing required fields, duplicate listings, and pricing that violates regulatory rules — and they have to do it fast enough that a new seller who uploads their catalog at 9am can receive their first order by noon.
What Teams Actually Do Day To Day
- 1Build and operate the catalog platform that ingests product data from millions of sellers, normalises it against category-specific attribute schemas, deduplicates listings that represent the same physical product, and makes the result searchable within minutes of a seller update.
- 2Maintain the search and discovery stack — query parsing, spell correction, intent classification, real-time inventory filtering, personalisation ranking, and A/B test infrastructure — knowing that a 10ms improvement in search latency correlates with measurable revenue lift at scale.
- 3Design inventory allocation systems that handle flash sale pre-allocation, split-warehouse fulfillment from the nearest available location, seller-managed vs. platform-managed inventory with different consistency guarantees, and cross-border inventory that involves customs clearance timelines.
- 4Build the order state machine and its compensating flows: partial cancellations where one item in a three-item order is out of stock after payment, seller non-fulfillment handling where the platform sourced a replacement from another seller without the customer noticing, returns and replacement flows where the original order's payment, shipment, and inventory records all need updates.
- 5Run the seller operations platform that handles seller onboarding, catalog quality scoring, SLA compliance measurement, payout calculation with returns and fee deductions reconciled across the settlement cycle, and the account health dashboard that determines whether a seller's listings stay active.
One End-to-End Flow: A Customer Buys a Laptop During a Sale Event
High-value electronics purchases during a sale event exercise inventory allocation, credit card payment, insurance add-on processing, multi-item logistics, and extended warranty registration — all in a single customer session.
Customer finds the product through search
The search query is processed through query understanding (intent: laptop buying, not repair), spellcheck, synonym expansion, and category classification before being sent to the index. The result ranking combines relevance score, seller rating, inventory availability, price competitiveness, and sponsored placement bids — all computed in under 100ms.
Systems Involved
Search service, query understanding model, product index, ranking service
Where It Usually Breaks
Real-time inventory signals are expensive to incorporate at query time. Platforms often use a slightly stale inventory flag in the search index, which means a product can appear in results and then show as out-of-stock when the customer lands on the product detail page.
Customer adds to cart and checks if the laptop is still available
The cart add triggers an availability check against live inventory (not the search index). For a high-value item with limited stock, the availability response also returns how many units are left, which may be used to display urgency signals ("Only 3 left").
Systems Involved
Cart service, live inventory service, product detail service
Where It Usually Breaks
If the availability check is cached at the CDN level for performance, the 'Only 3 left' message can be stale, showing scarcity for an item that actually has 200 units — or showing availability for an item that is gone.
Checkout applies pricing, coupons, and add-ons
The checkout service recalculates the price to apply any sale discount, checks coupon validity (one-use coupons require a distributed lock to prevent double-redemption), adds GST, calculates EMI options across 15 bank partner offers, and shows the insurance and extended warranty add-ons.
Systems Involved
Pricing engine, coupon service, tax calculation, EMI eligibility service, add-on catalog
Where It Usually Breaks
Price discrepancy between the search result page and checkout is a known trust issue. It happens when the pricing engine and the search index are not in sync — typically because the pricing engine was updated after the product was last indexed.
Payment completes via credit card with EMI
The customer selects a 12-month no-cost EMI offer from their bank. The payment gateway initiates an authorisation for the full amount, which the issuing bank converts to an EMI loan internally. The gateway returns an authorisation code and the checkout service creates the order.
Systems Involved
Payment gateway, issuing bank, EMI conversion service, order service
Where It Usually Breaks
EMI eligibility checks are made before checkout but the actual EMI availability is confirmed at the moment of payment. If the bank's EMI service is unavailable at payment time, the customer has to pay full price or abandon — with no graceful fallback.
Order is split and sent to fulfillment
The OMS determines which warehouse holds the laptop and assigns a pick task. If the customer also bought accessories from a different seller, the order is split into separate shipments. Each shipment gets a carrier assignment based on the customer's location and the carrier's current capacity.
Systems Involved
OMS, fulfillment engine, WMS, carrier assignment service
Where It Usually Breaks
Split shipment logic that is not clearly communicated to customers generates support contacts — the customer expects one box and gets two, on different days, from different carriers. The notification service needs to explain the split proactively.
Delivery, unboxing, and post-sale activation
After delivery, the extended warranty registration, GST invoice generation, and product review prompt are triggered. The warranty registration involves calling the manufacturer's API with the device serial number. If that fails, the warranty is considered unregistered and the customer may discover this months later when making a claim.
Systems Involved
Delivery confirmation service, invoice generation, warranty registration API, review prompt service
Where It Usually Breaks
Manufacturer API integrations for warranty registration are often the weakest link in the post-purchase flow — unstable, poorly documented, and with no retry logic built into the retailer's system.
Technology Architecture — How E-Commerce & Marketplaces Platforms Are Built
The diagram below reflects how production E-Commerce & Marketplaces systems are structured at scale — nine layers from client channels through edge security, API gateway, domain microservices, polyglot data stores, async event streaming, analytics, external partners, and cloud infrastructure. Solid arrows show synchronous REST/gRPC calls; dashed arrows show async event flows via Kafka or a message queue.
Industry Players & Real Applications
🇮🇳 Indian Companies
Flipkart
Marketplace
Java, React, Kubernetes
India's largest e-commerce, Walmart-owned
Amazon India
Marketplace + D2C
AWS, Java, React
Fastest growing market for Amazon globally
Myntra
Fashion E-commerce
React, Node.js, ML
Fashion marketplace, Flipkart subsidiary
Meesho
Social Commerce
Kotlin, React Native
130M+ transacting users, social selling
Nykaa
Beauty & Fashion
Custom Platform
Omnichannel beauty platform
Tata CLiQ
Luxury Marketplace
Salesforce Commerce
Tata Group's e-commerce platform
JioMart
Grocery & General
Custom, Java
Reliance's e-commerce arm
BigBasket
Grocery
Python, React
Online grocery, Tata-owned
🌍 Global Companies
Amazon
USAEverything Store
AWS, Java, React
World's largest e-commerce platform
Alibaba
ChinaMarketplace Giant
Custom, Java, AliCloud
Largest e-commerce by GMV globally
Shopify
CanadaE-commerce Platform
Ruby, React, GraphQL
Powers millions of online stores
eBay
USAMarketplace
Java, Node.js
C2C and B2C marketplace
Mercado Libre
LATAMMarketplace
Java, React
Largest e-commerce in Latin America
Zalando
EuropeFashion Platform
Kotlin, React
Europe's leading fashion platform
Coupang
KoreaE-commerce
Java, Kubernetes
Korea's largest e-commerce, Rocket Delivery
Sea/Shopee
SEAMarketplace
Golang, React
Largest in Southeast Asia
🛠️ Enterprise Platform Vendors
Shopify
Commerce Platform, Checkout, POS, Markets
Powers millions of merchants globally
Salesforce Commerce
B2C Commerce, B2B Commerce, Order Management
Enterprise commerce cloud
Adobe Commerce
Magento Commerce, Experience Platform
Open-source and enterprise commerce
BigCommerce
Open SaaS Commerce, Headless Commerce
Mid-market e-commerce platform
commercetools
Headless Commerce, MACH Architecture
API-first commerce platform
Fabric
Modular Commerce, OMS, PIM
Headless commerce modules
Vtex
Commerce Platform, Marketplace, OMS
Popular in Latin America
SAP Commerce
Hybris Commerce Suite
Enterprise omnichannel commerce
Core Systems
These are the foundational systems that power E-Commerce & Marketplaces 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 E-Commerce & Marketplaces Teams Actually Use. Every technology choice in E-Commerce & Marketplacesis 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 E-Commerce & Marketplaces 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 E-Commerce & Marketplacesplatforms 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
Order management, inventory, catalog services
Node.js
API gateway, BFF services, real-time features
Golang
High-performance services - cart, checkout, pricing
Python
ML services - recommendations, search ranking, fraud
🖥️ frontend
React/Next.js
Web storefront, seller portal, admin dashboards
React Native/Flutter
Mobile shopping apps
GraphQL
Flexible data fetching for frontend
🗄️ database
PostgreSQL
Order data, customer data, transactional systems
MongoDB
Product catalog, reviews, flexible schema data
Elasticsearch
Product search, autocomplete, filters
Redis
Cart data, session cache, rate limiting
Apache Kafka
Event streaming, order events, inventory updates
🔗 integration
REST APIs
Service-to-service communication
gRPC
High-performance internal services
GraphQL Federation
Unified API for frontends
Webhooks
Seller integrations, logistics updates
☁️ cloud
AWS/GCP
Cloud infrastructure, auto-scaling
Kubernetes
Container orchestration, microservices
CDN (CloudFront)
Static assets, images, API caching
S3/GCS
Product images, media storage
Interview Questions
Q1.How would you design an e-commerce product catalog that handles millions of products?
Use a combination of relational (PostgreSQL) for structured data like pricing and inventory, and NoSQL (MongoDB) for flexible product attributes. Implement PIM (Product Information Management) for data governance. Use Elasticsearch for search with denormalized product data. Cache hot products in Redis. Implement product data versioning for audit. Use CDN for images. Design for multi-tenant if marketplace. Partition data by category for scale.
Q2.How do you handle inventory consistency during flash sales with millions of concurrent users?
Implement pessimistic locking at database level for inventory updates. Use Redis for real-time inventory counters with Lua scripts for atomic operations. Implement circuit breakers to handle traffic spikes. Use queuing (SQS/Kafka) to serialize inventory updates. Reserve inventory on add-to-cart with timeout-based release. Implement rate limiting per user. Use eventual consistency for analytics but strong consistency for purchases. Consider overselling buffer for popular items.
Q3.Explain how you would implement a recommendation engine for an e-commerce platform.
Combine collaborative filtering (users who bought X also bought Y) with content-based filtering (similar product attributes). Use user behavior signals - views, cart adds, purchases, search queries. Implement real-time recommendations using feature stores. Use ML models (matrix factorization, deep learning) trained on historical data. A/B test recommendation algorithms. Implement hybrid approach with fallback rules. Consider cold-start problem for new users/products. Personalize based on session context.
Q4.How do you ensure order consistency in a distributed microservices architecture?
Implement Saga pattern for distributed transactions across services (inventory, payment, order). Use compensating transactions for rollback. Event sourcing for order state changes. Idempotency keys to handle duplicate requests. Two-phase commit for critical paths. Dead letter queues for failed events. Implement order state machine with clear transitions. Use distributed tracing for debugging. Monitor for orphaned orders and implement reconciliation jobs.
Q5.How would you design a seller settlement system for a marketplace?
Track order events (delivered, returned, cancelled) in event store. Calculate settlement per seller factoring in commission, shipping subsidy, penalties. Implement T+N settlement cycle (typically T+7). Handle refunds and returns affecting settlement. Deduct TDS at source. Generate detailed settlement reports. Implement reconciliation with logistics and payment data. Handle disputes and adjustments. Comply with GST invoicing requirements. Use batch processing for large-scale settlements.
Q6.How do you optimize checkout conversion rate from a technical perspective?
Minimize checkout steps, implement one-page checkout. Prefetch user data (addresses, payment methods). Lazy load non-critical elements. Implement address autocomplete. Cache payment tokens for returning users. A/B test checkout flows. Implement cart persistence across devices. Optimize for mobile-first. Reduce payment failures with fallback methods. Implement abandoned cart recovery with notifications. Use analytics to identify drop-off points.
Glossary & Key Terms
SKU
Stock Keeping Unit - unique identifier for each distinct product variant
GMV
Gross Merchandise Value - total value of goods sold on the platform
AOV
Average Order Value - average amount spent per order
CAC
Customer Acquisition Cost - cost to acquire a new customer
LTV
Lifetime Value - predicted revenue from a customer over their lifetime
PDP
Product Detail Page - the page showing full product information
PLP
Product Listing Page - page showing list of products (search results, category)
OMS
Order Management System - system managing order lifecycle
WMS
Warehouse Management System - system managing warehouse operations
PIM
Product Information Management - system for managing product data
3PL
Third-Party Logistics - external logistics provider for fulfillment
D2C
Direct-to-Consumer - brands selling directly without intermediaries