> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-shopify/shopify-integration/products/multiple-store-setup.md).

# Product Synchronization for Multiple Shopify Stores

Some retailers run more than one Shopify store for the same brand or catalog. In HotWax Commerce, the product store decides which catalog a Shopify shop belongs to.

For multi-store setups, the safest model is:

* Use one shared HotWax product store when Shopify shops sell the same catalog.
* Use separate HotWax product stores when Shopify shops sell different catalogs.
* Use the same product identifier across related Shopify shops when they share a catalog.

The product sync console asks users to confirm related Shopify stores before the first import because this choice affects orders, inventory, routing, fulfillment, and reporting.

## Primary and related shops

When several Shopify shops share one product catalog, one shop usually acts as the main source of product data. Related shops can share the same HotWax product store when their Shopify products use the same identifier convention, such as SKU or barcode.

This matters because HotWax uses the selected product store and identifier to decide whether incoming Shopify products link to existing HotWax products or create new product links.

## First-time setup for a multi-store catalog

Before starting product sync for a Shopify shop:

1. Open the shop in the Company app.
2. Open `Product sync`.
3. Review the selected product store.
4. Confirm whether related Shopify shops use the same catalog.
5. Confirm the product identifier matches the retailer's catalog convention.
6. Review counts and preflight warnings before starting import.

Read [First-time Product Sync Setup](/documents/learn-shopify/shopify-integration/products/product-sync-first-time-setup.md) for the full walkthrough.

## Ongoing product updates

Returning shops use the same product sync history and progress tracking as single-shop setups. HotWax reads product update runs for the selected Shopify shop and applies changes to the HotWax catalog linked to that shop's product store.

Read [Product Sync Console](/documents/learn-shopify/shopify-integration/products/product-sync-console.md) for progress and history behavior.

## What to avoid

Don't run legacy product import jobs for child catalogs. The old `Import Products`, `Import Product updates`, and `Import Products in Bulk` Job Manager flows no longer represent the current product sync path.

Don't connect unrelated Shopify shops to the same HotWax product store. If two shops use different catalogs or different identifier rules, sharing the same product store can create incorrect product links and downstream order or inventory issues.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hotwax.co/documents/learn-shopify/shopify-integration/products/multiple-store-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
