Playbook · Customer Account UI Extensions metafield blank
Shopify Customer Account UI Extensions metafield blank? Prove the TOML set, shared inputs, and published version.
Written for a Shopify owner whose Customer Account UI Extensions (plural) metafields stay blank across more than one account target. Start with shopify.extension.toml targets, shared metafield inputs, published extension set, and one account surface—not with a full account rebuild. This is distinct from Customer Account UI extension metafield blank (single extension runtime), from Customer Account UI API metafield missing, and from extension missing.
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
01
A blank across Customer Account UI Extensions is not the same bug as one extension field miss.
Use this page when more than one Customer Account UI Extensions target should share or expose a metafield, but the value is null or omitted in the set (profile, order status, full-page, or block targets). If only one already-mounting extension reads blank, use Customer Account UI extension metafield blank. If the Customer Account UI API payload is the miss, use Customer Account UI API metafield missing.
Capture every extension handle, target, TOML path, shared input declaration, and whether the blank appears in one target or every published target before redeploying.
02
Prove TOML targets, shared metafield inputs, and exact namespace.key.
Open each shopify.extension.toml (or equivalent) and list which targets declare the metafield input. A field declared on a profile block will not appear on an order-status full-page that never requests it.
Copy the exact namespace.key into every shared input that should read it. Mixed casing, missing namespace, or a typo in one TOML of the set makes the plural Extensions surface look inconsistently blank.
03
Check access, saved value, and which targets are allowed to read it.
In Admin, confirm the definition exists, customer-account access as required, and a reversible test value on the same customer. If Admin has no value, every Customer Account UI Extensions target will correctly return blank.
Confirm app scopes and metafield access flags allow the Customer Account UI Extensions set to read that field. Keep private tokens out of screenshots and public repos.
04
Inspect the published extension set vs the local workspace separately.
Compare Partners / Admin published Customer Account UI Extensions version with local TOML and input queries. Classify: one target omits the field, all targets return null, access denied, stale published set, or render drop in one target only.
Hard-refresh after confirming the published set matches the workspace you just edited. Do not bump API versions or redeploy the whole app until you know whether the miss is TOML, access, value, publish, or JSX.
05
Retest one account surface across the extension set and preserve the proof.
Use one known-valid customer account, one published set, and the targets that should show the field. Record Admin value, each target input presence, UI output, and package versions. Rebuild only after that packet exists.
Classify the miss as TOML/target, definition/value, access/scopes, stale publish, cache, or React render. Keep it separate from single-extension blanks, Customer Account UI API misses, and login failures.
06
When to stay DIY vs pay $997.
Stay DIY when one TOML target, access, value, publish, or render check explains the blank across the Extensions set. Keep the proof packet so future Customer Account UI Extensions upgrades are reversible.
Pay for the $997 one-time install when several Shopify surfaces, account extensions, 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.