Yes, that's correct. Since there can be all kinds of data stored in metafields, we are requiring developers to be intentional about what is exposed to the Storefront API. These restrictions do not apply to Admin API, since the merchants authorize tha...

So, the main issue here is the usage of the Storefront API. As that API has a different set of access scopes than Admin API, we require an additional step to expose product metafields to it. There's a tutorial for it. Because of that, there might be ...

So, that tutorial isn't very clear. The UI for editing the metafield value is provided by the sales channel app through the use of Admin Link app extension. The tutorial for doing that is here. So, your sales channel app needs to create the UI that a...

Hello,   How would the merchant fill in the value? Is that something that is happening through the UI of your sales channel?

Of course, no problem.   This is the general GraphQL page that has pointers to many resources. This is the specific Admin GraphQL API reference you can use.  Also, you do not need to change your code wholesale. You can start using the GraphQL API for...

Hello there,   Have you considered using the Admin GraphQL API? It's possible that it'll reduce the number of calls you have to make to synchronize product and product metafields' data.   { products(first: 50) { edges { node { # ...