Product Creation Order for new GraphQL APIs

Partner Discussions
1

There has been some unique changes regarding how products are now created via the newer GraphQL APIs (2025+).

Trying to figure out the best approach because I keep running into snags regarding product creations.

I am first using productCreate mutation to create the product.

I then need to add the sku and inventoryItem.tracked along with a inventoryPolicy (which can only be done on the variant level).

So after creating the product with productCreate I can no longer simply add this data for the variants it keeps saying I need options and/or the variant.id (which I cannot get from productCreate any longer).

I have tried productVariantsBulkUpdate and productVariantsBulkCreate but they need those fields which I dont have nor do I want to create any options. This is very frustrating, not sure why the productCreate got rid of the variants input.

Any ideas on how to get this going with the most effective approach?

2

Hey @Stats_Marketing :waving_hand: - the productSet mutation might help when it comes to creating variants/product options right off the bat.

It should also let you set SKUs/barcode data for inventory items and variants as well as the inventory item tracking state.

Hope this helps - let me know if you encounter any blockers, happy to help out with this for sure.

3

@Alan_G Thanks for the reply.

So when I try to use productSet it still requires product options (even though I have none):

Product options input is required when updating variants

It’s forcing me to add some silly options for some reason. I cannot just do this for my variables:

{
  "productSet": {
    "title": "Test",
    "descriptionHtml": "",
    "variants": {
      "inventoryItem": {
        "tracked": true
      },
      "sku": "99888"
    }
  }
}

Says this error message:
"message": "Product options input is required when updating variants"

4

No worries @Stats_Marketing, definitely understand where you’re coming from on this - I did a bit more digging into this and it looks like this might be being triggered by the “Default” variant which is created upon product creation (essentially a dummy variant). There’s a bit more info in this thread here on our old community forum.. It looks like my colleague Liam suggested this as a possible workaround though:

{
    "productSet": {
        "title": "Sample Product",
        "descriptionHtml": "<p>This is a sample product description.</p>",
        "vendor": "Sample Vendor",
        "productOptions": [
            {
                "name": "Title",
                "values": [
                    {"name": "Default Title"}
                ]
            }
        ],
        "variants": [
            {
                "price": "19.99",
                "optionValues": [
                    {
                        "optionName": "Title",
                        "name": "Default Title"
                    }
                ]
            }
        ]
    },
    "synchronous": false
}

I’m going to reach out to our developers to see if this is the recommended workaround or if we can escalate a feature request their way. I’ll loop back with you here once I hear back.

6

Hey @Stats_Marketing - was able to get an answer on this for you quickly here from our developers. The above is still the recommend method, but I was able to pass along feedback to our developers and they mentioned they will mention this to the product/variants component team to see if we can make creating option-less variants/products less restricted going forward.

Let me know if I can help with anything else on my end here.

7

@Alan_G Unfortunately this still does not work.

It seems to just give me an error message still:

Option value does not exist

Not sure if there is another solution here or not, but I appreciate the solutions thus far.

8

@Stats_Marketing - thanks for trying that - that is very odd. Can you try giving this syntax a go and letting me know if that works?

mutation createProductAsynchronous {
  productSet(
    synchronous: false, 
    input: {
      title: "Sample Product 3",
      descriptionHtml: "<p>This is a sample product description.</p>",
      vendor: "Sample Vendor",
      productOptions: [
        {
          name: "Title",
          values: [
            {name: "Default Title"}
          ]
        }
      ],
      variants: [
        {
          price: "19.99",
          optionValues: [
            {
              optionName: "Title",
              name: "Default Title"
            }
          ]
        }
      ]
    }
  ) {
    product {
      id
    }
    productSetOperation {
      id
      status
      userErrors {
        code
        field
        message
      }
    }
    userErrors {
      code
      field
      message
    }
  }
}

If not, just ping me here along with the mutation/variable input you’re using and I’m more than happy to keep digging into this with you for sure.

9

Thanks @Alan_G,

This actually did work, not sure where I went wrong with it.

Full code:

mutation createProductAsynchronous($input: ProductSetInput!) {
  productSet(synchronous: false, input: $input) {
    product {
      id
    }
    productSetOperation {
      id
      status
      userErrors {
        code
        field
        message
      }
    }
    userErrors {
      code
      field
      message
    }
  }
}

Variables

{
  "input": {
    "title": "Sample Product 3",
    "descriptionHtml": "<p>This is a sample product description.</p>",
    "vendor": "Sample Vendor",
    "productOptions": [
      {
        "name": "Title",
        "values": [
          {
            "name": "Default Title"
          }
        ]
      }
    ],
    "variants": [
      {
        "price": "19.99",
        "sku": "123456789",
        "inventoryPolicy": "CONTINUE",
        "inventoryItem": {
          "tracked": true
        },
        "optionValues": [
          {
            "optionName": "Title",
            "name": "Default Title"
          }
        ]
      }
    ]
  }
}
1 Like