
Summarize with AI
There is a lot of buzz around AI and commerce, with many new terms being misunderstood or conflated: agentic commerce, agentic storefronts, AI toolkits, commerce protocols, and MCPs. Agencies are repositioning themselves as AI-native, AI-first, or AI-engineering shops. Many developments are happening simultaneously under the "agentic commerce" label, and I felt the urge to organize this knowledge to gain a better understanding of the field. As the saying goes, if you want to learn something, try to teach it first.
Updated 4 November 2026. Shopify's AI stack changes almost every month, so we've rechecked the channels, MCP servers and tool names below against Shopify's documentation and dated the facts that move fastest.
The first facet is AI as the shopper: AI agents acting autonomously on behalf of humans – browsing, comparing, waiting for the right price, negotiating among themselves, and completing purchases across the web. Your Shopify store is already prepared for this, whether you have considered it or not. That is the Shopify philosophy – every store is AI-ready by default.
The second facet is AI as the builder and operator: using AI coding tools to build and run your Shopify storefront. As Daft Punk would say, it is "harder, better, faster, stronger." This model is more efficient and offers more control than the traditional development model, but it requires deliberate implementation.
This guide provides an overview of what is currently happening in the world of AI in e-commerce and explores where the industry might be headed in the near future.
The other question I ask myself is this: is Shopify the best positioned platform for this AI shift, what are its strengths and weaknesses. How it’s navigating the change. Where it’s placing its bets. Are ecommerce platforms that essential or maybe something else is the truth – the value moving from the platform layer to the AI layer.
Part 1: AI as the Shopper
What is agentic commerce?
Imagine this: You’re brushing your teeth in the morning and mention to your partner, “We’re running out of toothpaste.” By noon the next day, the toothpaste is delivered to your door. Your partner wasn’t even involved. Amazon Alexa or Google Assistant heard you, and your personal AI agent – authorized by you to make small purchase decisions – executed the order. It might buy it immediately, add it to a monthly list, redeem loyalty points, apply discounts, or even negotiate a price. It sounds like science fiction, but it is already happening. While some might argue it's easier to train a human partner, AI agents don't forget and can be communicated with as naturally as a person.

For the past two decades, e-commerce worked the same way: a human searched for something, clicked through a results page, landed on a product page, and decided whether to buy. Every part of that loop depended on a human being present and making decisions in real time.
Agentic commerce breaks that assumption. For the first time, the buyer is not necessarily a human. This shift was unthinkable just a few years ago, and we are only beginning to see the repercussions of this new actor on the e-commerce scene.
Consider a few more examples of goals customers might set for their agents: "Reorder my usual coffee before I run out" or "Find me a hotel in Rome for the first weekend in October, under €200 a night, with late checkout." The agent browses, compares, checks policies, and completes the transaction within pre-set parameters – even selecting preferred delivery methods and adding order notes.
This isn't theoretical. Presenting Shopify's Q4 2025 results in February 2026, Shopify's president Harley Finkelstein said that orders reaching Shopify stores from AI search had grown 15x since January 2025. That's growth from a low starting point, but it shows the channel is real and moving fast. Shopify's newer data points the same way: in Q1 2026, AI-referred orders on Shopify grew nearly 13x year over year and referral sessions from AI chatbots more than 8x, and AI-referred sessions converted at nearly 50% higher rates than organic search, with 14% higher average order values (Shopify, May 2026). Shopify also reports that new buyers are placing orders through AI channels at nearly twice the rate of other channels (Shopify, June 2026). This can likely be attributed to higher intent and better-informed decisions.
How Shopify enables it technically
I like this quote from Shopify’s CEO - Tobi Lutke:
“What looks like a smart strategy today is actually just a good technology choice we made years ago”.

