Guides

Connecting two Shopify stores: what actually links, and what never will

There is no connect button between Shopify stores. 'Connecting' is a different job per layer — products, inventory, orders, customers, gift cards — and each layer has different tools, different failure modes, and a few that cannot be linked at all.

People ask “how do I connect two Shopify stores” expecting a setting. There is no setting. What there is: seven or so layers of data, each with its own answer, ranging from “continuous sync, solved problem” to “genuinely impossible, plan around it”. Treating them as one question is how merchants end up buying a tool that links the layer they did not care about.

Here is the map. The verdicts assume you own both stores; supplier-retailer setups between different businesses change some tools but not the shape.

Inventory: the layer that must stay linked

If both stores sell the same physical stock, quantities are the one layer where a one-time copy is worthless — the copy is stale by the first sale. This is the best-served layer in the ecosystem precisely because it hurts the most: continuous, automatic, one-way sync from a source store is a solved problem, and the two-store guide compares the three ways to do it, from CSV routines to apps.

It is also the layer where the failure is a customer-facing incident rather than an inconvenience — an unlinked catalogue is extra work, an unlinked inventory oversells.

Products: copy is easy, ongoing sync is a decision

Getting products into the second store is a solved, one-time job — CSV export/import for simple catalogues, Matrixify for large ones or anything with metafields. Keeping them aligned afterwards is a genuine fork in the road: some setups want every edit mirrored, most want the catalogues to diverge on purpose — different prices, different titles, different collections per audience.

That decision, and the tools on each side of it, get their own guide. The one-sentence version: sync quantities always, sync product content only if you can say who owns which field.

Orders: forwarding, not merging

Orders belong to the store that took them and cannot be moved — but they can be echoed. The common patterns: forwarding destination orders to a source store for fulfilment (the supplier-retailer shape, which is Syncio’s home ground), or aggregating both stores’ orders in an external OMS or 3PL dashboard so one team ships from one queue.

If the second store exists for wholesale, think twice before forwarding B2B orders into your retail store’s order list — reporting and tax both get muddier.

Customers: a copy with holes in it

The CSV round-trip carries the records but not the relationship: no passwords (not exportable, by design), no order history (orders stay home), no store credit. Imported customers are new accounts wearing familiar names. For a brand split across stores this is mostly fine; for a migration it is the largest source of support tickets, so send the “set your password” campaign deliberately rather than letting customers discover it.

The layers with no bridge

Gift cards, discount codes, and blog/page content each live and die in one store. The first two are policy problems more than technical ones — decide what support says before the first “my code doesn’t work on your other site” email. Content is a copy-once job with the theme.

Analytics deserves its own sentence: Shopify will never show you both stores in one report. If “how is the brand doing” is a question you ask, wire both stores into one GA4 property or a reporting tool on day one — retrofitting history later is somewhere between painful and impossible.

Where StockUnison sits

StockUnison connects exactly one of these layers: inventory quantities, one-way, from a main store into every store you pair with a join code — matched by SKU, previewed in preview mode, logged write by write. It does not touch products, prices, orders or customers, on purpose: the quantities layer is the one where being narrow and refusing to guess is a feature. The free plan runs the match report against both catalogues, which is a fair way to find out how linkable your stores’ SKUs actually are before paying anyone for any layer.