Shopify POS UI Extensions React metafield missing? Prove the React package, hooks, and tile input.

Use this page when the React package (@shopify/ui-extensions-react/point-of-sale or equivalent) should expose a metafield via hooks or declared inputs, but the value is null or omitted in the React tree. If the miss is a rendered field inside an already-loading POS UI extension without a React-package angle, use POS UI extension metafield missing. If the POS UI Extensions API payload is blank, use POS UI Extensions API metafield blank.

Capture the React package version, hook or input query, tile target, resource owner, namespace.key, and whether the miss appears in hook return data or only in JSX before redeploying.

Confirm the POS UI Extensions React code requests the metafield on the correct owner available to the tile (product, variant, customer, cart, or location). A product metafield will not appear because a hook asks for a cart field that was never declared.

Copy the exact namespace.key from Admin into the React input selection or metafield accessor. Hooks that request metafields without namespace and key, or with a typo, look like missing React fields.

In Admin, confirm the definition exists, required POS / Admin access, and a reversible test value on the same owner. If Admin has no value, POS UI Extensions React will correctly return missing.

Confirm app scopes and the installed React package version match the docs for metafield helpers you call. Keep private tokens out of screenshots and public repos.

Log or inspect the React hook return / input on a blank register. Classify: hook omits the field, API returns null, access denied, stale tile version, wrong package, or render drop. Those are different failures.

Hard-refresh after confirming the active POS tile matches the deployed React package. Do not bump ui-extensions-react or redeploy until you know whether the miss is hook, access, value, version, or JSX.

Use one known-valid location, one staff role, one React input capture, and one known owner. Record Admin value, React hook/input data, tile UI output, and package versions. Rebuild only after that packet exists.

Classify the miss as owner/hook, definition/value, access/scopes, stale tile, package mismatch, cache, or React render. Keep it separate from POS UI runtime misses, POS UI Extensions API blanks, and inventory sync failures.

Stay DIY when one React hook, access, value, tile version, or render check explains the missing field. Keep the proof packet so future POS UI Extensions React upgrades are reversible.

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