Shopify has spent years collecting billions of data points and building the infrastructure that enables agentic commerce at scale. Having been a Shopify agency for over a decade, we have had a front-row seat to this evolution. Shopify is not just reacting to a trend; they are defining it. Their strategy has always been to be present wherever customers are – from Instagram and TikTok to Roblox and LLMs.
They are moving from being an e-commerce platform to becoming the data layer and infrastructure that AI commerce runs on. This is a strategic pivot toward infrastructure rather than just features – a move that, in hindsight, seems like a calculated bet on the future of commerce.
So here's what that stack actually looks like:
Universal Commerce Protocol (UCP)
This is the open standard Shopify co-developed with Google to connect merchants to AI shopping channels at scale. It serves as a shared language, allowing any AI agent to query product information, check availability, and initiate a purchase. Before UCP, each AI channel would require a bespoke integration; UCP standardizes the connection.
Moreover, it is as flexible as Jean Claude Van Damm doing an epic split on Volvo truck wing mirrors. It can serve any edge case and address the entire customer journey from product discovery (querying product catalog), through ordering and checkout to post purchase experience. We break it down in detail in Shopify UCP Explained.

Shopify Catalog
The structured data layer that agents access when they're researching products. This is more important than it sounds. AI agents have a strong incentive to call a product catalog via API rather than scrape a website. API calls require far fewer tokens, which translates to lower cost and faster responses. I think you might be sure that LLM’s will prioritize structured data over scrapped from websites.
A well-structured Shopify Catalog means agents can confidently read product attributes, variants, pricing, availability, and policies without inferring them from HTML. Stores with poor data—such as missing specs or vague descriptions—are harder for agents to recommend accurately.
Good news for Shopify merchants. If you’re on Shopify it is enabled by default. No surprises here. But what about those running on Magento, Presta or Shopware? We’ve got you covered. You can use Shopify’s Agentic plan (no monthly fee, you pay when you sell, publicly available worldwide since March 2026) and connect your store or your PIM to the Shopify catalogue. All you have to do is map your data to catalogue standards. This is the easiest way to enable your store to appear in LLMs and give your customers the possibility to buy from you via an agentic storefront.
There is another way obviously. You can add your product using the Google Merchant Center Route, setting up your business with Google Pay, publishing UCP profile and completing native checkout integration (Google has a well documented guide for this naturally).

Shopify knowledge base
I think this one is a little bit underestimated. It gives merchants direct control over what AI agents say about their brand. It started as the separate Knowledge Base app; as of November 2026 it lives inside the Agentic sales channel (Sales channels > Agentic > Knowledge Base), and the old app, which you can no longer install, is deprecated on 15 January 2027 (Shopify Help Center). Shopify scans your store and builds a set of facts in categories such as policies, returns and warranty, payment, fulfilment and brand. You review them, add your own (up to 1,000 facts in total), attach reference URLs and publish. Shopify can suggest updates, but never changes anything without your approval. AI agents then use these facts to answer shoppers' questions about your returns policy, delivery, sizing or anything else that commonly comes up. Think of it as SEO for AI answers rather than search rankings. Whether you like it or not, AI is collecting information about you, and it is definitely better to have a say in what is said about your brand, right?

