For brands running, or about to open, a second Shopify store

Syncing Multiple Shopify Stores: Decide First, Then Sync What Matters

A second Shopify store usually arrives for a good reason: a New Zealand or US launch, a wholesale site that should not show trade prices to retail shoppers, a second brand, or an outlet for end of season stock. Each new store is a completely separate Shopify instance with its own products, its own stock numbers, its own customers and its own payouts. Nothing is shared unless something shares it.

Before syncing anything, it is worth asking whether you need a second store at all. Shopify Markets and the B2B features on a single store now cover many of the reasons people used to open one. Where separate stores are genuinely right, the work is deciding which store or system owns each piece of data, mapping IDs that never match between stores, sharing one physical stock pool without overselling, and getting every order into the ledger under the right entity and tax treatment. This page walks through that decision and each sync, with the failure modes we see at launch.

Review Your Multi Store Plan (03) 9003 0111

The Structure of a Multi Store Setup

3 decisions

Before any sync is built

One store or several, who owns stock, which legal entity each store sells under

4 IDs

Differ per store for every variant

Product, variant, inventory item and location IDs all need a mapping table

1 owner

Per field across all stores

Title, price, stock and images each have exactly one place where they are edited

0 shared

Customers, stock or payouts by default

Separate stores share nothing until an integration or app makes them

Why a Second Store Is Harder Than It Looks

Most multi store problems trace back to one of these four facts. Knowing them early often changes the decision itself.

One store with Markets often does the job

Shopify Markets lets a single store sell into several countries with local currency, per market pricing or price adjustments, translated content, separate domains or subfolders and market specific product availability. If your reason for a second store is simply selling to New Zealand or the US from the same Australian business and warehouse, one store keeps a single catalogue, one stock count and one customer base, with nothing to sync. Separate stores start to earn their keep when the legal entity, warehouse, brand, theme or checkout rules genuinely differ between markets.

A second store is a full copy, not a view

An expansion store is not a filtered version of your main store. It has its own product, variant and inventory item IDs, its own metafield definitions, its own collections, its own installed apps and its own theme. Copying a catalogue once is easy with a CSV export. Keeping it in step for years, as products are added, retired, repriced and rewritten, is the actual job, and it needs a rule about which store is the master and what the other stores are allowed to change locally.

Shopify counts stock per store

Each store holds its own inventory quantity for each location, and a sale in one store does not reduce stock in another. If both stores sell from the same Melbourne warehouse, you have one physical pool and two independent counters that will drift apart within hours of launch. Something has to own the real number, usually the ERP, a warehouse system or a nominated master store, and push available quantity to each store with reservations and buffers applied.

Finance gets several of everything

Every store produces its own orders, refunds, payouts, fees, gift cards and reports, sometimes in different currencies and sometimes for different legal entities. If the NZ store belongs to a New Zealand company and the AU store to an Australian one, orders must land in different ledgers with different tax treatment. Shopify’s reports are per store, so month end turns into stitching exports together unless orders and settlements are posted into the accounting system consistently from day one.

What Has to Be Synced When Separate Stores Are Right

Six areas. Each one needs an owner, a direction and a rule for exceptions before any connector is switched on.

One catalogue, many stores

Catalogue master and ID mapping

One source creates products, usually the ERP or a PIM for operational fields and the main store for content. Every other store receives them. A mapping table links each SKU to its product, variant and inventory item ID in every store, because those IDs never match. Handles can stay consistent for clean URLs and hreflang, but matching should run on SKU or a dedicated metafield, never on title. Metafield definitions, collections, images and translations are replicated deliberately, with a list of fields each store may override locally.

Available to sell per store

One stock pool, many counters

A single owner holds on hand and committed quantities for each physical location, then publishes available to sell into every store that ships from it. Orders from any store reserve stock at the owner immediately, so a sale on the NZ site reduces what the AU site can sell within a minute or two. Buffers can differ per store, for example a larger buffer on the wholesale store where one order can take forty units. Stock held only for one store, such as outlet seconds, is kept as its own location.

Right price, right currency

Pricing per store and per list

Each store gets prices from a defined source rather than from hand edits: AUD retail, NZD retail set as its own price list rather than a currency conversion, and trade prices for the wholesale store. Decide whether NZD prices are GST inclusive at the New Zealand rate, and how rounding works. Compare at prices and sale schedules need the same treatment, otherwise a promotion ends on one store and keeps running on another. Price changes are logged with the store, the old value and the source.

Clean per store records

Customers kept separate

