# Product Vision

## What CommerceDex is

**CommerceDex — The Commerce Operating System.**

CommerceDex is a self-hosted commerce platform for businesses of every size — from SMEs to growing enterprises — that want complete ownership of their online store without the complexity of traditional e-commerce platforms.

The storefront is only one component. The real product is the complete business operating system underneath it: catalog, inventory, orders, customers, payments, shipping, tax, marketing, automation, and merchant health, all working together so a merchant spends their time running their business, not configuring software.

## What CommerceDex is not

- **Not a website builder.** Page layout is a small part of the product, not the point of it.
- **Not a CMS.** Content management is one supporting module, not the core value proposition.
- **Not another WooCommerce clone.** It is not a plugin-first, infinitely-configurable platform that pushes complexity onto the merchant or a developer.
- **Not a multi-tenant SaaS platform.** Each install runs one merchant's store (see `03-reference-architecture.md`). CommerceDex does not need to solve tenant isolation, noisy-neighbor, or SaaS-scale multi-tenancy concerns — "commercial-grade" here means reliability, data integrity, and a solid backup story for a single store, not SaaS-scale infrastructure.
- **Not a platform that requires plugins for basic best practices.** Image optimization, SEO metadata, duplicate detection, and similar hygiene are native behavior, not marketplace add-ons.

## Target user

A merchant who wants to **self-host** their commerce platform — own their data, avoid recurring SaaS fees, and control their infrastructure — but does **not** want to become a systems administrator or hire a developer agency to operate day-to-day. This is closer to a self-hosted WooCommerce or Shopify user than to an engineering team standing up a custom platform. Every architecture and UX decision should be judged against this user: does it reduce what they need to know, configure, or maintain?

## Core philosophy

> Merchants should spend their time running their business — not configuring software.

The system should quietly perform work in the background without requiring intervention. Never expose technical settings unless absolutely necessary. Prefer intelligent defaults over configuration, automation over manual setup, simplicity over flexibility.

## The module surface

CommerceDex is composed of 20 bounded modules (fully defined in `04-domain-modules.md`). This table is the product surface — what the system does, described in business language:

| Module | What it does for the merchant |
|---|---|
| Commerce Core | Ties the storefront and checkout together around the store's identity and rules |
| Catalog | What's for sale, and how it's organized and described |
| Inventory | How much stock exists, where, and when it's running low |
| Orders | What customers bought and where each order stands |
| Customers | Who's buying, and their history with the store |
| Payments | Getting paid, securely, without touching card data directly |
| Shipping | Getting orders to customers and pricing that delivery |
| Tax | Calculating the right tax at checkout |
| Marketing | Campaigns, promotions, and who to target with them |
| Discount Engine | Coupons, bundle pricing, and discount rules |
| Automation Engine | The store's built-in commerce intelligence — detection and recommendations |
| Notification Service | Getting the right message to the right person on the right channel |
| Media Manager | Storing and processing images and other assets |
| Content Manager | Pages, banners, and announcements outside the catalog |
| Analytics | Capturing what's happening in the store, as raw metrics |
| Reporting | Turning metrics into merchant-readable reports |
| Merchant Health | The store's health score and specific coaching recommendations |
| User Management | Staff accounts, roles, and permissions |
| Settings | Store-level configuration everything else reads |
| Search Engine | Helping customers find what they're looking for |

## Built-in automation catalog

These are native capabilities, not plugins, and not "AI features" — they are business-rule-driven commerce intelligence. Grouped by theme:

**Recovery & re-engagement** (owned by Automation Engine, delivered via Notification Service)
- Abandoned cart recovery
- Wishlist notifications
- Back-in-stock notifications
- Repeat purchase reminders
- Customer re-engagement campaigns

**Inventory intelligence** (owned by Automation Engine, sourced from Inventory)
- Low stock alerts
- Overstock alerts
- Slow-moving inventory detection
- Trending product detection
- Automatic reorder recommendations

**Merchandising intelligence** (owned by Automation Engine, sourced from Catalog + Orders)
- Frequently bought together
- Smart product recommendations
- Seasonal promotion suggestions
- Bundle recommendations
- Discount suggestions
- Cross-sell opportunities

**Catalog quality** (owned by Automation Engine, sourced from Catalog + Media Manager)
- Missing image detection
- Product quality scoring
- Duplicate detection
- Incomplete product detection
- Broken category detection

**Product upload assistance** (owned by Media Manager + Catalog, triggered on upload)
- Image compression
- Responsive image size generation
- Image quality optimization
- SEO-friendly URL generation
- Image alt text generation
- Basic SEO metadata generation
- Related/complementary product suggestions
- Bundle and upsell/cross-sell suggestions

**Store health coaching** (owned by Merchant Health, aggregating signals from across the system)
- A single Store Health Score
- Specific, actionable recommendations — not just charts (e.g., "Five products missing descriptions," "Three best-selling products running low on stock," "Twenty abandoned carts awaiting recovery")