| name | ecommerce |
| description | Use when defining the overall model, experience, trust, product-decision, and growth strategy for an online store; do not use for deep checkout, lifecycle, analytics, or omnichannel operating-system work. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Ecommerce
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use when
- A new or existing online store needs its business model, product-decision experience, customer promise, trust proof, and growth handoffs defined together.
- Product/category experience or channel strategy needs a store-wide decision before narrower checkout, funnel, analytics, or retail-system work.
Do not use when
- The issue is limited to checkout/payment recovery; use
ecommerce-checkout.
- The issue is acquisition/lifecycle orchestration or KPI/event design; use
ecommerce-funnel or ecommerce-analytics.
- Omnichannel systems, POS, inventory, fulfilment, or finance controls dominate; use
retail-commerce-operating-system.
Required Inputs
| Input | Source | Required | If absent |
|---|
| Business model, offer, customer, geography, and channel mix | Discovery/business brief | yes | Stop model selection and list the missing decisions. |
| Catalogue, pricing, fulfilment, returns, payments, and support reality |