Troubleshooting custom variant pickers.

Start With The Product Data

Confirm the product has at least one available variant and one sold-out variant. Check inventory tracking, option names, variant availability, and whether unavailable combinations are real variants or theme-generated choices.

Check Every Picker Surface

Many stores have more than one variant picker. Test the main product page, mobile product page, featured product section, quick view, sticky add-to-cart area, and any product template used for bundles or landing pages.

Identify The Picker Type

Variant pickers can be buttons, swatches, dropdowns, radio groups, image tiles, or custom page-builder elements. A behavior that works for dropdowns may need a different selector for custom swatches.

Look For Dynamic Rendering

Some themes rebuild the picker after a shopper chooses an option. If the sold-out state appears briefly and then disappears, the picker may be re-rendering after the app block runs.

Keep Selector Settings Narrow

Use the smallest selector that targets the variant choices on the product page. Broad selectors can affect unrelated buttons, filters, or product cards.

Test A Safe Mode First

If the theme is heavily customized, start with label mode before hide mode. Labeling unavailable options is easier to inspect because the original picker layout stays visible.

Record The Setup

Keep a short note with the theme name, product handle, picker type, behavior mode, selector setting, and tested surfaces. This makes support faster if a theme update changes the picker markup later.

Use Vaestic

Vaestic: Hide Sold Variants is being built with selector settings so merchants can test hide, disable, or label behavior on custom pickers without editing theme files.

Read the development-theme testing checklist, compare hide vs disable vs label, or view the app page.