Guides·
Why native Shopify variants win in agentic AI shopping
Native Shopify variants beat fragmented products in agentic AI shopping. Why ChatGPT, Google AI Mode, Copilot, and Perplexity reward consolidation.
How inventory behaves after a merge, what breaks when a third-party supplier reimports products, and how to restore sync with dropshippers like Printful and GigaB2B.
Merging creates a brand new Shopify product with brand new variant IDs. That is what makes the merge result a first-class Shopify product, but it also means anything outside Shopify that tracked the old IDs needs to be pointed at the new ones.
This page explains what stays in sync automatically, what breaks, and how to reconnect third-party fulfillment services after a merge.
For suppliers that perform a destructive catalog sync, avoid reimporting original products after merging. A reimport can recreate the old product IDs in your Shopify store, which competes with the merged product and can cause duplicate listings, split inventory, and broken links. Behavior varies by provider - some suppliers skip existing products, others overwrite them.
Check how your supplier's sync behaves before merging. If you are unsure, pause the supplier's automatic product sync before merging and re-enable it only after you have confirmed the merged product is recognized on their side. The provider-specific sections below call out which integrations are known to reimport aggressively.
Merges reads available and on_hand quantities from the source products at the time of merge and writes them to the merged variants across every location the source products stocked.
committed and reserved quantities are tied to unfulfilled orders placed against the original source variant IDs. These stay on the archived source products until the underlying orders fulfill; they do not transfer to the merged variants. incoming quantities from open purchase orders stay attached to the source products for the same reason.
If your stock is held entirely in Shopify and no external system writes to it, no further setup is required. If an external system manages stock (a supplier, warehouse, ERP, or 3PL), enable Sync original products so ongoing changes on the source products propagate to the merged variants. See the Sync original products section below.
Sync original products is the feature that keeps merged products aligned with their source locations. Enable it from Settings in the Merges app.
Per source location, you can enable any combination of:
Each sync type has its own toggle per location, so you can, for example, sync inventory but not price if prices are managed directly on the merged product.
The feature works with the source locations used by your original products, including:
The number of source locations you can sync from is plan-gated:
| Plan | Locations |
|---|---|
| Basic | 1 |
| Pro | 3 |
| Unlimited | 5 |
If your store uses more locations than your plan covers, pick the locations that represent your primary inventory sources and enable Sync original products on those. The merged product will show a "Syncing N of M location" indicator in the panel.
Sync original products is webhook-driven. A change on a source product is picked up within 5 seconds to 5 minutes. Very large catalogs (9,000+ variants) can take longer during peak update periods.
See the Sync original products entries in Troubleshooting common issues.
Because the merged product has new variant IDs, the fulfillment service must be told which of its SKUs now map to which merged variants. How this works depends on the provider.
Printful references products by Shopify variant ID. The new variant IDs created by a merge are not recognized by Printful until the merged product is connected to the original Printful variants.
The current supported workflow uses Sync original products and Order routing together:
With both features on, inventory on the merged product reflects the original Printful variant's stock, and orders for merged variants are rewritten to use the original variant IDs before Printful sees them. Printful fulfills the order against the IDs it already recognizes.
Full guide: Printful setup.
GigaB2B references products by Shopify variant ID internally. The new variant IDs created by a merge are not recognized until you ask GigaB2B's support to remap them. Their side does not expose a self-service SKU-based resync.
Steps.
Do not trigger a reimport from GigaB2B's catalog while waiting. A reimport will recreate the source products and split your inventory.
For any fulfillment service not listed above, the steps are the same:
Immediately after saving the merge, inventory may display as 0 on the merged product while third-party services catch up. Wait a few minutes for the next sync cycle, then:
If stock does not return within an hour, open the troubleshooting steps for your specific integration (linked above), or email support@merges.io with the merged product URL and the supplier you are using.
The original products are archived, not deleted. If you need to roll back, set their status back to Active in the Shopify admin and delete the merged product. Suppliers that reference the original IDs will resume syncing.
For complex cases, email support@merges.io - do not attempt a mass reimport, as it will create duplicates.
