Simplifying how metafield and metaobject permissions work

In the new year we’re simplifying how metafield and metaobject permissions work. This makes the system easier to work with and will further improve API response times.

In summary:

• On Jan 1, 2025, the 2025-01 admin API will remove both private and public permissions for app-reserved metafields and metaobjects from all mutations.
• On Feb 1, 2025, across all API versions, we will fully remove private permissions for app-reserved metafields and metaobjects. We will migrate all existing metafields and metaobjects to be merchant readable automatically. All metafields and metaobjects will also become accessible in liquid.
• On Apr 1, 2025, across all API versions, we will fully remove public permissions for app-reserved metafields and metaobjects.We will migrate all existing metafields and metaobjects to be only accessible by your app and the merchant automatically.

Details below:

On Jan 1, 2025:

• The following inputs to app-reserved metafield and metaobject API mutations will be removed in 2025-01: PRIVATE, PUBLIC_READ, PUBLIC_READ_WRITE
• The following outputs from app-reserved metafield and metaobject API queries will be removed in 2025-01: LEGACY_LIQUID_ONLY
• Otherwise, existing queries and data will continue to support these removed input types

On Feb 1, 2025:

• The following outputs from app-reserved metafield and metaobject API queries will be removed across all versions:PRIVATE
• Existing app-reserved metafields and metaobjects permissions will be migrated: PRIVATE → MERCHANT_READ
• All metafields and metaobjects will become accessible in liquid

On Apr 1, 2025:

• The following outputs from app-reserved metafield and metaobject API queries will be removed across all versions:PUBLIC_READ and PUBLIC_READ_WRITE
• Existing app-reserved metafields and metaobjects permissions will be migrated:PUBLIC_READ → MERCHANT_READ and PUBLIC_READ_WRITE → MERCHANT_READ_WRITE