The metaobject definition is locked — you cannot edit fields or entries.

Several “custom data” products can look like “I cannot edit this.” They do not share a fix. This page is only when a metaobject definition (type) is locked so you cannot change its field schema and/or cannot create or edit entries in admin. Customer metafield Save failing on Customers → customer is customer-metafield-not-saving. Automated / smart collection rules not matching products is shopify-collection-rules-not-matching. Translation API / Markets locales missing strings is shopify-translation-api-missing-locale.

Soft links when the bug is adjacent: entries exist but never appear on OS 2.0 / Hydrogen is shopify-metaobjects-not-showing. Product/variant metafields not rendering on storefront is shopify-metafields-not-showing-on-storefront. Product metafields definition / dynamic sources is product-metafields-not-showing. This playbook stays on Settings → Custom data → Metaobjects → definition locked / app-owned → cannot edit fields or entries.

Open Settings → Custom data → Metaobjects. Open the locked type. Record the type handle, display name, Access (Admin / Storefront), and any Managed by / Owner label naming a Partner app. App-owned definitions intentionally lock the field schema so merchants cannot break the app’s contract.

Attempt three edits and capture results: (1) Add or rename a field on the definition, (2) Create a new entry, (3) Edit an existing entry’s field values. Note whether fields are greyed out vs entries editable. Capture the admin toast or GraphQL Admin API error (DEFINITION_LOCKED, ACCESS_DENIED, TAKEN). Confirm your staff role includes Custom data / Metaobjects — limited collaborators often cannot edit definitions.

Soft-check: if the definition is editable but storefront never shows entries, leave this page and use shopify-metaobjects-not-showing. If the Save failure is on a Customer metafield, use customer-metafield-not-saving.

If an app owns the definition, edit schema and entries in that app’s admin — or accept entry-only access if the app allows values but not field changes. Do not uninstall casually; uninstalling an app-owned definition can delete its entries. Contact the app vendor only if their UI also blocks edits you need.

If you need a merchant-owned schema, create a new merchant-owned metaobject definition with the fields you control, migrate or recreate entries, then re-bind theme dynamic sources, product/page reference metafields, and any Hydrogen Storefront API selections to the new type. Keep Storefront access enabled on fields the theme reads.

Retest: merchant-owned definitions should allow Add field + Save entry; app-owned definitions should at least allow the edits the app documents. Soft notes: storefront blanks after a successful Save belong on shopify-metaobjects-not-showing. Collection membership bugs belong on shopify-collection-rules-not-matching. Locale / translation gaps belong on shopify-translation-api-missing-locale.

Customer metafield not saving is customer-metafield-not-saving. Collection rules not matching is shopify-collection-rules-not-matching. Translation API missing locale is shopify-translation-api-missing-locale. Metaobjects not showing on storefront is shopify-metaobjects-not-showing. Metafields on storefront is shopify-metafields-not-showing-on-storefront.

The only honest test for this page: staff with Custom data access → open the metaobject definition → confirm Owner / Managed by → attempt field edit and entry Save → either unlock via owning app / merchant-owned clone or document the intentional app lock. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove ownership, capture the lock error, edit via the owning app or create a merchant-owned definition and re-bind theme sources, retest entry Save. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: metaobjects not showing, customer metafield not saving, collection rules, Translation API, metafields on storefront.

Pay for help when the work is not the definition lock itself — it is connecting the stack you already have so lead capture is not dying in DMs, storefront and custom-data 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 metaobject-uptime 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.