help1
horizon-quick-addshopifyhorizon-themequick-addshopify-themes

Horizon Quick Add: Seven Questions Merchants Keep Asking

Horizon quick add trips merchants up in about seven recurring ways. Here are the questions I keep answering, with fixes that actually hold.

help1 Team
Horizon Quick Add: Seven Questions Merchants Keep Asking

A merchant posted on the Shopify Community forum earlier this year asking whether there was a setting to disable the Add to Cart buttons that appear on hover across their collection pages. They could not find one. The first reply confirmed the setting does not exist and told them to edit the code and comment it out. The Horizon quick add feature has been a steady source of questions like that for most of 2026, and the questions keep shifting as Horizon pushes new versions.

The through-line in one paragraph

Horizon's quick add is less a single feature than a stack of settings, two different block types, a Liquid snippet, and a JavaScript bundle that loads conditionally on newer versions. The theme editor exposes about forty percent of that stack. The rest, you find out about by hitting a failure mode and reading the schema. Below are the questions I keep answering, in roughly the order they show up for a merchant who just migrated to Horizon.

Why doesn't Horizon Quick Add show up on mobile when you already enabled it?

This is the one that sends merchants into the DOM inspector when they do not need to be there. The global quick_add setting in Theme Settings > Product Cards defaults to true and controls the desktop behavior. There is a second setting called mobile_quick_add, sitting a few rows below it in the same panel, that defaults to false. Enabling the global toggle does not enable the mobile toggle.

The mintlify Horizon documentation is where the public settings schema lives, and it lists both booleans as separate opt-ins. The theme editor preview simulates desktop, so you can look at your live preview, see the hover button appear, feel satisfied, publish, and then notice no button at all on your phone. The gap between editor and phone is where this one hides.

If you are on mobile, you have the global toggle on, and you still see nothing: open the theme editor, go to Theme Settings, scroll to Product Cards, and look for a separate "mobile quick add" checkbox below the main one. It is not well labeled. I missed it twice on two different stores before I stopped to read the schema.

Can you make Horizon Quick Add always visible instead of hover-only?

Yes, and there are two paths, and they are not equivalent.

The CSS approach is a single line tim_tairli posted on Shopify Community in March. You paste it into the custom CSS field on your theme:

product-card .button.quick-add__button { opacity: 1; }

That forces the hover button to render at full opacity on load. The variant picker modal flow stays intact. Mobile shoppers who do not hover get the button they otherwise would have missed.

The alternative is the block swap. You disable quick add in theme settings, then in the theme editor you open a product card section, click Add Block, and choose Buy Buttons. The Buy Buttons block is always visible, which sounds like the same outcome. It is not. Buy Buttons submits the product form directly rather than opening a variant picker modal, so a shopper on a multi-variant product no longer selects a size before the cart fires. Some merchants want that behavior. Most of the merchants who pick the block swap because they wanted "always-visible ATC" do not realize they also removed the variant selection step for every multi-variant product.

Pick on purpose. Use the CSS override when you want a visible button plus the modal. Use the block swap when your products are single-variant and you want the shortest path to cart.

The Quick Add button greys out when the first admin variant is sold out

This one is hard to spot because the button renders at full size, in the right place, and looks clickable. A shopper clicks, the modal opens, and the only variant offered is the unavailable one with no path to the in-stock options. The shopper closes the modal and moves on.

The root cause: Horizon pre-selects the first variant in your admin sort order for the quick add modal the same way it does for the product page, with no check for stock. If your first variant by admin order is sold out, horizon quick add silently funnels every shopper into that dead end for that product card.

The workaround is to open the product in Shopify admin and drag the variant list so an in-stock variant sorts first. This is ongoing maintenance. If that variant later sells out, the problem returns and you have to reorder the list again. There is no theme setting to tell quick add to default to the first available variant instead of the first listed one. A third-party guide (Craftshift) suggests editing snippets/quick-add.liquid to filter variants by availability before selecting a default. I have not run that patch in production and the community thread never confirmed a working version, so treat it as a candidate fix, not a confirmed one. If you want the adjacent surface mapped out, the ten variant picker gaps post covers the OOS-variant weirdness that shows up next to this bug.

Where did the Buy buttons on the homepage go after you updated Horizon?

If you installed Horizon on version 1.x and updated later, the native Buy Buttons on your homepage product cards disappeared. This was intentional on Shopify's side. Horizon 2.x replaced the default product card layout with the hover-activated quick add instead of a persistent ATC. Merchants who had built screenshots, email campaigns, or landing pages around the earlier behavior experienced that update as a breakage; the changelog described it as a design decision.

