008 ‐ eCommerce Domain Knowledge - rkb-sdet/SoftwareTesting GitHub Wiki

Session 8: eCommerce Domain Knowledge

Overview

This session covers critical e-commerce domain knowledge essential for software testers. It explores the purpose of e-commerce, different types of e-commerce business and revenue models, real-world examples, and the key terminology you must know to understand and test modern e-commerce applications effectively.

Key Concepts

  • E-commerce Purpose: Buying and selling goods and services online.
  • Domain Knowledge Importance: Understanding domain details helps testers grasp the client’s application and identify functional requirements and potential defects.

Types of E-commerce Application Models

By Business Model

Model Description Example
B2B (Business to Business) Businesses sell to other businesses. Automotive manufacturers buying parts online.
B2C (Business to Customer) Businesses sell directly to consumers. Amazon, Flipkart
C2C (Customer to Customer) Customers sell to other customers. OLX, eBay (for used goods)
C2B (Customer to Business) Individuals sell goods/services to businesses. Shutterstock (customers sell photos to the business)

By Revenue Model

Revenue Model Description Example
Drop-shipping Platform facilitates sales by other sellers in exchange for a commission. Amazon Marketplace
Subscription Customers pay recurring fees for access to goods/services. Online course platforms
Private Labeling Company sells its own manufactured goods online. Karachi Bakery online shop
White Labeling Sells goods from other manufacturers under own brand. (Amazon Basics, if Amazon brands third-party goods)
Wholesaling Sells goods in bulk to retailers, not individuals. Grocery wholesaler portals
Rental Products/services are rented for a fee, not owned. Movie rentals on YouTube
Freemium Basic services free, premium features paid. Zoom Meetings (free & paid plans)

By Application Type

  • Individual Brand Website: Company sells only its products (e.g., Adidas.com).
  • Online Retailer w/ Selected Sellers: Only certain authorized sellers can list products (e.g., Macy’s).
  • Marketplace: Open to any seller; broad selection (e.g., Amazon, eBay).

Example E-commerce Applications

  • Amazon/Flipkart: General goods marketplace, multiple sellers.
  • Myntra/Zalando: Fashion-specific.
  • MakeMyTrip: Travel bookings.
  • Uber/Ola: Rideshare, service-based.
  • Shutterstock: Digital content licensing (C2B).

E-commerce Terminology Cheat Sheet

Term Explanation
Product Display Page (PDP) Shows product details, price, images, reviews
Shopping Cart Temporary list of items selected for purchase
Checkout / Guest Checkout The process of entering shipping/billing to complete purchase. Guest checkout allows ordering without account creation.
Wishlist Items users plan to purchase in future
Affiliate Marketing External sites/blogs earn commission for sales referrals
Buyer's Persona Customer archetypes based on shopping behaviors
Call to Action (CTA) Buttons/links urging user action (e.g., “Buy Now”)
Content Management System (CMS) Platform for managing product info, media, prices by the admin/seller
Cookies Store user session data for persistency (e.g., cart retention)
Merchant Account Holds payments until order is fulfilled and released to seller
Email Marketing Promotional emails sent to users (offers, campaigns)
Payment Gateway Integrates with banks to process online payments (cards, UPI, wallets)
Hero Image Main large image/banner on homepage/product page
Search Functionality Enables product lookup across catalog
Categories Logical grouping (e.g., Electronics, Books)
Featured/Recommended Products Highlighted or algorithmically surfaced products
Order Management System tracking orders, shipping, returns
Return & Package Tracking Supports order status, returns, and tracking shipments

Useful Diagrams

1. E-commerce Business Models 

graph TD;
    A[Business Models] --> B(B2B)
    A --> C(B2C)
    A --> D(C2C)
    A --> E(C2B)
Loading

2. Order Flow (Simplified) 

sequenceDiagram
    Customer->>E-commerce App: Selects Product
    Customer->>E-commerce App: Adds to Cart
    Customer->>E-commerce App: Checkout
    E-commerce App->>Payment Gateway: Payment
    Payment Gateway-->>E-commerce App: Success/Fail
    E-commerce App->>Merchant Account: Hold Funds
    Merchant Account->>Seller: Transfer Funds on Fulfillment
    E-commerce App->>Customer: Order Confirmation & Tracking
Loading

Best Practices for E-commerce Domain Testing

  • Understand the business logic: Always map requirements to the specific business/revenue model.
  • Explore competitor apps: Compare feature behavior for defect detection and user experience benchmarking.
  • Master domain terminology: Clear understanding of domain vocabulary avoids miscommunication.
  • Emphasize security and privacy: Especially for payments, cookies, and user data.
  • Test on multiple platforms: For web and m-commerce (mobile e-commerce).
  • Review order management and fulfillment logic: Includes returns, refunds, and shipping flows.

Key Takeaways

  • Different e-commerce models mean different architecture, flows, and test cases.
  • Revenue and business models dictate user journey and platform features.
  • A robust knowledge of domain terms and real-world applications is essential.
  • Diagrammatic understanding simplifies complex concepts and supports defect identification.
  • Compare with top industry platforms to improve your testing approach and reporting.

Tip: For further reading and terminology, consult leading e-commerce, marketing, and tech documentation, or domain glossaries online for regular updates and deeper expertise.

⁂
⚠️ **GitHub.com Fallback** ⚠️