Shopify Adds Required owner_type Field for Metafield Declarations in UI Extensions

What Changed

Shopify has introduced a new owner_type field for metafield declarations in Checkout and Customer Account UI extensions, starting with API version 2026-10. This field applies to metafield declarations inside [[extensions.metafields]] and [[extensions.targeting.metafields]] blocks within the shopify.extension.toml configuration file.

The owner_type property specifies which resource owns a given metafield, such as product, customer, order, or other supported owner resources. Currently, this field is optional, allowing developers to adopt it ahead of the enforcement deadline.

Beginning with API version 2027-01, owner_type becomes a required field for every metafield declaration. Deployments that omit this field will be blocked starting with that API version.

Why This Matters for Developers

Metafields can be attached to multiple resource types across the Shopify admin. Without explicit ownership declarations, extensions relying on metafields may encounter ambiguity about which resource a given metafield value belongs to, particularly in cases where metafield keys and namespaces overlap across different owner types.

By requiring owner_type, Shopify aims to reduce configuration errors and ensure metafield declarations resolve correctly at runtime, improving reliability for checkout and customer account customizations.

Practical Implications

Developers maintaining Checkout or Customer Account UI extensions should audit their shopify.extension.toml files and add owner_type to existing metafield declarations now, rather than waiting until the 2027-01 deadline.

Teams building extension templates, starter kits, or CLI scaffolding tools should update their boilerplate to include owner_type by default. Testing deployments against API version 2026-10 ahead of time can help identify any metafield declarations missing this field before the requirement becomes enforced.

Read the full announcement →