Shopify Multipass metafield blank? Prove customer owner, namespace.key, access, and SSO consumer.

Use this page when a custom metafield used by Multipass token building, post-login apps, or account sync is present as a key but empty, null, or whitespace. If SSO login itself fails (bad token, wrong secret, return_to mismatch), start with Multipass login failing. If classic or new customer accounts loop on login, use account login loop.

Capture one customer ID, shop, Multipass endpoint, metafield namespace.key, Admin value state, API response field, and whether the token claim or downstream app expects that field. Do not rotate the Multipass secret or overwrite live customer data before proving the owner.

Write down that the definition is on the customer (or confirm the true owner if your app maps another resource). Confirm Plus Multipass is enabled, the shop domain matches the secret, and the customer record you inspect is the same ID the token encodes.

Use one synthetic, reversible test customer. Record its ID, email domain (redacted), the claim name your identity provider maps, and keep passwords, Multipass secrets, and raw tokens out of screenshots and logs.

Record the definition namespace and key exactly, including case, type, validations, list/reference shape, owner type, and app ownership. Confirm whether Admin shows a saved value, a cleared value, or never-saved. A value in your IdP, CRM, or JWT payload alone is not proof of a Shopify customer metafield value.

Check Admin API scopes and access required to read that customer metafield from the token builder or post-login app. Treat absent key, null, empty string, and empty list as separate observations.

Open Admin and the authorized Admin API response for the same customer and key. Then compare with how your Multipass token builder serializes claims and how the post-login app reads them. A blank Shopify field with a populated IdP attribute is a sync gap, not a Multipass crypto failure.

Separate blank input from login failure: if Admin/API shows empty, fix owner, definition, access, or saved value first. If Shopify has a non-empty value but the claim or app is blank, that is mapping, encoding, or cache—not Multipass secret rotation.

Issue one controlled Multipass login for one known test customer after a reversible metafield write. Record customer ID, namespace.key, type, saved vs blank state, claim presence, login result, and API field state. Retry only after the first trace is captured.

Classify the miss as wrong owner, never-saved value, cleared value, access, claim mapping, cache, or consumer mapping. Keep it distinct from Multipass login failing and account login loops.

Stay DIY when one owner, definition, access, channel, or consumer check explains the blank or missing field. Keep the proof packet so later edits are reversible.

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