Disclaimer: We recently redesigned our Admin Area. Your store may look different than the one shown in this video, but most click paths were not affected.

<< PREVIOUS                                                                                                        NEXT >>

Transcript

In this video, we'll cover how to read, modify, and prepare for import the CSV file we exported in the video called "How to Export Store Data". We'll begin by accessing the file in Microsoft Excel.

Because we chose to export all columns, the spreadsheet is extremely wide. Each column corresponds to a check box on the Export page. If you'd like to add new products, simply add new rows to this spreadsheet.

It's not necessary to input data in all or even most of these fields. Just as if you were adding an individual product through the Admin Area, it's only necessary to enter the required fields. You can of course fill out as many additional columns as you like, but you can leave the others blank or even delete them. In the case of adding new products, you may want to fill out all other important fields, like category IDs, which is vital for displaying a product on your storefront.

If you're modifying existing items rather than adding new ones, your spreadsheet may not look like this. As we discussed in the video called "How to Export Store Data", an export file created for that purpose needs only the value or values you'd like to modify, plus the unique identifier. But you can also modify your data on a large spreadsheet like this.

If you're trying to import a product list from another system, you'll have to make sure to rename every column to a valid column name found on the Export page. If a column's data doesn't fit into any of the Admin Area section’s values, you can remove it from the spreadsheet before you import. Or, if you don't know where to map the data in your Admin Area but you'd like to save it there anyway, you can map it to a custom field.

If the spreadsheet is missing any required columns, you can create them before importing. The left-to-right sequencing of the columns is irrelevant.

Finally, a column with system-specific data, like category ID, which refers to values in a third-party system, is highly unlikely to match category ID settings in Volusion. So delete information of this nature, or map it to a custom field, instead of mapping it to Volusion's corresponding value.

Once you're through editing, be sure to save the updated file locally. If you see this popup message, click Yes. The file is now ready for import.

Did this answer your question?