Shop Pay ships in Muse while Amazon blocks the agent

In the space of two days, the two biggest names in ecommerce took opposite positions on the same AI agent. Shopify opened agentic checkout with Shop Pay to Meta's Muse. Amazon blocked Muse from its site outright. If you sell online, you are not a spectator to this — you are the thing being fought over.

What actually happened

On September 21, Shopify CEO Tobi Lütke posted that Shopify is "partnering deeply with Muse to enable agentic checkout with Shop Pay on all Shopify stores." Meta chief AI officer Alexandr Wang confirmed the partnership on the other side. Shopify shares moved up on the news.

Amazon went the other way. Bloomberg and TechCrunch reported Amazon began blocking Muse from Amazon.com after Meta declined a request to keep the site out of the agent's scope. Shoppers hitting checkout through Muse got a popup: continued access by an unauthorized AI agent violates Amazon's Conditions of Use. Amazon's stated objections are that Muse does not identify itself while browsing and that credential handling creates privacy and security risk. Meta's response is that Muse "has no visibility into people's passwords or payment methods."

One detail we could not confirm from a primary source: whether individual Shopify merchants get a Muse-specific opt-out. Shopify documents agent controls for other crawlers and assistants. We have not found equivalent published controls for Muse, so treat "all Shopify stores" as the operative phrase until Shopify says otherwise.

Why agentic checkout matters for your business

Strip the platform drama and the merchant question is simple: when an agent shows up holding a wallet, does your store take the order or refuse it? Amazon can refuse because Amazon owns the demand. You do not. A refused agent order is not a saved conversion — it is a conversion that happened at a competitor while you were writing a policy.

But the Amazon objection is not noise either. An agent that does not identify itself in its user agent is an agent your analytics will misattribute, your bot rules may throttle, and your fraud model has never seen. Both platforms are right about their own incentives. Neither is describing yours.

What we would do this week:

Find out whether agent traffic is already hitting you. Look for sessions with no referrer, headless signatures, and single-tap wallet checkouts. If your analytics cannot answer that, that is the finding.

Write the opt-out question down and ask your platform. "Can I exclude my catalog from a specific agent?" is now a real procurement question. Get the answer in writing before it matters.

Keep product data structured and portable. Price, stock, variants and shipping terms in machine-readable form are what an agent reads. That asset works for Muse, for the next agent, and for the day you leave a platform.

We build storefronts where the catalog, checkout logic and fraud rules belong to the merchant — so a platform's bet on an agent is not automatically your bet.

Sources: Tobi Lütke on X, Bloomberg, TechCrunch.