Shopify MCP (Model Context Protocol)
My favourite analogy of MCP is an USB-C port. One universal standard and port that connects all your devices to your computer with one standard. So MCP is exactly that: a universal USB-C port for AI. It gives AI models an easy way to plug into data, tools, apps, your store’s info: catalogue, cart state, orders, policies, and checkout. MCP is what allows a shopping agent to not just show your products but actually complete a transaction — checking stock in real time, building a cart, and handing over to Shopify's checkout.
Shopify has created specialised MCP servers for different tasks. As of November 2026, shopping runs through UCP: Catalog, Cart, Checkout and Order MCP (the older Storefront MCP catalogue and cart tools were retired after 31 August 2026). The Customer Accounts MCP handles logged-in customers, and the Dev MCP connects developers' coding agents, such as Claude Code or Cursor, to Shopify's docs and API schemas. We unpack what each of them exposes in Shopify MCP Explained.
Shopify AI Toolkit
This layer is for coding agents like Claude Code and Codex and editors like Cursor and VS Code. Generally available since the Spring '26 Edition (June 2026), it ships as a plugin, a shopify agent skill and the Dev MCP server. It gives the agent Shopify's current docs and API schemas, validates GraphQL, Liquid and extension code, and can run supported store tasks through the Shopify CLI, with you deciding when they run. So one might say it gives the agent the architectural definitions and code blueprints it needs to build, for example, a custom Shopify app or some front-end functionality.
Agentic Storefronts
Where it all comes together. Agentic Storefronts is a sales channel that syndicates your product data and checkout into AI platforms. As of November 2026, Shopify's Help Center lists ChatGPT, Google AI Mode and Gemini, Microsoft Copilot and Meta surfaces, and shoppers can also pay with Shop Pay through personal AI agents connected to Shop. It's active by default for eligible stores, and you choose channels under Sales channels > Agentic. From a merchant's perspective, this is a new sales channel: one where the customer may never browse your website, but the transaction still runs through your Shopify infrastructure. How checkout works depends on the channel: ChatGPT sends shoppers to your store's checkout (in an in-app browser or a new tab), while Google AI Mode and Gemini, Copilot and Meta can run Shopify-powered checkout inside the channel if you switch it on (Shopify Help Center).
Key point: Architecture is secondary
Whether your store uses Liquid or Hydrogen, you have access to Agentic Storefronts. This is a platform-level feature, not a complex engineering project.
The philosophy behind all of this is worth naming: Shopify isn't adding an AI feature. They're becoming the infrastructure layer that AI commerce runs on — the same way Visa became the infrastructure layer that card payments run on. Brilliant move if you ask me. Good luck to competition trying to replicate this. Why?
Shopify's moat matters more than it looks
The strength of Shopify’s checkout moat was evidenced when a well-funded competitor struggled with the same challenge.
In September 2025, OpenAI launched ChatGPT Instant Checkout: the ability to complete a purchase directly inside a chat conversation, built on the Agentic Commerce Protocol it developed with Stripe. OpenAI is one of the best-resourced technology companies in the world, with obvious motivation to crack in-chat commerce. Yet in March 2026 it moved away from Instant Checkout towards product discovery and merchant apps inside ChatGPT, after only a small number of merchants had gone live.
Shopify, meanwhile, had the live product data layer and twenty years of commerce infrastructure: fraud detection, payment relationships, PCI compliance. That's why Shopify can keep its merchants discoverable in ChatGPT while the purchase runs through Shopify checkout, and why other AI channels (Google, Microsoft, Meta) plug into Shopify-powered checkout rather than building their own.
The AI shopping channel landscape
The picture below is as of November 2026; check it again before you plan around any single channel.
Google AI Mode and Gemini are arguably the most significant. Google has the Shopping Graph, and it co-developed UCP with Shopify, which gives it the deepest integration into the merchant stack. Since March 2026 select brands have been selling in AI Mode and the Gemini app through UCP, and Shopify merchants can switch on Shopify-powered checkout inside these channels. Buyers stay in Google's interface, but the retailer remains the merchant of record and keeps the customer relationship and data (quite different from marketplaces’ modus operandi, right?).
Microsoft Copilot gets less attention but moved early. Microsoft launched Copilot Checkout in January 2026, and by March Shopify said thousands of its merchants were already selling in Copilot. Worth watching.
Meta is the newest addition: Shopify's Help Center lists Meta surfaces among the Agentic Storefronts channels, with in-channel checkout if you switch it on.
Perplexity was the first mover, with "Buy with Pro" launched in November 2024 through a PayPal partnership. As of November 2026 it isn't among the channels in Shopify's Agentic Storefronts settings.
ChatGPT remains an important discovery channel despite the Instant Checkout pullback (see above). OpenAI has repositioned around product recommendations and merchant apps rather than in-chat purchasing, and Shopify sends ChatGPT shoppers to the store's own checkout.
What this means for your store today
As we have established before, the good news is that if you're on Shopify, you're AI-ready by default. The infrastructure is there. You are ready to sell through these new channels.
The question you should be asking yourself is: what determines whether AI agents recommend you over a competitor. Quick answer: the quality of your underlying data (in Shopify Catalog and your knowledge base), quality of your code structure and schema (the usual on-site SEO stuff) and user sentiment expressed in opinions, reviews, testimonials published mostly in different sources than your own website.
This is where Generative Engine Optimisation (GEO) fits in. Structuring your content not for Google's ranking algorithm but for AI agents making recommendations. We’ll tell you more about this in a different article.
Part 2: AI as the Builder and Operator
The old Shopify engineering workflow — and why it doesn't work for some brands
Another aspect of agentic commerce involves agents building and operating your store – analyzing, improving, and automating tasks to provide a competitive edge.
For many Shopify brands (mostly the small ones), the technical stack evolved the same way: start with a theme, add apps when you hit limitations, hire a developer when something breaks or needs changing, and gradually accumulate a dependency structure nobody fully understands.
For mid and upmarket the pattern is similar: design mockups in Figma, rebuild them manually in Liquid, add another app whenever native Shopify functionality doesn't quite fit, use developers for some more complex functionalities or anything that is risky. You know, the usual. Nothing wrong with this approach, it makes sense for most brands.
However, with the rise of AI’s capability, merchants begin to entertain these four aspects.
Speed: a layout change that could now take 10 minutes but historically took two weeks once you account for the development queue. Money: app subscriptions for functionality you could own outright. Flexibility: You have some specific logic for your loyalty program in mind but need to compromise on what is actually available in the app store? Or maybe you had some functionality in mind that was just too expensive to develop? With AI – not a problem anymore. Performance: compounding third-party apps come with a hidden tax of slowing down your page and affecting conversions.
Shopify is changing parts of this itself. Its built-in AI tools handle copy and image generation. Sidekick – Shopify's AI assistant – can, since the Winter '26 Edition (December 2025), build custom admin apps from a plain-language prompt, which can save you a godless amount of manual work. And since the Spring '26 Edition any app developer can build Sidekick App Extensions, so Sidekick can pull in data from your installed apps and act on it, letting you ask about an email campaign or open returns directly in the Sidekick interface, without switching between dashboards. If someone prefers to build their storefront with their favourite vibe-coding tools like Replit and Lovable it is now doable and easy to connect to Shopify. These are some real improvements for standard store management.
But they don't address the deeper problem for brands that have outgrown the default workflow. Shopify's built-in AI doesn't give you version control. Sidekick doesn't let you run your own custom operations model. Lovable and Replit are for vibe coding your way to a landing page – they're not built for enterprise engineering with the safety requirements that come with it.
That's where AI-assisted engineering is a genuinely different tool.
AI-assisted engineering: what it actually looks like
The tools at the center of this workflow include Claude Code, Cursor, Codex CLI, and the Shopify AI Toolkit.
Here's what you can actually build with them:
- Custom Hydrogen storefronts featuring clean, isolated component libraries versioned securely in GitHub
- Custom apps replacing SaaS subscriptions: cart logic, store locators, loyalty mechanics, and subscription management, effectively eliminating performance bottlenecks.
- Complex integration layers connecting Shopify to ERP, PIM, or WMS systems with specific business logic that standard solutions cannot accommodate.
The workflow itself: a developer writes a spec, the AI generates the implementation, the developer reviews, iterates, and merges. Everything lives in GitHub. Deployment is controlled. Nothing ships without a human review gate — we've documented the full AI-assisted Hydrogen workflow, end to end.
That's also how we work at wecanfly. AI agents do a large share of the implementation, but inside our processes and guardrails, built on experience from our client projects, and a person from our team reviews and approves the work before it goes live. More on our agentic commerce services for Shopify.
The benefits beyond speed are probably more important than the speed itself. Speed is the headline: some work that used to take months can now take weeks. But the structural changes are more significant:
Cost:Historically, headless builds were more expensive. That is changing. Replacing SaaS subscriptions with owned components involves a one-time build cost versus ongoing fees, and custom components reduce the long-term maintenance cost of managing multiple vendor roadmaps.
Fit: apps are built for the median merchant. If your business logic is non-standard — unusual pricing structures, complex B2B rules, custom checkout flows — you're always fighting against someone else's assumptions. A custom component does exactly what you specify.
Control: Your team owns the codebase. You can modify it and understand exactly how it functions without vendor lock-in or breaking changes.
The pitfalls are real. AI-generated code can be incorrect; it can hallucinate function signatures or fail in edge cases. Context drift is also a challenge in long sessions. Without structured review processes, AI-assisted development can lead to unstable production environments.
A good development team behind your project is more important than ever. Seasoned shopify developers will deliver high quality products faster, same goes for inexperienced devs - poor quality code only faster. If speed is your only northstar, you need to brace yourself for a rough ride and eventually pay a steep fare hike.
The workflow discipline matters more than the tools. Teams that ship successfully with AI coding tools have: a clear spec before any generation starts, consistent review gates, a testing framework that catches regressions, and explicit limits on what the AI can modify without human approval.
Running your store with AI
Beyond coding, brands should focus on managing Shopify stores using natural language. Shopify's MCP connects to the data layer, allowing you to query data, manage products, and generate reports within interfaces like Claude.
So why would one rather use this approach and not just Sidekick (which by the way runs on Anthropic's Claude)? The biggest advantage, in my opinion, comes from the simple fact that you can cross-reference data from multiple tools in one query. To give you an example: most brands review their Shopify analytics in isolation. A configured AI workspace can pull Shopify analytics alongside Google Analytics, surface discrepancies worth investigating, and implement technical SEO recommendations from Google Search Console and Ahrefs. All in a single working session. The integration work to set that up is real, but the ongoing operational leverage is significant. Oh, and you can have it run as a scheduled task in Claude Cowork or set up as a self-managed autonomous agent. Possibilities are limited only by your imagination. Or your LLM’s model ;)
OK, let’s say that you don’t want your marketing team to have access to all this critical areas of your store or they just want to have a regular CMS experience for their daily work and don’t want to or shouldn't be touching the codebase, a headless CMS (we like Strapi or Sanity) sits between Claude and the frontend. Editors can update content independently through a structured interface while developers maintain the component layer. Well, you can connect any tool actually - if you prefer to upload your blog posts from Notion it is totally doable.
For design iteration, tools like Paper.design change the Figma-to-Liquid cycle. Prompt a component variation, review it visually, push it to staging without a full design-to-dev handoff cycle each time you want to test something. We found it actually quite efficient in the “from code to design and back” cycle. Paper allows you to keep your design synchronized with your code base and edit as you like - either in natural language in claude code or let your designers have regular “figma-like” experience.
The guardrails problem
Would you give an AI agent unsupervised access to your product catalog, pricing, or ERP without guardrails?
Nobody should. Some people obviously do. No enterprise operation does.
Proper guardrails in an agentic Shopify setup look like this:
Controlled access: AI agents must operate within defined boundaries. Separate access contexts should be used for product updates, order management, and infrastructure.
Spec-driven operations: Changes must follow structured prompts and validation logic rather than freeform generation.
Review gates: Material changes—like pricing or collection logic—must include a "human-in-the-loop" approval step before going live.
Rollback strategy: Version control at every layer ensures that if an error occurs, the system can quickly return to a known good state.
This layer of governance is what makes AI operations reliable. For brands exploring agentic access to backend systems, guardrail design is the most critical architectural work.
When Shopify's architecture becomes the constraint
There's an honest limitation to Shopify's AI-assisted engineering story that's worth naming clearly.
Shopify's backend is proprietary. AI agents can work well on your frontend (Hydrogen is a clean TypeScript codebase), and they can read and write your store data via MCP. But they cannot read or modify Shopify's core backend logic — because you don't have access to it, and neither does an AI agent. Business logic lives in Shopify's servers.
When you need custom backend behaviour on Shopify, your options are: Shopify Functions (sandboxed WebAssembly, limited context, no external calls), webhooks (event-driven, stateless), and third-party apps (opaque to your codebase and to AI). These tools are workable for a wide range of use cases. But they create a ceiling.
That ceiling becomes visible when a brand needs: complex B2B pricing logic that can't be expressed in Shopify's discount/scripting model, custom data models (multi-vendor structures, bespoke order types), or workflows where the business logic itself needs to evolve – not just be configured.
For these cases, an open-source TypeScript commerce framework like for example Medusa.js offers a fundamentally different surface for AI-assisted engineering. Because the entire backend codebase is yours and readable by AI agents, Claude Code can understand data models, write and refactor business logic, and use Medusa's built-in Workflow Engine — which executes business processes step-by-step and rolls back automatically if something fails. The AI isn't working around a black box; it's working inside a codebase it can fully reason about.
This isn't a criticism of Shopify for what it is. Shopify is an excellent platform for the vast majority of direct-to-consumer e-commerce, and its AI channel distribution story (see the first part of this article) is genuinely platform-level infrastructure that open-source alternatives don't match. But for brands with complex backend requirements where AI engineering needs to reach into business logic, the architectural trade-off is real.
If your requirements point in that direction, we work on Medusa.js projects through our sister company mohi.to — that's the right conversation to have before committing to a Shopify rebuild that may hit the same walls.
Part 3: The Shopify Agentic Commerce Stack
Tool map
| Tool | What it does | Who it's for | Architecture requirement |
|---|---|---|---|
| Shopify UCP | Open standard for AI channel distribution | All Shopify merchants | None — platform-level |
| Shopify Catalog | Structured product data layer for AI access | All Shopify merchants | None — optimisation matters |
| Shopify knowledge base | Facts AI agents use to answer questions about your brand (in the Agentic channel) | All Shopify merchants | None |
| Shopify MCP | Exposes catalogue, cart, orders, policies, checkout to agents | All Shopify merchants | None — any architecture |
| Agentic Storefronts | Sales channel syndicating to ChatGPT, Google AI Mode and Gemini, Copilot, Meta | All Shopify merchants | None |
| Shopify Storefront API | GraphQL API for building headless (Hydrogen) storefronts | Headless / Hydrogen stores | Headless required |
| Shopify AI Toolkit | Plugin, shopify skill and Dev MCP for Claude Code, Codex, Cursor, VS Code | Developers building on Shopify | Hydrogen strongly recommended |
| Sidekick + App Extensions | AI store management assistant, connected to your app stack | All Shopify merchants | None |
Does headless (Hydrogen) matter for agentic commerce?
This is the question brands ask most often, and the answer depends on your specific goals.
For AI shoppers (UCP, Shopify MCP, Agentic Storefronts): No. Any Shopify store can access AI channel distribution regardless of whether it is Liquid or headless. Architecture is irrelevant for basic visibility in ChatGPT or Gemini.
For AI-assisted engineering and operations: yes — Hydrogen enables the full workflow.
One of the first questions I had when we explored this new workflow was why AI assisted engineering works better with Hydrogen compared to Liquid. It fundamentally comes down to how the AI tests its own work. Think of Hydrogen like a modern software project: because it is built on standardized, predictable code, AI tools like Claude Code can build a layout feature and instantly verify that every piece fits perfectly on the fly, catching and fixing its own mistakes locally in milliseconds. Liquid, by contrast, is an older system tightly glued directly to Shopify's cloud backend. The AI cannot test its code locally; instead, it has to upload the files to Shopify’s live servers and wait for an internet browser to physically render the web page just to see if something broke. This slow, blind "guess-and-check" loop creates massive friction for an AI agent, whereas Hydrogen turns your storefront into a clean, modern workspace that AI tools already understand perfectly. We've documented our AI-assisted Hydrogen workflow end to end, and our headless Shopify development team can help you scope the move.
It is worth noting that Shopify is actively developing AI tooling that works on Liquid stores too (Sidekick, and the AI Toolkit's Liquid validation), so this gap may narrow in the coming months. Consider this when evaluating your long-term architectural decisions.

Part 4: What Brands Should Do Now
For AI shopper readiness
The following checklist covers the foundations of AI readiness. These are primarily content and data operations, not technical projects.
Product data:
- Every product requires a comprehensive, specification-driven description—moving beyond marketing copy to include precise specs, materials, dimensions, and use cases. In our work with furniture brands, we’ve found that AI agents prioritize quantifiable signals of quality. While reviews are critical trust signals, structured data – like durability certifications – is increasingly influential. For example, explicitly documenting stress-test results (e.g., "guaranteed for 50,000 sitting cycles") provides a verifiable metric that agents can index to validate product longevity.
- All variants are fully specified with accurate attributes
- Product titles are descriptive, not clever
- Inventory accuracy is maintained – agents that recommend an out-of-stock item lose trust (btw. Did I mention that Shopify Catalog allows agents to fetch real-time inventory?)
Brand and policy content:
- Returns policy is clearly stated and findable
- Shipping information is current and specific
- FAQ coverage addresses the most common pre-purchase questions
- Your knowledge base (Sales channels > Agentic > Knowledge Base) is reviewed, filled in and published
Structured data and metadata:
- Schema markup is implemented for products
- Product categories map to standard taxonomies
- Images have accurate alt text (I know you have hundreds if not thousands of these, but hey - you can now write a Sidekick app that will help you patch this really quickly. Been there, done that.)
Distribution:
- Agentic Storefronts is enabled and connected (check your Shopify admin under Sales channels > Agentic and turn on the channels you want, including in-channel checkout where it's offered)
- You've verified how your store appears in ChatGPT shopping and Google AI Mode
Robots.txt — AI crawlers: Check yourstore.com/robots.txt. Shopify's default file doesn't block AI crawlers (we checked several stores in November 2026), but a customised robots.txt.liquid, an app or bot protection at your CDN can.
- Allow (search and user-triggered crawlers): OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot.
- Block optionally (training): GPTBot, ClaudeBot, and the Google-Extended token, which controls whether Google may use your content for Gemini training (it doesn't affect Google Search). The distinction is critical: OAI-SearchBot puts products in ChatGPT search results, while GPTBot collects training data. Blocking the wrong one can remove you from AI search results.
When agentic commerce isn't the right priority
Not every store benefits equally from investing in AI channel readiness now.
Highly configurable or bespoke products – custom furniture, made-to-measure clothing, anything requiring a consultation – lose too much of the purchase experience when an AI agent tries to compress it into a recommendation. The same applies to categories where tactile or sensory experience drives the purchase: luxury fragrance, artisan textiles, fine jewellery. An agent can describe these products accurately; it can't replicate the discovery experience that closes those sales.
What if you have a small catalogue? I think AI can actually help you get discovered: an AI answer can surface a brand that never made it to the first page of Google, as long as its product data answers the question. Shopify's Q1 2026 data shows that more than half of AI-referred sessions start on a product page, compared to about 20% for organic search (Shopify): the assistant sends shoppers straight to the product it recommended.
What about brands selling commodities on Amazon? I think this is a perfect product for agentic ecommerce. Anything that does not involve judgment or emotions can be easily delegated to be bought by agents. Moreover – I think it will be faster for anyone to just say or type in ChatGPT: order some coffee filters, find and buy the cheapest plastic hangers, get me a 3-pack of black t-shirts I always buy. It’s even faster than Amazon 1-click checkout, right? My prediction is that AI sale channels will go after marketplaces.
And I think merchants will benefit from this shift. When transactions happen inside marketplaces, brands lose direct traffic, first-party data, and can't control purchase experience. They are not merchants of record. There was the same concern with OpenAI’s attempt to create a checkout experience but with Shopify filling in this gap this is not an issue anymore. By the way, that’s one of the reasons I was always a Shopify fan. It's a completely different philosophy than Amazon. They’re all about supporting merchants and helping them thrive. Have you noticed they’ve named their AI assistant Sidekick? Love that.
For AI-assisted engineering
Before committing to a build or rebuild, the useful starting point is an audit of your current stack:
What is already custom-built, and how maintainable is it? Custom code you do not understand is a liability; custom code you do understand is an asset.
Which apps are you dependent on, and what would it cost to own that functionality? Not every app should be replaced, but those solving problems unique to your business logic are prime candidates.
What do you want to manage from Claude? Starting with a well-defined use case, like product descriptions or collection management, is more effective than attempting to connect everything at once.
Retrofit vs. rebuild decision framework:
If you are on a Liquid store that is functioning well, native tools like Sidekick and Shopify Flow may be sufficient. The case for Hydrogen is strongest when you require deep engineering control, custom frontend requirements, or complex server-side logic.
The early mover window
There's a real window here for brands willing to move before the playbook is written.
The structural shift is underway. Some brands will stay on the default stack, let the platform handle AI incrementally, wait for the methodology to be documented. Others will build the AI-native operations model now, accumulate the learning curve advantage, own the internal capability before it becomes a commodity hire. The first path is lower risk in the short term. The second path is where the structural advantage compounds.
The brands building AI-native Shopify operations today are doing it without a well-documented methodology, without a deep pool of agencies that know how to do it, and without the case studies that will eventually make it feel safe. That's uncomfortable. It's also why the window exists.
This isn't an argument to rush into something that isn't ready. The guardrails work is real, the Hydrogen rebuild commitment is significant, and the ROI case needs to be made seriously. But for brands where the underlying conditions are right – a team that wants more control, an existing stack that's becoming expensive, a technical appetite for early adoption – the timing is as good as it's going to be. If those conditions sound like yours, talk to our Agentic Commerce team.
FAQ
What is agentic commerce on Shopify?
Agentic commerce refers to AI agents – ChatGPT, Google's AI Mode, Copilot, Perplexity – acting as buyers on behalf of humans. Shopify enables this through its Agentic Storefronts infrastructure, which syndicates product data and checkout capabilities directly into AI platforms. Separately, "agentic commerce" is also used to describe AI-assisted store engineering and operations – using tools like Claude Code to build and run Shopify storefronts. These are two distinct things that often get conflated.
Does my Shopify store need to be headless for agentic commerce?
No. AI channel distribution (appearing in ChatGPT shopping, Google AI Mode, Copilot) works for any Shopify store regardless of architecture. Headless (Hydrogen) becomes relevant when you want to implement AI-assisted engineering – the developer workflow with Claude Code, Cursor, and the Shopify AI Toolkit works significantly better in a Hydrogen environment than Liquid.
What is Shopify MCP and what does it expose?
Shopify's Model Context Protocol implementation exposes your store's live data to AI agents: product catalogue, cart state, order information, store policies, and checkout. It's what allows a shopping agent to not just display your products but complete a transaction in real time. Full deep dive: Shopify MCP Explained.
What is Shopify UCP?
The Universal Commerce Protocol is an open standard co-developed by Shopify and Google to connect merchants to AI shopping channels at scale. Think of it as a common language that any AI agent can use to access product information and initiate purchases, without requiring bespoke integrations with each platform. More detail: Shopify UCP Explained.
What's the difference between agentic commerce and AI-assisted engineering?
Agentic commerce (as most people use the term) refers to AI agents shopping on behalf of humans – the consumer-facing side. AI-assisted engineering refers to using AI coding tools to build and operate Shopify storefronts – the merchant and developer side. Shopify's infrastructure supports both, but they require entirely different things from you as a merchant or agency.
Can I manage my Shopify store from Claude?
Yes, with setup work. On a properly configured Hydrogen storefront with Shopify MCP wired up, you can manage products, collections, content, and pull reports through Claude without opening Shopify admin. The setup involves MCP configuration, access controls, and guardrails design – it doesn't happen out of the box.
How do I make my Shopify store visible in ChatGPT shopping results?
Check Agentic Storefronts in your Shopify admin (Sales channels > Agentic). As of November 2026, ChatGPT is a discovery channel that sends shoppers to your store's checkout. Then focus on product data quality: complete descriptions, accurate variants, clear policies. The knowledge base in the same channel lets you control how AI answers brand-specific questions. GEO (Generative Engine Optimisation) – structuring your content for AI recommendation rather than search ranking – is the ongoing discipline for improving visibility.
What guardrails do I need before giving AI agents access to my store?
At minimum: controlled access scopes (agents can only act within defined boundaries), spec-driven operations (structured prompts with validation, not freeform generation), human review gates before changes go live, and a rollback strategy. For any connection to backend systems (ERP, PIM, WMS), the guardrails design is significant engineering work and where most of the risk lives.
Is Shopify agentic commerce available for B2B?
Yes, though with additional complexity. B2B agentic commerce involves connecting MCP to backend systems — ERP for pricing and availability, PIM for product specs, WMS for inventory. The Shopify B2B + headless + MCP stack is technically feasible but requires careful integration design, particularly for access control and data consistency.
Do I need a Shopify Plus plan for agentic commerce?
No. Agentic Storefronts and the consumer-facing AI channel infrastructure are available across Shopify plans. Shopify also offers a standalone Agentic plan (no monthly fee, you pay when you sell) for brands not currently on Shopify who want AI channel distribution without a full migration. AI-assisted engineering (Hydrogen, Claude Code workflow) doesn't require Plus either, though the ROI case typically makes more sense for brands with the project scale that usually correlates with Plus.
We also dig into this in our podcast episode Agentic Commerce – 15x more orders from AI channels!, and in E-commerce in the age of AI Marcin Kamiński explains what agent traffic means for store visibility (both episodes in Polish, with English subtitles and transcripts).
