Error and Warning Codes

This page documents error and warning codes you may encounter when using Ablestar Bulk Product Editor. Each code includes a short description and suggested next steps.

Metafield Errors (MTF)

MTF001 - Value Not In Allowed Choices

The metafield that you are trying to edit only lets you select from a limited set of values. The validations are configured in the Shopify admin.

How to fix

You can either change the value to one of the allowed choices, or update the validation in the Shopify admin.

MTF002 - Value Length Constraint

The definition for the metafield that you are trying to edit has a length constraint and the value you are trying to set is either too short or too long.

How to fix

There are two ways to fix this:

• Verify that the value you are trying to set is within the length constraints.
• Update the metafield definition's validations in the Shopify admin.

MTF003 - Duplicate Values Not Allowed

Metafields that are a list of values cannot contain duplicate values.

How to fix

Filter your products to exclude products with the duplicate value before editing.

MTF004 - Blank Values Not Allowed

The metafield value is blank when a value is required. This may occur if you are trying to set a list metafield and one of the elements in that list is blank.

How to fix

Provide a non-blank value. Check for formatting issues (e.g., trailing commas in lists).

MTF005 - Definition Constraint Mismatch

The metafield definition is configured to only show on products in certain categories and the product you are trying to edit is not in one of those categories.

How to fix

Either change the product's category first to match the definition's constraints or relax the constraints in Shopify admin.

MTF006 - Metaobject Not Found

The metaobject referenced by handle or title could not be found in the store.

How to fix

Verify the metaobject handle or title is correct, or refresh metaobjects data in Settings → Shopify Data and retry.

MTF007 - Metafield Definition Not Found

The metafield definition could not be found for the specified field.

How to fix

Verify the metafield definition exists and is accessible, or refresh metafield definitions in Settings → Shopify Data and retry.

MTF008 - Rich Text Metafield Format Error

The rich text metafield value you are trying to set is not in the correct JSON format. Rich text metafields require a specific JSON structure that describes the formatting and content.

This error can occur when:

• The JSON format for the rich text content is incorrect
• The HTML to JSON conversion process encountered an issue

How to fix

If you are providing rich text data in JSON format:

• Verify that your JSON follows the correct rich text metafield schema

If you are converting from HTML or other formats:

• Contact support for assistance with the conversion process
• Provide the original HTML that you are trying to convert

MTF009 - Invalid JSON In List Metafield

The value you provided for a list metafield looks like a JSON array (it starts with [ and ends with ]) but it contains invalid JSON that could not be parsed.

How to fix

Make sure the value is a valid JSON array. For example:

• ["Red", "Blue", "Green"] for a list of text values
• [1, 2, 3] for a list of numbers

Common issues include:

• Missing quotes around text values (e.g., [Red, Blue] instead of ["Red", "Blue"])
• Missing commas between values
• Unmatched brackets
• Backslash characters (\) in values that are not valid JSON escape sequences (e.g., ["Small\ Medium"]). Either remove the backslashes or escape them by doubling them (["Small\\ Medium"])

If you don't want to use JSON formatting, you can also separate list values with commas, pipes (|), or newlines instead.

MTF010 - Metaobject Reference Wrong Definition

The metafield you are editing is a metaobject reference, and the metaobject you are pointing at belongs to a different metaobject definition than the field expects. For example, a "Color" metafield that only accepts colors won't accept a reference to a "Material" metaobject.

How to fix

Pick a metaobject that belongs to the definition the metafield was set up to reference. You can see the expected definition in the Shopify admin under Settings → Custom data → the metafield's definition.

MTF011 - Value Outside Numeric Range

The metafield definition has a numeric minimum or maximum and the value you are trying to set falls outside that range. This is distinct from MTF002 which is about text length.

How to fix

Use a value inside the allowed range, or update the minimum/maximum in the metafield definition in the Shopify admin.

MTF012 - Value Format Invalid

The metafield value did not match the format the definition requires. This shows up on fields with a pattern-type validation (for example ISBN, MPN, or a regex) as well as single-line text and date fields where the input did not match the required shape.

How to fix

Check the metafield definition in the Shopify admin to see what format is required. Make sure dates use YYYY-MM-DD, single-line text fields don't contain line breaks, and any regex or pattern validations are satisfied.

MTF013 - Invalid Reference

The metafield is a reference type (product, collection, file, or similar) and the value you provided either does not point at an existing resource or does not match the expected type.

This error covers several Shopify messages:

• Value must be a valid product reference.
• Value must be a valid collection reference.
• Value must be a file reference string.
• Value must be one of the following file types: Image.
• Value references non-existent resource gid://...

How to fix

