Playbook · Customer Account API metafield missing
Shopify Customer Account API metafield missing? Prove the customer owner, value, API query, and one live account page.
Written for a Shopify DTC owner whose Customer Account API metafield or custom field exists in Admin but is blank in a Customer Account UI extension, app, or live new-customer-accounts page. Start with the customer owner, exact namespace.key, saved value, and one signed-in account surface. This is not a missing UI extension block, and it is not “customer metafield not saving” in Admin alone.
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
Buy the 72-hour install — $997UI ext fieldAdmin saveMerchant FAQ
01
A missing Customer Account API field is not automatically a missing UI extension.
Use this page when the value itself is missing: a definition is empty, Admin shows no value, or the Customer Account API / extension never receives the field you expected. If the extension target never mounts at all, use the customer account UI extension missing playbook instead. If Admin will not persist the value, use customer metafield not saving.
Do not add a second metafield or reinstall the account app yet. Capture the shop, customer ID, account type (new vs classic), extension target, and exact surface where the value is supposed to appear.
02
Prove the customer resource, definition, and exact saved value.
Open Settings → Custom data and confirm the definition is owned by Customer. Record the exact namespace and key, for example account.loyalty_tier, the type, validations, and whether it is a plain value, list, reference, or JSON value.
Open the exact customer used in the live account test. Save a short unmistakable test value, refresh, and confirm it survives in Admin. A filled definition on a different customer, a draft extension, or a label that only looks right is not proof.
03
Check access, type, namespace.key, and the Customer Account API query together.
Compare the saved definition with the Customer Account API query and UI extension code. The query must select the same namespace.key on the authenticated customer, and the app must have the intended Customer Account API scopes plus any protected customer data approval. A successful Admin request can still omit metafields from the Customer Account API when access or type is wrong.
Verify the deployed extension version and the target (profile, order index, order status, and so on). Log field presence without logging secrets or PII. If a plain text test arrives but the intended reference does not, fix type-specific parsing rather than rebuilding login.
04
Trace one account page, auth session, and published extension path.
New customer accounts are session-sensitive. Record whether the shop uses new customer accounts, the signed-in customer ID, the extension target, and whether the buyer is on the published extension version. Confirm the metafield belongs to that customer context and that classic account Liquid is not the surface under test.
Keep the diagnosis distinct from the customer account UI extension metafield blank and customer accounts login broken paths. They can affect related account UX while reading different resources and fields.
05
Retest one customer and keep a small proof packet.
Use one customer and one account page. Record the customer ID, namespace.key, type, saved test value, extension version/target, API field presence, and whether the live account surface shows the expected output. Sign out and back in only after the first trace is captured, then test a second customer only after the first path is proven.
If the field is still missing, classify it as definition/value, access/query, protected customer data, extension target, unpublished version, or type parsing. Do not call a missing UI extension failure until the API value is demonstrably present.
06
When to stay DIY vs pay $997.
Stay DIY when one definition, saved value, Customer Account API query, or published-extension check explains the miss. Keep the proof packet so future account changes are reversible.
Pay for the $997 one-time install when several Shopify surfaces, apps, 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.