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.
What happens to inventory when you merge - which quantities transfer to the merged product, which stay on the archived originals, and how to keep stock in sync with suppliers afterward.
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 inventory transfers at merge time, how to keep the merged product in sync afterward, and how to verify stock once the merge is saved.
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), keep the merged product aligned with Sync original products, covered next.
The transfer above is a one-time snapshot taken when you save the merge. To keep the merged product aligned as stock, price, SKUs, and barcodes keep changing on the source, turn on Sync original products in the Merges app Settings. It mirrors changes from each source location to the matching merged variant, usually within seconds. It is a paid feature, gated on how many source locations you sync from and the total number of synced variants.
For the full reference - what it syncs, the per-location toggles, plan limits, the Sync status states on the Merged products page, and requirements - see Sync original products.
Because the merged product has new variant IDs, any fulfillment service that tracks products by Shopify ID - Printful, GigaB2B, Podbase, and most dropshippers - has to be told which of its SKUs now map to the merged variants. The usual mechanism is Sync original products paired with Order routing (which rewrites order line items back to the original variant IDs before the service sees them), but the exact step differs by provider: some remap by SKU automatically, others need a support ticket, and a few cannot be merged at all.
For the provider-by-provider reconnection steps - Printful, GigaB2B, Spark Shipping, 3PLs, Microsoft Business Central, and the incompatible systems (BigBuy, Gooten) - see Using Merges with third-party fulfillment.
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 in Using Merges with third-party fulfillment, 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.
