WooCommerce 10.9 Brings Variation Galleries Into Core

The change ships in WooCommerce 10.9 and continues the "more in core" initiative that already brought Brands into core in 9.4. Variation galleries have, until now, lived behind a paid extension. From 10.9 the same capability becomes part of the default install, free to every WooCommerce store.

For UK merchants selling variable products (clothing, footwear, homeware, configurable hardware), this removes a long-standing friction point. Showing the right images for each colour, size or finish has historically meant either reaching for the Additional Variation Images extension, a third-party gallery plugin, or workarounds in the theme. From 10.9, the workflow is native.

How variation galleries work in 10.9

Each variation can now hold its own ordered list of images, beyond the single featured image variations have always supported. When a shopper selects a variation on the product page, the gallery swaps to show that variation's full image set rather than reusing the parent product's gallery.

The admin experience uses a single unified field. The variation's featured image and gallery sit together in one ordered list, with the first item automatically promoted to "primary". That removes the previous split between a separate featured image field and an extension-managed gallery, which was a frequent source of confusion for store managers updating product photography.

Under the bonnet, variation galleries are stored in the same _product_image_gallery postmeta key that WooCommerce already uses for parent-product galleries. The REST API exposes them on the variation endpoint via the gallery_image_ids property, in the same shape parent products use. That means integrations, headless storefronts and product feed exporters can consume variation galleries from day one without waiting for a separate API release, a notable improvement on the Brands merge which initially shipped without REST endpoints.

Examples and use cases

The most obvious use case is fashion. A T-shirt sold in five colours can finally show five proper galleries: front, back, detail shot and on-model image per colour, with the gallery swapping cleanly as the shopper toggles the colour swatch. Today most Woo fashion stores either accept that swatches only change the featured image, or pay for the AVI extension to bridge the gap.

The same pattern applies to furniture sold in multiple finishes, electronics with colourway variants, jewellery with metal options, and any made-to-order product where the visual difference between variations matters to the purchase decision. For these categories, variation galleries are not a polish feature, they are part of the conversion path.

There is also a long tail of less obvious use cases. Configurable B2B products (industrial fittings, components, signage) can show installation context per variant. Subscription boxes with seasonal options can show what each variant contains. Custom-printed products can show mockups per design choice. In each case, the alternative without variation galleries is either a longer description, a third-party plugin, or a custom theme template.

What this means for UK merchants and agencies

For merchants currently paying for the Additional Variation Images extension, the migration is meant to be seamless. WooCommerce moves the legacy data from _wc_additional_variation_images into the canonical core location on rollout, the AVI extension automatically deactivates when the core feature is switched on, and the legacy meta is preserved on disk so a rollback is possible without data loss. That is a sensible migration design and removes most of the upgrade risk for stores already on AVI.

For merchants who have never used a variation gallery, the feature is opt-in initially. It is disabled by default in 10.9 and has to be turned on under Settings, Advanced, Features, or via WP-CLI with wp option update wc_feature_woocommerce_additional_variation_images_enabled 'yes'. WooCommerce plans a phased rollout: opt-in in 10.9, a 5% canary in a later release that flips the option via a database updater for selected stores, then 100% enablement once the canary clears.

For agencies running Woo retainers, that phased rollout matters. A change that ships behind a feature flag and then quietly enables itself on selected stores can surprise client teams who were not briefed. The practical move is to audit which clients use variable products, add variation galleries to the next routine maintenance window as a deliberate opt-in, and document the new admin field for content teams before the canary catches them out. The same checklist sits naturally within an agency-grade WordPress maintenance routine.

For stores still on the fence about Woo versus a hosted platform, this is one more data point on the "platform investing in core merchant features" side of the ledger. Native variation galleries close a gap that hosted platforms have closed for years, and lower the total cost of ownership for fashion and configurable-product merchants on Woo. If you are scoping an ecommerce build, the calculation now assumes core variation imagery rather than a paid extension.

Practical considerations before enabling it

The first cut is deliberately scoped. WooCommerce has prioritised the things that are hard to get right later (migration path, backwards compatibility, feature parity with the AVI extension, REST API support) over UI polish. The admin gallery editor is described by the WooCommerce team as "still a little rough on the edges" in 10.9, with follow-up improvements expected through the canary phases. Stores that depend on a slick admin experience for non-technical merchandisers should set expectations accordingly.

Theme overrides also need a quick check. WooCommerce has preserved the legacy meta on disk so the runtime fallback keeps un-migrated variations rendering correctly and theme overrides of the affected templates continue to work, but any custom theme that reaches into AVI's meta keys or template parts directly should be tested against a 10.9 staging site before the canary rolls out. The migration handles the data, it does not retest your bespoke gallery template.

Finally, image weight is the silent cost of variation galleries. A product with five variations and six images per variation is thirty images served on a single product page, even with lazy loading. Stores enabling the feature should make sure their image optimisation pipeline (WebP or AVIF delivery, responsive srcsets, a sensible CDN) is in good shape before opening the floodgates. The feature gives merchants the tools to show much more imagery, it does not make the underlying pages lighter.

How to prepare for the 10.9 rollout

A short pre-flight checklist covers most stores. First, identify which products in the catalogue are variable and would benefit from per-variation imagery. For many stores this is a smaller set than expected, and the prioritisation work can start now without waiting for 10.9 to ship.

Second, decide whether to enable the feature in the opt-in phase or wait for the canary. Stores already running AVI have a clear path: enable the core feature in 10.9 on staging, validate the data migration, then promote to production. Stores not on AVI have less urgency, but enabling early gives the merchandising team time to learn the new unified field before the canary forces the decision.

Third, build the photography brief. Variation galleries reward stores that can produce consistent shot lists per variant. A capsule that calls for, say, front, back, lifestyle and detail per colourway makes it easy to brief a photographer and easy for the merchandising team to populate the new gallery field. Without that discipline, variation galleries quietly bloat into uneven, half-populated lists that hurt rather than help conversion.

FAQ