Shopify Markets Pro metafield missing? Prove the market owner, value, read path, and one cross-border checkout.

Use this page when the value itself is missing: a Market metafield definition is empty, an app shows blank market data, or Markets Pro tooling never receives the field. If landed cost / duties at checkout disagree with expected totals while the input fields are present, use the Markets Pro duties mismatch playbook instead. Non-Pro Markets storefront metafields are covered separately.

Do not add a second market metafield or toggle Managed Markets off yet. Capture the market name, country, currency, cart, and exact surface where the value should appear.

Open Settings → Custom data and confirm the definition is owned by the resource your Markets Pro app or Admin query reads — often a Market, MarketWebPresence, or related Markets resource — not a Product or Shop fallback. Record the exact namespace and key, the type, validations, and whether it is a plain value, list, reference, or JSON value.

Open the exact market used for the international checkout. Save a short unmistakable test value, refresh, and confirm it survives. A filled definition on a primary domestic market, a draft market, or a label that only looks right is not proof.

Compare the saved definition with the Admin API markets query or Markets Pro app sync. The query must select the same namespace.key on the same market GID, and the app must have the intended access scope. A successful request can still omit metafields, select another market, or serialize a reference/list differently than the code expects.

Verify Markets Pro / Managed Markets is active for the destination, and that the app version reading the field is the one currently installed. Log field presence without logging customer addresses or tax IDs. If a plain text test arrives but the intended reference does not, fix type-specific parsing rather than changing duty settings.

Markets Pro behavior is context-sensitive. Record the market, presentment currency, destination country, cart contents, shipping profile, and whether duties/import taxes are expected for that lane. Confirm the metafield belongs to that market context and that the buyer is actually in the market you edited.

Keep the diagnosis distinct from the Markets metafield blank and product taxonomy metafield blank paths. They can affect the same international catalog while reading different owners.

Use one cart and one destination country for the intended market. Record the market ID, namespace.key, type, saved test value, app version, read-path field presence, and whether Markets Pro surfaces (duties line, market note, app panel) reflect the value. Repeat in an incognito window with the market country forced, then test a second country only after the first path is proven.

If the field is still missing, classify it as definition/value, access/query, wrong market owner, Markets Pro not enabled for that lane, or type parsing. Do not call a duties mismatch until the input value is demonstrably present.

Stay DIY when one definition, saved value, market query, or Markets Pro status check explains the blank. Keep the proof packet so future market changes are reversible.

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