Agentic commerce: is your Magento store ready for AI shopping agents?

Shoppers are starting to hand the job to AI. They ask ChatGPT or Gemini to find a product, compare a few stores and, more and more, to buy it. The industry calls this agentic commerce, and in 2026 the big platforms started building the plumbing for it.

What agentic commerce is

An AI agent does what a shopper used to do by hand: search, compare price, stock and delivery, then check out once the shopper approves. To do that, it has to read your catalogue and talk to your checkout without anyone clicking through your pages.

The standards, in plain words

• Universal Commerce Protocol (UCP): an open standard Google announced on 11 January 2026, built with retailers and platforms such as Shopify, Etsy, Wayfair, Target and Walmart. It covers product discovery, the cart and checkout inside Google’s AI Mode and Gemini.
• Agentic Commerce Protocol (ACP): an open-source standard (Apache 2.0) from OpenAI and Stripe. ChatGPT was the first AI platform to use it, and stores apply to take part.
• Agent Payments Protocol (AP2): a standard for the payment step, so an agent can pay on a shopper’s behalf, with the shopper’s approval.

Where Magento stands

On 18 February 2026, Adobe said Adobe Commerce will support UCP and ACP, with more capabilities planned through 2026 but no detailed schedule. That announcement is for Adobe Commerce, the paid edition; it does not mention Magento Open Source. Open-source stores will reach these channels through extensions or custom work.

From Europe it is still early. Google’s checkout in AI Mode is open to selected merchants in the United States, with Canada and Australia following. That gives European stores time to prepare, and the preparation is work that already pays off on Google and in AI answers today.

Five things to prepare now

1. 01Product data an agent can trust: full titles, brand, GTIN or MPN, price, stock and variants, in your Google Merchant Center feed and as Schema.org Product markup on every product page. Agents compare facts, and missing facts lose the comparison.
2. 02Shipping and returns a machine can read: delivery costs, delivery times and the return policy, set in Merchant Center and marked up on the site. Google lists the product feed, shipping and returns as the first step of a UCP integration.
3. 03Stock you can stand behind: an agent that buys something you cannot ship means a refund and a bad review. Cron, indexers and stock sync have to run on time; on Magento, an “indexers are invalid” warning is the first thing to fix.
4. 04A payment provider that is ready for agents: Google’s checkout needs a provider that can process Google Pay tokens, and ACP starts with Stripe. Ask your provider what it supports before you need it.
5. 05A current platform: every protocol talks to your store through its APIs. A store on 2.4.6 or older, past standard support and full of outdated modules, is the wrong base to connect to anything new. Upgrade first, then connect.

Agents compare facts. The store with the clearest facts wins the comparison.

AI on your own store, safely

You do not have to wait for Google or OpenAI to put AI in front of your shoppers. On our Magento demo store, Neaterie, we built a shop assistant that answers from the live catalogue, the help pages and the signed-in customer’s own orders. It only reads: it cannot change orders, give refunds or create discount codes, it links only to the shop’s own pages, and it runs with limits per visitor and a daily budget. Any AI that touches a store should work the same way.

Where to start

Start with the data: a check of your feed, product markup, shipping and returns shows what an agent would see today. Then the platform: on 2.4.6 or older, the upgrade comes first. Our free audit covers both, with the fixes in order.

Sources: Google’s UCP developer guide and Merchant Center Help, agenticcommerce.dev, and Digital Commerce 360 (23 February 2026). These programmes change quickly; check them before you plan.