Skip to main content
Print

Shopify Troubleshooting

Messages from Shopify and from the Shopify Transmitter in the job log, what causes them and what to do. Shopify’s own messages are in English; the transmitter’s messages appear in the language of the Contentserv user.

Important: check your connector version first. Many problems are already fixed in a later version, and many features on these pages need a minimum version. How to read the Available from lines and where to find your version: Versions.

A version under a message means: the transmitter shows this message from that version on. Older versions report the problem differently, or not at all.

Connection and API version

MessageCauseWhat to do
Oauth error shop_not_permitted: Client credentials cannot be performed on this shop.The app was created in another organisation than the store’s.Create the app in the store owner’s organisation, see Shopify Transmitter.
Failed to obtain access token: <!DOCTYPE html> …The shop URL is an admin.shopify.com/store/… address.Use https://<your-shop>.myshopify.com.
Neither a Shopify connection nor a shop URL is configured for the transmitter. Nothing was sent to Shopify.
from 1.22.0
No connection is selected in the transmitter.Select the shop’s connection in the field HTTP Connection.
Shopify no longer supports API version “…” and uses “…” instead.
from 1.21.19
The configured API version is too old.Enter a current version, or leave the field empty (from 1.22.0).
API version “…” is the oldest one Shopify still supports and will probably be dropped with the next quarterly release.
from 1.22.0
The configured API version will soon be too old.Enter a newer version, or leave the field empty.
API version “…” is not in the expected format (YYYY-01, YYYY-04, YYYY-07, YYYY-10 or unstable). It is sent to Shopify anyway.
from 1.22.0
A typo in the API version.Correct it, e.g. 2026-07.
Shopify reports deprecated fields in the request, which a later API version removes: …
from 1.22.0
A datamap row sends a field Shopify will remove.Check the named fields in the datamap.
THROTTLEDShopify’s rate limit: too many requests to the shop at the same time, e.g. from several jobs or other apps.The transmitter pauses when the limit is nearly used up. From 1.21.20 it also waits and repeats a request Shopify refused. Before that, the record fails: run fewer jobs against the shop at the same time and export again.

Products and variants

MessageCauseWhat to do
Type can’t be blankThe metafield definition of the PIM identifier is missing.Create it for products and collections, see Shopify Transmitter.
PIM identifier is missing or incorrectly maintained.The first row’s key differs from the transmitter setting, or its value is empty.Use the same namespace.key in both.
Product could not be updated. / Variable … could not coerce … to FloatA number or price is sent as text, e.g. 380.00 g or "".Send numbers as numbers and skip empty values (row conditions).
invalid money ”An empty compare-at price.Add the condition “skip while empty”.
Option does not exist / You need to add option values for …A variant has no value for an option, or the option names of product and variant differ.Fill every option value; use the same option names. See Products, Variants and Options.
Variants … have no value for option “…”. Shopify creates no variant of the product until every variant has a value for every option.
from 1.22.0
Option formats: the named variants have no value for an attribute that other variants of the product have.Fill the values, or remove the attribute from the product’s variant-building attributes.
Shopify allows 3 options per product. Not sent: …
from 1.22.0
Option formats: more than three variant-building attributes have values.Reduce the product’s variant-building attributes to three.
Linked option “…”: the value “…” has no external key, so its metaobject entry cannot be found. The value is not sent.
from 1.22.0
Option formats: a value of a linked option has no external key, so it has no metaobject entry handle.Give the value an external key and export the metaobject entries again.
Linked option “…” has no metaobject type, so its values cannot be found. Enter the type under Linked options in the format, or give the attribute an external key.
from 1.22.0
Option formats: the linked option has no metaobject type in the format, and its attribute has no external key. Its values are not sent.Enter the definition’s type in the column Metaobject type, or give the attribute the type as external key.
Failed to create variants for product …Shopify rejected the variants; the details name the field.Check the named variant field.
The simpleproduct values are not transferred, because the product has variants in Shopify.
from 1.21.20
A product that has variants in Shopify is exported without them.Export the variants, or remove the simpleproduct values.
The linked product options could not be created … / Failed to update product options …The product metafield of the linked option is missing or of the wrong type.Create the product metafield with the type Metaobject, as a list.
Option “…” was added although the product already has … option(s) in Shopify.
from 1.21.20
An option was renamed in the PIM.Options cannot be renamed through the transmitter: rename it in Shopify, or delete and export the product again.
Gift card products can only be created after they have been activatedGift cards are not activated in the shop.Create one gift card product by hand (Products > Gift cards), then export again.
Stock … is not a number and is not transferred
from 1.21.20
The initial stock is not a number.Check the stock attribute.
The list of … could not be loaded completely from Shopify (loaded: …). Records missing from it are not created in this run, so that no duplicates arise.
Record with PIM identifier “…” is not created …
from 1.21.20
Shopify did not return the complete list of products or collections in this run.Export again. The records are created in a run that loads the list completely.
Record could not be processed because of an unexpected error and is skipped: …
from 1.21.20
The data of this record has an unexpected shape.Check the record’s data and the datamap rows named in the details. The other records are processed.

Collections

