Improve variant conversion by making option names, images, price differences, availability, measurements, compatibility, and disabled states clear. Preserve the shopper's selection across interactions, and when an exact variant is unavailable, capture that specific variant, quantity, expiry, and substitution tolerance.
- Product-level demand can hide variant-level failure.
- Unavailable options should be understandable, not silently removed.
- Substitutions require explicit shopper tolerance.
- Inventory is rechecked before any checkout path opens.
Find the exact failure before choosing a fix
Compare option interaction, unavailable selections, add to cart, error, and paid conversion by variant and device. Review whether names, swatches, images, sizing, price deltas, inventory, selling plans, and deep links remain synchronized. Inspect long option lists and products where the default selection masks an unavailable desired variant.
Use a segmented funnel rather than a storewide average. Compare product, variant, device, market, traffic source, new versus returning shopper, and purchase stage. Preserve counts and denominators, and inspect real sessions or support evidence before treating a correlation as a customer reason.
A practical, low-risk improvement plan
Use concise option names, accessible controls, variant-specific imagery and evidence, stable URL or state behavior, and an explicit unavailable state. Suggest substitutes only when the merchant has verified compatibility and the shopper has said what alternatives are acceptable.
- Test every option combination on mobile and keyboard.
- Keep image, price, inventory, SKU, and selection synchronized.
- Explain unavailable choices instead of deleting context.
- Capture exact variant, quantity, expiry, and substitution tolerance.
Where conditional demand adds useful evidence
BuyWhen can turn an unavailable variant into structured demand with product and variant binding, requested quantity, acceptable alternatives, and expiry. Capture does not reserve inventory or create a preorder, and checkout remains blocked if live sellable inventory is insufficient.
BuyWhen should not interrupt a shopper who can already complete the normal purchase. It is a secondary path for an unresolved condition, with explicit contact permission, merchant control, expiry, and live checkout validation. A request remains potential demand until it is qualified and never becomes guaranteed revenue merely because it was submitted.
Measure paid outcomes and guardrails
Track variant interaction, unavailable selection, request volume and units, substitute acceptance, restock response, paid conversion, cancellation, exchange, return, and sell-through. Do not multiply every request by list price and report it as recoverable revenue.
Track the complete path from eligible visit to interaction, request, merchant response, checkout, paid order, refund, cancellation, and contribution outcome. Separate direct orders, attributed recovered orders, and experimentally estimated incremental orders. Record the attribution window and exclusions so the report can be audited later.
Frequently asked questions
Should unavailable Shopify variants be hidden?
Usually preserve enough context for shoppers to understand the assortment and choose an alert or request, unless displaying the option would be misleading or operationally inappropriate.
Does a variant request reserve inventory?
No. A request expresses conditional demand. Reservation or preorder terms require separate explicit behavior, and live inventory must still be checked before checkout.
Sources and further reading
Product guidance is grounded in BuyWhen's documented behavior. The broader commerce and search principles in this guide also reference these primary sources: