Catalog Precheck
BigCommerce CSV guidance

BigCommerce Product CSV Template Guide

Start from a fresh export of the destination store, then map your source data to those exact columns before importing.
There is no permanent universal store template
Columns and accepted values can vary with export settings and platform changes. This page explains a workflow; it does not provide a forever-valid downloadable template.

Use the destination store as the baseline

Export a small current product set, preserve its headers and row structure, and document every source-to-destination field mapping. BigCommerce's Catalog API migration reference marks Name, Type, Weight, and Price as required for product creation; that API mapping is not a required-header list for your CSV importer.

Illustrative product field subset

This synthetic subset uses headers and uppercase boolean syntax observed in the public modern-format sample linked below. It omits other fields, including Weight, and is not an import-ready template. Keep the complete headers from your own export.

Item,ID,Name,Type,SKU,Price,Inventory Tracking,Current Stock,Is Visible
Product,,Synthetic Tee,physical,TEE,29.00,product,12,TRUE

Check before importing

Confirm UTF-8 encoding, required values, numeric and boolean syntax, unique SKUs, categories, images, custom fields, and the relationship between Product and Variant rows. Test a representative subset first.

Compare the template with your planned import

The validator uses a destination-store export as the baseline and keeps both CSV files in the browser.
Open BigCommerce CSV ValidatorReview import errors

Official BigCommerce guidance checked 1 October 2026.

Source: BigCommerce documentation

CSV shape reference: third-party public sample, not an official store export