Shopify Sidekick metafield blank? Prove the owner, value, Admin context, and one live prompt.

Use this page when Sidekick loads and responds, but it cannot see a metafield you expect on the open product, shop, or order. If Sidekick itself is missing, blank, or not responding at all, use the Sidekick not available playbook instead. If product copy AI fails while metafields are fine, use Magic AI not working.

Do not create a second metafield or reinstall Sidekick yet. Capture the shop, resource ID, staff role, market, exact namespace.key, and the prompt where Sidekick should cite the value.

Open Settings → Custom data and confirm the definition is owned by the same resource Sidekick has in context (Product is the common case). Record the exact namespace and key, for example ops.care_notes, the type, validations, and Admin visibility.

Open that exact resource in Admin. Save a short unmistakable test value, refresh, and confirm it survives in the metafields panel. A filled definition on a different variant, draft product, or unrelated shop metafield is not proof Sidekick can read the open context.

Compare the saved definition with what Sidekick can access for that staff user. A successful Admin save can still look blank to Sidekick when the field is Admin-hidden, the type is opaque (file/json without a readable summary), or the prompt never names the field Sidekick should use.

Verify Sidekick is enabled for the shop and the current staff account, then ask one direct question that names the metafield label or namespace.key. Log field presence without logging secrets. If Admin shows the test value but Sidekick still says it is empty, fix access/context rather than rewriting the whole product catalog.

Sidekick answers are context-sensitive. Record which Admin page is open, the resource ID, market/catalog context if relevant, and whether the staff role can read custom data. Confirm you are not testing Sidekick on a list view while the metafield only exists on a detail page Sidekick does not have loaded.

Keep the diagnosis distinct from product metafields not showing on the storefront and admin block extension metafield blank. Those can look similar while reading different surfaces.

Use one resource and one prompt. Record resource ID, namespace.key, type, saved test value, staff role, Sidekick availability, and whether the answer cites the test value. Repeat in a private Admin window, then test a second resource only after the first path is proven.

If Sidekick is still blank on the field, classify it as definition/value, Admin access, unsupported/opaque type, wrong resource context, staff permissions, or Sidekick product limitation. Do not call a Sidekick outage until the metafield is demonstrably present on the open resource and Sidekick itself is responding.

Stay DIY when one definition, saved value, staff permission, or Admin-context check explains the blank. Keep the proof packet so future Sidekick prompts stay grounded in real metafields.

Pay for the $997 one-time install when several Shopify surfaces, apps, catalogs, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can connect the agreed workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.