Playbook · Shopify company metafield missing
Shopify company metafield missing? Prove the B2B resource, value, and buyer context.
Written for a Shopify B2B owner whose company-level metafield is saved in admin but missing for the buyer. Start with Company custom data and the exact namespace/key. Then prove the intended company, company location, buyer context, access boundary, rendering path, and logged-out or buyer-safe output. This is not a customer metafield save failure and not a company-location catalog price problem. DIY first. No earnings claims or invented case studies.
Nico at Latch AI Ops · Sep 16, 2026 · ~8 minute read
Buy the 72-hour install — $997Customer fieldLocation pricingMerchant FAQ
01
A Company metafield is not a Customer field.
Use this page when a value belongs to a Shopify B2B company and the intended buyer experience renders nothing. The resource matters: company.metafields is not customer.metafields, shop.metafields, or a company-location catalog price.
A value can be present in admin while the buyer-facing path has no company context. Keep the diagnosis separate from customer metafield not saving and B2B company-location pricing wrong.
02
Prove Company custom data before editing output.
Open Settings → Custom data → Companies and record the exact namespace and key, for example custom.account_note. Note the type, list setting, validations, and whether an app owns the definition. A display label is not the identifier a theme or app reads.
Open the exact company record, confirm the field has a non-empty value, save, refresh, and record the company ID. Do not treat a value on a customer contact, company location, import file, or app dashboard as proof that the Company resource has the value.
03
Verify the company, location, and buyer context.
Identify the buyer account, the company they belong to, and the active company location. B2B sessions can switch companies or locations; a field attached to Company should not be silently replaced by a location-specific value. Reproduce the issue with a safe test account that has the intended relationship.
Check the current channel, customer-account mode, app scopes, storefront access, and any privacy rules that limit company data. Do not weaken access controls or render private pricing, contacts, or internal notes to an unauthenticated visitor just to make a field appear.
04
Trace the theme, app, or API output.
For an Online Store 2.0 block, inspect the dynamic-source picker on the current B2B template. For Liquid or an app, verify the actual Company resource and namespace/key rather than guessing from the label. For headless storefronts, confirm the buyer identity and the API query are authorized to request that field.
Classify the blank: wrong resource, empty value, wrong company, wrong location, missing permission, unbound source, type mismatch, conditional hiding, or stale published configuration. Avoid copying private values into page source, logs, analytics, or public markup.
05
Retest the exact buyer-safe production path.
- Record the company ID, namespace.key, type, active company location, and current theme or app version.
- Publish the agreed configuration, then reproduce with the intended buyer account and a separate logged-out visitor where the field is meant to be public.
- Inspect only redacted DOM, network status, and field presence; never expose credentials or private B2B values.
- Compare preview and production, then retest after cache or session reset.
If the value works only for an admin, the missing buyer context or access boundary is the first suspect. If the company value is correct but the page is blank, trace the binding and type-specific output before changing catalog or price-list settings.
06
DIY first. Pay when the wiring is the bottleneck.
Stay DIY when one Company definition, one value, one buyer context, and one published binding explain the missing field. Keep a redacted proof record so changes remain reversible.
Buy the $997 one-time install when several B2B resources, account contexts, apps, or live ops paths need a careful handoff. Nico at Latch AI Ops can trace the agreed store workflow and document the result. No earnings claim. Clock starts when collaborator access is in.