E-commerce Domain Knowledge

Analyze e-commerce platform requirements across B2C, B2B, C2C, and Marketplace models.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Danhvb/my-ba-skills --skill e-commerce-domain-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: E-commerce Domain Knowledge
Source: https://github.com/Danhvb/my-ba-skills/tree/main/multi-agent-ba/.agent/skills/domain-knowledge/ecommerce
Command: npx skills add https://github.com/Danhvb/my-ba-skills --skill e-commerce-domain-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understands e-commerce domain knowledge to support requirements analysis for B2C, B2B, C2C, and Marketplace platforms.

Core Features & Use Cases

  • Domain modeling guidance for e-commerce ecosystems (B2C, B2B, C2C, Marketplace)
  • Core module outlines and common requirements patterns (Product Catalog, Shopping Cart, Checkout, Orders, Promotions)
  • Real-world scenario mapping to requirements and architectural decisions

Quick Start

Ask the AI to summarize the differences between B2C and Marketplace platforms and outline core module requirements for each.

Frequently Asked Questions about E-commerce Domain Knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze requirements for a multi-model e-commerce platform?

To analyze e-commerce platform requirements, map real-world scenarios to core modules like product catalog, shopping cart, checkout, and orders across B2C, B2B, C2C, and Marketplace models to ensure accurate domain modeling and architectural decisions.

What is the difference between B2C and Marketplace e-commerce domain models?

B2C domain models focus on direct business-to-consumer transactions, while Marketplace models facilitate multi-vendor interactions. Core module requirements differ significantly in product catalog ownership, shopping cart logic, and checkout flows between these e-commerce architectures.

How do I scope core module features for an e-commerce system?

Scope core e-commerce module features by outlining common requirements patterns for product catalog, shopping cart, checkout, orders, and promotions to ensure comprehensive coverage of necessary platform functionalities.

Can I use this e-commerce domain knowledge for B2B requirements engineering?

Yes, this e-commerce domain knowledge supports B2B requirements engineering by providing domain modeling guidance and common requirements patterns applicable to B2B, B2C, C2C, and Marketplace platform architectures.

What architectural decisions are needed for a multi-vendor marketplace checkout?

Architectural decisions for marketplace checkout require mapping domain knowledge to handle multi-vendor shopping carts, split payments, and order routing to ensure the checkout module correctly supports complex marketplace requirements.

When should I customize e-commerce domain models for specific business patterns?

Customize e-commerce domain models when standard B2C, B2B, C2C, or Marketplace patterns do not fit specific business scenarios by mapping real-world requirements to core modules like product catalog and orders to guide necessary architectural adaptations.