Shopify header megamenu / dropdown navigation not opening on hover or tap — theme JS, megamenu app, mobile drawer conflict.

Several products can look like “the top of the store is broken.” They do not share a settings panel. This page is only when a parent header link’s megamenu / dropdown / mega menu never opens on hover or tap. A missing or dead collection quick-view modal is quick view modal not opening. A missing sticky add to cart / mobile buy bar is sticky add to cart not working. A stale cart drawer after a successful add is cart drawer / AJAX cart not updating. Empty or stuck collection facets are collection filters / facets not working. Empty or wrong predictive search is storefront search not returning. This page is only: header megamenu / dropdown navigation.

Seven ordinary reasons the menu stays closed: theme header / mega-menu section disabled or dropped after a theme publish, header / dropdown JS unbound after a section reorder, megamenu app embed fighting the native dropdown, mobile drawer listeners swallowing desktop hover, CSS display:none / pointer-events:none on the panel, z-index under announcement / chat overlays, or you are debugging quick view / sticky ATC / cart drawer / collection filters / storefront search instead. Walk them in that order. You already pay for the theme or megamenu app. You do not need another seat to make a dropdown that already exists open.

Open the live storefront homepage in an incognito window on desktop and phone-width. Hover a parent menu item that should show a megamenu / dropdown. Tap the same item on mobile (or open the hamburger → parent). Screenshot whether a panel / flyout / nested list mounts; whether Theme editor → header / mega-menu section (or app block) is present and enabled on the live theme; and DevTools → Console for uncaught header / disclosure / details-summary errors when hover or tap should fire.

Honest proof: if product pages and collections still work but the header dropdown never opens, stay on this page — that is theme header JS, megamenu app, mobile drawer, or CSS. If collection Quick view never opens a modal, leave for quick view modal not opening. If the sticky / mobile buy bar is the broken surface, use sticky add to cart not working. If add succeeds but the cart drawer stays stale, use cart drawer / AJAX cart not updating. If facets / filters empty the grid, use collection filters / facets not working. If the header search suggest is empty or wrong, use storefront search not returning. Do not mix those proofs.

Many OS 2.0 themes ship Mega menu, Dropdown, or Nested menu as a header section setting (“Enable mega menu”, menu type, or a megamenu block on the header group). A theme switch, duplicate, “reset sections,” or a customizer edit that unchecks / removes that setting is the most common “menu stopped opening” ticket — collection pages still work; the header flyout surface is gone.

Fix: Theme editor → Header (and header group) — re-enable Mega menu / Dropdown / Nested menu on the parent links that need it, assign the correct Navigation menu in Online Store → Navigation, Save, preview, then hard-refresh the live homepage. Compare against an unmodified Dawn / theme starter if you forked heavily. Quick view and sticky ATC sections are still different products — do not confuse a missing collection Quick view control or mobile buy bar with a missing header megamenu.

Megamenus usually open via details / disclosure / custom-element header menus that listen for mouseenter, focusin, or click. A section reorder, sticky-header re-render, or customizer publish that removes data- attributes / trigger aria-expanded hooks leaves a visible parent whose hover or tap does nothing — or a panel that never mounts because the header observer never attaches.

Fix: confirm the megamenu / dropdown panel markup still exists in the header section. Check console for custom-element upgrade failures after sticky header / localization / announcement bar remounts (those often re-render the header and orphan listeners). Restore the theme’s header / megamenu JS from an unmodified copy if you deleted the open handler. Empty predictive search inside a working header still belongs on storefront search not returning— that is search suggest, not the megamenu open.

Stores that installed a megamenu / mega menu / advanced nav app on top of a theme that already ships one often leave both: two panels, one covering the other, or the app’s preventDefault killing the native hover. A theme switch that leaves the old app embed on while the new theme’s mega-menu setting is also on is the same class of ticket.

Fix: keep one megamenu owner. Theme editor → App embeds — disable the megamenu app if you want the native dropdown, or disable the theme mega-menu setting if you want the app. Remove orphan megamenu liquid / sections on a development theme first. Preview then hard-refresh. Collection filter / facet bugs that empty the grid are still collection filters / facets not working— different surface from a dead header dropdown.

Many themes share one menu tree between the desktop megamenu and the mobile hamburger drawer. A drawer script that always preventDefaults parent clicks, a media-query mismatch that leaves the drawer open handler bound on desktop, or a “tap to expand” accordion that never resets on resize all look like “hover stopped working after we fixed mobile.” Cart drawers are a different product — a stale cart after add is cart drawer / AJAX cart not updating.

Fix: test desktop hover with the mobile drawer closed and with DevTools device mode off. Confirm the header uses separate desktop vs mobile containers (or correctly gated media queries). Re-bind or restore the theme’s disclosure / details open for desktop hover and the drawer accordion for mobile tap. Do not “fix” desktop by disabling the whole menu JS.

Custom CSS that sets display:none, visibility:hidden, opacity:0, or pointer-events:none on megamenu / dropdown classes, an announcement / cookie / chat bar with a higher z-index than the panel, or overflow:hidden on a sticky header that clips the flyout all look like “the menu is broken.”

Fix: Inspect the parent trigger and the megamenu panel — note computed display, visibility, pointer-events, overflow, and z-index. Lower announcement / chat overlays or raise the panel. Confirm sticky header overflow allows the flyout. Sticky ATC / mobile buy bar visibility on the product page is still sticky add to cart not working— that is a product-page buy bar, not a header megamenu.

A missing or dead quick view / product preview modal is quick view modal not opening. A missing or dead sticky add to cart / mobile buy bar is sticky add to cart not working. Stale cart drawer / AJAX cart after add is cart drawer / AJAX cart not updating. Empty or stuck collection facets are collection filters / facets not working. Empty or wrong storefront predictive search is storefront search not returning.

The only honest test for this page: a published header parent opens its megamenu / dropdown on desktop hover and mobile tap as designed, theme mega-menu section (or one megamenu app) is enabled on the live theme, header JS binds, the panel mounts with menu links, console is clean on hover/tap, mobile drawer does not swallow desktop handlers, and announcement / chat overlays do not cover the panel. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove hover vs tap failure, re-enable the theme header / mega-menu section, re-bind header JS, keep one megamenu owner (theme or app), fix mobile drawer conflicts, and fix CSS / pointer-events / z-index hides. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: quick view modal not opening, sticky add to cart not working, cart drawer / AJAX cart not updating, collection filters / facets not working, storefront search not returning.

Pay for help when the work is not the megamenu toggle — 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, perfect megamenus forever, 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.