MessageCauseWhat to do
Handle has already been takenTwo collections or products with the same handle, often product nodes in a structure group exported as collections.Keep the node condition of the collections datamap; use unique handles.
Collection not found in Shopify (Collection PIM identifier: …)The product’s collection does not exist in Shopify yet.Export the collections before the products.
Cannot publish a collection to a publication that does not belong to a channel catalogA market catalog in the collection’s salesChannel.Collections can only be published to sales channels.
Collection image is not transferred to Shopify: the media upload contains no file name
from 1.21.19
The collection has no image, and the image row has no condition.Skip the row while the image attribute is empty.

Metafields and references

MessageCauseWhat to do
Value must be a valid product referenceA comma-separated text was sent as one list value.Split the text into a list first.
Field “…” is not transferred: reference “…” was not found in Shopify
from 1.21.20
The referenced record is not in Shopify (yet).Export it first; references to records created in the same run are found in the next run.
The metaobject type / metaobject handle is not specified correctly (expected format: @metaobjectRef:type|handle)A metaobject reference without type or handle.Use @metaobjectRef:<type>|<handle>.
Metafield discarded because value for transfer to Shopify is not correctThe value does not fit the metafield type.See the value formats on Metafield Field Plugin.
Metafield “…” is not transferred to Shopify: not a namespace/key/value structure
from 1.21.18
A row built by hand lacks namespace or key.Complete the array, or use the metafield format.
This metafield is connected to an option. To make changes, edit the option.The list metafield of a linked option is written directly.Don’t send it as a metafield: it follows the option.

Media

MessageCauseWhat to do
Media file Id “…” has not yet been processed by Shopify. … new attempts will be madeShopify is still processing the file.Nothing; the transmitter waits.
Media file from the station cache no longer exists in Shopify and is uploaded again
from 1.21.19
The file was deleted in Shopify.Nothing. Before 1.21.19: empty the station cache.
Media files Shopify could not process were deleted
from 1.21.19
Shopify could not process an uploaded file.Check the file in the DAM; it is uploaded again in the next run.
Media files Shopify could not process could not be deleted. Please delete them in Shopify under Content > Files
from 1.21.19
Deleting the broken file failed.Delete it in Shopify under Content > Files.
Media files Shopify could not process were left untouched, because they were not uploaded by the connector.
from 1.21.19
A broken file on the product that came from elsewhere.Check it in Shopify under Content > Files.
The changed media file “…” could not be uploaded, the previous version stays on the product
from 1.21.20
Shopify did not accept the new version of the file.Check the file in the DAM and export again.
The file list could not be loaded completely from Shopify. The station cache for media stays empty, and files are looked up in Shopify one by one in this run.
from 1.21.20
Shopify did not return the complete file list.Nothing; the run is slower.
Variant image “…” is not among the exported product images and is left unchanged
from 1.21.20
The variant’s mediaFile is not one of the product’s media.Use the same file name and preset as the product media.

Bundles

MessageCauseWhat to do
No product id found for PIM-Identifier “…”, product could not be added to bundleThe component is not in Shopify yet.Export the products twice on an empty shop.
components.….optionSelections.….componentOptionId (Expected value to not be null)An option name of the selection does not match the component.Use the component’s option names exactly.
Bundle operation not finished after … seconds, the product is skipped.
from 1.21.19
Shopify takes long to create the bundle.If the bundle appears in Shopify later, it has no PIM identifier: delete it before the next export.
Bundle component … has variants and is skipped. Use one of its variants as the component.
from 1.22.0
Bundle format: a product with variants is a component as a whole.Make one of its variants the component.
Bundle component … is a variant without option values and is skipped. Check the variant-building attributes of the format.
from 1.22.0
Bundle format: the field Variant-building attributes is empty, or the variant has no values for them.Select the attribute in the format, and fill the variant’s option values.

Market prices and translations

MessageCauseWhat to do
No pricelist for catalog (Id “…”) foundThe market has no price list.Create a price list for the market in Shopify.
(no message, prices missing)The market name doesn’t match the catalog title, or the price table row has no price type selected.See Markets, Sales Channels and Prices.
Empty translations were rejected by Shopify, existing translations stay unchanged
from 1.21.20
A translated value is empty in one language.Fill the value, or ignore: the existing translation stays.
Translations were rejected by Shopify: …
from 1.21.20
Shopify refused a translation; the details name the field and the reason.Check the named value.

Metaobject entries

MessageCauseWhat to do
Shopify did not delete the metaobject entry; it is probably still in use …
from 1.21.19
The entry is a value of a product option.Remove it from the products first.
The Shopify job deleting the metaobject entries has not finished yet, the result was not checked
from 1.21.19
Shopify deletes in the background and took longer than the transmitter waits.Check in Shopify whether the entries are gone.
Meta object handle or type missing, please check the data map.An entry without type or handle: the attribute or one of its values has no external key.Give the attribute and its values external keys, or send the type as a fixed value in the row type.
The capabilities of the metaobject entries … are not transferred under the key “metaobject”.
from 1.21.20
Status or template suffix under the old key.Use the key metaobjectInput.

Deleting

MessageCauseWhat to do
An error occurred when trying to delete the product from Shopify … Product does not existThe product is no longer in Shopify, e.g. it was deleted by hand or is listed twice in the job.Nothing, if the product should be gone.
Shopify ID of record “…” not cleared: it does not point to the deleted object
from 1.21.19
The ID in Contentserv belongs to another Shopify object.Check the record’s Shopify ID.
Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents