Admin metafield definition is locked.

Several “metafield” bugs look alike. They do not share a fix. This page is only when the metafield definition itself is locked in Admin Custom data. Customer metafield value Save failing on Customers → customer is customer-metafield-not-saving. Metaobject definition locked (entries / type managed by an app) is shopify-metaobject-definition-locked. Metafields defined but blank on the Online Store is shopify-metafields-not-showing-on-storefront.

Soft links when the bug is adjacent: product metafields not showing on PDP is product-metafields-not-showing. Metaobjects not showing is shopify-metaobjects-not-showing. This playbook stays on Settings → Custom data → Metafields → definition locked / app-owned → merchant cannot edit definition schema.

Open Settings → Custom data → Metafields (product, variant, customer, order, shop, or other resource). Open the definition. Note whether Shopify shows Managed by app / Owner. Copy namespace.key. If Edit definition is greyed or Save is rejected with an ownership error, you have a definition lock — not a value-entry bug.

Soft-check staff permissions: some roles can view Custom data but cannot change definitions. Soft-check that you are not on a Markets / translated admin surface that only shows read-only copies. Soft-check Storefront API access toggles separately — those control storefront exposure, not whether Admin lets you edit the definition schema.

If values on a customer card refuse to Save while the definition edits fine, switch to customer-metafield-not-saving. If the lock is under Metaobjects (not Metafields), use shopify-metaobject-definition-locked.

If an app owns the definition, change fields in that app’s admin UI or reconfigure / uninstall intentionally — do not fight Shopify’s lock. Fighting an app-owned definition usually breaks the app’s expected schema. For merchant-owned content you need to control: create a merchant-owned metafield definition with the type and validations you need, migrate values (CSV / Admin API / bulk editor), and re-bind theme dynamic sources or Hydrogen queries to the new namespace.key.

Honest retest: open the definition → Edit fields / validations → Save succeeds when merchant-owned → sample resource shows the new definition → storefront (if needed) still maps. If Save of a customer value fails while the definition edits, switch to customer-metafield-not-saving. If values exist in Admin but theme shows blank, use shopify-metafields-not-showing-on-storefront.

Customer metafield not saving is customer-metafield-not-saving. Metaobject definition locked is shopify-metaobject-definition-locked. Metafields not showing on storefront is shopify-metafields-not-showing-on-storefront. Product metafields not showing is product-metafields-not-showing. Metaobjects not showing is shopify-metaobjects-not-showing.

The only honest test for this page: Settings → Custom data → Metafields → open definition → you can (or cannot) edit and Save the definition schema, with ownership proven. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove app ownership, separate value-Save from definition lock, separate metafields from metaobjects, clone to merchant-owned when needed, re-bind theme sources, retest definition Edit / Save. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: customer metafield not saving, metaobject definition locked, metafields not showing on storefront.

Pay for help when the work is not the definition screen itself — it is connecting the stack you already have so metafield / custom-data / app-definition exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever metafield-definition guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.