The fix is a block addition. Open the theme editor, go to your homepage, find your Product Highlights or Featured Products section, click into a product card, and choose Add Block > Buy Buttons. That restores the always-visible ATC on those cards. As with the question above, Buy Buttons runs the direct submit flow rather than the modal, so multi-variant products behave differently. If you want the modal back, keep quick add enabled and lean on the CSS override from the earlier section.

Horizon 3.3.0 (February 2026) also added quick add directly inside the Product Highlights section. If you updated past that version you may now have quick add on the homepage whether you asked for it or not. The two features coexist on the same card; which one dominates visually depends on which block is active.

How do you remove Quick Add for one product, or for one collection only?

Horizon ships no setting for this. The fix lives in Liquid.

To hide quick add on specific products, open Online Store > Themes > Edit Code and find snippets/_product-card-gallery.liquid. Locate the line that renders the quick add snippet. Wrap it:

{% unless closest.product.tags contains 'hide-quick-add' %}
  {% render 'quick-add', product: closest.product, section_id: section.id %}
{% endunless %}

Then tag the relevant products in admin with hide-quick-add. That is namphan's pattern from the August 2025 community thread. I have run it on three stores with no side effects beyond what the tag implies.

For a per-collection toggle, the same wrap applies with a different condition. Use {% if section.settings.collection.handle != 'wholesale-only' %} (or whichever handle you want to exclude), or invert the condition for an allow-list. oscprofessional posted this version in February 2026.

One thing to check before you edit any code: your Horizon version. On 4.2.0 and later, the quick add JavaScript only loads when the quick_add setting is enabled globally. Turning quick_add off at the theme level is lighter touch than Liquid edits if you want it gone everywhere. If you want it gone on some pages and kept on others, the template edit is the only path.

The dropdown caret inside the Quick Add modal renders at the browser default

If you use dropdown variant pickers (rather than button swatches) and you open a quick add modal on your live storefront, the caret icon inside the dropdown may render at two or three times its designed size. In the theme editor it looks fine. On the live site, in Chrome and Safari, it is huge.

The mechanism is specific. The dropdown's caret styling sits in a {% stylesheet %} block inside variant-main-picker.liquid. Shopify's CSS pipeline bundles that stylesheet per page at build time. The quick add modal loads via JavaScript after the page is already rendered, which means the modal arrives without the page's compiled CSS bundle. The caret falls back to the browser's native unstyled size.

You have three options, in rough order of safety. First, switch your variant picker from dropdown to buttons in Theme Settings > Variant Pickers; that avoids the bundling path entirely. Second, create or open snippets/quick-add-modal-styles.liquid and add caret sizing CSS there. Third, move the dropdown caret styles out of the Liquid stylesheet block and into assets/base.css directly (tim_tairli's preferred fix). Option one is cleanest. Options two and three will likely be overwritten the next time you accept a Horizon update, and that is worth saying out loud before you ship them.

Shopify has not released a fix as of this writing. The thread is unresolved.

Why does an AI-generated upsell block add items but never refresh the cart drawer?

This is a 2026 question that did not exist in January. Merchants have started using Build With AI, Sidekick, and various third-party generators to produce custom product sections: frequently-bought-together blocks, related-product rows, recommendation modals. The generated JavaScript dispatches a cart:updated event after it calls /cart/add. Horizon's cart components listen for cart:update, no trailing 'd'. The item lands in the cart, but the drawer never refreshes until the shopper hits reload.

Wes-Dev-Shopify confirmed the mismatch on the Shopify developer community forum in May and said the AI generators would be flagged to internal teams. As of late October, the generators had not been corrected, so any section you produce today almost certainly carries the wrong event name.

The code fix is one line. Find the generated JavaScript in the section template, locate the line that dispatches the event (usually inside a function named handleAddToCart or similar), and change cart:updated to cart:update. The expected detail shape is { cart: <cart JSON from /cart.js> }.

The bigger issue is regeneration. If you ask the AI tool to regenerate the section for a layout change, the wrong event name comes back with it. Save the corrected version under source control, or at minimum keep the diff in a note. If you want a second pair of eyes on an AI-generated section before Black Friday, the first fifteen minutes with a help1 expert is free, and this specific bug takes about three minutes to find with the Network tab open.

The take

The take I keep landing on after hundreds of these questions: horizon quick add is really a stack of settings, blocks, a Liquid snippet, and a conditionally loaded JavaScript bundle, and the theme editor exposes maybe forty percent of that stack. The rest surfaces only when you hit the failure mode. If the editor UI covered the whole surface, this post would be three sections long instead of seven.

Still stuck? Talk to an expert.

Our vetted Shopify experts can fix this issue for you in a live session. $39 per session. Your first 15 minutes are free.