Shopify exchange metafield missing? Prove exchange owner, namespace.key, and consumer.

Use this page when a custom metafield on an exchange (often modeled as a Return with exchange lines) is absent as a key, never defined, or never written. If the exchange record itself never creates, start with exchange not creating. If the blank is a generic return metafield after refund-only flows, use return metafield blank.

Capture one exchange/return ID, parent order ID, metafield namespace.key, Admin value state, API response field, and whether the returns portal or ops app expects that field. Do not bulk-overwrite live exchange metafields before proving the owner.

Write down that the definition is on the exchange owner your app uses (Return-as-exchange, exchange line item, or related order metafield). Confirm the ID you inspect is the same ID the returns app and consumer use, including test vs live shop and multi-line exchanges.

Use one reversible test exchange when possible. Record exchange/return ID, order ID, status, staff or app actor, and the moment the metafield should be written (create, approve, fulfill replacement). Keep customer PII and payment tokens out of screenshots and tickets.

Record the definition namespace and key exactly, including case, type, validations, list/reference shape, owner type, and app ownership. Confirm whether Admin shows a missing key, a cleared value, or never-saved. A value only in your returns-app sheet is not proof of a Shopify exchange metafield value.

Check Admin API scopes and access required to read that exchange metafield from the returns connector or ops app. Treat absent key, null, empty string, and empty list as separate observations.

Open Admin and the authorized Admin API response for the same exchange owner and key. Then compare with how the returns portal, Flow, or ops app reads them. A missing Shopify field with a populated returns-app attribute is a sync gap, not an exchange-create failure.

Separate missing definition from consumer mapping: if Admin/API shows no key, fix owner, definition, access, or write path first. If Shopify has a non-empty value but the returns app or ops view is blank, that is mapping, cache, or exchange-ID scope—not inventory alone.

Run one controlled exchange metafield write on one known test order after a reversible metafield definition or value change. Record exchange/return ID, order ID, namespace.key, type, missing vs present state, consumer read result, and API field state. Retry only after the first trace is captured.

Classify the miss as wrong owner, never-defined key, never-saved value, access, exchange-status mapping, cache, or consumer mapping. Keep it distinct from exchange not creating and return metafield blank.

Stay DIY when one owner, definition, access, exchange-status, or consumer check explains the missing field. Keep the proof packet so later exchange writes are reversible.

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