Shopify product metafields / custom fields not showing on storefront — definition, namespace, theme dynamic sources, OS 2.0.

Several products can look like “my custom product field is missing.” They do not share a settings panel. This page is only when a product metafield or custom field never appears on the live product page — blank text, missing specs block, or dynamic source that never connected. A missing app embed or theme app extension is app embed not loading. Theme editor Save / Publish refusing or edits never going live is theme editor publish failing. Facets / filters empty on a collection is collection filters not working. A size chart / fit guide popup that never opens is size chart popup not opening. This page is only: product metafields / custom fields not showing on the storefront.

Six ordinary reasons metafields stay blank: no metafield definition (or wrong type) under Settings → Custom data, wrong namespace.key vs what the theme / Liquid / dynamic source expects, theme dynamic sources never connected on the Current OS 2.0 product template, you connected them only on a draft theme while Current stayed live, the product row has an empty value even though the definition exists, or you are debugging app embed / theme editor publish / collection filters / size chart instead. Walk them in that order. You already pay for Shopify Online Store. You do not need another seat to create a definition and connect a dynamic source.

Settings → Custom data → Products. Confirm the definition exists. Note type (single line text, rich text, integer, file, etc.) and the exact namespace.key. Open Products → pick the SKU buyers see → Metafields / custom fields panel. Confirm a non-empty value is saved on that product. Then Online Store → Themes → Customize on Current → product template → find the block that should show the field and check whether a Metafield / dynamic source is connected.

Honest proof: if the definition is missing, namespace.key is wrong, the product value is empty, or dynamic sources are not connected on Current, stay on this page. If Save / Publish itself fails with a JSON / app-block toast, leave for theme editor publish failing. If an App embeds toggle is off and a whole app is missing, leave for app embed not loading. If only collection facets are empty, leave for collection filters. If a size chart popup never opens (even when metafields exist), leave for size chart popup. Do not mix those proofs.

Typing a value into an old CSV column, a private app metafield, or an unstructured “notes” field does not create a storefront- ready definition. Online Store 2.0 themes and the theme editor dynamic source picker only surface metafields that have a definition under Settings → Custom data for the Products owner, with a matching type. A theme or app that expects custom.material will stay blank if you saved my_fields.fabric or a variant-level metafield while the product template reads product metafields.

Fix: create (or fix) the Products metafield definition with the exact namespace.key and type your theme / Liquid expects. Re-save values on the products that should show. Confirm the product admin panel shows the definition row filled. Do not confuse product metafields with shop, collection, or variant metafields — the wrong owner is a silent blank on the product page. Collection filter facets that rely on product metafields but never list options is a different product — collection filters not working.

A filled metafield does not auto-print on Dawn / OS 2.0 product templates. You must connect it: Customize → product template → select a text / rich text / custom liquid / metafield-capable block → dynamic source (plug icon) → pick the product metafield → Save. Hard-coded Liquid that references the wrong key, a section removed from the template, or a block set to “hide when empty” while the value is blank will also look like “metafields not showing.”

Fix: on the Current / Published theme, connect the metafield via dynamic sources (or correct Liquid to product.metafields.namespace.key with the right value accessor for the type). Save. Preview the product in the editor, then open the live marketed URL logged-out Incognito and hard-refresh. If Save / Publish fails with JSON / app-block errors, that is theme editor publish failing, not a metafield-definition problem. If a whole app embed is missing from the storefront, leave for app embed not loading.

Dynamic source connections are per theme (and often per template / product template alternate). Connecting a metafield on an unpublished copy makes the editor preview look perfect — then buyers still see a blank live product page because Current never received the connection. Staff with limited Themes permissions may edit a copy but not Publish. Separately: the definition can exist while this SKU’s metafield value is empty, imported blank, or only filled on a duplicate product.

Fix: Themes list — connect dynamic sources on the Current theme, or Publish the theme you edited after Save. Have an owner / full Themes role publish if your staff login cannot. Open the exact product URL buyers use and confirm the metafield value is non-empty in admin. Retest logged-out Incognito and on a phone. Hard refresh. If the only failure is a size chart popup that never opens (theme JS / app block), leave for size chart popup not opening.

App embed / theme app extension missing on the live storefront is app embed not loading. Theme editor Save / Publish failing or changes not live is theme editor publish failing. Collection facets / filters empty or stuck is collection filters not working. Size chart / fit guide popup not opening is size chart popup not opening.

The only honest test for this page: product metafields or custom fields are missing on the live product page while you expected them to print — prove definition + namespace.key + filled values, connect theme dynamic sources on Current OS 2.0, Publish if you edited a draft, hard-refresh logged-out. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove the Products metafield definition and namespace.key, fill values on the live SKUs, connect dynamic sources on the Current OS 2.0 product template, Publish the theme you edited, and stop confusing app embed / theme editor publish / collection filters / size chart with a blank metafield. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: app embed not loading, theme editor publish failing, collection filters not working, size chart popup not opening.

Pay for help when the work is not the metafield definition row — it is connecting the stack you already have so lead capture is not dying in DMs, storefront and checkout-ready 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 rebuild 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-proof theme guarantee, 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.