BigCommerce CSV guidance

BigCommerce Variant CSV Format

Keep each Variant row with its Product parent, use consistent option names, and make each option combination unique.
Official BigCommerce guidance checked 1 October 2026.

Preserve the product group

Place the Product row before its Variant and Image rows. Keep all rows for one product together so option and image data cannot drift to another group.

Illustrative product and variant rows

This synthetic subset demonstrates the Options format observed in the linked public sample and supported by the current checker. Each option has Type, Name and Value fields separated by vertical bars; join options directly, with the next Type= starting a new option. Other dialects are not inferred from the baseline. Copy the complete header set from a fresh destination-store export.

Item,ID,Name,Type,SKU,Options,Price
Product,,Synthetic Tee,physical,TEE,,29.00
Variant,,,,TEE-BLUE-S,Type=Dropdown|Name=Color|Value=BlueType=Dropdown|Name=Size|Value=Small,
Variant,,,,TEE-BLUE-M,Type=Dropdown|Name=Color|Value=BlueType=Dropdown|Name=Size|Value=Medium,

Review identity and option risks

Duplicate option combinations, inconsistent option names, orphan variants, and repeated SKUs require manual correction. Do not generate or overwrite variant identity values automatically.

Check variants against the store baseline

Run the local precheck before a limited test import, then verify option display, SKU mapping, visibility, price, and inventory in the control panel and storefront.

Source: BigCommerce documentation

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