Shopify product or variant metafields not showing on Online Store 2.0.

Several products can look like “custom field never appears on PDP.” They do not share a settings panel. This page is only when a product or variant metafield (Settings → Custom data) never renders via Online Store 2.0 dynamic sources, or never returns from a Hydrogen Storefront API query — including Storefront access left off on the definition. Description tabs / accordion UI is shopify-product-tabs-not-showing. Size chart / fit guide widgets are shopify-size-chart-not-showing. Unit price / price-per-unit labeling is shopify-unit-price-not-showing. Hydrogen cartCreate / cartLinesAdd failures are shopify-hydrogen-cart-broken. A shorter companion for generic “custom fields blank” is product-metafields-not-showing. Stay here when the bug is definition namespace + Storefront access + OS 2.0 dynamic sources + variant / Hydrogen path.

Six ordinary reasons metafields stay blank on the storefront: missing or mismatched metafield definition (namespace.key), Storefront access disabled so Liquid / Storefront API cannot read the value, theme dynamic source unbound on the published Current Online Store 2.0 product template (wired only on a draft), empty values on the product or on the selected variant while you read product-level Liquid, Hydrogen query omitting metafield / metafields selections or using a token without storefront metafield scopes, or you tested tabs / size chart / unit price / Hydrogen cart instead. Walk definition + Storefront access + dynamic sources first. You already pay for Shopify Custom data. You do not need another metafield SaaS to print a value the theme can already bind.

On the live shop, open Settings → Custom data → Products and Variants. Open the definition you expect on the PDP. Note type, namespace.key, and whether Storefront access (Storefront API access) is enabled. Then open Online Store → Themes → Current → Customize → product template: find the text / rich text / block that should show the field and confirm a dynamic source is connected to that exact metafield — not a different namespace, not a variant field on a product-only block. Open the product admin: product-level metafields filled, and for variant metafields each variant that should print has a value.

If the storefront is Hydrogen / Oxygen, open the product query (or fragment) and confirm it requests metafield(namespace: "…", key: "…") or an equivalent metafields list for both product and selected variant. Confirm the Storefront API token used in that environment can read storefront metafields. Honest proof: screenshot definition + Storefront access, Current-theme dynamic source binding, product/variant values, and (for Hydrogen) the GraphQL selection + a Storefront API response that includes or omits the metafield. If the only symptom is tabs / size chart / unit price UI missing, switch pages instead of editing Custom data.

Create or fix the Product / Variant definition so namespace.key matches what the theme or Hydrogen query expects. Enable Storefront access on that definition and save. On the Current published OS 2.0 product template, connect the block’s dynamic source to that metafield — publish if you only fixed a draft theme. Fill non-empty values on the product and on every variant that should show variant-scoped fields; switch variants on the live PDP to confirm selected-variant Liquid updates. For Hydrogen, add the metafield selection to the product/variant query, redeploy Oxygen if needed, and retest with the live Storefront API token.

Honest proof: one live PDP (or Hydrogen product route) where the metafield text / number / rich text appears for a product that was blank, including after switching to a variant that has its own value. Product tabs stay on shopify-product-tabs-not-showing. Size chart stays on shopify-size-chart-not-showing. Unit price stays on shopify-unit-price-not-showing. Hydrogen cart failures stay on shopify-hydrogen-cart-broken. Keep those panels off this Custom data / Storefront access path.

Online Store 2.0 themes print metafields when a definition exists, Storefront access allows storefront reads, a dynamic source (or Liquid metafield reference) is bound on the published product template, and the product/variant has a non-empty value. Hydrogen does not use theme dynamic sources — it only sees what the Storefront API query requests. A field visible in Admin but missing from the GraphQL selection will stay blank in React. Variant metafields must be read from the selected variant object, not only from the product.

Do not enable Storefront access on every private metafield “just in case.” Expose only what the storefront needs. After parity, keep one owner for each public metafield (theme block vs Hydrogen component). If the Hydrogen storefront is blank or fails to deploy entirely, use hydrogen-storefront-blank-or-error. If cart mutations fail but metafield queries work, use shopify-hydrogen-cart-broken.

Switch pages if any of these is true: description tabs / accordion never mount (product tabs), size chart / fit guide missing (size chart), unit price / price-per-unit missing (unit price), Hydrogen cart empty after add (Hydrogen cart), or Hydrogen / Oxygen blank deploy (Hydrogen blank). Stay here only when a product or variant metafield should print on OS 2.0 or via Storefront API and does not.

Stay DIY if you can spend one afternoon on the list above: prove definition + namespace.key, enable Storefront access, bind Current-theme dynamic sources, fill product and variant values, fix Hydrogen metafield selections if headless, and stop confusing product tabs / size chart / unit price / Hydrogen cart with this Custom data path. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: product metafields companion, product tabs, size chart, unit price.

Pay for help when the work is not flipping one Storefront access toggle — it is connecting the stack you already have so lead capture is not dying in DMs, checkout and ops exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme agency retainer, not a conversion guarantee, not a brand or theme job.

Other shops' public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever metafield-uptime guarantee, a custom Hydrogen rewrite retainer, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.