Guides

Syncing products between stores: copy once, diverge on purpose

Product sync is really two different jobs — getting the catalogue into the second store, and deciding which fields stay aligned afterwards. The tools for each, the fields that should never sync, and why 'sync everything' is usually the wrong default.

“Sync products between stores” hides two jobs that want different tools and different levels of caution. Job one is getting the catalogue over there — a one-time copy, low-risk, boring, solved. Job two is keeping fields aligned afterwards — an ongoing marriage between two catalogues that were usually supposed to diverge. Merchants who conflate them end up mirroring fields they needed to keep different, or hand-maintaining fields a tool should own.

Job one: the copy

Three tiers, by catalogue complexity:

• Native CSV — Products → Export in the first store, import in the second. Fine up to a few hundred simple products. Images travel as URLs, variants as rows, SKUs intact. No metafields.
• Matrixify — the workhorse for big catalogues, metafields, selective re-runs, and update-in-place. If the copy is something you will do more than once, start here and skip the native CSV entirely.
• Duplication apps — when the second store should start as a clone of the first, store-wide. What happens the morning after a duplication is its own guide, because the copy is the easy half.

Whichever tier: audit SKUs first. The copy faithfully propagates every duplicate and blank SKU into the second store, doubling the cleanup and pre-breaking any future matching.

Job two: what stays aligned — a field-by-field decision

After the copy, every product field is either owned by the main store (edits flow across) or owned by each store (allowed to diverge). The failure mode is not choosing: then whichever tool you installed chooses for you, silently, on its defaults.

Two rows deserve their warnings in full. Price sync across stores with different positioning is a slow-motion incident — one update in the main store and the wholesale store is selling at retail, or the outlet at full price. And status sync turns a routine tidy-up in one catalogue into products vanishing from another storefront.

The tools that do ongoing product sync

Being direct about what this site’s own app does not do: StockUnison syncs quantities only. For field-level product sync between Shopify stores, the real candidates and their framings, consistent with the full comparison:

• Multi-Store Sync Power — products, collections and inventory, with field-level toggles. The breadth pick; its review record has sharp edges worth reading first.
• Tipo Multistore Sync — SKU-based product and inventory sync, reaching into pages and blogs. Variant-count pricing.
• SyncLogic — clones products store-to-store with per-feature sync toggles and a wholesale angle; compared separately.
• Syncio — product fields as a paid add-on beside its inventory sync; strongest when the stores belong to different businesses (supplier–retailer).

The question that separates them in practice is not coverage but restraint: can you exclude a field, and what happens to an unmatched product? A product-sync tool that responds to “no match” by creating the product is the most common way catalogues get duplicated — reasonable when you asked, catastrophic as a silent default.

The pattern that works for most two-store setups

1. Copy once with Matrixify — full catalogue, metafields included, SKUs audited first.
2. Let content diverge. Prices, tags, collections and copy belong to each store’s audience. Batch genuine content updates through Matrixify re-runs on the fields you choose, on your schedule.
3. Sync quantities continuously, one way, out of the store that tracks the shelf — because stock is the one field where divergence is never intentional.

This “copy once, diverge on purpose, sync the quantities” shape is less automated than mirroring everything, and that is its virtue: every difference between your stores is one you chose.

Where StockUnison sits

StockUnison is the third step and only the third step: one-way quantity sync between SKU-matched variants, with duplicates refused, preview mode first, every write logged, and no product ever created, edited or deleted anywhere. If you need job two — ongoing field sync — the honest answer is one of the tools above. If your setup is copy-once-and-diverge, quantities are the only field left needing a tool at all, and the free plan will show you exactly how well the copy holds up as a matching base.