Product Catalog CSV Files

How to Read Your Exported CSV File

The column headers contain your products' attributes. The header format depends on the type of attribute.

• A standard attribute contains only the name of the attribute.
• A custom attribute begins with c__, for example, c__fabric.
• A site-specific attribute ends with __siteID, for example, fragrance__globalsite.
• A localized attribute ends with __locale, for example color__en.

When the export processes a cell with multiple values, you sometimes see punctuation that didn't exist on your site. The import process translates these characters back to their original value when you import. For this reason, make sure that when you add new applicable values, you're adding any necessary punctuation.

• Our CSV files use semicolons to delineate multiple values in a cell. When a value contains a semicolon, a backslash is added in front of the semicolon. For example, a typical cell with variation products "a", "b", and "c" shows "a;b;c". If the product has the values "a;1", "a;2", and "a;3", the values in the cell are "a\;1;a\;2;a\;3"
• When a value in a multi-value cell contains a backslash, another backlash is added. For example, a cell with the variation product values "a\1", "a\2", and "a\3", show as "a\\1;a\\2;a\\3"

Microsoft Excel changes the formats of certain values. Excel removes leading zeros in cells, which can cause certain values, such as product IDs, that start with a zero to show incorrectly. It also saves certain long numeric values in scientific notation. Keep these in mind when importing your CSV after opening it in Excel.

To protect your site from injection attacks, a zero width joiner (ZWJ) is inserted in front of any value that begins with =, +, -, or @. A ZWJ is invisible and is removed from your file when you import it.

Preparing Your CSV for Import

Keep in mind the following to prepare your file for import.

To make sure your CSV file fits the standards for importing, export a catalog first and modify it with your changes. You can create a new CSV file but this isn’t a best practice.

A CSV file can only update a catalog. The import process can't create a new catalog from a CSV file. Select which catalog you want to update during the import process.

Business Manager only accepts a CSV file in UTF-8 format. All CSVs downloaded from Business Manager are automatically exported in UTF-8 format, so if you don't change the file type, you're all set!

Attributes are case-sensitive, so make sure all your cases match if you edit any attribute IDs.

Empty cells are ignored during the import process. If you export a catalog and delete the value in a cell and import the catalog, that cell retains its original value. The import process doesn't replace the value with a null value.

Make sure all your attributes are valid before beginning the import process. Any site-specific or localizable attributes without suffixes as defined previously are skipped during the import process. Non-site-speific or non-localizable attributes with suffixes are also skipped. After the import process completes, you are shown the logs with all invalid attributes. If you don't see all your attributes in your newly imported catalog, check the logs.

You can only import a CSV in MERGE mode and must specify which catalog you are importing before starting the process.

CSV Limitations

The CSV process supports any system or custom attribute that is available in System Object Types > Product and supported by the XML catalog schema. Additionally, the process supports a few additional elements, to allow references to main variation products, variation groups, and products included in a product set. Elements deprecated in XML aren’t supported.

Elements not supported by the CSV process

• Bundled-products
• Category-assignment
• Classification-category
• Images and all child elements
• Options
• Product-detail-page-meta-tag-rules and all child elements
• Product-links
• Variations > attributes
• Variations > attribute values