Muse, the personal shopping agent Meta launched on September 8, 2026, can reach your products by two routes, and they can run at once.
- Catalog presence. Shopify documents a Meta channel that makes products available “through Shopify Catalog”, with direct checkout on Meta surfaces “including Muse when available”.
- Browser discovery. Meta’s Muse marketing page and launch post describe Muse as a browser-using agent that researches and compares prices across retailers.
An outside vendor ran 50 prompts in one retail category through one Muse account and saw both routes feed the final product cards. That’s useful evidence that both exist. It’s one category on one account, so it can’t tell you either route’s share of the market.
The practical upshot: check your catalog data and your live product page separately, because each route reads a different copy of your facts. Checked on 2026-10-27; re-check before acting.
The evidence teardown: catalog versus browser
This table is the core of the page. Each row is one question, answered separately for each route, with the source and its status.
| Question | Catalog route | Browser route | Source and status |
|---|---|---|---|
| Does Meta describe it? | Not on Meta’s Muse pages. Shopify describes it | Yes: Meta describes Muse as using a browser to research and compare retailers | Meta marketing page and launch post. Shopify help, current |
| How do products get in? | Shopify Catalog. “You don’t need to do anything” if eligible | Muse visits sites live. No submission | Shopify help, current. Meta marketing page and launch post |
| What data does it read? | Your Shopify product data and store policies | Whatever your page shows a browser | Shopify help, current. Reading method from Profound’s trace |
| What’s required? | Catalog-eligible products. For direct checkout: supported market, supplemental terms, three store policies | Nothing documented. The page has to load and work | Shopify help, current |
| How does the buyer pay? | Shopify-powered direct checkout on Meta surfaces, on by default. Shop Pay may show in Muse | Muse checks out on your site. Meta names Link by Stripe, with a one-time card | Shopify help, current. Meta announcement |
| Can you switch it off? | Yes, two separate switches in Shopify. Products may still appear through crawling | Not documented | Shopify help, current |
| What did the 50-prompt trace see? | About 60 products from 30 merchant sites per prompt, about 2 of 6 final cards | About 3 domains visited, 4 products from 2 sites, about 4 of 6 final cards | Profound, third-party vendor trace |
| What isn’t known? | Which catalog Muse queries, and how it ranks | How Muse picks sites to visit, and how it ranks | Not documented by Meta |
Two things are worth noticing. First, Meta’s own public pages describe only the browser route. The catalog side of Muse is documented by Shopify, and described by Profound as “a Meta product catalog” that “also powers shopping on Instagram and Facebook”. Meta itself hasn’t said that in what we read.
Second, the routes read different copies of your facts. The catalog route reads your structured product data. The browser route reads your rendered page. If they disagree on price, stock or a spec, Muse could see two different products.
What the 50-prompt trace does and doesn’t show
The trace is the most detailed public look at how Muse shops, and it will get quoted out of context. Here’s what Profound reported, beside what it would take to claim more.
| Profound reported | What that supports | What it doesn’t support |
|---|---|---|
| 50 prompts, one consumer retail category, one Muse instance. Profound called it “small, exploratory” and “illustrative rather than definitive” | Both routes existed in that test | Anything about other categories, accounts or dates |
| Typical final set: 6 cards, 2 from the catalog and 4 from the browser | The browser route contributed cards despite a much smaller candidate pool | “Two-thirds of Muse sales come from browsing.” Cards aren’t purchases, and one category isn’t the market |
| The catalog returned about 60 products from 30 sites per prompt | The catalog route offers a wide candidate pool | That catalog products are disadvantaged. The ranking step wasn’t measured |
| Muse checks the user’s shopping profile before searching | Personal history shapes the request | How much it changes the result |
| Muse’s browser sessions don’t name themselves and use residential connections | Server logs may not show Muse visits clearly | A reliable way to count Muse traffic |
The sentence to remember: a 50-prompt vendor trace is not a market share. Use it to decide that both routes deserve attention. Don’t use it to decide which one matters more for your store.
We can’t add a test of our own. We haven’t run Muse, and we can’t see what it shows any shopper.
Checking the catalog route
If you sell on Shopify, here’s what the Meta channel documentation says, in the order to check it.
1. Is the store in Shopify Catalog? The catalog route depends on it. The plan rule is Starter or higher and no private mode. A store on the Agentic plan that hasn’t published an online store on a paid plan is an exception and can still be included through agentic storefronts. Products need a title, an image, a price above 0 and a product URL, and the store needs good account standing. The details are in our Shopify agentic storefronts guide.
2. Do you meet the direct-checkout conditions?
| Condition | Shopify’s wording | Note |
|---|---|---|
| Market | Sell to customers in the United States, Canada, Mexico, Brazil, Japan or Singapore | Wider than the markets Meta names for Muse itself |
| Terms | Agree to the Agentic Storefronts Supplemental Terms | Someone with admin rights must accept |
| Policies | Terms of service, privacy, and return and refund policies completed | Keep them current. Shopify says what Meta shows should match your store |
| Product types | Subscriptions, bundles, customizable and B2B-only products not supported | They may still be discoverable |
| Delivery | Local delivery and pickup not supported | — |
| Disclosures | Put relevant legal disclosures in the first 6,000 characters of the description | — |
3. Know the two switches. Shopify describes separate controls for Shopify Catalog access and Direct checkout, under Sales channels > Agentic > Meta AI and Muse, after turning off “Allow Shopify to manage for me”. We haven’t seen these screens. Shopify warns that turning off Catalog access doesn’t hide products from crawling, and points to a separate setting for hiding products from AI channels.
4. Expect the reporting gap. Google Analytics and custom pixels won’t fire in Meta’s direct checkout. Orders show up in Shopify attributed to Meta, and you stay merchant of record. Shopify’s agentic reports combine referral and direct-checkout sales per channel. So you can see Meta-attributed sales, but not which Muse route produced them.
Shoppable ads are a separate requirement: they need the Facebook and Instagram by Meta sales channel with product syncing on. That’s ad inventory, not Muse discovery, and Meta says Muse doesn’t share people’s conversations with its ad systems.
Checking the browser route
There’s no switch and no submission. Muse opens the page the way a shopper’s browser would. So the check is whether a browser can read the facts, and whether the checkout works for an agent.
| What to check on the live page | Why it matters for an agent | How to check it yourself |
|---|---|---|
| The deciding spec, with its unit and condition, appears as text | An agent comparing products needs the number, not a picture of it | Select the text on the page. If you can’t highlight it, it’s probably an image |
| Price and stock match your catalog data | Two routes, two copies. A mismatch makes the product look unreliable | Compare the page with the product record in Shopify |
| Key facts load without a click, tab or app widget | Profound reports Muse navigates using the page’s accessibility tree, built from your HTML and labels | Turn off JavaScript, or use a screen reader, and see what’s left |
| Buttons and options have labels | Same reason. An unlabelled size picker is hard for an agent to use | Check the variant selector and add-to-cart button have readable names |
| Checkout doesn’t force an account | Muse completes purchases for the user, with approval | Try a guest checkout from a private window |
| Return policy is one click from the product | Muse files returns through merchant support flows | Find it from the product page in one step |
The accessibility-tree point comes from Profound’s write-up, not from Meta. It’s sensible advice for any browsing agent, and it overlaps with ordinary accessibility work. Our AI visibility audit turns these checks into a full pass.
A worked case: one product, two copies
Hypothetical store, for illustration only: a Shopify store, Basic plan, selling a large-room humidifier to the US and Canada. We checked the case against the Shopify Meta channel page and a pattern from our own catalog snapshot.
In that snapshot of 10 humidifier listings for “humidifier for dry winter air large room quiet top fill”, a decibel figure was in the description of 4 listings and in the description or Shopify-generated metadata of 6. None put it in the title. So the same fact can live in one copy of a product’s data and not the other.
| Fact | Product page (browser route) | Catalog data (catalog route) | What to fix |
|---|---|---|---|
| Noise level | A decibel figure and its setting in the description text | Only in Shopify-generated metadata, without the setting | State the number with its setting in the description, so both copies carry it |
| Room size | In a comparison image only | Missing | Write it as text in the description |
| Fill type | “Top fill” in the title | “Top fill” in the title | Nothing |
| Price | Sale price shown | Sale price synced | Nothing, but re-check after every promotion |
| Returns | Policy linked in the footer | Return and refund policy completed in Settings | Link it from the product page too |
Where each fact sits in this store is made up for the illustration. The pattern isn’t: facts often sit in one copy of the data and not the other. Fixing the description fixes both routes at once, which is why it’s the first thing to do.
How this compares with other assistants
Muse is the only assistant in this group whose maker describes it mainly as a browsing agent. On ChatGPT, OpenAI says Shopify data is “already integrated” through Shopify Catalog and names the factors it uses to rank merchants. Meta publishes nothing equivalent for Muse. Our platform comparison puts the routes side by side. The sibling guides cover Perplexity, Copilot and Amazon’s assistant.
Your next step
Pick your best-selling product and put two things side by side: its product record in Shopify, and the live product page in a private browser window. Go down the worked-case table and fill in both columns for your own product. Every row where the two copies disagree, or where a fact sits only in an image, is something to fix in the description first.