Variations not showing
The product has six colors. The page is only willing to admit one.
Missing variations are retail's phantom limb: the inventory exists, the prices are set, and the shopper stares at an empty dropdown or a lone option — then leaves to buy the blue one somewhere that shows blue. The causes live in a predictable stack: data, limits, and theme.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
WooCommerce variations sit on a strict data hierarchy, and display failures are almost always hierarchy failures. Attributes must exist and be marked 'used for variations'; variations must be generated from them; each variation needs a price (unpriced variations are deliberately hidden — the single most common cause of 'my size medium vanished'); and stock status must allow display. One unmet requirement anywhere in that chain and the option silently disappears — not an error, a rule, faithfully enforced.
Past the data layer come the scaling and rendering layers. Big catalogs hit genuine limits: products with many attribute combinations exceed WooCommerce's variation-display thresholds and AJAX loading quirks, where dropdowns arrive empty because the browser gave up waiting. And the theme layer: swatch plugins and builder templates overriding the stock variation form — after an update, their JavaScript breaks and selections stop registering, or the form renders but 'Add to cart' never activates. Which layer you're in is diagnosable in minutes; guessing across all three is the afternoon-killer.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
Unpriced or incomplete variations
Variations missing a price are hidden by design. Bulk edits and CSV imports that skip prices delete options from view without deleting them.
Attribute configuration drift
Attributes not flagged for variations, renamed terms orphaning existing combinations, or import mismatches between attribute slugs.
Combination-count limits
Products with hundreds of combinations tripping display thresholds and AJAX timeouts — the enterprise-catalog version of the disease.
Swatch and theme conflicts
Variation-UI plugins and theme templates breaking after updates — options render but don't select, or the form is simply blank.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Audit one broken product's data
Edit product → Variations: does every combination exist, with a price, in stock? Nine times out of ten the phantom option is sitting there priceless.
- 2
Switch to a default theme for sixty seconds
Storefront or a default theme on a staging copy: variations reappearing convicts the theme/swatch layer instantly.
- 3
Test with the browser console open
Red JavaScript errors while operating the dropdowns implicate the rendering layer — and name the script responsible.
Stop and call when…
- The catalog needs bulk data repair — hundreds of products with import-damaged attributes is tooling work, not clicking
- Combination limits require threshold and AJAX tuning — code-level, with performance tradeoffs to balance
- The swatch plugin everyone likes is the culprit — fix-or-replace needs someone who can read its conflict
From there it’s our job: same-day look, flat quote, and the $229 flat repair covers most cases of exactly this.
Single Error Fix — buy it now, skip the hunt.
One error, hunted down and fixed — 500s, white screens, redirect loops, broken pages.
Covers one specific error or broken behavior on one site. Diagnosis, the fix, and a plain-English note on what happened. If we can't fix it, you get a full refund.
Questions we hear a lot.
The variations exist in admin — how can they not show?
Because display has requirements beyond existence: a price on every variation, purchasable stock status, attributes properly flagged, and combination counts inside limits. Admin shows what you've built; the storefront shows what passes the rules. The gap between those two views is precisely where this diagnosis lives — and why the fix is usually data, not code.
This started after an update. Coincidence?
Probably not. Theme and swatch-plugin updates are the leading cause of sudden-onset variation failure — their JavaScript overrides the stock variation form, and a version mismatch breaks selection silently. The sixty-second default-theme test sorts coincidence from cause before anyone touches anything.
What does the $229 fix cover?
The layer-by-layer diagnosis, data repair on affected products (prices, attributes, regeneration), limit tuning where catalogs are large, the theme/swatch conflict resolved or the plugin replaced, and a walk through your top products verifying every option shows, selects, and adds to cart. Sell what you stock, everywhere it should show.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Every size, every color, buyable again.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.