Shopify B2B catalog metafield blank? Prove the company, catalog, read path, and one B2B buyer.

Use this page when the catalog-backed or company-backed value itself is missing: Admin shows a blank B2B catalog metafield, an app never receives it, or a B2B buyer never sees the field-driven rule. If the whole catalog is hidden or empty for the company, use the B2B catalog not showing playbook instead. Company-owned metafields on the wrong company location are a separate owner path — see company metafield missing.

Do not invent a second product metafield to shadow catalog context yet. Capture the company ID, catalog ID, metafield key, and the exact B2B surface that should show the value.

Open the company in Admin and confirm which catalog is assigned to the location you are debugging. B2B catalog metafields only matter when that catalog (or company owner) is the one the buyer session resolves. A filled field on a draft catalog duplicate is not proof for the live company.

Record the exact namespace.key, type (single line, boolean, list, or reference), and save a short unmistakable test value on that owner. Refresh and confirm it survives. Note whether the definition is app-owned or merchant-owned.

Compare the saved metafield with the Admin GraphQL company/catalog query or the B2B app consumer. The read must select the same company or catalog GID and the same namespace.key. A successful company query can still omit catalog metafields, select another location, or serialize a list/reference differently than the app expects.

Verify storefront / Customer Account API access if a B2B theme or Hydrogen storefront reads it, and any catalog price list or quantity rule that depends on the metafield. Log field presence without logging secrets.

B2B metafields are context-sensitive. Record the company ID, location, catalog ID, buyer contact, presentment currency, and whether the session is Company location checkout vs Online Store. Confirm the metafield belongs to that catalog/company context and that the buyer is actually on the company you edited.

Keep the diagnosis distinct from the Shop Pay Installments API metafield missing path and from wholesale payment-terms bugs. They can affect checkout while reading different owners.

Use one company location and one catalog. Record the company ID, catalog ID, namespace.key, type, saved test value, app/API field presence, and whether the B2B buyer UI shows the field-driven behavior. Repeat as the company buyer (not staff), then test a second location only after the first path is proven.

If the field is still blank, classify it as wrong owner, definition/value, access/query, wrong catalog assignment, or type parsing. Do not call a price-list failure until the metafield input value is demonstrably present.

Stay DIY when one catalog assignment, saved metafield, Admin query, or B2B session check explains the blank. Keep the proof packet so future B2B catalog migrations are reversible.

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