New / Channels

Meta now sits alongside the
AI channels in your admin

Meta now appears alongside the other AI channels inside Agentic Storefronts in the Shopify admin. Products areshared with Meta by default.

What's on this page
  1. In 30 seconds: what happened
  2. How it works: how products reach Meta
  3. Three things you can do in the admin
  4. What "shared by default" means
  5. How to check (3 steps)
  6. What this announcement doesn't say
  7. Five points developers should know
  8. Three use cases you can put to work
  9. A one-line summary for your pitch

1In 30 seconds: what happened

In the Shopify admin's Agentic Storefronts ,Meta now appears as one of the AI channels.
Products are shared with Meta by default via Shopify Catalog. Merchants can manage Catalog and direct checkout access from agentic settings, and review how Meta is performing.

① Listed with the rest

Meta now shows up on thesame screen, in the same listas the other existing AI channels. Not a special slot — just one channel among the rest.

② Products are shared by default

Through Shopify Catalog, products are shared with Metaby default. Do nothing, and sharing stays on.

③ Control and measurement

Manage Catalog / direct checkout access in agentic settings, and view Meta's performance.

2How it works: how products reach Meta

Products in your store Shopify admin Shopify Catalog Sharing is ON by default Access can be managed Foundation for sharing Meta As an AI channel Other AI channels (listed on the same screen) agentic settings Managing Catalog access Managing direct checkout Reviewing Meta performance Where merchants take action
Agentic Storefrontsis: a framework that treats the paths by which AI discovers products and guides shoppers to purchase as "channels" within the Shopify admin.
This change is that, to that list, the name Meta has been added. It is not a newly created mechanism, but ratheran added connection— that is the accurate reading.

3Three things you can do in the admin

The announcement explicitly states the following three points. No other settings or actions are mentioned.

Managing Catalog access

You can manage access for product sharing through Shopify Catalog.Sharing defaults to ON , so this is where to act if you want to limit it.

Managing direct checkout

Access to direct checkout is managed from the same settings screen. This is the control point for whether checkout is completed on the AI channel side.

Reviewing Meta performance

You can view Meta channel results within the agentic settings.No details are given on the metrics breakdown, granularity, or update frequency.

4What "shared by default" means

AspectWhat the announcement statesHow to read it
Initial state Sharing ON Shared by default via Shopify Catalog Products are passed to Meta without the merchant applying or setting up a connection.
Control Managed in settings Catalog and direct checkout access If you want to stop or limit it, you need togo into the settings yourself(opt-out model).
Where it appears Same level Listed alongside other AI channels Rather than a Meta-specific screen, you manage it across AI channels.
Performance visibility Viewable Meta performance in the agentic settings Per-channel measurement is expected to be self-contained in the admin.
Eligible stores and regions Not stated The announcement says nothing about plan requirements or supported countries. Check what actually shows up in your admin.
"Doing nothing means it gets shared" is the key point of this change. Stores with internal rules about sharing product data externally (B2B-only products, region-restricted products, products with wholesale pricing, and so on) should assumeit may already be ON by default without you noticingand check the settings screen once.

5How to check (3 steps)

1

Open Agentic Storefronts

See whether Meta is listed under Agentic Storefronts in the admin.

2

Check access in the agentic settings

Confirm that Catalog and direct checkout access match your intent.

3

Review performance

Check results coming through Meta and compare them with other AI channels.

The announcement gives no detailed screen flow or menu names. The steps above follow the places it does mention (Agentic Storefronts / agentic settings).For the exact steps, see the "Sell on Meta" help docs.

6What this announcement does not say

It is a short announcement, so much of what you need in order to decide is missing.treat it as "not stated" rather than guessing and turn it into a verification task— that is the safe approach.

Not stated

Supported countries and plans

There is no statement of which stores can use it. Availability for Japanese stores is also unstated.

Not stated

Fees and costs

Nothing is said about whether there are additional costs or fees on sales made through Meta.

Not stated

How APIs and webhooks are handled

