
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 Route orders to originals rewrites new-order line items from the merged variant back to its original source variant, so third-party fulfillment, 3PLs, and ERPs keep working after a merge.
A merge creates new variant IDs. Anything that fulfills your orders by Shopify variant ID, such as a print-on-demand service, a 3PL, a dropship feed, or an ERP, no longer recognizes the merged variants, and orders stop routing. Route orders to originals, under Settings, fixes that by quietly putting the original variant back on each new order before those systems see it. It markets as Order Routing.
An order line item on a merged variant is swapped to the original variant before fulfillment
Routing is needed only when a third-party service handles your fulfillment through the original products. A print-on-demand service, a dropshipper, a warehouse, or an ERP that cannot be switched over to the merged products, and cannot match them by SKU, has to receive the original variants on the order.
You don’t need this if you manage stock yourself in Shopify, if your fulfillment service can have the merged products assigned to it, or if it finds products by SKU. Most stores are in that group and can leave routing off.
If you are not sure where your service fits, Using Merges with third-party fulfillment walks through the common providers.
When Route new orders to originals is on, Merges watches for new orders. For every line item on a merged variant, it rewrites the order: the original source variant is added at the same quantity and the merged line is zeroed out. Your storefront and the customer still show the merged product they bought, while your fulfillment, 3PL, or ERP receives a variant ID it already recognizes and fulfills as it always did. No reconfiguration on their side.
Each merged variant carries a reference to the source variant it came from (written at merge time), which is how Merges knows what to swap back to. The rewrite happens automatically on new orders. The customer is not notified, and stock is not restocked by the swap.
The permission is requested only when you enable the setting. Revoke order access later and Merges turns routing back off automatically.
Routing is for fulfillment systems that identify products by Shopify variant ID, Printful and Podbase for example. Systems that match by SKU (Spark Shipping, and GigaB2B after a manual remap) recognize the merged variants on their own and don’t need it, because Merges preserves SKUs. It pairs naturally with Mirror original products: one keeps the merged catalog’s stock accurate, the other sends fulfillment back to the source.
For the exact reconnection steps per provider, covering Printful, GigaB2B, Spark Shipping, 3PLs, Microsoft Business Central, and the systems that can’t be merged at all, see Using Merges with third-party fulfillment.
Only if your fulfillment service has to see the original variants. That means a print-on-demand service, a dropshipper, a 3PL, or an ERP that identifies products by Shopify variant ID and cannot have the merged products assigned to it. If your service finds products by SKU, or you fulfill orders yourself, you can leave routing off.
No. The storefront and the order confirmation still show the merged product the customer bought. Only the line items your fulfillment service reads are changed, and the order total stays the same.
That line is skipped and ships as the merged variant. Merges archives originals at merge time, so keep them archived rather than deleting them.