Platform Vision
One platform, many brands
This is not a store for a single company. It is a white-label commerce + after-sales platform for the class of business that manufactures or distributes physical products and services them in the field:
- Solar (panels, inverters, PCUs, batteries) — e.g. UTL Solar
- Power backup (inverters, batteries, stabilizers) — e.g. Luminous, Exide
- HVAC / cooling (ACs, coolers, VRV) — e.g. Daikin, Voltas
Every one of these brands shares the same operational DNA: serial-numbered products + a tiered dealer network + installation, warranty and AMC service. We build that DNA once and let each brand run on it.
The white-label promise
A new brand goes live by supplying configuration, not code.
A company onboards by providing:
- Branding assets — logo, favicon, hero images, color tokens → stored in the tenant's object-storage bucket.
- Configuration — locales, currency, payment keys, courier keys, feature flags, legal entity / GST details → supplied via environment variables + the Tenant Config Contract (see Multi-Tenancy & White-Label).
The application code is tenant-agnostic. No brand name, color, or business rule is hard-coded. UTL Solar is simply the first tenant.
Tenancy model: per-tenant deployment
Each company runs in its own isolated deployment — a dedicated Kubernetes namespace on Vultr with its own databases and asset bucket — built from one templated pipeline off the shared codebase. This gives strong data isolation and per-brand scaling, while keeping a single code/config contract. (See Deployment.)
What "full software" means here
The platform spans five systems that most teams buy separately and never integrate:
- Storefront + Catalog (PIM) — D2C and B2B selling across channels (self, Amazon, Flipkart).
- Dealer/Distribution Management (DMS) — the tiered channel that actually moves product.
- Field Service Management (FSM) — installation, complaints, AMC, the technician app.
- Warranty & Asset Registry — serial lifecycle, registration, claims, decisioning.
- Back-office — finance/GST, loyalty, CRM, content/marketing, analytics.
The differentiator is that these are one system sharing one customer/asset graph, so a panel sold on Amazon, installed by a dealer, registered for warranty, and serviced under AMC three years later is one continuous record.
Design principles
- Config over code — anything that varies per brand is configuration.
- Commerce vs domain separation — Medusa owns commerce; bespoke NestJS services own service/warranty/DMS. See Polyglot Data Stores.
- Event-driven — modules react to domain events, not to each other's tables. See Eventing & Integration.
- Service is first-class — after-sales is half the business, so FSM/AMC are core modules, not bolt-ons.
- India-first — GST, e-invoicing, UPI/RuPay, vernacular languages, government solar subsidy flows are baseline, not afterthoughts.
Who this documentation is for
- Engineers building the services — architecture, data models, APIs, integration contracts.
- Product / ops — module capabilities and the delivery roadmap.
- New-tenant onboarding — the config contract and onboarding runbook.
Start with Business Shape & Personas, then the System Architecture.