2. Catalog / PIM
Purpose — Rich product information for technical, serial-numbered goods, including kits/BOM, compatibility, spares, and downloadable docs — multilingual.
Personas served
Customer, Dealer, Marketing admin, Technician (spec lookup), Service head.
Key capabilities
- Technical specs per model (capacity kVA/kWh, dimensions, efficiency, certifications) as structured attributes.
- Variants & SKUs (capacity, phase, voltage, color).
- Kits / bundles / BOM — a "3 kW solar system" = many SKUs sold as one configurable system; drives the configurator in Storefront.
- Compatibility & accessory mapping — which battery fits which inverter; which spare fits which model (also used by FSM for repairs).
- Documents — datasheets, manuals, certificates, energy-rating labels (object storage).
- Spare-parts catalog linked to parent products (critical for service); see Inventory.
- Lifecycle — discontinued/EOL handling while keeping warranty + service history alive (Warranty).
- Multilingual content — localized titles/descriptions (i18n).
Data owned
Medusa (PG): products, variants, options, categories, collections, kits. Translation sidecar for localized fields. Compatibility & spares mapping: lightweight relations in a NestJS catalog-extension service (Mongo) referencing Medusa product IDs when they exceed Medusa's native model.
Events
- Emits:
product.created/updated,product.eol,price.updated. - Consumes:
supplier.part.updated(from procurement).
APIs
- Admin (Medusa): product/variant/category CRUD, kit definition.
GET /catalog/compatibility?productId=,GET /catalog/:id/spares,GET /catalog/:id/docs
Tenant-config knobs
Default locale set for catalog; attribute templates per product family (solar/inverter/AC); document categories.
Dependencies
Storefront, Inventory, Warranty, i18n.
Open questions
- Is a dedicated PIM beyond Medusa needed at scale, or do Medusa attributes + sidecar suffice?
- Source of authoritative technical specs (ERP import vs manual)?