Shopify delivery promise metafield blank? Prove the owner, value, read path, and one in-zone checkout.

Use this page when the value itself is missing: a definition is empty, an app shows blank data, or the theme/app never receives the field you expected. If delivery promise is missing because radius or postal codes are wrong, use the estimated delivery wrong playbook instead. Carrier pickup points and Delivery Customization Functions are separate paths.

Do not add a second metafield or install another delivery app yet. Capture the shop, location, postal code, cart, and exact surface where the value is supposed to appear.

Open Settings → Custom data and confirm the definition is owned by the resource your implementation reads — often a Location, Shop, Order, or Delivery method record. Record the exact namespace and key, for example delivery.local_note, the type, validations, and whether it is a plain value, list, reference, or JSON value.

Open the exact location or delivery record used for delivery promise. Save a short unmistakable test value, refresh, and confirm it survives. A filled definition on the wrong location, a draft theme copy, or a label that only looks right is not proof.

Compare the saved definition with the Admin API query, Liquid/metaobject read, or delivery-app sync. The query must select the same namespace.key on the same resource, and the app must have the intended access scope. A successful request can still omit metafields, select another location, or serialize a reference/list differently than the code expects.

Verify the published Online Store theme and the active delivery app version. Log field presence without logging customer addresses or secrets. If a plain text test arrives but the intended reference does not, fix type-specific parsing rather than changing estimated-date arithmetic.

Delivery promises are context-sensitive. Record the market, currency, destination postal code, cart contents, shipping profile, and whether the selected fulfillment location has processing and transit inputs. Confirm the metafield belongs to that location context and that the current checkout profile is the one published to buyers.

Keep the diagnosis distinct from the pickup point metafield and delivery customization metafield paths. They can affect the same checkout while reading different resources and fields.

Use one cart and one destination for the intended destination. Record the resource ID, namespace.key, type, saved test value, theme/app version, read-path field presence, and whether the delivery promise and any custom instruction appear. Repeat logged out if the result is customer-facing, then test a second postal code only after the first path is proven.

If the field is still blank, classify it as definition/value, access/query, location context, unpublished theme/app, or type parsing. Do not call a zone-radius failure until the input value is demonstrably present.

Stay DIY when one definition, saved value, read-path query, or published-version check explains the blank. Keep the proof packet so future delivery changes are reversible.

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