We maintain a bundles app. Around 3 to 4 days ago we started seeing a new issue that our clients are experiencing.
Our app creates a product to represent each bundle (with the variant set to requiresComponents: true) and publishes it only to the Online Store publication. We never request any AI / agentic channel.
The symptom: merchants whose stores have the Agentic channel with “Allow Shopify to manage for me” enabled can no longer save or activate bundles. Any productUpdate on the bundle product now returns these userErrors and the mutation fails:
{ "field": ["resourcePublications", "channelId"],
"message": "Resource publications channel Microsoft Copilot does not support bundle products" }
{ "field": ["publications", "0", "channelId"],
"message": "Channel Microsoft Copilot does not support bundle products" }
The same surfaces in the admin product page as “There are 2 errors with this product” for the bundle (screenshot below).
What we understand so far:
- Bundle products are not supported on some agentic channels (Microsoft Copilot, Google AI Mode / Gemini).
- With “Allow Shopify to manage for me” on, Shopify auto-enrolls and publishes eligible products to those channels via Shopify Catalog. The merchant did not publish to Copilot, and there is no per-product or per-channel toggle they can find short of disabling Copilot globally.
- Our
productUpdateinput contains nopublicationsfield, yet the error referencespublications.0.channelId, which suggests the mutation is validating or auto-syncing the product against the managed publications and rejecting it because it is a bundle.
Our questions:
-
Is this the intended behavior? It seems wrong that a
productUpdatewhich does not touch publications fails entirely because of an auto-managed, incompatible channel. We would expect Shopify to simply skip publishing an unsupported product type to that channel rather than rejecting the whole mutation. -
What is the API-supported way for an app to exclude bundle products from agentic channels?
-
How can we test agentic storefronts in development stores? They do not appear to be available for password-protected stores, which makes it hard to reproduce and verify a fix.
Any clarification on the intended pattern here would help.
