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.
A provider-by-provider guide to merging products that are fulfilled by third-party services - Printful, GigaB2B, Spark Shipping, and generic dropshippers - with the exact reassignment steps for each.
Merging creates a new Shopify product with new variant IDs. Third-party fulfillment services that track products by Shopify ID need to be told about the new IDs. This page covers the providers we see most often, with the exact steps for each.
For general inventory behavior after a merge, see Managing inventory after product merging.
Order routing makes merged products work with fulfillment services that identify products by Shopify variant ID. When a customer orders a merged variant, it rewrites the line item back to the original source variant before the fulfillment service sees it — so an ID the service already recognizes comes through, and it fulfills normally. Enable it under Settings → Order routing (“Route orders to originals”).
For how it works, the order-access permission it requires, the originals-must-stay-in-your-store requirement, and setup, see the full guide: Order routing.
| Provider | Requires Order routing |
|---|---|
| Printful | Yes |
| Podbase | Yes |
| Spark Shipping | No (SKU-based) |
| GigaB2B | No (SKU-based, but needs manual remap by their support) |
| Shopify Fulfillment Network | No |
Printful identifies products by Shopify variant ID. After a merge, the new variant IDs will not match anything in Printful, and stock and fulfillment will break unless you connect the merged product back to the original Printful variants.
The supported workflow:
With both features enabled, inventory on the merged product mirrors the original Printful variant’s stock, and orders placed on the merged product are rewritten to use the original variant IDs before they reach Printful.
Full setup guide: Printful setup.
Spark Shipping identifies products by SKU rather than Shopify variant ID. Because Merges preserves the original SKUs on merged variants, Spark Shipping recognizes the merged product automatically on its next sync cycle.
Steps.
No manual reassignment is needed. Order routing is not required for Spark Shipping.
If duplicate product records appear in Spark’s dashboard after a merge, wait until you have confirmed the merged product is syncing correctly, then delete the originals in Spark.
GigaB2B assigns products to its internal catalog by Shopify variant ID, not by SKU. When Merges creates a merged product with new variant IDs, GigaB2B’s existing mappings no longer resolve, and stock drops to zero on the merged product.
Resyncing requires GigaB2B’s side. Their SKU-based remap is not self-service; you need to contact their support.
Steps.
Most dropshipping apps reference products by Shopify product ID. After a merge, the merged product will show zero stock on their side until it is reassigned. The steps:
If a 3PL (including Shopify Fulfillment Network) manages stock via Shopify’s native fulfillment service API, the merged product is visible to them as soon as Shopify reflects it - typically seconds. The 3PL’s system should pick up the new product on their next read.
If they track products by an internal SKU rather than Shopify ID, confirm the merged variants carry the same SKUs as the source variants. Merges preserves SKUs from the source products unless you edit them in the editor.
If your fulfillment integration is custom-built or uses an older API:
If the integration stores data outside Shopify, you may need to push a manual update to the integration’s system via API or CSV. Most vendors accept a “remap these old IDs to these new IDs” request.
BC’s internal mapping table keys on the original Shopify variant IDs. Running “Sync Products” after a merge only updates the staging tables, not the Item Cards, so merged variants remain orphaned in BC. If you are on BC, contact support before merging; we can walk through the resync path.
Some systems cannot be made to work with merged products. Their sync models overwrite or reject Merges’ output in ways we cannot work around.
BigBuy performs a destructive catalog sync, which overwrites all product data in your Shopify store from BigBuy’s catalog on each sync cycle. After a merge, BigBuy recreates the original products and the merged product is orphaned. We do not recommend merging products managed by BigBuy.
Gooten’s API does not expose the endpoints we need to implement Order routing. Their mapping is variant-ID-based and they do not support manual SKU remap at scale. Merchants on Gooten should not merge products fulfilled by Gooten.
If you are on either platform and still want to consolidate your catalog, contact support first. We may be able to recommend an alternative approach for your specific setup.
If a fulfillment provider cannot handle reassignment - or the cost of reassigning is high - consider whether the merge is worth it. A good sanity check:
Tell us the provider and what is happening. Email support@merges.io with:
We have seen most of these cases and can usually point to the exact step the provider needs from you.
