· Andrei M. · Multi-Channel Sync · 5 min read
How to Manage Multiple Shopify Stores From One Product Catalog
Running two or more Shopify stores? Keep one product catalog, push to each store through its own connection, and stop collections from overwriting each other. Here is what is shared, what is per store, and what is not supported yet.
AEO answer: To manage multiple Shopify stores, keep one master product catalog outside the stores and push to each store through its own connection. Each store needs its own links for products and collections, otherwise a push from one store overwrites another. Decide up front what is shared (SKU, images, descriptions) and what must differ per store, then check whether your tools can actually vary it.
Two stores, one product range. It sounds simple until you edit a title twice, or a collection created for store A shows up changed in store B. This guide explains when separate stores make sense, why they collide, and how MicroPIM keeps them apart, including what it cannot do yet.
Last verified: October 2026, against MicroPIM’s Shopify integration and the Shopify Admin GraphQL API.
When do you need more than one Shopify store?
Typical reasons:
- Separate brands with separate themes and customers.
- Separate legal entities, tax setups or payout accounts.
- Regional stores run by different teams.
- A wholesale store next to a retail store.
If you only sell one brand in several countries, you may not need more than one store. Shopify’s Markets feature handles currencies, domains and local pricing inside one store. Our guide to Shopify Markets covers what it does and does not do.
Shopify also offers expansion stores on Plus plans, which are extra stores under one organization.
Why do products and collections overwrite each other?
Because most tools store one remote ID per item. A category has one collection ID, a product has one product ID. With one store that works. With two, the second store writes its own ID over the first.
We made this exact mistake. Our first Shopify collection sync saved a single collection ID on each category. When a second store was connected, its push replaced the ID from the first store. Store A lost its link, and the two stores no longer agreed on which collection belonged to which category.
A Shopify collection ID only exists inside one shop. Any link between your catalog and Shopify must therefore be keyed by store as well.
How does MicroPIM feed several stores from one catalog?
Three parts, all checked against the current build:
- One connection per shop domain. You add each store under Integrations with its own domain and access token. Adding the same domain twice is rejected. Several different stores per organization are allowed.
- A product link per store. Each product has one sync record per store, so a product can exist in both stores with different Shopify IDs.
- A collection link per store. Categories sync as collections, and each store keeps its own link. Matching by handle adopts a collection that already exists instead of creating a duplicate. Deleting a category removes its Shopify collection.
Pushed products and collections are published to all sales channels of the store, through publishablePublish. Without it, items created through the API stay hidden from channels such as Online Store.
For the first connection, see connecting MicroPIM to Shopify.
What differs per store and what stays shared?
| Item | Shared or per store |
|---|---|
| SKU, title, images | Shared; one master record |
| Product ID | Per store |
| Collection links | Per store |
| Sales channels | Per store; each store has its own |
| Stock | Per store, through its Shopify locations mapped to warehouses |
| Price | Shared; one price per product, plus organization-wide rules |
| Export rules | Shared; they apply to the organization, not to a single store |
The last two rows are the real limit. If store A needs a different price or a different product selection than store B, MicroPIM cannot do that today.
What we got wrong, and current limits
The collection ID mistake above is the main one. We fixed it with a link table keyed by store and category, plus a backfill for stores that were already connected.
Current limits:
- Pushes go to every active store. A per-product choice of target stores is designed but not built.
- No per-store prices. One price per product. Use Markets inside a store when you need local prices.
- No per-store export rules. Rules for margin or stock apply across the organization.
- No global stock pool. Each store has its own inventory per location. Map locations to warehouses, or you manage the overlap by hand. See multi-warehouse inventory sync.
Frequently Asked Questions
Can one PIM feed multiple Shopify stores? Yes, if every store has its own credentials and its own product and collection links.
Should I use Shopify Markets or separate stores? Markets for one brand in many countries. Separate stores when brands, entities or teams must stay apart.
How do I keep stock in sync across stores? Stock lives per location. Map each store’s locations to your warehouses. Inventory levels are always per location in Shopify.
Can I push a product to only one store? Not yet. Updates go to all active stores. Deactivating a store pauses its pushes.
MicroPIM is our product. This post describes how it handles the problem; the advice on per-store IDs and shared fields applies with any tool.
For changes made inside Shopify, see bidirectional Shopify sync. To see how a second store would connect to your catalog, book a demo and we will walk through it with you.