Customer accounts belong to each store, and there is no automatic shared login between separate stores. That is usually fine: a retail shopper and a trade buyer have different accounts and expectations anyway. Where you want a single customer view, build it in the ERP, CRM or email platform by matching on email with consent recorded per store, rather than copying accounts between stores. Copying customers can send marketing to people who never opted in on that store and can mix entities that hold data under different privacy policies.

Correct ledger and GST code

Orders into the right entity

Every store’s orders flow into the ERP or accounting system tagged with the source store, legal entity, currency, tax treatment and sales channel. An AU store selling to Australian consumers posts with GST. An NZ store run by a New Zealand entity posts into that entity with New Zealand GST. An AU store shipping to NZ consumers may have its own obligations, so the tax code is set from the destination and the entity, not guessed. Payouts and fees are reconciled per store, per currency, against the right bank account.

One view, no silent drift

Consolidated reporting and drift checks

Sales, margin and stock are reported across stores from the ledger or a reporting layer, converted to AUD at a stated rate, rather than by adding up Shopify exports. Alongside the numbers, scheduled checks compare the stores: products present in the master but missing elsewhere, variants with no mapping, price lists out of date, apps installed on one store but not another, and theme sections or scripts that diverged. Drift is reported weekly so it is fixed while the gap is small.

Common Multi Store Situations, Before and After

Task	Traditional	Synced Properly	Notes
AU and NZ store, one warehouse	Two stock counters, oversells	ERP publishes one pool to both	If the NZ store is the same entity, ask first whether Markets on the AU store would remove the problem entirely.
Retail plus wholesale store	Products keyed in twice	Master catalogue replicated with trade fields	Wholesale store adds pack sizes, minimums and trade pricing as local fields while content stays mastered centrally.
Several brands, one company	Separate ad hoc connectors	One order flow tagged by brand	Each brand keeps its own store and theme while orders, stock and payouts land in one ledger with brand reporting.
Outlet store for seconds	Seconds sold as full stock	Separate location and SKU suffix	Seconds stock lives at its own location so the main store never sells a damaged unit as new.
New product launch	Live on one store, missing on others	Published to each store by rule	Launch date, price and availability set per store, with a check that every mapping exists before go live.
Stock arrives at the warehouse	Updated on the main store only	Every store updated within minutes	Receipts post once at the stock owner, then flow to each store using the location and buffer for that store.
Customer wants one login	Accounts copied between stores	Separate accounts, joined in CRM	A single customer view built where consent and entity are recorded, not by duplicating accounts across stores.
Month end across stores	Exports stitched in a spreadsheet	Posted per entity, reported together	Each payout reconciled to its own clearing account, then consolidated in AUD for management reporting.

Failure Modes to Design Out

Sync loops between stores

If store A updates store B and store B updates store A, one edit can bounce back and forth, overwriting newer values or burning through API rate limits. Give every field a single direction from its owner, ignore updates that originated from the sync itself by tagging them, and never let two stores both write the same field. Test by editing a product in each store and watching what happens for ten minutes.

Duplicate products

Duplicates appear when matching runs on title or handle, when a CSV import is repeated, or when staff create the product manually in the second store before the sync arrives. Match only on SKU or a dedicated identifier metafield, make creation one directional, and run a daily report of products in any store with no mapping row. Fix the mapping rather than deleting the product, or you lose its reviews and URL history.

Oversells in launch week

Launch is when oversells are most likely: marketing sends traffic to a store whose stock was loaded from a spreadsheet days earlier, and both stores sell the same last units. Load stock from the owner on launch morning, set wider buffers for the first fortnight, and rehearse the sync with real order volumes in a development store before switching the new store to live payments.

Customer data across entities

Copying customer records between stores run by different entities, or into an overseas entity, is a disclosure of personal information. Under the Privacy Act 1988 and the Australian Privacy Principles, that should match what your privacy policy says and what customers consented to, including for marketing. Keep accounts per store, share only what is needed, and check the approach with your privacy adviser.

Wrong tax treatment on cross border sales

New Zealand GST works differently from Australian GST, and an Australian store selling low value goods to New Zealand consumers may have New Zealand GST obligations once sales pass a threshold set by Inland Revenue. Exports from Australia may be GST free if conditions are met. Set tax codes by entity and destination, and confirm the position with an accountant familiar with both countries.

Building what one store already does

A second store doubles apps, theme work, staff accounts and sync risk. If the stores would share an entity, a warehouse and a brand, Shopify Markets for currencies and countries, or the B2B features on one store for trade buyers, is often the better answer. Plan features change, so check your current Shopify plan and agreement for what Markets, B2B and expansion stores include before deciding.