There is no mention of configuring this via the Admin API, of any identifier attached to orders, or of webhook behavior.

Not documented

Scope of the product data that gets shared

It only says "products are shared." Which fields are included, and how often inventory and pricing sync, is unclear.

Not documented

Definition of the performance metrics

Which metrics are available, and at what granularity or over what period, is not stated.

Not documented

Relationship to existing Meta integrations

How this coexists or overlaps with Meta-related sales channels and apps you already use is not addressed.

7Five points developers should know

Default

1. It is opt-out by design

Sharing is ON by default."Whether to turn it off," not "whether to turn it on"— that is the task to create. In practice, add "check the agentic settings" to the audit checklist for your client stores.

2. What actually does the sharing is Shopify Catalog

This is not a Meta-specific integration setting; it goes through Catalog, a shared foundation. In other words, how well you maintain the product data that lands in Catalog directly determines the quality of your exposure across every AI channel.

3. direct checkout is a separate control

The changelog states explicitly that Catalog (= showing your products) and direct checkout (= letting people buy there) can bemanaged separately. So "we want the exposure, but keep checkout on our own site" is a split the settings can express.

API ?

4. Nothing is said about the API surface

The announcement stays entirely at the admin UI level; how this is handled in Admin GraphQL / webhooks isNot documented. If you plan to build automation or attribute orders to their source, expect to verify against real data first.

5. Build monitoring on the assumption that channels will keep being added

It says Meta appears "alongside other AI channels."A structure where more names keep filling that same slotis the reasonable read. Rather than handling each channel one at a time,a checklist that periodically reviews the agentic settingsis easier to budget for once you build it into your operations.

8Three ways to use this in practice

USE CASE 1

A blanket "should this be shared?" review across the stores you maintain

Problem
Products are shared with Meta by default. Stores with B2B-only products, region-restricted products, or merchandise meant to stay unlisted have no visibility into whether unintended external exposure is already happening.
What to do
Open the agentic settings on every store you manage and record the access state of Catalog and direct checkout → share "here's where you stand today" with the client and get their decision on whether to keep it or turn it off.
Impact
You defuse complaints before they start, and at the same time you create a new proposal touchpoint: an "AI channel status report."
Technical notes
Bulk checking via the API isnot documented. Start by writing this up as an admin-based runbook, then switch to automation once API support is confirmed.
Catalog checkout Meta
USE CASE 2

A phased rollout plan: take the exposure, keep checkout in-house

Challenge
The business wants the revenue that comes through AI channels, but worries that if checkout also completes on the channel side, the design of their customer data, package inserts, and CRM programs falls apart.
Approach
Take advantage of the fact that Catalog access and direct checkout access are managed separately: first run withproduct exposure onlyenabled, then decide whether to allow direct checkout after seeing the performance — a two-stage approach.
Impact
Avoids the fruitless "all on or all off" debate and lets you decide while gathering data.
Technical notes
The announcement explicitly states that the two can be configured independently. However,the specific granularity of each setting is not documented, so check the settings screen in a live store before turning this into a proposal.
Meta
USE CASE 3

Build a per-AI-channel performance comparison report into your regular meetings

Challenge
You have no way to explain to the business whether AI-driven traffic and revenue are growing, or which channels are actually working.
Approach
Since Meta and the other AI channels now sit on the same screen, take the performance view in the agentic settings andadd it to your monthly recurring report. Set it up so that when a channel is added, you just add a row.
Impact
No more wasted effort starting from research every time a new channel appears, and you accumulate evidence for decisions — keep the exposure, turn it off, or invest more.
Technical notes
The types and granularity of the metrics you can view arenot documented. For the first round, decide the report format from screenshots of the actual screen, then consider automated aggregation once the metric names are settled.

9A one-line summary you can use in a proposal

"Meta has joined the list of AI channels in the Shopify admin, andproducts are shared by default via Shopify Catalog.
The decision isn't whether to do it, but whether to stop it— start by opening the agentic settings and
checking that Catalog and direct checkout access are set the way you intend."