Build your catalog once in one Shopify store and publish it to your other stores — each one with its own brand name, vendor, prices and copy. Nothing is written until you approve the preview, and inventory is never touched.
Build your catalog once in one Shopify store and publish it to your other stores — each one with its own brand name, vendor, prices and copy. Nothing is written until you approve the preview, and inventory is never touched.
A group that runs more than one Shopify store usually builds the catalog properly in exactly one of them. The others get a copy — made by CSV export, by a bulk tool, or by someone recreating products by hand. From that moment the stores drift. A description is fixed in one place and not the other, a metafield definition exists on one store under a slightly different key, a new collection never makes it across.
The usual tools make this worse rather than better, for two reasons. They sync, which means they overwrite: the sister store cannot have its own brand name, its own vendor, its own price list, because the next sync flattens it. And they are blunt — you find out what changed after it has been written, not before.
So teams fall back to doing it by hand, which does not scale past a few hundred SKUs, or they accept catalogs that disagree with each other.
It treats one store as the main store — the place the catalog is actually built — and the others as brand stores. You pick what to publish, you see a field-by-field preview of exactly what each brand store will receive, you change anything you want per brand, and only then does anything get written.
What travels is the catalog and the content around it: products with their variants, media and metafields; manual and smart collections; metafield and metaobject definitions and entries; files; pages; blogs and articles; navigation menus. Links and images inside descriptions are rewritten for each store.
What does not travel is everything that belongs to the store rather than the catalog: inventory, orders, customers, discounts, URL redirects, translations and theme templates. The app never requests inventory, order or customer access, so it cannot change stock even by accident.
| What it does | Why it matters to the business |
|---|---|
| One catalog, many stores | The work of building a product properly is done once, not once per store. |
| A field-by-field preview per brand store | You see what each store will get before it is written, instead of auditing afterwards. |
| Per-brand name, vendor, price formula and rules | Sister stores can stay genuinely different without being re-synced back into sameness. |
| Field locks and conflict detection | An edit made in a brand store is surfaced as a conflict, not silently overwritten. |
| Updates waiting | Changes in the main store queue for review; nothing is pushed until someone publishes. |
| Publish back, with approval | A brand team can send a correction upstream without being given the main store. |
| Scheduled launches, undo and full history | A launch can go live everywhere at one moment, and be rolled back if it is wrong. |
| Inventory is never synced | Stock stays the responsibility of each store, which is usually what a finance team wants. |
Probably not for you if: you want inventory, orders or customers kept in step between stores — the app deliberately does none of those — or you only run a single Shopify store.
Still stuck? Email [email protected] — we reply within 24 hours, every day of the year.
NIVI Solutions builds and supports the app. Contact our team through the app or our contact page for help.
Yes. We can configure the app, import your data and connect it to your ERP as part of a Shopify project.
Yes. NIVI Solutions is a Shopify Partner with 15+ years of B2B commerce experience.