# Is My Product Catalog Shared Automatically? Two Cases

> Shopify shares products to Meta by default. Microsoft publishes your catalog when you accept an analytics tool's terms. Neither is a syndication decision anyone made.

Canonical: https://brandonlazovic.dev/articles/catalog-shared-by-default/  
Author: Brandon Lazovic  
Published: 2026-09-23

## The short version

- Shopify made Meta an AI channel with catalog sharing on by default and no opt-in step, so a merchant's products reach Meta's shopping surfaces without anyone choosing it.
- Microsoft publishes a merchant's catalog to its own Merchant Center when they accept the Brand agents terms, which happens while installing a free analytics product.
- The two mechanisms are different and the difference matters. One is a default with no opt-in, the other is consent bundled into a terms acceptance. Both end with the catalog distributed.
- Microsoft also obliges the merchant to add specific wording to their own site privacy statement, which is a compliance change nobody reviewing a feed would think to look for.

Two product announcements landed this month that read as ordinary feature news and are not. Shopify made Meta an AI channel, with a merchant's products shared there by default. Microsoft put a shopping assistant inside its free analytics product, and installing it publishes the merchant's catalog to Microsoft's own Merchant Center. In neither case did a merchant sit down and decide to syndicate anything.

> Shopify shares products to Meta through Shopify Catalog by default, with no manual sync required.

## What did Shopify actually turn on?

Meta became a sales channel inside Shopify admin, and the catalog connection is on rather than offered. Shopify's changelog says products "are shared with Meta by default through Shopify Catalog." [1] The changelog says a merchant can manage access for Catalog and for direct checkout, and see performance scoped to Meta. [1]

Shopify's help documentation complicates that, describing discovery for Meta as powered by the sales channel itself rather than by a Catalog access setting. Confirm in your own admin which control governs Meta.

Read that ordering carefully, because it inverts the usual one. The controls are there to turn something off, not to turn it on. A merchant who never opens the agentic settings panel has still made a distribution decision, and made it in the affirmative.

Shopify's Spring 2026 Catalog repositioning has arrived here in a form you can point at. I argued in an earlier piece that Shopify had turned Catalog into the substrate underneath agentic commerce, letting merchants who do not even run Shopify storefronts sync in and sell through AI channels. That was the strategic read. Default-on sharing to Meta is what it looks like from inside one merchant's admin.

## How is Microsoft's version different?

Microsoft asks permission, which sounds better until you notice where the asking happens. Clarity is Microsoft's free session-recording and analytics product, installed on a great many sites for reasons that have nothing to do with product feeds. Brand agents is a shopping assistant a merchant adds through it, currently in beta for Shopify and WooCommerce stores.

The relevant sentence is Microsoft's own, and it is worth quoting exactly: "When you accept the Brand agents terms, you consent to having your catalog published to Microsoft Merchant Center (MMC)." [2] That is a genuine opt-in. It is also a terms acceptance during an analytics install, which is the least likely moment in a merchant's month for anyone to be thinking about where their product data goes.

The destination is worth naming too. Microsoft Merchant Center is the counterpart to Google's, so what happens here is concrete: a copy of the catalog enters a feed system, and from there it reaches Bing, Copilot and other Bing-grounded assistants.

<aside class="guardrail"><span class="lab">Accuracy guardrail</span> Marketing coverage of Brand agents quotes a conversion-lift multiple for agent-assisted sessions. I went looking for it in Microsoft's own documentation and could not find it there, so I am not repeating the number, and neither should anyone pitching this internally. Everything else in this piece comes from the two companies' own product documentation, read on September 14, 2026.
</aside>

## Why does the Shopify and Microsoft distinction matter?

Flattening the two into "both are default-on" would be wrong, and a merchant who checks will find it wrong. Shopify's mechanism is a default with no opt-in step anywhere in the flow. Microsoft's is a consent, obtained properly and recorded in terms the merchant accepted.

What the two share is that neither decision was made on its own merits. One merchant never saw a question. The other saw a question wearing the clothes of an analytics install. Both end with a product catalog distributed to an AI shopping surface. The useful audit question is what your existing integrations already syndicate for you.

Both belong on a feed review checklist that has never carried them. Feed audits look at data quality, identifier coverage, disapprovals, and the destinations you configured. Neither of these two arrived through a destination anyone configured.

## What does accepting the Brand agents terms commit you to?

Microsoft requires a change to your own site's privacy statement, and this is the part nothing else has covered. The documentation supplies the wording merchants must include, disclosing that business and order-management data is used to deliver the experience, that data may be captured through first-party and third-party cookies, and that conversational content and interaction events are shared with Microsoft. [3]

Installing a free analytics tool therefore creates a legal obligation on a document the marketing team owns, written in language the vendor supplies, about data flows nobody in the feed review has looked at.

Shopify's Meta channel carries no equivalent requirement in its changelog. That asymmetry is not a criticism of Microsoft, which documented the obligation plainly. It is an argument that these two integrations need reviewing in different places by different people, which is exactly what makes them easy to miss.

## What should a merchant actually check this week?

Open the settings rather than the feed, because the data is fine and the distribution is the part nobody configured. Three checks cover it, none of them long, and two of them live in screens a feed review never opens.

In Shopify admin, look at the agentic or AI channels panel and read which channels are connected and what each one shares. The controls for catalog sharing and for direct checkout are separate, so confirm both, and treat anything you did not deliberately switch on as a finding rather than a default you accepted.

If Clarity is installed anywhere on your properties, find out whether Brand agents was ever enabled with it, and if it was, whether your privacy statement carries the required wording. The install may well have been done by someone measuring user behavior who had no reason to think about product data.

Then widen the question past these two vendors. The pattern is that catalog distribution has started arriving bundled with tools bought for other jobs, and Shopify and Microsoft are simply where it became visible first. Ask what already holds a copy of your feed, and check the integrations you installed for other reasons first.

## Sources

1. Shopify Changelog: Meta is now an AI channel in your admin — https://changelog.shopify.com/posts/meta-is-now-an-ai-channel-in-your-admin
2. Microsoft Learn: Brand agents overview — https://learn.microsoft.com/en-us/clarity/brand-agents/brand-agents-overview
3. Microsoft Learn: Sample wording for Brand agents site and privacy policy disclosure — https://learn.microsoft.com/en-us/clarity/brand-agents/brand-agents-privacy-disclosure
