How to sync product variations and images across multiple WooCommerce stores

Why variations are the hard part

Simple products sync easily: a title, a price, a description, done. Variable products are a different problem entirely. A single running shoe might have three colors and eight sizes, which means 24 individual variations, each with its own SKU, price, stock count and often its own image. Multiply that across a catalog of a few hundred styles and you have tens of thousands of moving parts that all have to land correctly on every connected store.

This is the point where CSV re-imports and hand-rolled scripts usually start producing bugs: a size disappears, a color swatch points at the wrong image, or a variation SKU collides with one already on the spoke store. Getting WooCommerce variation sync across stores right means treating attributes, variations and media as three separate but linked problems, not one generic "copy the product" operation.

Recreating attributes on each store

Before a single variation can sync, the attributes it depends on — Color, Size, Material — need to exist on the destination store in a form WooCommerce recognizes. Global attributes are taxonomies under the hood, so a naive sync either has to create matching taxonomy terms on each spoke or, worse, falls back to plain custom product attributes that lose swatches, ordering and reusability across products.

Variations & Attributes Sync handles this by recreating the attribute taxonomy and its terms on the spoke store automatically the first time a product using it is synced, then reusing that same taxonomy for every subsequent product. A "Size" attribute created once for your UK store's shoes is the same "Size" attribute every later product syncs against — no duplicate taxonomies with slightly different slugs piling up over time.

• Global (taxonomy-based) attributes are recreated with matching slugs, so filtering and swatch plugins keep working on every store.
• Attribute terms used by a product are created on demand — you don't have to pre-populate every possible color on every spoke before the first sync.
• Attribute ordering and "used for variations" flags carry over, so the variation dropdowns look the same everywhere.

Per-variation fields that must travel

Once the parent attributes exist, each individual variation needs its own complete set of fields synced — not just the attribute combination that identifies it. It's easy to sync the variation's existence and still end up with wrong prices or missing stock on the spoke store.

Full Product Data Sync covers the parent product; variation-level detail is what Variations & Attributes Sync adds on top, so every variation arrives on the spoke store as a complete, orderable record rather than a placeholder that needs manual cleanup.

Images, galleries and deduplication

Images are the other place multistore sync commonly goes wrong. Referencing an image by URL — as a CSV export does — means a spoke store's product page breaks the moment the source image moves, gets renamed, or the hub's CDN configuration changes. Proper WooCommerce image sync across stores should copy the actual file into each store's own media library, not link back to the hub.

Images & Media Sync does exactly that: featured images, full galleries, and individual variation images are uploaded into each connected store's media library and deduplicated by source, so re-running a sync — which happens constantly as products get edited — never leaves you with five copies of the same shoe photo cluttering the media library.

• Featured image and gallery images sync as real media attachments on every target store.
• Variation-specific images (a colorway's own photo) are matched to the correct variation, not just dumped into the general gallery.
• Deduplication by source means editing a product's description ten times doesn't re-upload the same images ten times.

Keeping variations in sync after launch

The first sync is the easy part. The real test is what happens six months later when a merchandiser adds a new size, discontinues a color, or runs a seasonal sale price on half the variations.

Auto-Sync on Edit means saving the parent product on the hub queues the update to every targeted store automatically, variations included — nobody has to remember to manually re-push a product just because a size was added. If you'd rather review before anything goes out, or you're auditing the whole catalog at once, the Product Sync Matrix shows every product's sync status per store in one grid, with the ability to re-sync a single product or an entire filtered set in one click.

• New variations added after launch sync the same way as the original set — no separate "add variation" workflow to remember.
• Discontinued variations can be removed or set out of stock and that status propagates, rather than leaving a phantom size buyable on a spoke store.
• Bulk price changes across many variations (a seasonal sale) go out through the normal auto-sync path, no special-casing needed.

Worked example: a shoe retailer

Picture a running shoe brand with a UK hub store and connected spoke stores for Australia and Germany. Each shoe style is a variable product with Color and Size attributes, roughly 20 variations per style, and a handful of photos per colorway. Prices differ by market — GBP on the hub, AUD and EUR on the spokes — but the catalog, sizing structure and imagery need to match exactly.

The merchandising team authors every style once, in the UK hub: title, description, Color and Size attributes, per-variation SKUs and stock, and a gallery plus per-color variation images. New styles are targeted to AU and DE using per-store targeting the same way as any simple product — see the catalog rules covered in the guide to managing multiple WooCommerce stores from one dashboard.

When that style saves, the Color and Size attributes are created (or matched, if already present) on both the AU and DE stores, all 20 variations sync with their own SKU, stock and image, and the gallery photos land in each store's media library. A month later, when a new colorway is added mid-season, the same flow handles it: the new attribute term, the new variations, the new images — no manual re-export, no re-uploading photos three times.

A pre-launch checklist

Before switching a variable-product catalog over to automated sync across stores, it's worth confirming a few things directly on a test product:

• Global attributes exist with matching names and slugs on every connected store, not just the hub.
• A variation's SKU, price and stock all appear correctly on the spoke store, not just the parent product's fields.
• Variation images match the correct color or style, and the featured image and gallery both transferred.
• Editing the hub product and re-saving updates the spoke store without creating a duplicate product.
• Draft or out-of-stock variations behave the same way on spokes as they do on the hub — see Draft & Unpublished Product Sync if you stage new styles before launch day.

If you're evaluating tools for this rather than building it in-house, this is the exact set of behaviors to test during a trial. Stillpoint's product sync features are built around variable products as a first-class case rather than an edge case, and plans covering variation and image sync are on the pricing page.