Webhooks and variant metafields

Just gonna throw my two cents in here, along with everyone that’s done it in the last couple of years.

At the moment, the behaviour of the products/update-webhook is so that if a product has variants, even if only one, the act of updating a variant metafield triggers the webhook. I don’t think the actual metafield data is in the payload, but I can query graphql for the updated variant metafield based on the fact that I got a notice that the product was updated. It’s noisy as all hell, but it works.

If a product doesn’t have any variants though, the act of editing a variant metafield doesn’t fire a single webhook. Just none. That’s just really poor design, if you ask me.

People all over Shopify are using variant metafields for tracking stuff like bin/shelf-numbers, ingredients, etc, and the fact that there is no webhook support for tracking updates in these fields is just not very fun to work with at all. And this has been reported for years and years.

Is there any plan to change/fix this? Is anything being done about it, or atleast looked at?

Hey @Deathmelon :waving_hand:, thanks for flagging this. I do know this is a fairly common feature request, but I’m happy to see if we can share any more info on this or confirm if it’s on the product roadmap. I can’t confirm anything specific on my end at the moment, but I’m happy to dig into this for you for sure.

I’ll loop back here when I have some more info to share :slight_smile:

Hey @Deathmelon, just following up on this! I was able to speak with our product team for you here and I can’t share too many specifics, but did want to let you know that we agree the way variant metafield updates interact with webhook triggers isn’t ideal at the moment.

I can’t guarantee exactly what a fix will look like or if/when it would be implemented, but they have opened an issue internally to look into improving the behaviour. Just wanted to share an update with you to let you know it’s on our radar.

Hope this helps a little bit!