Import Mapping
The mapping layer is most explicit in product and category imports, where previews detect headers and expose real importable fields derived from company configuration.
Field Mapping
Map CSV columns to PIM attributes
| Source Column (CSV) | Target Attribute (PIM) | Preview | |
|---|---|---|---|
| sku_code | → |
SKU
|
NIKE-423-BL |
| product_title | → |
Name (EN)
|
Nike Air Max... |
| retail_price | → |
Price (Standard)
|
129.00 |
| unmapped_field_01 | → |
Select attribute...
|
Value X |
How it works in the app
Imports and exports are implemented per entity rather than through one generic pipe. Products, categories, brands, suppliers, customers, payment terms, and resource items all have their own actions, DTOs, parsers, previews, or exporters.
The most concrete import UX appears in product and category previews, which remove empty rows and columns, detect likely headers, and expose mapping against real fields such as currencies, custom fields, and property groups.
Included in the current implementation
Entity-specific import actions and services
Preview-first spreadsheet validation
Mapping against configured company fields
Dedicated spreadsheet exporters
Need spreadsheet exchange that matches the actual data model?
The current codebase already ships with previewable imports and module-specific exports across the core entities.