How to Create a Magento 2 Product Import CSV

Prerequisites and version scope

These steps apply to current Magento Open Source 2.x and Adobe Commerce Admin workflows. Before a significant import, take an appropriate backup or use a safe staging environment, confirm the target attribute set and attribute codes already exist, and save the CSV as UTF-8.

In Admin, go to System > Data Transfer > Import, choose Products as the entity type, and use Download Sample File as the header reference for the installed version.

Start with the smallest safe CSV

For an existing product update, omit columns you do not intend to change. A minimal price-and-name update can look like:
sku,name,price
TSHIRT-BLUE,Blue T-Shirt,29.00

For a new simple product, the installation's sample file is the safer template because required attributes vary. A typical starting shape is:
sku,attribute_set_code,product_type,name,price,product_online
TSHIRT-BLUE,Default,simple,Blue T-Shirt,29.00,1

Map fields deliberately

Keep sku stable because Magento uses it to identify the product being updated. Match CSV headers to Magento attribute codes rather than storefront labels. Do not assume a blank cell and an omitted column are equivalent for every attribute or import behavior; test a small file first and omit fields that are not meant to change.

• Use existing attribute codes and the intended attribute set.
• Use store-view rows only when a store-scoped value is intentionally different.
• Treat category paths, websites, images and multi-value attributes as installation-specific mapping work.
• For configurable products, validate the child simple SKUs and configurable-variation fields against an export or sample from the same Magento version before bulk import.

Choose import behavior with care

For routine catalog changes, Add/Update is usually the appropriate behavior. Replace and Delete can be destructive and should only be used when that outcome is intentional and has been tested. Magento shows the available behavior in the Import screen.

Validate before importing

Upload the CSV, configure separators to match the file, and run Check Data before importing. Resolve structural or attribute errors first; then import a small batch and verify the expected product fields, storefront state, categories, website assignment and images before scaling up.

• Unknown attribute code: confirm the CSV header and target attribute set.
• Duplicate or missing SKU: correct the identifier before import.
• Invalid option value: create or map the allowed attribute option instead of inventing a label in the CSV.
• Unexpected field clearing: compare the source export and test how blank values behave for that attribute/import behavior.
• Configurable relationship errors: verify child SKUs and configurable attributes before retrying the parent row.

Expected result and rollback mindset

A successful import finishes without validation errors and changes only the fields and products intended by the file. Keep the source CSV, the pre-change export or backup, and the import result so unexpected catalog changes can be investigated rather than repeated blindly.

• Adobe Commerce: Import data
• Magento support services