Shopify webhook metafield blank? Prove the topic, owner, empty value, and payload path.

Use this page when delivery logs show a successful (or attempted) POST whose body includes the expected metafield key but the value is empty, null, or whitespace. If the subscription itself is misconfigured or the metafield never appears on the subscription resource, start with webhook subscription metafield blank. If HMAC fails, the endpoint 4xx/5xx, or the topic never fires, fix delivery first—not the metafield value.

Capture one delivery ID, topic, shop, endpoint URL, HTTP status, HMAC pass/fail, the exact JSON path, and whether the body shows blank, null, empty string, or whitespace-only. Do not overwrite a live value before proving the owner the webhook payload references.

Write down the webhook topic, destination URL, API version, and the JSON path your handler reads. Confirm the delivery is for the shop and resource ID you expect. A blank value on a different order/product/customer in the same topic stream is not a definition bug.

Use one synthetic, reversible test resource. Record its ID, the delivery timestamp, the raw body (redacted), and the handler log line. Keep customer data, credentials, and private 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 label that looks right or a value on a different resource is not proof.

Check whether the webhook topic includes metafields for that owner, or whether your app must fetch the metafield after receiving the base payload. Treat absent key, null, empty string, and empty list as separate observations. Do not paste secrets into webhook notes or handler comments.

Open the live delivery body and compare the field path with your parser. Verify the topic payload actually includes metafields (some topics omit them unless requested via metafield namespaces or a follow-up Admin API read). A stale cache, wrong API version, or handler that collapses blank can make a saved Admin value look empty.

Separate blank input from parser failure: if the webhook JSON shows empty for the field, fix owner, definition, access, saved value, or follow-up fetch first. If the JSON contains a non-empty value but your app stores blank, that is a mapping or deserialization issue—not a blank metafield.

Trigger one known-valid resource for the topic. Record topic, delivery ID, owner ID, namespace.key, type, saved vs blank state, payload field state, HTTP status, and handler path. Retry only after the first trace is captured.

Classify the miss as delivery/HMAC, owner/topic mismatch, never-saved value, cleared value, access, field path, type parsing, missing follow-up fetch, or handler mapping. Keep it distinct from a subscription-config blank and from an app-proxy blank response.

Stay DIY when one topic, payload path, owner, definition, access, or handler check explains the blank. Keep the proof packet so later webhook 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 webhook metafield path in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.