E-Commerce and WWW
1. Why the WWW Made E-Commerce Possible
Before the web, electronic trading existed over EDI (value-added networks) — costly, closed, company-to-company. The World Wide Web turned the Internet into a cheap, global, open storefront:
| Web capability | E-commerce consequence |
|---|---|
| Hypermedia (HTML pages + links) | rich, self-service product catalogues |
| HTTP over TCP/IP | universal, cheap global reach — a shop open 24×7 to the world |
| Browsers as universal clients | zero-install customer access (thin client) |
| Forms + CGI/JSP/PHP | order capture, interaction, dynamic pricing |
| Search engines | product discovery, marketing channel |
| HTTPS/TLS | secure payment over an open network |
2. Anatomy of a Web-Based E-Commerce Transaction
CUSTOMER BROWSER MERCHANT WEB/APP SERVER BACKEND
1. browse catalogue --HTTP--> presentation tier
2. add to cart --HTTPS--> session (cart bean / cookie)
3. checkout form --HTTPS--> order processing (servlet/JSP/PHP)
4. payment --HTTPS--> payment gateway (card/UPI/wallet)
| | authorization request
| v
| BANK / PSP --- approve/decline
5. order confirmation <--HTTP-- order DB, inventory, ERP/CRM, shipping
6. tracking emails / push <-- notification services
3. Functional Areas of a Web Storefront
- Catalogue / content management — product pages, media, search & filters.
- Shopping cart & wish-list — session state (cookie/session/database cart).
- Order management — checkout, tax, shipping cost, invoice.
- Payment processing — gateway integration (card, UPI, wallets, COD).
- Customer service — FAQ, chat, returns/RMA, ticketing.
- Customer accounts & CRM — profile, order history, loyalty points, recommendations.
- Analytics — traffic, funnel conversion, abandonment rate, A/B testing.
4. Technology Stack (typical, module-wise relevance)
- Presentation — HTML/CSS/JS, AJAX, responsive/mobile UI.
- Application tier — PHP / JSP & Servlets / ASP.NET / Node; session handling.
- Data tier — RDBMS (MySQL/Oracle) for catalogue & orders; caches (Redis) for carts.
- Integration — payment gateway APIs, logistics APIs, ERP/CRM connectors, web services.
5. Advantages and Limitations of WWW-Based E-Commerce
Advantages
- Global reach, 24×7 availability; low setup cost versus physical stores.
- Reduced search & transaction costs for buyer and seller; price transparency.
- Personalisation (recommendations), mass customisation, rich product information, quick comparison.
- Disintermediation (direct sales), better inventory/SCM integration, new digital products/services.
Limitations / barriers
- Trust & security — fraud, data theft, identity misuse; needs SSL, PCI-DSS compliance.
- Privacy — tracking of consumer data; regulation (IT Act, GDPR).
- Digital divide, low bandwidth areas; logistics for physical delivery and returns.
- Tax/legal jurisdiction issues; product-touch-and-feel absence; dot-com failure economics (customer acquisition cost).
6. Impact Areas of E-Commerce on WWW Usage
- Retail — e-tail/marketplaces; Services — travel, banking, insurance (e-banking, e-governance);
- Media — digital delivery of music, video, e-books, software, SaaS (fully digital products);
- Marketing — search/affiliate/social marketing, personalisation engines;
- Payments — wallets, UPI, BNPL — moving commerce to mobile commerce (m-commerce).
7. Exam Points
- Explain the role of WWW in the growth of e-commerce with the architecture of a web transaction — 10 marks.
- List and explain functional areas of an e-commerce website — 7-10 marks.
- Advantages and limitations of e-commerce — 5-7 marks (very frequent).
- Short notes: shopping cart, payment gateway, conversion rate — 3-5 marks each.