Product CSV import
Last updated
Last updated
Copyright Chainbox 2008-2023
Please read! Best practise for CSV import:
Before importing and changing large amounts of product data, create and save an export as backup
Only include relevant columns and rows that are actually changed, or vital for import (unique identifyer) - exclude columns from import that hasn't been changed.
Also ways check the number of products changed with how many you intended to change, so avoid errors.
Note that exported files are in parsing culture US, so if your export contains decimals and dates, make sure the import parsing culture matches.
CSV-format for product import MUST be format CSV UTF-8 (semicolon separated)
Importing product by CSV-file into PIM are for two main reasons:
Creating new products in PIM not existing in the ERP-system
Enriching existing products in PIM with data fields not mapped to the ERP-system.
Please note, the product ID is a unique identifier - this means you cannot change existing product ID's - either manually nor through import. You can create new ones (manually or by CSV-import) and you can delete existing product ID's (manually). But not change the product ID itself.
Images and files cannot be uploaded through CSV import
Consider if Channels and Categories are easier maintained through bulk-update on product view.
Ensure that empty fields are indeed empty and not containing non-visible char2 characters.
Preparing the file, if you erase rows in the file, ensure you delete the rows instead of deleting just the content of the rows.
Fields mapped to ERP are maintained in the ERP-system only.
Easiest way to ensure the file-format is correct (UFT-8) and that a mapping happens automatically upon import, is to export a product with the exact same fields that you wish to import. Remember the product ID be included in the import file.
If the purpose for the import is to alter fields on existing Product ID's, it is recommended to export the existing product ID's with relevant fields - save as CSV UTF-8 - change the data and import. However, any CSV UFT-8-file with any headlines can be used. Mapping just needs to be done upon import.
Export relevant products from PIM, to have correct column headlines, or create your own file - in both cases the format must be CSV UTF-8 and Product ID/sku must be part of the file:
Do the changes necessary (marked in yellow) and save file as CSV UTF-8:
Go to Import/export - Product CSV Import - Upload file. Drag and drop your import file in the marked area. Choose type of delimiter if different that semicolon (mostly relevant if you have created your own file). Click Upload.
Unclick fields in column "Include" of not changed in file. Ensure mapping is correct/do mapping. Set delimiter for fields with more than one value (e.g. multiple tags or multiple related items) and mark if any fields empty should action a deletion of current PIM data. Last mark if creations of products are allowed only - or updates only. This helps to ensure that a misspelled product ID/sku doesn't result in a creation of a new product. Click "Import" when ready.
Ensure the below import details - number of products changes, and sample data - matches the expectations before clicking "Confirm import". If not click "Close" and check the file and import-markings again.
