2027-01 or later, every metafield declaration in shopify.extension.toml must specify owner_type. The property is already supported in 2026-10. Add it before upgrading to prevent deployment validation failures.On this page
What changed
On October 8, 2026, Shopify announced explicit resource ownership for UI extension metafield declarations. A namespace and key alone do not tell Shopify whether you need a product, customer, or another supported resource’s metafield. The owner_type field makes that relationship explicit so Shopify can fetch only relevant data.
The change affects declarations under both [[extensions.metafields]] and [[extensions.targeting.metafields]]. It does not require every UI extension to add metafields: if your extension declares none, this requirement does not apply.
Fix the TOML, not the runtime JavaScript
Find every metafield declaration in each extension configuration. Identify the resource that owns the field and set the correct owner_type. For example, a product-owned field can be declared as follows:
[[extensions.metafields]]
namespace = "custom"
key = "gift_message"
owner_type = "PRODUCT"
Use the owner that actually contains your field; do not copy PRODUCT into a declaration for a customer field. If the same namespace/key pair is required from multiple resource types, create separate declarations, one for each owner type. Review target-specific declarations as well as extension-wide ones.
Upgrade safely
First add the declarations while still on 2026-10, where Shopify already accepts them. Run the app deployment validation and preview the extension with data from the expected owner. Then update the API version and deploy again. This isolates configuration mistakes from other API-version changes.
Do not mistake this requirement for the earlier checkout-metafield migration. Checkout metafields were replaced by cart/order metafields for affected extension APIs; owner_type is about declaring the owner of fields the extension reads.
owner_type.How to test this
- Search all
shopify.extension.tomlfiles for both metafield declaration forms. - For each declaration, verify the actual owner resource and add the corresponding
owner_type. - Deploy or validate on API
2026-10first, and confirm the extension reads the expected field. - Upgrade a development extension to
2027-01and confirm deployment passes validation. - Preview checkout and customer account targets with populated and missing metafield values to check fallbacks.

