I would like use the unitPriceMeasurement field for my products, in the documentation it says that it exists under ProductVariant object but when I fetch it in Shopify GraphiQL API I cannot find it.
Someone can provide me with any information about this?
It is supposed to be only for customers in certain countries. You get that field if you are Germany for example, but not Canada. At least that is how it looked a few years ago when they introduced the unit pricing schema. Maybe it is just an oversight... I dunno. Is this released in general now?
Not sure then. A Dev Store should have everything turned on. Maybe it requires an actual setting of the API itself to turn that on. Meaning you have to ask if you want it and it won't work unless you qualify.
I tried it on a live client store which is located in Germany. The merchant has the unit prices setup and configured. Same error that I got on the dev store.
When the dev store was configured to be in a different country, the option was not available. It's only available after switching to Germany, inline with what is said here: https://help.shopify.com/en/manual/intro-to-shopify/initial-setup/sell-in-germany/price-per-unit
Who should I contact to check whether this API can be "turned on", if it needs to be?
the link you provided only talks about the integration of the unitprices in a theme that does not support them by default yet,
but not the write access to the ProductVariant fields through the api.
We are also located in Germany ourselves and face this problem every day, especially when bigger clients who want to migrate to shopify from another shop system or need to update their unitprices through an ERP-software.
It is frustrating since the api needs to exist internally (I'm pretty sure the admin-frontend also only triggers an api..) and is just not published or documented.
Calling out to the german partner manager Roman Zenner did not help yet.
The thread was discussed by a lot of people in the german partner slack channel but nothing happened.
Even noticing losing potential plus leads due to that lack of api support did not bother them.
A very sad story.
we are still hoping for the best.
It is money left on the table for sure. Not the first case, not the first time. I guess you just want to keep monitoring the API released in GQL to see when those aspects are covered.