CSV File Format for Importing Product Data to B2B Stores

The name of a field on the Product2 object. FieldName is the api name of the field. You can use any updateable field on the Product2 object, including a custom field, as a column heading. You can specify as many fields as you want. The import process supports fields with data type checkbox, currency, date, date/time, email, number, percent, phone, picklist, picklist (multiselect), text, text area, text area (long), text area (rich), time, url, or string. The data format in this column depends on the field data type.

• Checkbox—Allowed values are true or false.
• Date, date/time—Values are locale-specific. See Supported Date and Time Formats (ICU).
• Picklist—Use the picklist value.
• Picklist (Multiselect)—Use the picklist values separated by a semi-colon (;).

For formatting guidelines for the other supported data types, see Custom Field Types.

The product’s stock-keeping unit (SKU) number. SKU is one of the four columns that uniquely identify a product. ProductCode, Product Id, and Product ExternalId are the others. At least one of the four is required in your import file. The SKU column name is equivalent to the Product StockKeepingUnit column name. There’s no difference between them functionally, but SKU has fewer characters to enter. This column corresponds to the Product2.StockKeepingUnit field. You can’t update the product SKU using the import file.p

The SKU field is required for several commerce features, such as cart and checkout, and for importing product image references into Salesforce CMS. If you’re creating products, make sure that your import file specifies the SKU. If you’re updating products, the SKU is optional as long as you uniquely identify the product.

(Optional) The SEO-friendly URL slug for the product in a specified language. Use a separate column for each language you want to specify a slug for.

• For language code, specify a Salesforce-supported language code. For example, Slug en_US. For a slug to be used in a store, the language must be available in the org and in that store.

• Use of the term Product2 isn’t allowed in a URL slug. This URL is reserved for use in your site.

URL slugs have a character limit of 150 and allow these characters: a-z A-Z 0-9 . - _ $ & : ; * , = @. Foreign language characters are also allowed.

(Optional) URL to the media to use as the listing image for the product. If you’re updating information about the listing media, include the URL, even if you don’t want to change it, because the URL uniquely identifies the media. If you’re updating existing listing media, the fields that you omit default to the values for the existing listing media. If you’re using the enhanced CMS, the URL must use the HTTPS protocol. If you import new media for a product, the import creates an image in the CMS workspace. This process can result in having multiple copies of the same image in the workspace.

Note You can't add videos while importing products. If you include a video URL, it is added as an image during the import process.

Important When you publish content in a CMS workspace, it’s shared to all channels in the workspace, including the public channel. Your content doesn’t have restricted access.

(Optional) You can have up to eight columns that contain the URLs to media associated with the product, labeled Media Standard 1, Media Standard 2, and so on. If you’re updating information about the standard media, include the URL, even if you don’t want to change it, because the URL uniquely identifies the standard media. If you’re updating existing media, the fields that you omit default to the values for the existing media. If you’re using the enhanced CMS, the URL must use the HTTPS protocol. If you import new media for a product, the import creates a new image in the CMS workspace. This process can result in having multiple copies of the same image in the workspace.

When you publish content in a CMS workspace, it’s shared to all channels in the workspace, including the public channel. Your content doesn’t have restricted access.

The product’s unique Product Code. ProductCode is one of four columns that uniquely identify a product. SKU, Product Id, and Product ExternalId are the others. At least one of the four is required in your import file. This column corresponds to the Product2.ProductCode field. If you identify an existing product using a SKU column, you can update the Product Code to a new value that you specify in this column.

The ProductCode field doesn’t enforce a unique constraint. If you use this column to identify products, it’s possible that duplicate records will be created or if there are already records with duplicate values, any one of the records will be updated.

The product’s External ID. Product ExternalId is one of four columns that uniquely identify a product. SKU, Product Id, and ProductCode are the others. At least one of the four is required in your import file. This column corresponds to the Product2.ExternalId field. If you identify an existing product using either a SKU or a ProductCode column, you can update the External ID to a new value that you specify in this column.

The Product ExternalId field doesn’t enforce a unique constraint. If you use this column to identify products, it’s possible that duplicate records will be created or if there are already records with duplicate values, any one of the records will be updated.

(Optional) You can have up to five category columns, labeled Category 1, Category 2, and so on. You can’t update existing categories for a product. You can only add new categories.

For the first category, you can use the label Category without the number 1. In a category column, you can specify a nested category, using the / character to separate the levels. For example, Products/Machines/Espresso.

(Optional) The name of an entitlement policy to associate with the product. You can specify up to 50 entitlement policies in columns labeled Entitlement 1, Entitlement 2, and so on. You can’t update existing entitlement policies for a product. You can only add new entitlement policies. Create the entitlement policies before you import the CSV file. For more information, see Create an Entitlement Policy.

For the first entitlement policy, you can use the label Entitlement without the number 1.

To specify prices, use a column labeled Price, followed by optional values. The import process determines where to add the prices based on the values, if any, that you include in the column label.

• Price or Price <currency code>—When you use Price as the column label, or Price followed by a currency code, you’re asked which price book to use during the import process. The prices in all columns without an alias are added to the same price book. If a currency code isn’t specified, the default is the currency code for the user who’s running the import.
• Price (alias) or Price (alias) currency code—You can use any alias you want to describe a price book. For each alias, you’re asked which price book to use during the import process. The prices in all columns using the same alias are added to the same price book. If a currency code isn’t specified, the default is the currency code for the user who’s running the import.
• Price price book ID or Price price book ID currency code—The system adds the prices to the price book with the specified ID. If a currency code isn’t specified, the default is the currency code for the user who’s running the import.

The parent product for the variation. In the column heading, include an identifier to indicate the value that you’re using to identify the parent. Valid column headings are:

• Variation Parent (Id)—Use Product ID.
• Variation Parent (StockKeepingUnit)—Use SKU.
• Variation Parent (ProductCode)—Use Product Code.
• Variation Parent (ExternalId)—Use External ID to identify variation parent.

The parent product must exist or be specified in the CSV file before the variations are created.