Formatting First Columns on your Spreadsheet

It is important to understand how Ablestar Bulk Product Editor handles formatting on spreadsheets and the first column identifier.

1. General Format

The spreadsheet should have a header row and at least two columns, but you can include as many as you need. You have two options to specify the first column identifier:

• Spreadsheet first column: The system will recognize if you place a variant or product-level in the first column position and treat it as the identifier
• Advanced Options: Clicking 'Advanced options' during your spreadsheet upload can allow you to tell the system which column to use, in case they are out of order.

The identifier field will be used to locate products or variants to edit, with the remaining action columns dictating which data to modify.

Learn more about CSV or Excel file formats in this related article

2. Identifier Column

There are two types of data types to consider when prepping your spreadsheet. The type of data you are editing will dictate which first column "identifier" should be present:

• Variant-Level fields: When editing Variant-level fields like 'price' or 'barcode', you can use one of these identifiers:
• SKU
• Variant ID
• Barcode
• Product-Level fields: When editing Product-level fields like 'tags' or 'descriptions' or 'type', you can use any of these identifiers:
• Barcode
• URL handle
• Product ID
• Product Title
• SKU
• Variant ID

For example, if you wanted to edit the price and inventory levels based on SKUs, you would use a Variant-level match field because 'Inventory' is a Variant-level data type. Your spreadsheet might look similar to this, with SKU being the Variant-level identifier:

Once you upload your spreadsheet, from the mapped column view, click 'Advanced settings' to specify the exact identifier column:

The app will then determine whether it should update at a product or variant level.

Learn more about CSV or Excel file formats in this related article

✅ Tips and Troubleshooting

• If you upload a CSV file and receive an error, try saving it as an Excel spreadsheet and upload it again.
• See more Variant-Level data examples
• See more Product-Level data examples

(03.24)