Shopify metaobjects or entries not showing on the storefront or theme.

Several products can look like “custom content never appears on PDP.” They do not share a settings panel. This page is only when a metaobject definition and its entries (Settings → Custom data → Metaobjects) never render via Online Store 2.0 dynamic sources, product/page references, or a Hydrogen Storefront API query — including Storefront access left off on the metaobject definition. Scalar product/variant metafields blank on OS 2.0 are shopify-metafields-not-showing-on-storefront. Description tabs / accordion UI is shopify-product-tabs-not-showing. Size chart / fit guide widgets are shopify-size-chart-not-showing. Stay here when the bug is metaobject type + entries + references + OS 2.0 dynamic sources + Storefront API path.

Six ordinary reasons metaobjects stay blank on the storefront: missing or mismatched metaobject definition (type handle), entries draft / empty / unpublished, product or page reference metafield not pointing at those entries, theme dynamic source unbound on the published Current Online Store 2.0 template (or wired to a different type), Storefront access disabled so Liquid / Storefront API cannot read the metaobject, or Hydrogen query omitting metaobject / metaobjects / referenced fields. Walk definition + entries + references + dynamic sources first. You already pay for Shopify Custom data. You do not need another CMS SaaS to print an entry the theme can already bind.

On the live shop, open Settings → Custom data → Metaobjects. Open the definition type you expect on the PDP or page. Note the type handle, field keys, and whether Storefront access is enabled for that definition. Open Entries: confirm at least one Active entry with non-empty fields (not Draft-only). Then open the product or page that should show it: confirm a reference metafield (single or list of metaobject references) points at that entry. Online Store → Themes → Current → Customize: find the block that should render the entry and confirm a dynamic source is connected to that metaobject type / referenced field — not a scalar product metafield, not a different type handle.

If the storefront is Hydrogen / Oxygen, open the product or page query and confirm it requests the reference metafield and nested metaobject fields (or a top-level metaobject(handle: …) / metaobjects(type: …) selection). Confirm the Storefront API token can read those metaobjects. Honest proof: screenshot definition + Storefront access, Active entry fields, product/page reference, Current-theme dynamic source binding, and (for Hydrogen) the GraphQL selection + a Storefront API response that includes or omits the metaobject. If the only symptom is scalar metafields / tabs / size chart missing, switch pages instead of editing Metaobjects.

Create or fix the metaobject definition so the type handle and field keys match what the theme or Hydrogen query expects. Publish Active entries with the fields you need filled. On the product or page, set the reference metafield to those entries and save. Enable Storefront access on the metaobject definition (and on any reference metafield definition that must be storefront-readable). On the Current published OS 2.0 template, connect the block’s dynamic source to the metaobject / referenced fields — publish if you only fixed a draft theme. For Hydrogen, add the metaobject / reference selections to the query, redeploy Oxygen if needed, and retest with the live Storefront API token.

Honest proof: one live PDP or page (or Hydrogen route) where the metaobject text / rich text / file / list fields appear for an entry that was blank. Product/variant metafields stay on shopify-metafields-not-showing-on-storefront. Product tabs stay on shopify-product-tabs-not-showing. Size chart stays on shopify-size-chart-not-showing. Keep those panels off this metaobject definition / entries / references path.

Online Store 2.0 themes print metaobjects when a definition exists, entries are Active with values, a reference (or liquid metaobject access) is present, Storefront access allows storefront reads, and a dynamic source is bound on the published template. Hydrogen does not use theme dynamic sources — it only sees what the Storefront API query requests. An entry visible in Admin but missing from the GraphQL selection will stay blank in React. List references must be iterated; a single-reference field will not behave like a list.

Do not enable Storefront access on every private metaobject “just in case.” Expose only what the storefront needs. After parity, keep one owner for each public metaobject type (theme block vs Hydrogen component). If scalar product metafields are blank but metaobject Admin looks fine, use shopify-metafields-not-showing-on-storefront. If the Hydrogen storefront is blank or fails to deploy entirely, use hydrogen-storefront-blank-or-error.

Switch pages if any of these is true: product or variant metafield never prints (metafields on storefront), description tabs / accordion never mount (product tabs), size chart / fit guide missing (size chart), or Hydrogen / Oxygen blank deploy (Hydrogen blank). Stay here only when a metaobject entry 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 metaobject definition type + Active entries, attach product/page references, enable Storefront access, bind Current-theme dynamic sources, fix Hydrogen metaobject selections if headless, and stop confusing product metafields / product tabs / size chart with this Metaobjects path. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: metafields on storefront, product tabs, size chart, product metafields companion.

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 metaobject-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.