We are migrating products from our client’s online store to Shopify using the latest API version 2023-10. The product attributes are migrated as metafields, and we just noticed a serious problem with metafield definition and access settings since the API version 2023-01 to 2023-10. There are some i…

Hello, You should be able to create a metafield definition in a non app reserved namespace (e.g. “custom”) as long as you are not setting a value for the access input. If you do not use a reserved namespace, the merchant and other apps should be able to edit the definition and set metafield values. …

How should I go about creating a definition in a “custom” namespace with storefront access?? EDIT/UPDATE: So it seems that creating the namespace with “$app:custom” is the answer

That is correct. Prefixing a namespace with “$app:” produces a metafield definition in a reserved namespace that is owned by the app that created it. The owning app has full control over the definition including the definition’s admin and storefront access settings. Apps can also create non-reserve…

@JohnBerry Do you know we will be able to create non-reserved namespace metafields for any owner type? I would like to create a shop metafield as a non-reserved namespace metafields, but it seems like there’s no way to currently define it from the Shopify Admin.

Shop metafields can be created using the metafieldDefinitionCreate Admin API mutation with an ownerType = SHOP. Shop metafields cannot be created through the Admin interface.

A non app reserved namespace with no access input is the best solution :+1: . *Note: if anyone is trying this solution, remember to use the API stable versions, as it doesn’t work with the “Unstable” versions. Thank you so much, John!

Hi. Is there a way to access a product image metafield from the storefront api and liquid? I defined it with [storefront] => PUBLIC_READ access, but I can’t find any query to access it. The image object in the back end include metafields, but not the one in the front end. Thanks

Within an app, I attempted to create a metafield definition with the following settings: metafieldDefinitionCreate(definition: { name: “Custom Test”, namespace: “customtest”, key: “config”, type: “json”, ownerType: SHOP access: { admin: MERCHANT_READ_WRITE storefront: PUBLIC_READ } }) { …

Hi :slightly_smiling_face: The issue is now : by default storefront access is set to “LEGACY_LIQUID_ONLY” instead of “PUBLIC_READ” and there is no way to update access of no-owned metafields. The default value should be set to “PUBLIC_READ” by default like metafieldStorefrontVisibilityCreate did …

Yes but by default storefront access is set to “LEGACY_LIQUID_ONLY” instead of “PUBLIC_READ” Metafields will not be accessible by the Storefront API unless merchant is going trough admin to change itself to “Read” which is adding more steps than before. did you figured out a solution ?

Metafield definition and access settings, this is a big problem

Shopify Discussion

tuzmusic January 7, 2025, 6:03pm 16

@SoumenDana do we need “unauthenticated” or is that just something you were trying? (Note: Soumen is my colleague in this project)

Topic		Replies	Views
Error on creating shopify metafield definition Metafields optimization , troubleshooting , Setting-Up	3	87	September 9, 2024
Metafield definitions for owner type SHOP not accessible in admin Metafields troubleshooting	9	238	July 17, 2024
Access denied for access field on metafieldDefinition Technical Q&A migration , javascript	4	459	June 21, 2025
Metafield definition StorefrontAPI visibility management Metafields troubleshooting , Setting-Up	3	82	June 4, 2024
app cannot create theme/storefront-accessable metafields Shopify Apps third-party-apps	0	30	October 27, 2024

Metafield definition and access settings, this is a big problem

Related topics