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).
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 productUpdate input contains no publications field, yet the error references publications.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 productUpdate which 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.
Thanks Anton. Confirming your findings and the workaround too on our end. Definitely seems like a Shopify bug related to Bundles trying to automatically published to Global Catalog and Copilot even though they are not compatible.
@Alan_G sorry to tag you directly, but this doesn’t look like it’s been picked up by any Shopifolk on the forum. When you have a moment could you please raise this issue?
Thanks for flagging this. I checked into it and this does look like a it’s a possible issue on our end rather than something related to your apps.
My understanding is that Bundle products aren’t currently supported in direct checkout for some agentic channels like Microsoft Copilot, but a normal product save/update generally shouldn’t fail just because a managed agentic channel has an incompatible publication record that the merchant/app isn’t actively publishing to.
It looks like we may have a fix on the way for this and I’m checking on rollout timing now and will loop back once I can confirm it’s live.
For now, the best workaround is still to disable Direct checkout / manage Microsoft Copilot manually from the Agentic settings if merchants are blocked. Not super ideal, but that should avoid the failing validation until the fix is fully rolled out.
Let me know if I can clarify anything on our end here!
No problem @Anthony_SL - it looks like the fix I had been tracking is deployed - can you let me know if you’re still seeing the issue? If so, if you’re able to share a request ID from the failed call I can take another look!
I checked this on our end and can confirm you’re still hitting the same Microsoft Copilot bundle-product publication validation. The fix I was tracking has deployed, but your request looks like it’s hitting another path, so I’m going to look into this further on my end.
For now, the workaround is still to disable Direct checkout / manage Microsoft Copilot manually from the Agentic settings if merchants are blocked. Appreciate your patience folks, I’ll loop back here once I have a confirmed fix or a better workaround.
Following up on this one. We’re still seeing the error daily, so it looks like that second code path is still affected. Any progress on the investigation?
Happy to send over fresh request IDs if that would help. Thanks!
Just confirming this is still being worked through on our end but I don’t have a concrete timeline to share. If you’re able to share one or two fresh request IDs from recent failures, ideally from the last day or two, I can tie those back to the active investigation and advocate prioritization on my end though for sure.
For now, the workaround is still to disable Direct checkout / manage Microsoft Copilot manually from the Agentic settings for merchants who are blocked. I know that’s not ideal, but it should avoid the failing validation while the cleanup work is still in progress.
I’ll keep tracking this and loop back once I have a more concrete rollout update.
