Import Product Variants Tool for BigCommerce
🔧 Quick Info: Import Product Variants updates existing BigCommerce product variants from a CSV or Excel spreadsheet. Each row is matched using the Variant SKU, and only the fields you map are changed.
What It Does
Import Product Variants updates existing product variants in your BigCommerce store from a spreadsheet.
You upload a CSV or Excel file, match its columns to the available variant fields, and the tool uses each row’s Variant SKU to find the correct variant in BigCommerce.
You can update variant prices, inventory, dimensions, weights, identifiers, images, purchasing status, shipping costs, and other supported fields.
Updates Existing Variants Only: Import Product Variants does not create new variants. If a Variant SKU in your file does not match an existing variant, the row is skipped and added to the error file.
Only the fields you include and map are updated. Fields that are not included in your file remain unchanged in BigCommerce.
The import runs as a background job, so you can close the page after starting it. When the import is complete, you’ll receive an email notification. If any rows could not be processed, the email includes access to a downloadable error file.
When Should You Use This?
- You want to update prices for many product variants at once.
- You need to refresh variant stock levels or low-stock warning levels.
- You want to update variant weights, widths, heights, or depths in bulk.
- You need to update identifiers such as UPC, MPN, GTIN, or Bin Picking Number.
- You want to assign or change variant image URLs.
- You prefer editing a spreadsheet instead of updating variants individually in BigCommerce.
- You exported your variant data, edited it, and want to import the changes back into your store.
Before You Get Started
- Make sure every variant you want to update already exists in BigCommerce.
- Prepare a CSV or Excel spreadsheet.
- Make sure the first row contains your column names or headers.
- Include a Variant SKU column. This field is required and is used to match each row to an existing variant.
- Confirm that every Variant SKU exactly matches the value stored in BigCommerce.
- Decide which variant fields you want to update.
- Confirm that you are working with the correct connected store.
Only Mapped Fields Change: You do not need to include every supported column. Any field that is not included or mapped remains unchanged in BigCommerce.
How to Use It
1 Open the Tool
Open the Import Product Variants tool from your BigCommerce tools dashboard.
2 Review the File Requirements
On the Upload Variants step, review the on-screen requirements. The first row of your file must contain column headers, and the file must include a Variant SKU column.
3 Upload the Variant File
Upload your CSV or Excel spreadsheet. The tool reads the first row to identify the available columns.
4 Match the Columns
After the file is uploaded, the column-matching section appears. Match each spreadsheet column to the corresponding BigCommerce variant field.
At minimum, map the column containing your variant SKUs to Variant SKU.
Only mapped fields are updated, so review the selections carefully before continuing.
5 Confirm Email Delivery
Continue to the Email step and confirm the address where the completion notice should be sent.
6 Start the Import
Start the import. A confirmation appears to let you know the process has begun.
The import runs as a background job, so you can close the page while it processes.
7 Review the Results
When the import is complete, check your email for the completion notice.
If any rows could not be processed, download the error file, review the reported problems, correct the rows, and import them again.
How Variants Are Matched
Each row is matched to an existing BigCommerce variant using the value in the Variant SKU column.
| Variant SKU Result | What Happens |
|---|---|
| Matches an existing variant | The mapped fields are updated on that variant. |
| Does not match an existing variant | The row is skipped and reported as Variant not found in the error file. |
| Blank or missing | The row cannot be matched and is not processed. |
Exact Match Required: Variant SKUs must match the values stored in BigCommerce. Check for extra spaces, spelling differences, or confusion between a parent product SKU and a Variant SKU.
File and Field Reference
The first row of your spreadsheet must contain headers. After uploading the file, map your columns to the fields below.
| Column | Required? | Notes |
|---|---|---|
| Variant SKU | Yes | Used to find the existing variant. It must match a Variant SKU already stored in your BigCommerce store. |
| SKU | No | The SKU of the parent product. This can help identify the product containing the variant. |
| Price | No | The variant’s regular price. Use a numeric value. |
| Sale Price | No | The variant’s sale price. Use a numeric value. |
| Retail Price | No | The variant’s retail or manufacturer’s suggested price. Use a numeric value. |
| Fixed Cost Shipping Price | No | The fixed shipping charge assigned to the variant. Use a numeric value. |
| Cost Price | No | The internal cost assigned to the variant. Use a numeric value. |
| Weight | No | The weight assigned to the variant. Use a numeric value. |
| Width | No | The variant’s width. Use a numeric value. |
| Height | No | The variant’s height. Use a numeric value. |
| Depth | No | The variant’s depth. Use a numeric value. |
| Purchasable | No | Controls whether the variant can be purchased. Use a true or false value. |
| Image URL | No | The complete web address of the image assigned to the variant. |
| UPC | No | The Universal Product Code assigned to the variant. Supports up to 32 characters. |
| MPN | No | The manufacturer’s part number assigned to the variant. |
| GTIN | No | The Global Trade Item Number assigned to the variant. |
| Stock | No | The variant’s inventory level. Use a numeric value. |
| Low Stock | No | The inventory warning level assigned to the variant. Use a numeric value. |
| Bin Picking Number | No | The warehouse bin or picking reference assigned to the variant. |
Troubleshooting and FAQ
My import didn’t change anything or rows were skipped
Each row is matched using Variant SKU. If the value does not match an existing variant, the row is skipped and reported as Variant not found in the error file.
Confirm that you used the Variant SKU rather than the parent product SKU and check for extra spaces or typing errors.
The tool cannot read my columns
Make sure the first row of your spreadsheet contains the column names and that the file includes a Variant SKU column. Correct the header row and upload the file again.
Can I create new variants with this tool?
No. Import Product Variants only updates variants that already exist in BigCommerce. A row with an unknown Variant SKU is reported as an error instead of creating a new variant.
Fields I left out were not changed
This is expected. Only columns included in your file and mapped during the upload are updated. All other variant values remain unchanged.
Where do the results go?
The changes are written directly to your BigCommerce store. When the background job is complete, you’ll receive an email notification. Any rows that could not be processed are included in a downloadable error file.