CSV mapping is the forgotten step in e-commerce import guides. We talk about format, encoding, separator — but rarely about the correspondence between source file columns and CMS target fields. Yet that is where 60% of post-import errors originate.
Mappable data sources
The most common column correspondences
| Typical supplier column | Shopify field | PrestaShop field |
|---|---|---|
| Product name / Label | Title | Name * |
| Long description | Body (HTML) | Description |
| Short description | Tags or metafield | Short description |
| Reference / Part number | Variant SKU | Reference |
| Barcode / EAN13 | Variant Barcode | EAN13 |
| Main category | Product Category | Default category (ID) |
| Supplier price excl. tax | Variant Price (× tax) | Price (excl. tax) |
| Stock / Available qty | Variant Inventory Qty | Quantity |
| Main image URL | Image Src | Image URL |
| Brand / Manufacturer | Vendor | Manufacturer (ID) |
3 types of transformation during mapping
Value transformation
Structural transformation
Enrichment during mapping
Documenting your mapping: an investment that pays off
If you manage multiple suppliers with different CSV schemas, document each mapping in a reference table. This avoids redoing the same work on every new supplier catalog delivery.
Seegea saves mappings per supplier. The next time you receive a CSV from the same supplier, Seegea automatically applies the previous mapping and only flags new columns or anomalous values.
Built in France between Annecy and Chantilly, Seegea makes CSV mapping accessible to the whole team — not just developers.
Test Seegea visual mapping on a live call
Send your supplier CSV — we do the mapping live
