Shopify menu metafield not displaying? Prove the menu, value, and theme.

Use this page when a custom value belongs to a navigation menu and the published header or menu section shows nothing. A Menu metafield is attached to the menu resource; its child links are separate entries with their own URLs and labels.

If the value belongs to one link, inspect the storefront metafield path and its object type. If the dropdown itself will not open, use the mega menu playbook. Do not diagnose a missing Menu field as a CSS-only problem before proving the resource.

Open Settings → Custom data → Menus and record the definition namespace and key, for example custom.header_note. Record its type and validations. The display label is not the identifier a theme reads.

Open the exact menu in Content or Navigation and confirm the field contains a value, is saved, and remains after refresh. Check whether it is plain text, rich text, a reference, a list, or a file; each type has different storefront rendering rules. A field on another menu is not proof.

In Content → Menus or Online Store → Navigation, identify the exact menu assigned to the live header. Compare its handle and child-link structure with the menu your theme reads. A similarly named draft menu or an old handle can make a correct field appear blank.

Open each intended child link and confirm its destination is published and not a dead custom URL. A visible parent with empty children is a navigation data problem; a complete menu with no field output is a binding or access problem.

In Online Store → Themes → Customize, verify the Current published theme and the header or section that renders the assigned menu. Choose the dynamic source for the Menu definition, not a Page or Shop field with the same label.

If the theme uses Liquid, follow the object shape exposed by the theme and the exact namespace.key; do not guess from the display label. Check storefront access where applicable, reference/list rendering, section settings, and whether an app block replaced the native header. Previewing a draft theme is not production proof.

1. Save the field, section, and menu; publish the current theme, not only a preview.
2. Open the exact storefront URL in a logged-out window and inspect the rendered header.
3. Compare a plain text test value with the original type-specific value.
4. Check the menu handle, source picker, browser console, and app/theme conflicts only after proving the data.

If the admin value is blank, this is a data or save issue. If the menu is wrong, it is an assignment or handle issue. If the source picker is missing, it is a definition, access, or template compatibility issue. If the source is bound but output is empty, inspect type-specific rendering and live theme output.

Stay DIY when one Menu definition, one assigned navigation menu, or one Current theme binding explains the blank. Record the namespace.key, menu handle, theme, and exact public URL so the next edit is reversible.

Buy the $997 one-time install when the store has several menus, conflicting app/theme paths, or a live ops workflow that needs a careful handoff. Nico at Latch AI Ops can trace the live store, wire the agreed workflow, and leave the proof path documented. No earnings claim. Clock starts when collaborator access is in.

Start the $997 installRead the FAQPage metafield