Shopify customer account UI extension metafield blank? Prove the owner, value, input, and active version.

Use this page when the extension mounts or its surrounding customer account UI is available, but the expected customer field is empty, null, omitted, or not reflected in the account UI. If the block never appears, use the extension missing playbook. If the customer cannot authenticate or is redirected, use the customer accounts login playbook.

Capture the account surface, extension target, customer ID, field path, and the exact surface where the value should appear before changing the app or account editor.

Confirm the field belongs to the customer object used by the logged-in new customer account. A product or company metafield will not appear because a customer extension asks for a customer field. Record one synthetic test customer and its ID.

Copy the exact namespace.key, including case, and verify the extension reads the same owner in the live account context. Do not add a duplicate definition because its label looks identical.

Record the definition type, validations, list or reference shape, app ownership, and customer-account access settings. Save one unmistakable, reversible test value on the exact customer, refresh the account, and confirm it persists. A populated definition alone is not proof the extension can read it.

Keep customer data, tokens, and passwords out of screenshots and logs. Treat an absent field, null, empty string, and empty list as separate observations.

Open the extension input query and verify it selects the same customer owner and namespace.key. Confirm the app has the intended access, the extension version is active, and the published customer account profile uses that version. A draft query, stale generated schema, wrong owner, or inactive version can make a correct Admin value look blank.

Trace input presence separately from rendering. If the field is present in input but absent in the UI, that is a rendering or parsing issue—not proof that the metafield is missing.

Use one customer, one account surface, and one extension version where the block is known to mount. Record customer ID, namespace.key, type, saved test value, input field state, active version, and rendered output. Hard-refresh only after the first trace is captured.

Classify the miss as owner, definition/value, access, query, type parsing, inactive version, or rendering. Keep it separate from account login and extension boot failures.

Stay DIY when one owner, definition, access, query, or active-version check explains the blank field. Keep the proof packet so future customer-account changes are reversible.

Pay for the $997 one-time install when several Shopify surfaces, apps, markets, 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.