Playbook · B2B company metafield missing
Shopify B2B company metafield missing? Prove the company owner, access, and B2B read.
Written for a Shopify Plus B2B owner whose company catalog or B2B app mounts but the company metafield it needs is missing. Start with the company / company location owner, namespace.key, access, and what B2B actually reads—not with a full catalog rebuild. This is distinct from company metafield missing (general), B2B catalog prices wrong, company location pricing wrong, and B2B catalog not showing.
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
Buy the 72-hour install — $997Catalog not showingMerchant FAQ
01
A missing company metafield is not the same bug as catalog pricing.
Use this page when B2B company surfaces load (company admin, location, or app-driven catalog rules) but the expected company metafield is absent, null, or never exposed. If buyers see wrong prices for a location, use company location pricing wrong. If the wholesale catalog is hidden, use wholesale catalog hidden.
Capture Plus plan, company ID, location ID, namespace.key, and the exact place B2B should consume the value before changing the app or catalog.
02
Prove the company owner and exact namespace.key B2B expects.
Confirm whether the field belongs to the Company, CompanyLocation, shop, or another owner the B2B app documents. A shop metafield will not appear because B2B reads a company-level key. Record one synthetic test company and its ID.
Copy the exact namespace.key, including case. Do not create a duplicate definition because its label looks identical in Admin Custom data. Distinct from the general shopify-company-metafield-missing playbook when you are debugging B2B catalog / location-specific reads.
03
Check type, B2B access, and a saved reversible test value.
Record the definition type, list or reference shape, and whether Admin / Storefront / B2B access is enabled for the surfaces company catalogs use. Save one unmistakable, reversible test value on the exact company owner, refresh Admin, and confirm it persists. If Admin itself has no value, B2B will correctly look empty.
Keep customer data, tokens, and passwords out of screenshots. Treat an absent field, null, empty string, and empty list as separate observations.
04
Inspect B2B company and location reads separately from theme Liquid.
Open company Admin, company location catalog assignment, or the app that reads company metafields and confirm which namespace.key it expects. Separate: catalog never published to the location, catalog published but metafield missing, metafield present but type mismatch, or buyer not logged into the company so the read never runs.
B2B often reads company metafields through Admin GraphQL or an app—not theme Liquid. A correct Online Store storefront value with B2B access off will look like a missing company field even when the theme shows the metafield.
05
Retest one company buyer and preserve the proof.
Use one company, one location, and one known buyer. Record company ID, location ID, namespace.key, type, saved test value, access flags, catalog/app output, and a screenshot of the logged-in buyer catalog. Hard-refresh only after the first trace is captured.
Classify the miss as owner, definition/value, access, B2B parse, or catalog pricing instead. Keep it separate from wholesale payment terms, quantity breaks, and product publish sync.
06
When to stay DIY vs pay $997.
Stay DIY when one company owner, access, or B2B-parse check explains the missing field. Keep the proof packet so future B2B or app changes are reversible.
Pay for the $997 one-time install when several Shopify surfaces, 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.