Skip to main content

1. Storefront & Sales Channels

Purpose — Sell one catalog across many channels (own web/app, dealer B2B, Amazon, Flipkart, retail/POS, WhatsApp), each with its own pricing and availability, and capture high-ticket leads that aren't pure "add-to-cart."

Personas served​

Customer (D2C), Dealer (B2B), Marketing admin.

Key capabilities​

  • Multi-channel from one catalog — Medusa sales channels: web, app, dealer-b2b, amazon, flipkart, pos. Per-channel product availability + price.
  • Channel-specific pricing — D2C vs dealer vs distributor vs project/B2B (Medusa price lists + DMS tiers, see DMS).
  • Product configurator / "build your system" — solar kit builder (panels + inverter + battery + structure → BOM). See Catalog/PIM.
  • Lead / quote flow — "Request a quote" for high-ticket items → routed to nearest dealer (DMS) / CRM.
  • Buy-online-fulfill-by-dealer (BOPIS) — order routed to nearest authorized dealer.
  • Financing & subsidy — EMI options; solar government-subsidy workflow (PM Surya Ghar) when subsidyWorkflow flag on.
  • Conversion aids — wishlist, compare, recently-viewed, cart-abandonment recovery.
  • SEO/accessibility/perf — SSR/ISR, localized URLs + hreflang, Lighthouse-gated (Testing).
  • Calculators — ROI / bill-savings (solar) as lead magnets (Marketing).

Data owned​

None of its own — composes Medusa (PG): products, channels, prices, carts. Leads persist to CRM (Mongo). Channel connectors sync state (see Marketplaces).

Events​

  • Emits: lead.created, cart.abandoned.
  • Consumes: price.updated, inventory.changed (to reflect availability).

APIs (via BFF → Medusa Store API)​

  • GET /store/products (channel + locale aware), GET /store/products/:id
  • POST /store/carts, POST /store/carts/:id/line-items, POST /store/carts/:id/complete
  • POST /leads (quote request) → CRM/DMS
  • GET /channels/:channel/catalog

Tenant-config knobs​

featureFlags.amazonChannel, flipkartChannel, subsidyWorkflow; enabled SUPPORTED_LOCALES; currency; channel price-list mapping.

Dependencies​

Catalog/PIM, DMS, Orders/Fulfillment, Payments.

Open questions​

  • Is POS/retail channel in scope for v1 or v2?
  • Quote-to-order conversion: dealer-led or HQ-led by default?