How Yes AI Approaches Multiple Shopify Stores

The decision before the build

We start with whether you need separate stores at all, comparing Markets and single store B2B against expansion stores for your entity, warehouse, brand and checkout needs. Sometimes the recommendation is one store and no sync work.

Ownership mapped field by field

We document who owns every product, price, stock and customer field, which store may override what, and how each store maps to an entity, location and tax code, so the design is agreed before anything is connected.

Built and monitored by us

Catalogue replication, stock publishing, order posting and drift checks run on a managed cloud automation layer we operate, with ID mapping tables, logs of every change, and alerts when a store falls out of step.

Launch rehearsed, then handed over

We rehearse the new store launch in a development store, review staff accounts and permissions on every store, and hand over runbooks so your team knows how to add a product, a store or a price list.

From One Store to Several, Without the Mess

Five steps. A second store with shared stock and orders into the ledger is typically live in six to ten weeks, depending on the ERP and how clean the catalogue is.

Decide the store structure

One store with Markets or B2B, or separate stores, based on entity, warehouse, brand, theme and plan inclusions.

Agree owners and mappings

Master for each field, SKU matching rules, the ID mapping table, and each store’s entity, location and tax codes.

Build catalogue and stock sync

Products, metafields, collections, images and translations replicated, with one stock pool published to every store.

Connect orders and payouts

Orders from every store posted to the right entity and tax code, with payouts reconciled per store and currency.

Rehearse launch, then monitor

Test orders on every store, launch day stock load, wider buffers, then weekly drift and mapping reports.

FAQ

Should we use Shopify Markets or open a separate store?

Start with Markets if the same Australian business sells the same products from the same stock to other countries. You keep one catalogue, one stock count and one customer base, with local currency and pricing per market. Choose a separate store when the market is run by a different legal entity, ships from a different warehouse, needs a different brand or theme, or needs checkout and app behaviour Markets cannot provide. Check your current plan, because what Markets includes varies by plan.

Can Shopify share inventory between stores automatically?

Not across separate stores on its own. Each store counts its own stock per location, so a sale in one store does not reduce another. Shared stock needs an owner that both stores read from, typically your ERP, warehouse system or a nominated master store, connected by an integration or an app. For two stores on one warehouse with simple products, a well reviewed app may be enough. With an ERP, bundles or a 3PL involved, the ERP should usually own the number.

Should wholesale be on the same store or a separate one?

It depends on your plan and how different trade buying is. Shopify’s B2B features on a single store can give trade buyers their own catalogues, price lists and payment terms while sharing products and stock, which removes most sync work. Availability of those features depends on your Shopify plan, so check your agreement. A separate wholesale store makes sense when the trade experience, theme, minimums or apps are very different, or when retail shoppers must never see the wholesale site.

Can customers use one login across our stores?

Not automatically. Customer accounts belong to each store, so a shopper with an account on your AU store has no account on your NZ or outlet store until they create one. Some businesses accept that, since retail and trade customers rarely overlap. If you need a single view of a customer, build it in your CRM, email platform or ERP by matching on email address, with consent recorded per store. Avoid bulk copying accounts between stores, particularly between different legal entities.

How is GST handled when we add a New Zealand store?

It depends on which entity runs the store. If a New Zealand company runs it, those sales generally fall under New Zealand GST in that company’s books. If your Australian business sells directly to New Zealand consumers, New Zealand GST registration may be required once sales pass the Inland Revenue threshold, and the Australian side treats exports under its own rules. Set tax codes by entity and destination, and confirm with an accountant familiar with both countries. This is general information only.

Do expansion stores cost extra?

That depends on your Shopify plan and agreement, and the inclusions have changed over time, so check your current terms rather than relying on an old blog post. Remember the hidden costs too: every store needs its own apps, often billed per store, its own theme maintenance, its own staff accounts and its own payment and tax setup. Those running costs often decide whether a second store is worthwhile, more than the plan fee itself.

How long does it take to sync a second store properly?

For a second store sharing stock with the first, with orders posting to an existing ERP or accounting system, six to ten weeks is a typical range including a rehearsal in a development store. A catalogue that needs cleaning first, a new legal entity, translations, or a third and fourth store add time. Most of the effort sits in agreeing ownership and mappings, not in the connectors, which is why we start there.

Get a Straight Answer on One Store or Several

Book a call. We look at your entities, warehouses, brands and Shopify plan, tell you plainly whether Markets or B2B on one store would do the job, and if separate stores are right, give you a priced plan to sync them safely.

Book a Multi Store Review (03) 9003 0111

All discussions held in confidence. Australian-based consultants.