If I have a pricing file that contains short descriptions of my products, its SKU, and its current price, I should not have to select a name for the field during a CSV import. I can understand that during a create action, a name is required. However, couldn't the import process skip those or throw a warning for a missing name instead?

Hello,

The import supports both creating new products and updating existing products from the same file. Therefore, the CSV structure requires a Name column.

However, couldn't the import process skip those or throw a warning for a missing name instead? If I supply update in the action column, it could skip the name field entirely.

Quote from: Basara on September 22, 2026, 10:51:41 AMHello,

The import supports both creating new products and updating existing products from the same file. Therefore, the CSV structure requires a Name column.

Thanks for the clarification. I have one question about how AbanteCart handles the import when the same CSV file is used to both create new products and update existing ones. How does AbanteCart determine whether a product already exists and should be updated, or whether it is a new product that needs to be created? For example, if the CSV contains a Name column, is the product name used to match an existing product? If so, what happens if two products have the same name? Or should we use another field, such as the Product ID or SKU, to identify existing products? It would be helpful if you could provide an example of the correct CSV structure for both creating new products and updating existing products.