• Verify that the referenced product, collection, or file still exists in the store.
• If you are using a handle or title, refresh the relevant data in Settings → Shopify Data.
• For file references, make sure the file matches the allowed type (for example, an image field won't accept a PDF).

MTF014 - Metafield Owner Does Not Exist

Shopify reported that the product the metafield is being set on no longer exists. This usually means the product was deleted between the time Ablestar loaded it and the time the edit ran.

How to fix

Refresh your product data in Settings → Shopify Data and re-run the edit. If the product was deleted intentionally you can ignore the error.

MTF015 - Metafield Linked To Option

Some Shopify metafields (for example shopify.color-pattern) are linked to a product option. When a metafield is linked to an option, you cannot edit it directly — the value is driven by the option instead.

How to fix

Edit the option on the product (for example the "Color" option) rather than the metafield. If you want the metafield to be editable independently, unlink it from the option in the Shopify admin.

MTF016 - Metafield Value Must Be Unique

The metafield definition has a uniqueness constraint and the value you are trying to set is already in use on another product.

How to fix

Use a different value, or update the other product that currently holds the value first.

MTF017 - Multiple Values For Single File Reference

A single file_reference metafield holds exactly one file, but the value you provided contains multiple files (a JSON array, or a comma-, pipe-, or newline-delimited list).

How to fix

Provide a single file (one URL, filename, or GID) for a file reference column. To set multiple files, map the column to a list.file_reference metafield instead.

MTF018 - Too Many Values In List

The metafield is a list, and its definition sets a maximum number of values. The edit would put more values in the list than the definition allows, for example "Value of list has a maximum size of 5."

How to fix

• Remove values from the list so that it has no more than the maximum.
• Or increase the maximum in the metafield definition's validations in the Shopify admin.

MTF000 - Generic Metafield Error

A metafield-related error occurred when communicating with the Shopify API.

How to fix

Read the error message in the edit log for details. If you need help, contact support with the edit link.

Product Errors (PRD)

PRD001 - Product Handle Already In Use

The product's new handle is already used by another product in the store.

How to fix

For an in-app edit, select the 'Make sure handle is unique' checkbox. The app then adds a number to the end of each handle that is not unique. For a spreadsheet import, change the handle in the file to one that no other product uses.

PRD002 - Product Does Not Have An Option

Attempted to edit option 2 or 3, but the product does not have that option. For example, if the product has only one option, Size, you cannot edit the option 2 value or name.

How to fix

For an in-app edit, add a filter for the option 2 or option 3 name to be sure that you are editing products with those options.

PRD003 - Invalid Product Status

The product status value is invalid. Status must be one of the allowed values: draft, active, archived or unlisted.

How to fix

Use one of the valid status values: draft, active, archived or unlisted.

PRD004 - Invalid Image URL

When you add an image to a product the app sends the image's URL to Shopify and then Shopify tries to download the image. This error message means that Shopify was unable to download an image from the provided URL.

There are a few reasons that Shopify could be unable to download an image:

• There is a typo in the URL or it is not valid. URLs should start with http:// or https://
• The URL is invalid or points to a page that is not an image file.
• The URL requires you to be logged in to a site to view it. When Shopify requests the URL it is not logged in so will not be able to see the file
• The site hosting the images has code in place to prevent automatic access to image URLs. This is usually done to block bots or scrapers but will also interfere with the automated requests from Shopify

How to fix

There are several things you can do to check the image URLs:

• Make sure that the image URL works on your computer in a private browsing window
• Make sure that the URL points directly to the image, and not to an HTML page containing the image

If you are able to view the images correctly but they still are not uploading, it's likely that the remote webserver is blocking automated requests for the images. Please contact us and we will see what we can do.

PRD005 - Tag Limit Exceeded

Shopify limits the number of tags a single product can have (currently 250). The edit would have pushed the product past that limit.

How to fix

• Remove some existing tags before adding new ones.
• If you are using "Add tags" in bulk, filter to products that have room for more tags first.

PRD006 - Product Suspended

The product has been suspended by Shopify (usually for a policy, fraud, or payments reason). Suspended products cannot be edited through the API until the suspension is resolved.

How to fix

Open the product in the Shopify admin — you should see a notice explaining the suspension. Resolve the underlying issue with Shopify and then retry the edit.

PRD007 - Deprecated Category

The product references a category in Shopify's product taxonomy that has been deprecated. Shopify periodically removes old categories when the taxonomy is updated.

How to fix

Refresh the product taxonomy data in Settings → Shopify Data, then pick a current category for the product.

PRD008 - Title Required

You tried to save a product with a blank title. Shopify requires every product to have a title.

How to fix

Provide a non-blank title for the product.

PRD009 - Media IDs Do Not Exist

The edit referenced media or file IDs that Shopify doesn't recognize. This usually happens if the media was deleted between the time Ablestar loaded the product and the time the edit ran, or if you're importing a spreadsheet that has media IDs from a different store.

How to fix

• Refresh the product data in Settings → Shopify Data and re-run the edit.
• If you are importing from a spreadsheet, make sure the media IDs come from the same store.

PRD010 - Too Many File References

The image file already has the maximum number of product references allowed by Shopify, for example "Cannot add more than 50 references to a file." This can happen when you add the same image to many products, or set it as a variant image on many products.

How to fix

Use a different image for these products, or remove an existing product reference from the file in the Shopify admin before re-running the edit. To use the same picture on more products, upload it again as a separate file.

PRD011 - Invalid Tags

Shopify did not accept the product's tags ("Product tags is invalid"). Shopify does not say which tag is the problem. One possible cause is a tag that is longer than 255 characters, for example when the tags in a spreadsheet cell use a separator other than commas.

How to fix

• Make sure the tags in the cell are separated by commas.
• Make each tag shorter than 255 characters.
• If the error continues, contact support with the edit link.

PRD000 - Generic Product Error

A product-related error occurred with the Shopify API.

How to fix

Read the error message in the edit log for details. If you need help, contact support with the edit link.

Image and Media Errors (IMG)

IMG001 - Shopify Could Not Process The Image

When you add an image or video by URL, the app sends the URL to Shopify and Shopify downloads the file. This error names the image that failed and means Shopify tried the download and marked the file as failed, so it can't be added to the product. The causes are the same ones behind PRD004: the URL doesn't point directly at a file, the file has been removed, it needs a login to view, or the host blocks automated requests.

How to fix

• Open the URL in a private browsing window to confirm it loads the file directly, then re-run the edit for the rows that failed.
• For large batches, upload the files to Shopify first (Content → Files) and put the filenames in your spreadsheet instead of the URLs.

IMG002 - Image File Is In A Failed State

Shopify refused to attach an image file to a product because that file is marked as failed on Shopify's side: "File with id … is in the FAILED state and cannot be associated with a product." The product is fine — the file is not.

A file ends up in that state when Shopify couldn't fetch or process it, or hadn't finished preparing it when the app attached it. Large imports pulling many files from one image host make this more likely.

How to fix

• Re-run the edit for the affected rows. The app asks Shopify for a fresh copy of the file, so rows that failed on timing usually go through on a second attempt.
• Split large image imports into smaller batches, with a gap between runs.
• If your spreadsheet references a file already in Shopify by filename or id, check it in Content → Files. A file showing an error has failed and needs uploading again.

IMG003 - No Image Selected

The edit adds or replaces product images, but no image file was uploaded and no image URL was entered, so there is nothing to add. This can happen when the edit is previewed or saved before an image was added.

How to fix

• Upload an image file or enter an image URL in the edit, wait for the upload to finish, then preview or run the edit again.

IMG004 - File Still Processing

Shopify has not finished processing the file yet, so it cannot be attached to the product ("Non-ready files cannot be updated."). This can happen when a file was uploaded a short time before the edit ran.

How to fix

Wait a few minutes, then re-run the edit for the products with this error. If the file shows an error in Content → Files, upload it again.

Option Errors (OPT)

OPT001 - Option Already Exists

The option name you are trying to add, or to rename an option to, already exists on the product. Shopify requires each option on a product to have a unique name. For example, you cannot rename option 1 to "Size" on a product that already has a "Size" option.

How to fix

• Choose a different option name, or edit the existing option instead of adding a new one.
• When you rename an option, add a filter so that the edit skips products that already have an option with the new name.

OPT002 - Maximum Options Reached

Products in Shopify can have at most 3 options (e.g., Size, Color, Material). You are trying to add an option to a product that already has 3 options.

How to fix

Remove an existing option before adding a new one, or filter your product selection to exclude products that already have 3 options.

Variant Errors (VAR)

VAR001 - Duplicate Variant Options

You're trying to create a variant that already exists. Each variant on a product must have a unique combination of options (like size, color, material, etc.).

For example, if you have a t-shirt with these existing variants:

• Small, Red
• Medium, Red
• Large, Blue

You cannot create another "Medium, Red" variant because that combination already exists.

How to fix

Choose different option values that don't match any existing variant, or edit the existing variant instead of creating a new one.

VAR002 - Blank Or Zero Value For Compare-at Price or Cost

You are trying to set a value that's based on a calculation from either the compare-at price or cost field, but that field is not set. For example, you want the price to be 90% of the compare-at price, but the compare-at price is blank.

How to fix

Ensure that the compare-at price or cost fields have a value before running the edit. You can use Ablestar to filter for products with a blank compare-at price or costs to help identify the products that need to be fixed.

VAR003 - Product Variant Does Not Exist

The product or variant you are trying to edit no longer exists in your Shopify store. Messages include "Product variant does not exist" and "Product does not exist". This usually means the product or variant was deleted after the app last synced it.

How to fix

In most cases you can ignore this error, because the product or variant no longer exists. If the product is still in your Shopify admin, refresh your product data and run the edit again.

VAR004 - Variant Already Has An Image

The variant already has an image attached ("The given variant already has attached media."), so Shopify did not attach another one.

How to fix

Remove the variant's current image in the Shopify admin, then run the edit again for this product.

VAR005 - Daily Variant Creation Limit Reached

Shopify enforces a per-store per-day cap on how many new variants can be created. Once the cap is hit, all further variant creation attempts for that day will fail with this error. This is a hard limit enforced by Shopify, not by Ablestar.

How to fix

• Wait until the next day and retry the edit for the variants that didn't get created.
• If you need a higher limit for a specific store, contact Shopify Support — they may be able to raise it for you.

VAR006 - Option Value Linked To Metafield

The variant option you are trying to edit is linked to a metafield (Shopify's "linked options" feature). When an option is linked, you cannot change its name directly — the value is driven by the metafield.

How to fix

Edit the linked metafield instead, or unlink the option from the metafield in the Shopify admin.

VAR007 - Combined Listing Parent Not Supported

The product is the parent of a Shopify combined listing. Variant-level edits aren't supported on combined listing parents — the child products hold the real variants.

How to fix

Target the child products of the combined listing instead of the parent.

VAR008 - Price Out Of Range

The price you are trying to set falls outside the range Shopify allows. This covers several messages, including "Price must be greater than 0", "Price cannot be negative", and "Price can't exceed <currency amount>".

How to fix

Provide a price that is greater than 0 and below the currency-specific maximum for the store.

VAR009 - Not Allowed On Gift Cards

The edit changes a setting that Shopify does not allow on gift cards. Gift cards are never taxable and never need shipping, so Shopify rejects "Taxable" and "Requires shipping" changes on them.

How to fix

Add a filter to the edit that excludes your gift card products, for example by product type or title, then run the edit again. You can ignore this error for gift cards.

VAR000 - Generic Variant Error

A variant-related error occurred with the Shopify API. One example is "Something went wrong, please try again.", which is a temporary error on Shopify's side.

How to fix

Run the edit again for the products with this error. If the error continues, read the message in the edit log and contact support with the edit link.

Edit and Validation Errors (EDT)

EDT001 - Not A Whole Number (Integer)

Provided value is not numeric where a number is required. Do not include any commas or spaces in the number.

How to fix

Provide a valid whole number (e.g., 12, 12.0).

EDT002 - Not A Valid Decimal Number

Provided value is not a valid number where a decimal number is required. Do not include any commas or spaces in the number.

How to fix

Provide a valid number (e.g., 12, 12.5, 0.3).

EDT003 - Unable To Convert Measurement

The value of a weight, dimension or volume metafield starts with {, but it is not valid JSON, or it has no value.

How to fix

Enter a number and a unit, such as 1.4 kg or 12 cm. This is the format that exports use. The JSON format, such as {"value": 1.4, "unit": "kg"}, also works.

EDT004 - Invalid Reference

Invalid reference handle or ID.

How to fix

Use a valid Shopify handle or GID/ID.

EDT006 - Invalid Number Formatting

The input number contains invalid spacing.

How to fix

Remove spaces or invalid separators in the number.

EDT012 - Not A Number (Parameter)

An edit parameter expected a number but received a non-numeric value.

How to fix

Provide a numeric value for the parameter.

EDT013 - Price Must Be A Number

Price needs to be set to a valid number during the edit.

How to fix

Provide a numeric price and retry.

EDT014 - Invalid Link Metafield Format

Link metafields must be of the form {"url": "http://...", "text": "Label"}.

How to fix

Provide the exact JSON structure with url and text.

EDT015 - Price Is Null

Attempted a percentage-based price change but the base price is null.

How to fix

Set a base price first.

EDT016 - Price Needs To Be A Valid Number

Price validation failed because the value is not numeric, or a market/catalog compare-at price was provided without a price. Blank market/catalog price cells are skipped without an error; use [DELETE] to remove a fixed price.

How to fix

Provide a numeric price value, and always include a price when setting a compare-at price.

EDT017 - Unable To Convert To Date/Time

The provided value could not be converted to a valid date/time.

How to fix

Provide a correctly formatted date/time or use a supported conversion.

EDT018 - Missing Date Value Or Outdated Metaobjects

Either a required date value was not found, or metaobject data is out of date.

How to fix

Provide the missing date value, or refresh metaobject data in Settings → Shopify Data.

EDT019 - Tags Must Be A String

Tag lists must be provided as a string.

How to fix

Provide a comma-separated string of tags.

EDT020 - Markets Catalog Data Out Of Date

Markets catalog data appears outdated. Only older edits show this code. New edits show MKT004 for the same problem.

How to fix

Refresh Markets Catalog data in Settings → Shopify Data.

EDT021 - No Price Configured For Catalog

The edit sets a catalog price, but the edit has no price for that catalog, so there is nothing to set. The message names the catalog: No price configured for Wholesale.

How to fix

Open the edit and enter a price for the catalog, then run the edit again.

EDT022 - Invalid Published Value

The value for a sales channel column could not be interpreted, for example Invalid published value: maybe.

How to fix

Use TRUE, FALSE or a date. A date publishes the product on that date. The words yes, no, published, unpublished, 1 and 0 also work.

EDT023 - No Published Value Set

The value for a sales channel could not be used. This happens in two cases:

• A sales channel cell is empty: No published value set (cell is empty). Use true or false.
• The Visible on Point of Sale (POS) value could not be interpreted, for example Could not interpret "Visible on Point of Sale (POS)" value 'asdf'. Use true or false. For other sales channels, a value that cannot be interpreted gives EDT022.

How to fix

Use one of the following in the cell:

• true, yes, 1, or published — to publish the product to that channel.
• false, no, 0, or unpublished — to unpublish.
• For the Visible on Point of Sale (POS) column you can also use Shopify's raw values: global (visible on POS) or web (hidden from POS).

If the cell is empty and you did not intend to change the value for that row, delete or unmap the column before re-running the edit.

EDT024 - Invalid Price Format

Shopify rejected a price value because it was not in a parseable format. This most often happens when the price was formatted for a locale that uses a comma as the decimal separator (for example 4,00 instead of 4.00), or when the price included a currency symbol like $55.00 or €10,99.

How to fix

• Use a period (.) as the decimal separator — for example 4.00, not 4,00.
• Don't include currency symbols in the price field. The currency is determined by the store or market.
• If you are importing from a spreadsheet that was exported for a non-US locale, re-export it with period decimal separators.

EDT025 - Invalid Country Code

The country code you provided (for example for Country/region of origin) is not a valid ISO 3166-1 alpha-2 code that Shopify accepts, so the value was not sent to Shopify. For example, VI is not accepted: Shopify treats the U.S. Virgin Islands as part of the United States.

UK and EL are converted to GB (United Kingdom) and GR (Greece) automatically.

How to fix

Use the correct two-letter ISO 3166-1 alpha-2 country code, or the country name as Shopify spells it. A few examples:

• United Kingdom → GB
• Greece → GR
• Switzerland → CH
• United States → US

EDT026 - Unrecognized Country Of Origin

A Country of Origin value in a spreadsheet could not be matched to a country, so it was skipped instead of being sent to Shopify. The rest of the row is still imported. The message tells you which value was rejected — for example Country of Origin was not set: could not interpret value 'Spane'. Use a country name or its two-letter ISO code.

This most often happens when:

• The country name is misspelled or abbreviated (Spane, USA, Holland).
• The two-letter code isn't a real ISO code (for example XX). UK and EL are converted to GB and GR automatically.
• The cell holds something other than a country, such as a supplier or region name.

How to fix

Use either the full country name as Shopify spells it (Spain, United States, United Kingdom) or its two-letter ISO 3166-1 alpha-2 code (ES, US, GB). See EDT025 for commonly-mistaken codes.

If you did not intend to set a country of origin, delete or unmap the column before re-running the import.

EDT027 - Sales Channel No Longer Exists

The edit, rule or undo changes the publishing status for a sales channel that is no longer in your Shopify store — for example because the channel's app was uninstalled. The message names the channel: Sales channel no longer exists in Shopify: Faire: Sell Wholesale. Remove it from the edit. Shopify's own message for this is Publication does not exist or is not publishable. Older edits showed that message as SAPI017.

When the same edit also changes other fields or other sales channels, those changes are still applied and the missing channel is skipped. You only see this error when the missing channel was the only change for the product.

How to fix

• Remove the sales channel from the edit, product rule or scheduled edit, then run it again.
• If the channel was reinstalled, it has a new ID in Shopify. Resync your store data, then select the channel again in the edit or rule.

EDT028 - Invalid Barcode

A barcode in the edit does not match the format of its barcode type, so the variant was not changed. Shopify checks barcodes that have a type, and it rejects all the variants that are sent with an invalid one, so the app checks them first. The message names the barcode, for example EAN '4006381333932' has a wrong check digit.

Shopify's rules for each type:

• UPC: 8 or 12 digits.
• EAN: 8 or 13 digits.
• GTIN: 8, 12, 13 or 14 digits.
• ISBN: 10 characters (the last can be X) or 13 digits that start with 978 or 979. Hyphens and spaces are allowed.
• ASIN: 10 letters and digits.
• NS-PID and barcodes without a type (Custom): any text.

UPC, EAN, GTIN and ISBN barcodes also have a check digit (the last digit), which must match the other digits. A variant also can't have the same barcode twice, even with different upper and lower case.

How to fix

• Check the barcode for a typing error or a missing leading zero. Spreadsheet programs often remove leading zeros, so format the barcode column as text.
• Remove spaces and hyphens from UPC, EAN and GTIN barcodes.
• If the barcode is an internal code that follows no standard, remove the type prefix (for example upc:) so it is saved as a Custom barcode.

EDT029 - Too Many Barcodes

Shopify allows at most 20 barcodes on a variant. The edit would give the variant more than 20, so the variant was not changed.

How to fix

Remove some barcodes from the variant first, or add fewer barcodes. To replace all of a variant's barcodes, use Barcodes: Replace all instead of Barcodes: Add.

EDT030 - Publish Date Before 1970

A sales channel column in a product import has a publish date before 1970. Shopify does not accept these dates, so the product was published on that sales channel without the date. The rest of the row is still imported. The message names the channel and the value, for example Sales channel 'Online Store' was published without its publish date: '1965-03-01' is before 1970, which Shopify does not accept.

This most often happens when a date column was read as a very old date, for example an empty or zero date from another system, or a two-digit year that the spreadsheet program read as 19xx.

How to fix

If the product must not be visible yet, set the sales channel cell to FALSE or to a date after 1970, then import the row again. Otherwise no action is needed.

EDT031 - No Category Set

A Category edit has no category to set, so no products were changed. The message is No category set for the Category edit.

This can happen when the field of an edit was changed to Category after another field was configured, so the edit was saved without a category.

How to fix

Start a new edit, select the Category field, choose a category from the list, and run the edit again.

EDT032 - Measurement Unit Missing

The value of a weight, dimension or volume metafield has a number but no unit, for example 12.

How to fix

Add a unit after the number, such as 12 cm, 1.5 kg or 500 ml. The unit is not case sensitive, and the space is optional. The error message shows the units for the metafield.

EDT033 - Measurement Unit Not Supported

The unit of a weight, dimension or volume metafield is not one that Shopify supports for that metafield type. For example, kg is a weight unit, so it does not work for a dimension metafield.

How to fix

Use one of these units. Full names, such as inches or kilograms, also work.

• Weight: g, kg, oz, lb
• Dimension: mm, cm, m, in, ft, yd
• Volume: ml, cl, l, m3, us fl oz, us pt, us qt, us gal, imp fl oz, imp pt, imp qt, imp gal

EDT034 - Measurement Value Not A Number

The value of a weight, dimension or volume metafield does not start with a valid number. Commas are not accepted in the number, because 1,500 can mean 1500 or 1.5.

How to fix

Start the value with a number, and use a period for decimals, such as 1.5 kg. Do not use thousands separators: enter 1500 g, not 1,500 g.

EDT035 - Measurement Value Negative

The value of a weight, dimension or volume metafield is less than 0. Shopify accepts only values of 0 or more.

How to fix

Enter a value of 0 or more, such as 12 cm.

EDT036 - Sales Channel Does Not Support Bundles

The product is a bundle, and the sales channel does not accept bundle products, for example Channel Pinterest does not support bundle products. Shopify did not publish the product to that channel.

How to fix

Add a filter to the edit to exclude bundle products for this channel. You can ignore this error if you did not intend to publish bundles to the channel.

Unit Price Errors (UNT)

UNT001 - Invalid Unit Price Format

The unit price value is not in the correct format. Unit price fields require a JSON object with specific fields defining the quantity and reference measurements.

How to fix

Provide a valid JSON object with the required fields:

{
  "quantityUnit": "G",
  "quantityValue": "100",
  "referenceUnit": "KG",
  "referenceValue": "1"
}

Valid unit values include:

• Weight: MG, G, KG, OZ, LB
• Volume: ML, CL, L, M3, FLOZ, PT, QT, GAL
• Length: MM, CM, M, IN, FT, YD
• Area: M2, FT2
• Count: ITEM

UNT002 - Invalid Unit Price JSON

The unit price value contains invalid JSON that could not be parsed.

How to fix

Verify that your unit price value is valid JSON. Check for:

• Missing or extra quotes
• Missing commas between fields
• Unescaped special characters

UNT003 - Unit Price Missing Required Fields

The unit price JSON is missing one or more required fields. All of the following fields are required:

• quantityUnit - The unit of the product quantity (e.g., "G" for grams)
• quantityValue - The quantity value (e.g., "100")
• referenceUnit - The reference unit for the price (e.g., "KG" for kilogram)
• referenceValue - The reference value (e.g., "1")

How to fix

Include all required fields in the unit price JSON object.

Markets Errors (MKT)

MKT001 - No Catalogs For Market

No active catalogs were found for the market.

How to fix

Create/activate a catalog for the market, then retry.

MKT002 - No Currency For Market

The market does not have a currency set.

How to fix

Set the market's currency in Shopify.

MKT003 - No Catalog For Market

No catalog is associated with the specified market.

How to fix

Assign a catalog to the market and retry.

MKT004 - Markets Data Out Of Date

Markets data appears outdated and the price list for the market could not be found.

How to fix

Refresh Markets data in Settings → Shopify Data and retry.

MKT005 - Unable To Parse Catalog Price Data

The catalog price and compare-at price data could not be parsed properly. This occurs when the price data is missing, empty, or in an incorrect format. If you are editing these in a spreadsheet file, the price and compare-at price need to be in the following format:

{ "price": 10.0, "compare_at_price": 15.0 }

How to fix

Ensure that catalog price data is provided in the correct format with both price and compare-at price values properly structured.

MKT006 - Null Response When Setting Fixed Price

The Shopify API returned a null response when attempting to add a fixed price to a price list. This typically occurs when there was an unexpected error when making the API request to Shopify.

How to fix

This is usually a temporary API issue. Try the following:

• Retry the operation after a short wait
• Verify that the price list and product variant still exist
• Check that the price values are valid and properly formatted
• If the issue persists contact support and we will investigate.

MKT007 - No Price List Found For Catalog

In Shopify, a catalog is a group of products that can be sold in a certain market. If these products have unique prices, Shopify also needs to have a 'price list' for that catalog, which keeps track of which price each product has.

Usually Shopify will automatically create a price list for you when you create a catalog. In some cases though, there will be no price list for a catalog which will cause an edit to fail since the prices cannot be updated.

How to fix

To fix this you'll need to get Shopify to create the price list for you and then refresh the markets data in Ablestar Bulk Product Editor

1. In the Shopify Admin, go to Markets → Catalogs and select the catalog that you are trying to edit
2. Make a change in the 'Pricing' section and save it. For example, set the 'Overall price adjustment' to be an increase of 1%. This will force Shopify to create a new price list for the catalog. You can revert the change you made immediately after saving it.
3. In Ablestar Bulk Product Editor go to Settings → Shopify Data and click on the refresh icon next to 'Shopify Markets'
4. Wait 60 seconds, reload the app and try the edit again.

Shipping Profile Errors (SHP)

SHP001 - Missing Shipping Permission

The app does not have permission to read or change shipping profiles. Shipping profile edits use an optional Shopify permission that a store owner grants from inside the app.

How to fix

Open the edit configuration, select the Shipping Profile field, and approve the permission request when Shopify shows it. Staff accounts without the "Manage and install apps and channels" permission cannot approve it; ask the store owner.

SHP002 - Shipping Profile Not Found

The shipping profile selected for the edit (or the profile a variant was in before the edit, for an undo) no longer exists in Shopify.

How to fix

Choose another shipping profile and run the edit again.

SHP003 - No Shipping Profile Selected

The edit does not have a shipping profile selected.

How to fix

Select a shipping profile in the edit configuration before running the edit.

SHP004 - Store Uses Market-Driven Shipping

The store has moved to Shopify's market-driven shipping. Shipping rates are set per market under Settings → Markets and apply to all products or to collections; there are no shipping profiles to move products between. Shipping profile edits are not available on these stores, including scheduled edits and undos created before the store moved.

How to fix

To change which shipping rate applies to a product, add the product to the collection that the rate uses. You can do this in bulk with the Collections field in Ablestar Bulk Product Editor. To change the rate itself, edit it in Shopify under Settings → Markets, select the market, and open its shipping options.

SHP000 - Other Shipping Profile Error

An unexpected error occurred while reading or changing shipping profiles.

How to fix

Try again. If the error continues, contact support with the edit link.

Shipping Dimension Errors (DIM)

DIM001 - Length, Width and Height Must All Be Set

Shopify saves the packed dimensions of a variant only when the length, width and height are all above 0, or all 0 (no dimensions). The edit would leave some dimensions at 0 and others above 0. This often happens when an edit sets only one dimension on a variant that has no dimensions yet.

How to fix

Set the length, width and height together for variants that have no dimensions. To remove the dimensions, use Remove dimensions or set all three to 0.

DIM002 - Variant Has No Dimensions to Change

An increase or decrease (by amount or by percent) needs a current value to start from, and the variant has no packed dimensions.

How to fix

Set the length, width and height first, with Set dimensions or a spreadsheet, then run the increase or decrease again.

DIM003 - Dimension Would Be 0 or Less

A decrease would make a dimension 0 or less. Shopify needs each dimension above 0 while the others are set.

How to fix

Use a smaller decrease. To remove the dimensions, use Remove dimensions.

DIM004 - Invalid Dimension Value

A length, width or height is not a number, or it is negative.

How to fix

Enter numbers of 0 or more, such as 12.5. Leave a value blank to keep the current one.

DIM005 - Unsupported Dimension Unit

Shopify accepts packed dimensions in centimeters (cm) or inches (in) only.

How to fix

Use cm or in as the unit. Convert other units, such as millimeters, before you run the edit.

DIM006 - No Dimension Change Entered

The edit has no value to apply: no length, width, height or unit was entered.

How to fix

Enter at least one value in the edit configuration, or in the spreadsheet row.

DIM007 - Not a Physical Product

The variant is not a physical product (Physical product is off in Shopify), so the edit skipped its packed dimensions. The other variants in the edit are still changed. The edit preview shows this code before the edit runs.

Shopify does not use the dimensions of a variant that is not a physical product. Also, when Physical product is turned on later in the Shopify admin, the admin shows empty dimensions and saves them as 0. The skip makes sure that values from the edit are not lost that way.

How to fix

Turn on Physical product for the variant first. You can do this in the same edit: add a modification to the Physical product (requires shipping) field, set it to true, and keep the Shipping Dimensions modification. The edit turns on Physical product before it sets the dimensions.

DIM000 - Other Shipping Dimension Error

An unexpected error occurred while reading or changing the packed dimensions, for example Shopify did not return the variant.

How to fix

Refresh your product data and try again. If the error continues, contact support with the edit link.

Shopify API / GraphQL Client Errors (SAPI/GQL)

GQL005 - GraphQL Client Not Initialized

The GraphQL client session was not initialized. The app will reinitialize the session automatically.

How to fix

Usually automatic; if persistent, re-authenticate and retry.

SAPI008 - Shopify Rejected The Request

Shopify rejected the request with an error message while the app applied the changes. The message in the edit log is Shopify's own text. For some media changes, the app tries again in a different way before it shows this error.

How to fix

Read the message in the edit log. Run the edit again for the products with this error. If the error continues, contact support with the edit link.

SAPI009 - Shopify API Error

Shopify returned an error that the app does not recognize while it applied the changes. The message in the edit log is Shopify's own text.

How to fix

Run the edit again later. If the error continues, contact support with the edit link.

SAPI010 - Shopify Rate Limit Reached

Shopify limits how many API requests an app can make per second. The app waits and retries when it reaches the limit, but this request was still limited after all retries. This can happen when other apps use a lot of your store's API capacity at the same time.

How to fix

Run the edit again later for the products with this error. If it happens often, run large edits when fewer other apps or imports are running.

SAPI014 - Shopify Internal Error

Shopify's API returned an internal error for this product after several retries, for example while saving metafields, files or sales channels. The other products in the edit are still changed.

How to fix

Retry the edit for the products with this error. If it continues, contact support.

SAPI015 - Product Locked By Shopify

Shopify returned a TOO_MANY_PARALLEL_REQUESTS_FOR_THIS_PRODUCT error or the message "This product is currently being modified. Please try again later.", which means that another process is currently modifying the same product. This is a limit enforced by Shopify to prevent conflicting edits to a product at the same time. The app will automatically retry several times, but if the product remains locked after all retries this error is raised.

How to fix

• Wait a few minutes and try the edit again. The lock is usually temporary.
• Make sure no other apps or bulk operations are editing the same products at the same time.
• If the issue persists, contact support.

SAPI016 - Unable to Create Bulk Operation

Ablestar Bulk Product Editor uses Shopify's Bulk Operations API to perform a full download of all metafields on your store. This error indicates that the app was unable to create a bulk operation in Shopify. The most likely reason is that there is already a bulk operation in progress on the store, and Shopify only allows one bulk operation at a time.

How to fix

Wait until the other bulk operation is finished, then try again. Another app can be running it, for example an import, export or backup app.

SAPI017 - Shop Under Review Or Sales Channel Not Found

New edits show this code when Shopify has put the store under review. While the store is under review, Shopify blocks changes through the API.

Older edits also showed this code when the edit targeted a sales channel that Shopify no longer recognizes. New edits show EDT027 for that case.

How to fix

• If the store is under review, check the Shopify admin for a notice from Shopify and wait until the review is finished, then run the edit again.
• For a missing sales channel, see EDT027.

Inventory Errors (INV)

INV001 - Cannot Unstock Last Location

You tried to remove a product or variant from a location, but that location is the only place the item is currently stocked. Shopify requires variants to be stocked at a minimum of one location.

How to fix

• Stock the product or variant at another location first, then retry unstocking this location.
• If you want the product to no longer be tracked, delete the product instead of unstocking every location.

INV002 - Cannot Unstock With Unfulfilled Orders

You tried to remove a product or variant from a location, but Shopify has unfulfilled orders that are pulling inventory from that location. Shopify won't let you detach the inventory until those orders are handled.

How to fix

• Fulfill or cancel the open orders that reference this location.
• Alternatively, move the unfulfilled orders to a different location before unstocking.

INV003 - Incoming Transfers Or POs Block Unstock

Similar to INV002, but the blocker is an incoming inventory transfer or purchase order that expects stock to land at this location.

How to fix

• Complete, cancel, or reroute the incoming transfer or purchase order.
• Then retry the unstock operation.

INV004 - Cannot Stock Without SKU

You tried to activate a variant at a new location, but the variant has no SKU set. Some fulfillment services and locations require a SKU before they'll accept inventory.

How to fix

Set a SKU on the variant first, then retry stocking it at the location.

INV005 - Inventory Managed By Another App

The inventory for this item is managed by a fulfillment service or third-party app (for example Gardners, ShipBob, Gelato). Shopify won't let Ablestar change the stock configuration for items under external management.

How to fix

• Make the change in the app or fulfillment service that manages the inventory.
• If you want Ablestar to manage the inventory directly, switch the item to be managed by Shopify in the Shopify admin first.

INV006 - Harmonized System Code Format

The harmonized system (HS) code you provided isn't in a valid format. Shopify requires HS codes to be between six and thirteen digits.

How to fix

Provide an HS code that is a number between six and thirteen digits long, with no dots, spaces, or other separators.

INV007 - Not Stocked At Location

You tried to change the inventory quantity of a variant at a location, but the variant isn't stocked at that location. Ablestar can only change quantities at locations where the variant is already stocked, so the variant was skipped.

When a spreadsheet edit also changes other fields, or variants that are stocked at the location, those changes are still applied and only the unstocked variant is skipped. You only see this error when nothing else could be changed for the product.

How to fix

• Run a Stocked at Location edit to stock the variant at the location, then run the inventory edit again.
• If the variant is already stocked there in the Shopify admin, wait a few minutes for Ablestar to receive the change from Shopify, then run the edit again.

INV008 - Location Not Found

You tried to stock or unstock a product at a location, but the location ID in the edit isn't a location in your store. The message shows the value that couldn't be used, for example Location ID "abc" isn't a location in your store. The product wasn't changed.

This usually means the value isn't a location ID. For example, an Inventory Item ID from a product export is a different ID and won't work.

How to fix

• Find the location ID in the Shopify admin: go to Settings → Locations, click the location, and copy the number at the end of the URL.
• To use several locations in one spreadsheet cell, separate the IDs with commas, for example 68080664829, 76277252349.
• If the location was recently removed from your store, remove it from the edit, product rule or scheduled edit.

INV009 - Location Deactivated

You tried to stock a product or variant at a location that is deactivated in Shopify, for example The variant couldn't be stocked at Main Street because the location was deactivated. Shopify does not stock products at deactivated locations.

How to fix

• Remove the location from the edit, product rule or scheduled edit.
• Or, if you still use the location, activate it again in the Shopify admin under Settings → Locations, then run the edit again.

INV010 - Bundle Inventory Cannot Be Changed

The variant is a bundle. A bundle has no inventory of its own: Shopify calculates it from the products in the bundle, so the quantity cannot be changed directly.

How to fix

Change the inventory of the products in the bundle instead. Add a filter to the edit to exclude bundle products.

INV011 - Inventory Item Not Found

The variant's inventory item does not exist in Shopify. This usually means the variant was deleted after the app last synced your products.

How to fix

Refresh your product data, then run the edit again. You can ignore this error if the variant was deleted.

INV000 - Generic Inventory Error

An inventory-related error occurred with the Shopify API.

How to fix

Read the error message in the edit log for details. If you need help, contact support with the edit link.

Collection Errors (COL)

COL001 - Collection Does Not Exist

The collection the edit was adding to or removing from no longer exists in the store, or it was deleted between the last sync and the edit running. Shopify also uses the message "Collection does not exist" for some automated collections that the app cannot change directly.

How to fix

Refresh the store's collections from the app, then check the collection name in your spreadsheet or in-app edit against the collections that actually exist.

COL002 - Collection Managed By Other Collections

The collection gets its products from other collections rather than from its own conditions, so individual products can't be added to it or removed from it.

How to fix

Add or remove the product on one of the source collections instead, or change the collection in the Shopify admin so it has its own conditions.

COL003 - Product Excluded By Collection Conditions

The product was added to the automated collection, but the collection also has exclude conditions that the product matches, so Shopify keeps it out of the collection.

How to fix

Edit the collection's exclude conditions in the Shopify admin so they no longer match the product, or add the product to a different collection.

COL004 - Too Many Manually Excluded Products

When you remove a product from an automated collection, the product is manually excluded from the collection. Shopify lets a collection exclude at most 1,000 products this way, for example A source can manually exclude at most 1000 products (collection "Spring 2024").

How to fix

• Change the collection's conditions in the Shopify admin so that they no longer match the products, instead of removing the products one by one.
• Or add a tag to the products and add an exclude condition for that tag to the collection.

COL000 - Generic Collection Error

A collection-related error occurred with the Shopify API.

How to fix

Read the error message in the edit log for details. If you need help, contact support with the edit link.

If you encounter an unresolved issue: include the error code, message, and the action you were performing when contacting support. This helps us diagnose quickly.