Identifier Column for Variant-Level Spreadsheet

It's important to understand how Ablestar Bulk Product Editor handles the first column identifier on spreadsheet edits for Variants.

When you export or import any store data, we want to make sure we can easily identify if you are trying to update all products or all variants or both.

Importing and exporting spreadsheets is simple if you keep in mind the Variant and Product-level identifiers:

1. Exports

The export function gives you several format options to choose from:

Each dropdown option is considered either product-level or variant-level (and sometimes both):

  • Barcode: product level
  • Product Handle: product level
  • Product ID: product level
  • Product Title: product level
  • SKU: Both variant and product-level (as long as each SKU is unique)
  • Variant ID: variant level only

When you choose a 'Variant ID' export, we configure the first-column identifier to be the 'Variant ID' as:

This layout will also make it easier for you to re-import your changes and spreadsheet once finished.

2. Imports

Subsequently, when you are bulk editing any variant detail, you want to make sure that the first-column identifier is always one of two options:

  • Variant ID
  • SKU (only if SKU is unique)

This format ensures that each variant will be updated accurately. If you were to use a Product-level identifier, you might unintentionally update all your variant data with the same info.

If you are unsure of the Variant ID for your products, try exporting a copy of your store data and looking for the 'Variant ID' column in the spreadsheet.

3. Special Cases

There could be times when you want to update all products and product variants to the same value. In the example of changing all price (variant) fields to $19.99 you could use a product-level import as:

Product Handle Price
my-product-1 19.99
my-product-2 19.99

✅ Tips and Troubleshooting


(05.271)

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us