Business Shape & Personas
Why the feature set is what it is
The target brands (UTL, Luminous, Exide, Daikin, Voltas …) share one operating profile:
Serial-numbered physical products + tiered distribution + after-sales service.
That profile forces four distinct user groups ("personas"), each needing its own surface (web, app, portal). Every feature in the platform maps to one or more of them.
The four personas
1. Customer (D2C buyer / product owner)
Buys via web, app, marketplace, or a dealer. Owns serial-numbered assets, registers warranty, raises complaints, buys/renews AMC, tracks technicians. Surfaces: Next.js storefront, Customer React Native app, "My Products" portal.
2. Dealer / Distributor / Installer (channel partner)
The tiered network that actually moves volume. Places orders, manages credit/ledger, hits targets, earns schemes/loyalty, captures leads, often performs installs. Surfaces: Dealer portal (web) + Dealer React Native app.
In the
notesthis persona is called "vendor." Throughout the docs we use the precise term channel partner / dealer. See Glossary.
3. Technician / Service engineer (field workforce)
Employed by the company or by a third-party service partner. Receives jobs, navigates to site, performs install/repair/AMC visits, consumes spare parts, closes jobs with photos/signature. Surfaces: Technician React Native app (offline-first).
4. Company admin (HQ ops / marketing / finance / service head)
Runs the business: catalog, pricing, promotions, content, finance/GST, warranty policy, dispatch oversight, analytics. Needs role-scoped views. Surfaces: Medusa Admin + custom team dashboards (marketing / finance / technician-head).
Manager data-scoping (from the notes)
Managers are a sub-type of admin with data-scoping: a regional/area manager sees only the channel partners assigned to them (their sales, targets, ledgers), while a national manager sees across all. This scoping is enforced in Auth & RBAC and reflected in every DMS/analytics query.
Persona → primary modules
| Persona | Primary modules |
|---|---|
| Customer | Storefront, Catalog, Orders/Fulfillment, Warranty, FSM/AMC, CRM/Loyalty, CMS |
| Dealer / Distributor | DMS, Orders, Loyalty, CRM, Inventory (their stock) |
| Technician | FSM, Inventory (van stock), Warranty |
| Admin / Manager | All modules + Admin/Analytics, Finance, RBAC scoping |
The continuous-record principle
The platform's reason to exist: one product is one record across its whole life —
manufactured → sold (any channel) → delivered → warranty-registered
→ installed/commissioned → serviced (AMC/repair) → claims → end-of-life
No persona ever loses sight of that record. A panel sold on Amazon, installed by a dealer, and serviced under AMC three years later is the same asset in the Warranty & Asset Registry.