Quick Buy Across Themes: The Settings, Defaults and How It Is Wired

A merchant who searches shopify quick view usually wants one answer: does the theme have it, yes or no. That question misses what actually varies. Every one of the six themes published by UTD in the official Shopify Theme Store, Allure, Boutique, Gain, Impression, Ultra and Victory, ships quick view enabled by default through a setting called is_quick_view_enabled. The real differences sit one layer down, in how many other settings surround that checkbox, which file it lives in, and what it quietly does not control. Those details were read straight from each theme’s own configuration files, and they are the part a screenshot of a product grid never shows.

The checkbox is the same, the surrounding settings are not

In every theme checked, is_quick_view_enabled is a checkbox living in config/settings_schema.json, and it defaults to enabled. That part is consistent enough to ignore. What is not consistent is the size of the settings group Shopify’s editor treats as belonging to that feature. Allure ties quick view to 8 total settings. Boutique jumps to 18. Gain sits at 13. Impression comes in at 11. Ultra reaches 21. Victory carries the largest group at 25. A merchant moving a catalog from Allure to Victory is not getting a bigger feature, they are getting three times the configuration surface around the same single checkbox, and every one of those settings needs to be reviewed after a theme switch or it silently reverts to whatever the new theme shipped with.

Sticky add to cart is the smallest feature group in this whole comparison

show_sticky_add_to_cart appears as a checkbox in sections/product-template.liquid in five of the six themes, Allure, Boutique, Gain, Impression and Ultra, and in all five it defaults to off and carries just 1 total setting attached to it. That is the flattest feature group measured across this entire set. There is no secondary color option, no layout select, nothing to misconfigure. A merchant turns it on and that is the whole decision. Victory was not part of the sticky add to cart fact set in this pass, so nothing is claimed about it here.

Mega menu sometimes has no switch at all, and that absence is the point

Three of the six themes, Allure 1.2.4, Impression 1.1.0 and Victory 1.2.1, implement mega menu entirely inside snippets/header-mega-menu.liquid with no separate toggle in the theme editor. It is not disabled, it is not hidden behind a setting a merchant forgot to find. It runs as a fixed part of the header block, full stop, as read from the theme’s own files. The other three themes expose a setting, but none of them expose an on-off switch either: Boutique’s main_mega_menu_text_color (6 total settings), Gain’s enable_mega_menu_borders (6 total settings), and Ultra’s megamenu_image_text (4 total settings) all control appearance, not presence. So across all six themes, a merchant who wants to disable mega menu through the editor cannot do it through a dedicated switch in any of them, only reshape how it looks.

Predictive search has the widest range of neighboring settings of anything checked

The core setting, predictive_search_articles, is a checkbox that defaults to enabled in every theme, and it always lives in config/settings_schema.json with a matching Search section in sections/search-template.liquid. But the total settings count around it swings harder than any other feature in this data: Gain sits at just 2, Impression at 5, Victory at 5, Boutique at 6, Ultra at 6, and Allure at 7. A theme with a count of 2 is not necessarily worse, it just means fewer knobs to turn if a merchant wants finer control over how article results mix into product results.

The rest of the storefront tells the same story: same checkbox, different weight

Product compare uses show_compare_at_price_in_cart in five of six themes and it always defaults to off, but its total settings count runs from 1 in Allure and Gain’s neighbor group up to 26 in Victory. Countdown timer swings even wider, from 8 total settings in Allure to 74 in Ultra, all built around a setting that is either a plain enable checkbox or a date-type select depending on the theme. None of these differences show up in a theme preview, because a preview shows one merchant’s chosen configuration, not the settings panel behind it. That is why the file paths and setting ids matter more than a screenshot: they were read directly from each theme’s own settings_schema.json and section liquid files, across the six published versions, as they stood when checked on September 8, 2026.

Anyone shopping by feature name alone will pick two themes that both say “quick view” and end up with settings groups eight versus twenty-five settings apart. Open the theme’s own settings_schema.json before buying, not after, and compare the setting id and its default, not the marketing copy above it.